Commit | Line | Data |
---|---|---|
c906108c | 1 | \input texinfo @c -*-texinfo-*- |
c02a867d | 2 | @c Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998, |
b620eb07 | 3 | @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 |
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 | |
24 | ||
41afff9a | 25 | @c readline appendices use @vindex, @findex and @ftable, |
48e934c6 | 26 | @c annotate.texi and gdbmi use @findex. |
c906108c | 27 | @syncodeindex vr cp |
41afff9a | 28 | @syncodeindex fn cp |
c906108c SS |
29 | |
30 | @c !!set GDB manual's edition---not the same as GDB version! | |
9fe8321b | 31 | @c This is updated by GNU Press. |
e9c75b65 | 32 | @set EDITION Ninth |
c906108c | 33 | |
87885426 FN |
34 | @c !!set GDB edit command default editor |
35 | @set EDITOR /bin/ex | |
c906108c | 36 | |
6c0e9fb3 | 37 | @c THIS MANUAL REQUIRES TEXINFO 4.0 OR LATER. |
c906108c | 38 | |
c906108c | 39 | @c This is a dir.info fragment to support semi-automated addition of |
6d2ebf8b | 40 | @c manuals to an info tree. |
03727ca6 | 41 | @dircategory Software development |
96a2c332 | 42 | @direntry |
03727ca6 | 43 | * Gdb: (gdb). The GNU debugger. |
96a2c332 SS |
44 | @end direntry |
45 | ||
c906108c SS |
46 | @ifinfo |
47 | This file documents the @sc{gnu} debugger @value{GDBN}. | |
48 | ||
49 | ||
9fe8321b AC |
50 | This is the @value{EDITION} Edition, of @cite{Debugging with |
51 | @value{GDBN}: the @sc{gnu} Source-Level Debugger} for @value{GDBN} | |
52 | Version @value{GDBVN}. | |
c906108c | 53 | |
8a037dd7 | 54 | Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998,@* |
b620eb07 | 55 | 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006@* |
7d51c7de | 56 | Free Software Foundation, Inc. |
c906108c | 57 | |
e9c75b65 EZ |
58 | Permission is granted to copy, distribute and/or modify this document |
59 | under the terms of the GNU Free Documentation License, Version 1.1 or | |
60 | any later version published by the Free Software Foundation; with the | |
959acfd1 EZ |
61 | Invariant Sections being ``Free Software'' and ``Free Software Needs |
62 | Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,'' | |
63 | and with the Back-Cover Texts as in (a) below. | |
c906108c | 64 | |
b8533aec DJ |
65 | (a) The FSF's Back-Cover Text is: ``You are free to copy and modify |
66 | this GNU Manual. Buying copies from GNU Press supports the FSF in | |
67 | developing GNU and promoting software freedom.'' | |
c906108c SS |
68 | @end ifinfo |
69 | ||
70 | @titlepage | |
71 | @title Debugging with @value{GDBN} | |
72 | @subtitle The @sc{gnu} Source-Level Debugger | |
c906108c | 73 | @sp 1 |
c906108c | 74 | @subtitle @value{EDITION} Edition, for @value{GDBN} version @value{GDBVN} |
9e9c5ae7 | 75 | @author Richard Stallman, Roland Pesch, Stan Shebs, et al. |
c906108c | 76 | @page |
c906108c SS |
77 | @tex |
78 | {\parskip=0pt | |
53a5351d | 79 | \hfill (Send bugs and comments on @value{GDBN} to bug-gdb\@gnu.org.)\par |
c906108c SS |
80 | \hfill {\it Debugging with @value{GDBN}}\par |
81 | \hfill \TeX{}info \texinfoversion\par | |
82 | } | |
83 | @end tex | |
53a5351d | 84 | |
c906108c | 85 | @vskip 0pt plus 1filll |
8a037dd7 | 86 | Copyright @copyright{} 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, |
b620eb07 | 87 | 1996, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2006 |
7d51c7de | 88 | Free Software Foundation, Inc. |
c906108c | 89 | @sp 2 |
c906108c | 90 | Published by the Free Software Foundation @* |
c02a867d EZ |
91 | 51 Franklin Street, Fifth Floor, |
92 | Boston, MA 02110-1301, USA@* | |
6d2ebf8b | 93 | ISBN 1-882114-77-9 @* |
e9c75b65 EZ |
94 | |
95 | Permission is granted to copy, distribute and/or modify this document | |
96 | under the terms of the GNU Free Documentation License, Version 1.1 or | |
97 | any later version published by the Free Software Foundation; with the | |
959acfd1 EZ |
98 | Invariant Sections being ``Free Software'' and ``Free Software Needs |
99 | Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,'' | |
100 | and with the Back-Cover Texts as in (a) below. | |
e9c75b65 | 101 | |
b8533aec DJ |
102 | (a) The FSF's Back-Cover Text is: ``You are free to copy and modify |
103 | this GNU Manual. Buying copies from GNU Press supports the FSF in | |
104 | developing GNU and promoting software freedom.'' | |
3fb6a982 JB |
105 | @page |
106 | This edition of the GDB manual is dedicated to the memory of Fred | |
107 | Fish. Fred was a long-standing contributor to GDB and to Free | |
108 | software in general. We will miss him. | |
c906108c SS |
109 | @end titlepage |
110 | @page | |
111 | ||
6c0e9fb3 | 112 | @ifnottex |
6d2ebf8b SS |
113 | @node Top, Summary, (dir), (dir) |
114 | ||
c906108c SS |
115 | @top Debugging with @value{GDBN} |
116 | ||
117 | This file describes @value{GDBN}, the @sc{gnu} symbolic debugger. | |
118 | ||
9fe8321b | 119 | This is the @value{EDITION} Edition, for @value{GDBN} Version |
c906108c SS |
120 | @value{GDBVN}. |
121 | ||
b620eb07 | 122 | Copyright (C) 1988-2006 Free Software Foundation, Inc. |
6d2ebf8b | 123 | |
3fb6a982 JB |
124 | This edition of the GDB manual is dedicated to the memory of Fred |
125 | Fish. Fred was a long-standing contributor to GDB and to Free | |
126 | software in general. We will miss him. | |
127 | ||
6d2ebf8b SS |
128 | @menu |
129 | * Summary:: Summary of @value{GDBN} | |
130 | * Sample Session:: A sample @value{GDBN} session | |
131 | ||
132 | * Invocation:: Getting in and out of @value{GDBN} | |
133 | * Commands:: @value{GDBN} commands | |
134 | * Running:: Running programs under @value{GDBN} | |
135 | * Stopping:: Stopping and continuing | |
136 | * Stack:: Examining the stack | |
137 | * Source:: Examining source files | |
138 | * Data:: Examining data | |
e2e0bcd1 | 139 | * Macros:: Preprocessor Macros |
b37052ae | 140 | * Tracepoints:: Debugging remote targets non-intrusively |
df0cd8c5 | 141 | * Overlays:: Debugging programs that use overlays |
6d2ebf8b SS |
142 | |
143 | * Languages:: Using @value{GDBN} with different languages | |
144 | ||
145 | * Symbols:: Examining the symbol table | |
146 | * Altering:: Altering execution | |
147 | * GDB Files:: @value{GDBN} files | |
148 | * Targets:: Specifying a debugging target | |
6b2f586d | 149 | * Remote Debugging:: Debugging remote programs |
6d2ebf8b SS |
150 | * Configurations:: Configuration-specific information |
151 | * Controlling GDB:: Controlling @value{GDBN} | |
152 | * Sequences:: Canned sequences of commands | |
21c294e6 | 153 | * Interpreters:: Command Interpreters |
c8f4133a | 154 | * TUI:: @value{GDBN} Text User Interface |
6d2ebf8b | 155 | * Emacs:: Using @value{GDBN} under @sc{gnu} Emacs |
7162c0ca | 156 | * GDB/MI:: @value{GDBN}'s Machine Interface. |
c8f4133a | 157 | * Annotations:: @value{GDBN}'s annotation interface. |
6d2ebf8b SS |
158 | |
159 | * GDB Bugs:: Reporting bugs in @value{GDBN} | |
6d2ebf8b SS |
160 | |
161 | * Command Line Editing:: Command Line Editing | |
162 | * Using History Interactively:: Using History Interactively | |
0869d01b | 163 | * Formatting Documentation:: How to format and print @value{GDBN} documentation |
6d2ebf8b | 164 | * Installing GDB:: Installing GDB |
eb12ee30 | 165 | * Maintenance Commands:: Maintenance Commands |
e0ce93ac | 166 | * Remote Protocol:: GDB Remote Serial Protocol |
f418dd93 | 167 | * Agent Expressions:: The GDB Agent Expression Mechanism |
23181151 DJ |
168 | * Target Descriptions:: How targets can describe themselves to |
169 | @value{GDBN} | |
aab4e0ec AC |
170 | * Copying:: GNU General Public License says |
171 | how you can copy and share GDB | |
6826cf00 | 172 | * GNU Free Documentation License:: The license for this documentation |
6d2ebf8b SS |
173 | * Index:: Index |
174 | @end menu | |
175 | ||
6c0e9fb3 | 176 | @end ifnottex |
c906108c | 177 | |
449f3b6c | 178 | @contents |
449f3b6c | 179 | |
6d2ebf8b | 180 | @node Summary |
c906108c SS |
181 | @unnumbered Summary of @value{GDBN} |
182 | ||
183 | The purpose of a debugger such as @value{GDBN} is to allow you to see what is | |
184 | going on ``inside'' another program while it executes---or what another | |
185 | program was doing at the moment it crashed. | |
186 | ||
187 | @value{GDBN} can do four main kinds of things (plus other things in support of | |
188 | these) to help you catch bugs in the act: | |
189 | ||
190 | @itemize @bullet | |
191 | @item | |
192 | Start your program, specifying anything that might affect its behavior. | |
193 | ||
194 | @item | |
195 | Make your program stop on specified conditions. | |
196 | ||
197 | @item | |
198 | Examine what has happened, when your program has stopped. | |
199 | ||
200 | @item | |
201 | Change things in your program, so you can experiment with correcting the | |
202 | effects of one bug and go on to learn about another. | |
203 | @end itemize | |
204 | ||
49efadf5 | 205 | You can use @value{GDBN} to debug programs written in C and C@t{++}. |
79a6e687 | 206 | For more information, see @ref{Supported Languages,,Supported Languages}. |
c906108c SS |
207 | For more information, see @ref{C,,C and C++}. |
208 | ||
cce74817 | 209 | @cindex Modula-2 |
e632838e AC |
210 | Support for Modula-2 is partial. For information on Modula-2, see |
211 | @ref{Modula-2,,Modula-2}. | |
c906108c | 212 | |
cce74817 JM |
213 | @cindex Pascal |
214 | Debugging Pascal programs which use sets, subranges, file variables, or | |
215 | nested functions does not currently work. @value{GDBN} does not support | |
216 | entering expressions, printing values, or similar features using Pascal | |
217 | syntax. | |
c906108c | 218 | |
c906108c SS |
219 | @cindex Fortran |
220 | @value{GDBN} can be used to debug programs written in Fortran, although | |
53a5351d | 221 | it may be necessary to refer to some variables with a trailing |
cce74817 | 222 | underscore. |
c906108c | 223 | |
b37303ee AF |
224 | @value{GDBN} can be used to debug programs written in Objective-C, |
225 | using either the Apple/NeXT or the GNU Objective-C runtime. | |
226 | ||
c906108c SS |
227 | @menu |
228 | * Free Software:: Freely redistributable software | |
229 | * Contributors:: Contributors to GDB | |
230 | @end menu | |
231 | ||
6d2ebf8b | 232 | @node Free Software |
79a6e687 | 233 | @unnumberedsec Free Software |
c906108c | 234 | |
5d161b24 | 235 | @value{GDBN} is @dfn{free software}, protected by the @sc{gnu} |
c906108c SS |
236 | General Public License |
237 | (GPL). The GPL gives you the freedom to copy or adapt a licensed | |
238 | program---but every person getting a copy also gets with it the | |
239 | freedom to modify that copy (which means that they must get access to | |
240 | the source code), and the freedom to distribute further copies. | |
241 | Typical software companies use copyrights to limit your freedoms; the | |
242 | Free Software Foundation uses the GPL to preserve these freedoms. | |
243 | ||
244 | Fundamentally, the General Public License is a license which says that | |
245 | you have these freedoms and that you cannot take these freedoms away | |
246 | from anyone else. | |
247 | ||
2666264b | 248 | @unnumberedsec Free Software Needs Free Documentation |
959acfd1 EZ |
249 | |
250 | The biggest deficiency in the free software community today is not in | |
251 | the software---it is the lack of good free documentation that we can | |
252 | include with the free software. Many of our most important | |
253 | programs do not come with free reference manuals and free introductory | |
254 | texts. Documentation is an essential part of any software package; | |
255 | when an important free software package does not come with a free | |
256 | manual and a free tutorial, that is a major gap. We have many such | |
257 | gaps today. | |
258 | ||
259 | Consider Perl, for instance. The tutorial manuals that people | |
260 | normally use are non-free. How did this come about? Because the | |
261 | authors of those manuals published them with restrictive terms---no | |
262 | copying, no modification, source files not available---which exclude | |
263 | them from the free software world. | |
264 | ||
265 | That wasn't the first time this sort of thing happened, and it was far | |
266 | from the last. Many times we have heard a GNU user eagerly describe a | |
267 | manual that he is writing, his intended contribution to the community, | |
268 | only to learn that he had ruined everything by signing a publication | |
269 | contract to make it non-free. | |
270 | ||
271 | Free documentation, like free software, is a matter of freedom, not | |
272 | price. The problem with the non-free manual is not that publishers | |
273 | charge a price for printed copies---that in itself is fine. (The Free | |
274 | Software Foundation sells printed copies of manuals, too.) The | |
275 | problem is the restrictions on the use of the manual. Free manuals | |
276 | are available in source code form, and give you permission to copy and | |
277 | modify. Non-free manuals do not allow this. | |
278 | ||
279 | The criteria of freedom for a free manual are roughly the same as for | |
280 | free software. Redistribution (including the normal kinds of | |
281 | commercial redistribution) must be permitted, so that the manual can | |
282 | accompany every copy of the program, both on-line and on paper. | |
283 | ||
284 | Permission for modification of the technical content is crucial too. | |
285 | When people modify the software, adding or changing features, if they | |
286 | are conscientious they will change the manual too---so they can | |
287 | provide accurate and clear documentation for the modified program. A | |
288 | manual that leaves you no choice but to write a new manual to document | |
289 | a changed version of the program is not really available to our | |
290 | community. | |
291 | ||
292 | Some kinds of limits on the way modification is handled are | |
293 | acceptable. For example, requirements to preserve the original | |
294 | author's copyright notice, the distribution terms, or the list of | |
295 | authors, are ok. It is also no problem to require modified versions | |
296 | to include notice that they were modified. Even entire sections that | |
297 | may not be deleted or changed are acceptable, as long as they deal | |
298 | with nontechnical topics (like this one). These kinds of restrictions | |
299 | are acceptable because they don't obstruct the community's normal use | |
300 | of the manual. | |
301 | ||
302 | However, it must be possible to modify all the @emph{technical} | |
303 | content of the manual, and then distribute the result in all the usual | |
304 | media, through all the usual channels. Otherwise, the restrictions | |
305 | obstruct the use of the manual, it is not free, and we need another | |
306 | manual to replace it. | |
307 | ||
308 | Please spread the word about this issue. Our community continues to | |
309 | lose manuals to proprietary publishing. If we spread the word that | |
310 | free software needs free reference manuals and free tutorials, perhaps | |
311 | the next person who wants to contribute by writing documentation will | |
312 | realize, before it is too late, that only free manuals contribute to | |
313 | the free software community. | |
314 | ||
315 | If you are writing documentation, please insist on publishing it under | |
316 | the GNU Free Documentation License or another free documentation | |
317 | license. Remember that this decision requires your approval---you | |
318 | don't have to let the publisher decide. Some commercial publishers | |
319 | will use a free license if you insist, but they will not propose the | |
320 | option; it is up to you to raise the issue and say firmly that this is | |
321 | what you want. If the publisher you are dealing with refuses, please | |
322 | try other publishers. If you're not sure whether a proposed license | |
42584a72 | 323 | is free, write to @email{licensing@@gnu.org}. |
959acfd1 EZ |
324 | |
325 | You can encourage commercial publishers to sell more free, copylefted | |
326 | manuals and tutorials by buying them, and particularly by buying | |
327 | copies from the publishers that paid for their writing or for major | |
328 | improvements. Meanwhile, try to avoid buying non-free documentation | |
329 | at all. Check the distribution terms of a manual before you buy it, | |
330 | and insist that whoever seeks your business must respect your freedom. | |
72c9928d EZ |
331 | Check the history of the book, and try to reward the publishers that |
332 | have paid or pay the authors to work on it. | |
959acfd1 EZ |
333 | |
334 | The Free Software Foundation maintains a list of free documentation | |
335 | published by other publishers, at | |
336 | @url{http://www.fsf.org/doc/other-free-books.html}. | |
337 | ||
6d2ebf8b | 338 | @node Contributors |
96a2c332 SS |
339 | @unnumberedsec Contributors to @value{GDBN} |
340 | ||
341 | Richard Stallman was the original author of @value{GDBN}, and of many | |
342 | other @sc{gnu} programs. Many others have contributed to its | |
343 | development. This section attempts to credit major contributors. One | |
344 | of the virtues of free software is that everyone is free to contribute | |
345 | to it; with regret, we cannot actually acknowledge everyone here. The | |
346 | file @file{ChangeLog} in the @value{GDBN} distribution approximates a | |
c906108c SS |
347 | blow-by-blow account. |
348 | ||
349 | Changes much prior to version 2.0 are lost in the mists of time. | |
350 | ||
351 | @quotation | |
352 | @emph{Plea:} Additions to this section are particularly welcome. If you | |
353 | or your friends (or enemies, to be evenhanded) have been unfairly | |
354 | omitted from this list, we would like to add your names! | |
355 | @end quotation | |
356 | ||
357 | So that they may not regard their many labors as thankless, we | |
358 | particularly thank those who shepherded @value{GDBN} through major | |
359 | releases: | |
7ba3cf9c | 360 | Andrew Cagney (releases 6.3, 6.2, 6.1, 6.0, 5.3, 5.2, 5.1 and 5.0); |
c906108c SS |
361 | Jim Blandy (release 4.18); |
362 | Jason Molenda (release 4.17); | |
363 | Stan Shebs (release 4.14); | |
364 | Fred Fish (releases 4.16, 4.15, 4.13, 4.12, 4.11, 4.10, and 4.9); | |
365 | Stu Grossman and John Gilmore (releases 4.8, 4.7, 4.6, 4.5, and 4.4); | |
366 | John Gilmore (releases 4.3, 4.2, 4.1, 4.0, and 3.9); | |
367 | Jim Kingdon (releases 3.5, 3.4, and 3.3); | |
368 | and Randy Smith (releases 3.2, 3.1, and 3.0). | |
369 | ||
370 | Richard Stallman, assisted at various times by Peter TerMaat, Chris | |
371 | Hanson, and Richard Mlynarik, handled releases through 2.8. | |
372 | ||
b37052ae EZ |
373 | Michael Tiemann is the author of most of the @sc{gnu} C@t{++} support |
374 | in @value{GDBN}, with significant additional contributions from Per | |
375 | Bothner and Daniel Berlin. James Clark wrote the @sc{gnu} C@t{++} | |
376 | demangler. Early work on C@t{++} was by Peter TerMaat (who also did | |
377 | much general update work leading to release 3.0). | |
c906108c | 378 | |
b37052ae | 379 | @value{GDBN} uses the BFD subroutine library to examine multiple |
c906108c SS |
380 | object-file formats; BFD was a joint project of David V. |
381 | Henkel-Wallace, Rich Pixley, Steve Chamberlain, and John Gilmore. | |
382 | ||
383 | David Johnson wrote the original COFF support; Pace Willison did | |
384 | the original support for encapsulated COFF. | |
385 | ||
0179ffac | 386 | Brent Benson of Harris Computer Systems contributed DWARF 2 support. |
c906108c SS |
387 | |
388 | Adam de Boor and Bradley Davis contributed the ISI Optimum V support. | |
389 | Per Bothner, Noboyuki Hikichi, and Alessandro Forin contributed MIPS | |
390 | support. | |
391 | Jean-Daniel Fekete contributed Sun 386i support. | |
392 | Chris Hanson improved the HP9000 support. | |
393 | Noboyuki Hikichi and Tomoyuki Hasei contributed Sony/News OS 3 support. | |
394 | David Johnson contributed Encore Umax support. | |
395 | Jyrki Kuoppala contributed Altos 3068 support. | |
396 | Jeff Law contributed HP PA and SOM support. | |
397 | Keith Packard contributed NS32K support. | |
398 | Doug Rabson contributed Acorn Risc Machine support. | |
399 | Bob Rusk contributed Harris Nighthawk CX-UX support. | |
400 | Chris Smith contributed Convex support (and Fortran debugging). | |
401 | Jonathan Stone contributed Pyramid support. | |
402 | Michael Tiemann contributed SPARC support. | |
403 | Tim Tucker contributed support for the Gould NP1 and Gould Powernode. | |
404 | Pace Willison contributed Intel 386 support. | |
405 | Jay Vosburgh contributed Symmetry support. | |
a37295f9 | 406 | Marko Mlinar contributed OpenRISC 1000 support. |
c906108c | 407 | |
1104b9e7 | 408 | Andreas Schwab contributed M68K @sc{gnu}/Linux support. |
c906108c SS |
409 | |
410 | Rich Schaefer and Peter Schauer helped with support of SunOS shared | |
411 | libraries. | |
412 | ||
413 | Jay Fenlason and Roland McGrath ensured that @value{GDBN} and GAS agree | |
414 | about several machine instruction sets. | |
415 | ||
416 | Patrick Duval, Ted Goldstein, Vikram Koka and Glenn Engel helped develop | |
417 | remote debugging. Intel Corporation, Wind River Systems, AMD, and ARM | |
418 | contributed remote debugging modules for the i960, VxWorks, A29K UDI, | |
419 | and RDI targets, respectively. | |
420 | ||
421 | Brian Fox is the author of the readline libraries providing | |
422 | command-line editing and command history. | |
423 | ||
7a292a7a SS |
424 | Andrew Beers of SUNY Buffalo wrote the language-switching code, the |
425 | Modula-2 support, and contributed the Languages chapter of this manual. | |
c906108c | 426 | |
5d161b24 | 427 | Fred Fish wrote most of the support for Unix System Vr4. |
b37052ae | 428 | He also enhanced the command-completion support to cover C@t{++} overloaded |
c906108c | 429 | symbols. |
c906108c | 430 | |
f24c5e49 KI |
431 | Hitachi America (now Renesas America), Ltd. sponsored the support for |
432 | H8/300, H8/500, and Super-H processors. | |
c906108c SS |
433 | |
434 | NEC sponsored the support for the v850, Vr4xxx, and Vr5xxx processors. | |
435 | ||
f24c5e49 KI |
436 | Mitsubishi (now Renesas) sponsored the support for D10V, D30V, and M32R/D |
437 | processors. | |
c906108c SS |
438 | |
439 | Toshiba sponsored the support for the TX39 Mips processor. | |
440 | ||
441 | Matsushita sponsored the support for the MN10200 and MN10300 processors. | |
442 | ||
96a2c332 | 443 | Fujitsu sponsored the support for SPARClite and FR30 processors. |
c906108c SS |
444 | |
445 | Kung Hsu, Jeff Law, and Rick Sladkey added support for hardware | |
446 | watchpoints. | |
447 | ||
448 | Michael Snyder added support for tracepoints. | |
449 | ||
450 | Stu Grossman wrote gdbserver. | |
451 | ||
452 | Jim Kingdon, Peter Schauer, Ian Taylor, and Stu Grossman made | |
96a2c332 | 453 | nearly innumerable bug fixes and cleanups throughout @value{GDBN}. |
c906108c SS |
454 | |
455 | The following people at the Hewlett-Packard Company contributed | |
456 | support for the PA-RISC 2.0 architecture, HP-UX 10.20, 10.30, and 11.0 | |
b37052ae | 457 | (narrow mode), HP's implementation of kernel threads, HP's aC@t{++} |
d0d5df6f AC |
458 | compiler, and the Text User Interface (nee Terminal User Interface): |
459 | Ben Krepp, Richard Title, John Bishop, Susan Macchia, Kathy Mann, | |
460 | Satish Pai, India Paul, Steve Rehrauer, and Elena Zannoni. Kim Haase | |
461 | provided HP-specific information in this manual. | |
c906108c | 462 | |
b37052ae EZ |
463 | DJ Delorie ported @value{GDBN} to MS-DOS, for the DJGPP project. |
464 | Robert Hoehne made significant contributions to the DJGPP port. | |
465 | ||
96a2c332 SS |
466 | Cygnus Solutions has sponsored @value{GDBN} maintenance and much of its |
467 | development since 1991. Cygnus engineers who have worked on @value{GDBN} | |
2df3850c JM |
468 | fulltime include Mark Alexander, Jim Blandy, Per Bothner, Kevin |
469 | Buettner, Edith Epstein, Chris Faylor, Fred Fish, Martin Hunt, Jim | |
470 | Ingham, John Gilmore, Stu Grossman, Kung Hsu, Jim Kingdon, John Metzler, | |
471 | Fernando Nasser, Geoffrey Noer, Dawn Perchik, Rich Pixley, Zdenek | |
472 | Radouch, Keith Seitz, Stan Shebs, David Taylor, and Elena Zannoni. In | |
473 | addition, Dave Brolley, Ian Carmichael, Steve Chamberlain, Nick Clifton, | |
474 | JT Conklin, Stan Cox, DJ Delorie, Ulrich Drepper, Frank Eigler, Doug | |
475 | Evans, Sean Fagan, David Henkel-Wallace, Richard Henderson, Jeff | |
476 | Holcomb, Jeff Law, Jim Lemke, Tom Lord, Bob Manson, Michael Meissner, | |
477 | Jason Merrill, Catherine Moore, Drew Moseley, Ken Raeburn, Gavin | |
478 | Romig-Koch, Rob Savoye, Jamie Smith, Mike Stump, Ian Taylor, Angela | |
479 | Thomas, Michael Tiemann, Tom Tromey, Ron Unrau, Jim Wilson, and David | |
480 | Zuhn have made contributions both large and small. | |
c906108c | 481 | |
ffed4509 AC |
482 | Andrew Cagney, Fernando Nasser, and Elena Zannoni, while working for |
483 | Cygnus Solutions, implemented the original @sc{gdb/mi} interface. | |
484 | ||
e2e0bcd1 JB |
485 | Jim Blandy added support for preprocessor macros, while working for Red |
486 | Hat. | |
c906108c | 487 | |
a9967aef AC |
488 | Andrew Cagney designed @value{GDBN}'s architecture vector. Many |
489 | people including Andrew Cagney, Stephane Carrez, Randolph Chung, Nick | |
490 | Duffek, Richard Henderson, Mark Kettenis, Grace Sainsbury, Kei | |
491 | Sakamoto, Yoshinori Sato, Michael Snyder, Andreas Schwab, Jason | |
492 | Thorpe, Corinna Vinschen, Ulrich Weigand, and Elena Zannoni, helped | |
493 | with the migration of old architectures to this new framework. | |
494 | ||
c5e30d01 AC |
495 | Andrew Cagney completely re-designed and re-implemented @value{GDBN}'s |
496 | unwinder framework, this consisting of a fresh new design featuring | |
497 | frame IDs, independent frame sniffers, and the sentinel frame. Mark | |
498 | Kettenis implemented the @sc{dwarf 2} unwinder, Jeff Johnston the | |
499 | libunwind unwinder, and Andrew Cagney the dummy, sentinel, tramp, and | |
db2e3e2e | 500 | trad unwinders. The architecture-specific changes, each involving a |
c5e30d01 AC |
501 | complete rewrite of the architecture's frame code, were carried out by |
502 | Jim Blandy, Joel Brobecker, Kevin Buettner, Andrew Cagney, Stephane | |
503 | Carrez, Randolph Chung, Orjan Friberg, Richard Henderson, Daniel | |
504 | Jacobowitz, Jeff Johnston, Mark Kettenis, Theodore A. Roth, Kei | |
505 | Sakamoto, Yoshinori Sato, Michael Snyder, Corinna Vinschen, and Ulrich | |
506 | Weigand. | |
507 | ||
ca3bf3bd DJ |
508 | Christian Zankel, Ross Morley, Bob Wilson, and Maxim Grigoriev from |
509 | Tensilica, Inc.@: contributed support for Xtensa processors. Others | |
510 | who have worked on the Xtensa port of @value{GDBN} in the past include | |
511 | Steve Tjiang, John Newlin, and Scott Foehner. | |
512 | ||
6d2ebf8b | 513 | @node Sample Session |
c906108c SS |
514 | @chapter A Sample @value{GDBN} Session |
515 | ||
516 | You can use this manual at your leisure to read all about @value{GDBN}. | |
517 | However, a handful of commands are enough to get started using the | |
518 | debugger. This chapter illustrates those commands. | |
519 | ||
520 | @iftex | |
521 | In this sample session, we emphasize user input like this: @b{input}, | |
522 | to make it easier to pick out from the surrounding output. | |
523 | @end iftex | |
524 | ||
525 | @c FIXME: this example may not be appropriate for some configs, where | |
526 | @c FIXME...primary interest is in remote use. | |
527 | ||
528 | One of the preliminary versions of @sc{gnu} @code{m4} (a generic macro | |
529 | processor) exhibits the following bug: sometimes, when we change its | |
530 | quote strings from the default, the commands used to capture one macro | |
531 | definition within another stop working. In the following short @code{m4} | |
532 | session, we define a macro @code{foo} which expands to @code{0000}; we | |
533 | then use the @code{m4} built-in @code{defn} to define @code{bar} as the | |
534 | same thing. However, when we change the open quote string to | |
535 | @code{<QUOTE>} and the close quote string to @code{<UNQUOTE>}, the same | |
536 | procedure fails to define a new synonym @code{baz}: | |
537 | ||
538 | @smallexample | |
539 | $ @b{cd gnu/m4} | |
540 | $ @b{./m4} | |
541 | @b{define(foo,0000)} | |
542 | ||
543 | @b{foo} | |
544 | 0000 | |
545 | @b{define(bar,defn(`foo'))} | |
546 | ||
547 | @b{bar} | |
548 | 0000 | |
549 | @b{changequote(<QUOTE>,<UNQUOTE>)} | |
550 | ||
551 | @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))} | |
552 | @b{baz} | |
c8aa23ab | 553 | @b{Ctrl-d} |
c906108c SS |
554 | m4: End of input: 0: fatal error: EOF in string |
555 | @end smallexample | |
556 | ||
557 | @noindent | |
558 | Let us use @value{GDBN} to try to see what is going on. | |
559 | ||
c906108c SS |
560 | @smallexample |
561 | $ @b{@value{GDBP} m4} | |
562 | @c FIXME: this falsifies the exact text played out, to permit smallbook | |
563 | @c FIXME... format to come out better. | |
564 | @value{GDBN} is free software and you are welcome to distribute copies | |
5d161b24 | 565 | of it under certain conditions; type "show copying" to see |
c906108c | 566 | the conditions. |
5d161b24 | 567 | There is absolutely no warranty for @value{GDBN}; type "show warranty" |
c906108c SS |
568 | for details. |
569 | ||
570 | @value{GDBN} @value{GDBVN}, Copyright 1999 Free Software Foundation, Inc... | |
571 | (@value{GDBP}) | |
572 | @end smallexample | |
c906108c SS |
573 | |
574 | @noindent | |
575 | @value{GDBN} reads only enough symbol data to know where to find the | |
576 | rest when needed; as a result, the first prompt comes up very quickly. | |
577 | We now tell @value{GDBN} to use a narrower display width than usual, so | |
578 | that examples fit in this manual. | |
579 | ||
580 | @smallexample | |
581 | (@value{GDBP}) @b{set width 70} | |
582 | @end smallexample | |
583 | ||
584 | @noindent | |
585 | We need to see how the @code{m4} built-in @code{changequote} works. | |
586 | Having looked at the source, we know the relevant subroutine is | |
587 | @code{m4_changequote}, so we set a breakpoint there with the @value{GDBN} | |
588 | @code{break} command. | |
589 | ||
590 | @smallexample | |
591 | (@value{GDBP}) @b{break m4_changequote} | |
592 | Breakpoint 1 at 0x62f4: file builtin.c, line 879. | |
593 | @end smallexample | |
594 | ||
595 | @noindent | |
596 | Using the @code{run} command, we start @code{m4} running under @value{GDBN} | |
597 | control; as long as control does not reach the @code{m4_changequote} | |
598 | subroutine, the program runs as usual: | |
599 | ||
600 | @smallexample | |
601 | (@value{GDBP}) @b{run} | |
602 | Starting program: /work/Editorial/gdb/gnu/m4/m4 | |
603 | @b{define(foo,0000)} | |
604 | ||
605 | @b{foo} | |
606 | 0000 | |
607 | @end smallexample | |
608 | ||
609 | @noindent | |
610 | To trigger the breakpoint, we call @code{changequote}. @value{GDBN} | |
611 | suspends execution of @code{m4}, displaying information about the | |
612 | context where it stops. | |
613 | ||
614 | @smallexample | |
615 | @b{changequote(<QUOTE>,<UNQUOTE>)} | |
616 | ||
5d161b24 | 617 | Breakpoint 1, m4_changequote (argc=3, argv=0x33c70) |
c906108c SS |
618 | at builtin.c:879 |
619 | 879 if (bad_argc(TOKEN_DATA_TEXT(argv[0]),argc,1,3)) | |
620 | @end smallexample | |
621 | ||
622 | @noindent | |
623 | Now we use the command @code{n} (@code{next}) to advance execution to | |
624 | the next line of the current function. | |
625 | ||
626 | @smallexample | |
627 | (@value{GDBP}) @b{n} | |
628 | 882 set_quotes((argc >= 2) ? TOKEN_DATA_TEXT(argv[1])\ | |
629 | : nil, | |
630 | @end smallexample | |
631 | ||
632 | @noindent | |
633 | @code{set_quotes} looks like a promising subroutine. We can go into it | |
634 | by using the command @code{s} (@code{step}) instead of @code{next}. | |
635 | @code{step} goes to the next line to be executed in @emph{any} | |
636 | subroutine, so it steps into @code{set_quotes}. | |
637 | ||
638 | @smallexample | |
639 | (@value{GDBP}) @b{s} | |
640 | set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>") | |
641 | at input.c:530 | |
642 | 530 if (lquote != def_lquote) | |
643 | @end smallexample | |
644 | ||
645 | @noindent | |
646 | The display that shows the subroutine where @code{m4} is now | |
647 | suspended (and its arguments) is called a stack frame display. It | |
648 | shows a summary of the stack. We can use the @code{backtrace} | |
649 | command (which can also be spelled @code{bt}), to see where we are | |
650 | in the stack as a whole: the @code{backtrace} command displays a | |
651 | stack frame for each active subroutine. | |
652 | ||
653 | @smallexample | |
654 | (@value{GDBP}) @b{bt} | |
655 | #0 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>") | |
656 | at input.c:530 | |
5d161b24 | 657 | #1 0x6344 in m4_changequote (argc=3, argv=0x33c70) |
c906108c SS |
658 | at builtin.c:882 |
659 | #2 0x8174 in expand_macro (sym=0x33320) at macro.c:242 | |
660 | #3 0x7a88 in expand_token (obs=0x0, t=209696, td=0xf7fffa30) | |
661 | at macro.c:71 | |
662 | #4 0x79dc in expand_input () at macro.c:40 | |
663 | #5 0x2930 in main (argc=0, argv=0xf7fffb20) at m4.c:195 | |
664 | @end smallexample | |
665 | ||
666 | @noindent | |
667 | We step through a few more lines to see what happens. The first two | |
668 | times, we can use @samp{s}; the next two times we use @code{n} to avoid | |
669 | falling into the @code{xstrdup} subroutine. | |
670 | ||
671 | @smallexample | |
672 | (@value{GDBP}) @b{s} | |
673 | 0x3b5c 532 if (rquote != def_rquote) | |
674 | (@value{GDBP}) @b{s} | |
675 | 0x3b80 535 lquote = (lq == nil || *lq == '\0') ? \ | |
676 | def_lquote : xstrdup(lq); | |
677 | (@value{GDBP}) @b{n} | |
678 | 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\ | |
679 | : xstrdup(rq); | |
680 | (@value{GDBP}) @b{n} | |
681 | 538 len_lquote = strlen(rquote); | |
682 | @end smallexample | |
683 | ||
684 | @noindent | |
685 | The last line displayed looks a little odd; we can examine the variables | |
686 | @code{lquote} and @code{rquote} to see if they are in fact the new left | |
687 | and right quotes we specified. We use the command @code{p} | |
688 | (@code{print}) to see their values. | |
689 | ||
690 | @smallexample | |
691 | (@value{GDBP}) @b{p lquote} | |
692 | $1 = 0x35d40 "<QUOTE>" | |
693 | (@value{GDBP}) @b{p rquote} | |
694 | $2 = 0x35d50 "<UNQUOTE>" | |
695 | @end smallexample | |
696 | ||
697 | @noindent | |
698 | @code{lquote} and @code{rquote} are indeed the new left and right quotes. | |
699 | To look at some context, we can display ten lines of source | |
700 | surrounding the current line with the @code{l} (@code{list}) command. | |
701 | ||
702 | @smallexample | |
703 | (@value{GDBP}) @b{l} | |
704 | 533 xfree(rquote); | |
705 | 534 | |
706 | 535 lquote = (lq == nil || *lq == '\0') ? def_lquote\ | |
707 | : xstrdup (lq); | |
708 | 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\ | |
709 | : xstrdup (rq); | |
710 | 537 | |
711 | 538 len_lquote = strlen(rquote); | |
712 | 539 len_rquote = strlen(lquote); | |
713 | 540 @} | |
714 | 541 | |
715 | 542 void | |
716 | @end smallexample | |
717 | ||
718 | @noindent | |
719 | Let us step past the two lines that set @code{len_lquote} and | |
720 | @code{len_rquote}, and then examine the values of those variables. | |
721 | ||
722 | @smallexample | |
723 | (@value{GDBP}) @b{n} | |
724 | 539 len_rquote = strlen(lquote); | |
725 | (@value{GDBP}) @b{n} | |
726 | 540 @} | |
727 | (@value{GDBP}) @b{p len_lquote} | |
728 | $3 = 9 | |
729 | (@value{GDBP}) @b{p len_rquote} | |
730 | $4 = 7 | |
731 | @end smallexample | |
732 | ||
733 | @noindent | |
734 | That certainly looks wrong, assuming @code{len_lquote} and | |
735 | @code{len_rquote} are meant to be the lengths of @code{lquote} and | |
736 | @code{rquote} respectively. We can set them to better values using | |
737 | the @code{p} command, since it can print the value of | |
738 | any expression---and that expression can include subroutine calls and | |
739 | assignments. | |
740 | ||
741 | @smallexample | |
742 | (@value{GDBP}) @b{p len_lquote=strlen(lquote)} | |
743 | $5 = 7 | |
744 | (@value{GDBP}) @b{p len_rquote=strlen(rquote)} | |
745 | $6 = 9 | |
746 | @end smallexample | |
747 | ||
748 | @noindent | |
749 | Is that enough to fix the problem of using the new quotes with the | |
750 | @code{m4} built-in @code{defn}? We can allow @code{m4} to continue | |
751 | executing with the @code{c} (@code{continue}) command, and then try the | |
752 | example that caused trouble initially: | |
753 | ||
754 | @smallexample | |
755 | (@value{GDBP}) @b{c} | |
756 | Continuing. | |
757 | ||
758 | @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))} | |
759 | ||
760 | baz | |
761 | 0000 | |
762 | @end smallexample | |
763 | ||
764 | @noindent | |
765 | Success! The new quotes now work just as well as the default ones. The | |
766 | problem seems to have been just the two typos defining the wrong | |
767 | lengths. We allow @code{m4} exit by giving it an EOF as input: | |
768 | ||
769 | @smallexample | |
c8aa23ab | 770 | @b{Ctrl-d} |
c906108c SS |
771 | Program exited normally. |
772 | @end smallexample | |
773 | ||
774 | @noindent | |
775 | The message @samp{Program exited normally.} is from @value{GDBN}; it | |
776 | indicates @code{m4} has finished executing. We can end our @value{GDBN} | |
777 | session with the @value{GDBN} @code{quit} command. | |
778 | ||
779 | @smallexample | |
780 | (@value{GDBP}) @b{quit} | |
781 | @end smallexample | |
c906108c | 782 | |
6d2ebf8b | 783 | @node Invocation |
c906108c SS |
784 | @chapter Getting In and Out of @value{GDBN} |
785 | ||
786 | This chapter discusses how to start @value{GDBN}, and how to get out of it. | |
5d161b24 | 787 | The essentials are: |
c906108c | 788 | @itemize @bullet |
5d161b24 | 789 | @item |
53a5351d | 790 | type @samp{@value{GDBP}} to start @value{GDBN}. |
5d161b24 | 791 | @item |
c8aa23ab | 792 | type @kbd{quit} or @kbd{Ctrl-d} to exit. |
c906108c SS |
793 | @end itemize |
794 | ||
795 | @menu | |
796 | * Invoking GDB:: How to start @value{GDBN} | |
797 | * Quitting GDB:: How to quit @value{GDBN} | |
798 | * Shell Commands:: How to use shell commands inside @value{GDBN} | |
79a6e687 | 799 | * Logging Output:: How to log @value{GDBN}'s output to a file |
c906108c SS |
800 | @end menu |
801 | ||
6d2ebf8b | 802 | @node Invoking GDB |
c906108c SS |
803 | @section Invoking @value{GDBN} |
804 | ||
c906108c SS |
805 | Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started, |
806 | @value{GDBN} reads commands from the terminal until you tell it to exit. | |
807 | ||
808 | You can also run @code{@value{GDBP}} with a variety of arguments and options, | |
809 | to specify more of your debugging environment at the outset. | |
810 | ||
c906108c SS |
811 | The command-line options described here are designed |
812 | to cover a variety of situations; in some environments, some of these | |
5d161b24 | 813 | options may effectively be unavailable. |
c906108c SS |
814 | |
815 | The most usual way to start @value{GDBN} is with one argument, | |
816 | specifying an executable program: | |
817 | ||
474c8240 | 818 | @smallexample |
c906108c | 819 | @value{GDBP} @var{program} |
474c8240 | 820 | @end smallexample |
c906108c | 821 | |
c906108c SS |
822 | @noindent |
823 | You can also start with both an executable program and a core file | |
824 | specified: | |
825 | ||
474c8240 | 826 | @smallexample |
c906108c | 827 | @value{GDBP} @var{program} @var{core} |
474c8240 | 828 | @end smallexample |
c906108c SS |
829 | |
830 | You can, instead, specify a process ID as a second argument, if you want | |
831 | to debug a running process: | |
832 | ||
474c8240 | 833 | @smallexample |
c906108c | 834 | @value{GDBP} @var{program} 1234 |
474c8240 | 835 | @end smallexample |
c906108c SS |
836 | |
837 | @noindent | |
838 | would attach @value{GDBN} to process @code{1234} (unless you also have a file | |
839 | named @file{1234}; @value{GDBN} does check for a core file first). | |
840 | ||
c906108c | 841 | Taking advantage of the second command-line argument requires a fairly |
2df3850c JM |
842 | complete operating system; when you use @value{GDBN} as a remote |
843 | debugger attached to a bare board, there may not be any notion of | |
844 | ``process'', and there is often no way to get a core dump. @value{GDBN} | |
845 | will warn you if it is unable to attach or to read core dumps. | |
c906108c | 846 | |
aa26fa3a TT |
847 | You can optionally have @code{@value{GDBP}} pass any arguments after the |
848 | executable file to the inferior using @code{--args}. This option stops | |
849 | option processing. | |
474c8240 | 850 | @smallexample |
3f94c067 | 851 | @value{GDBP} --args gcc -O2 -c foo.c |
474c8240 | 852 | @end smallexample |
aa26fa3a TT |
853 | This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set |
854 | @code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}. | |
855 | ||
96a2c332 | 856 | You can run @code{@value{GDBP}} without printing the front material, which describes |
c906108c SS |
857 | @value{GDBN}'s non-warranty, by specifying @code{-silent}: |
858 | ||
859 | @smallexample | |
860 | @value{GDBP} -silent | |
861 | @end smallexample | |
862 | ||
863 | @noindent | |
864 | You can further control how @value{GDBN} starts up by using command-line | |
865 | options. @value{GDBN} itself can remind you of the options available. | |
866 | ||
867 | @noindent | |
868 | Type | |
869 | ||
474c8240 | 870 | @smallexample |
c906108c | 871 | @value{GDBP} -help |
474c8240 | 872 | @end smallexample |
c906108c SS |
873 | |
874 | @noindent | |
875 | to display all available options and briefly describe their use | |
876 | (@samp{@value{GDBP} -h} is a shorter equivalent). | |
877 | ||
878 | All options and command line arguments you give are processed | |
879 | in sequential order. The order makes a difference when the | |
880 | @samp{-x} option is used. | |
881 | ||
882 | ||
883 | @menu | |
c906108c SS |
884 | * File Options:: Choosing files |
885 | * Mode Options:: Choosing modes | |
6fc08d32 | 886 | * Startup:: What @value{GDBN} does during startup |
c906108c SS |
887 | @end menu |
888 | ||
6d2ebf8b | 889 | @node File Options |
79a6e687 | 890 | @subsection Choosing Files |
c906108c | 891 | |
2df3850c | 892 | When @value{GDBN} starts, it reads any arguments other than options as |
c906108c SS |
893 | specifying an executable file and core file (or process ID). This is |
894 | the same as if the arguments were specified by the @samp{-se} and | |
d52fb0e9 | 895 | @samp{-c} (or @samp{-p}) options respectively. (@value{GDBN} reads the |
19837790 MS |
896 | first argument that does not have an associated option flag as |
897 | equivalent to the @samp{-se} option followed by that argument; and the | |
898 | second argument that does not have an associated option flag, if any, as | |
899 | equivalent to the @samp{-c}/@samp{-p} option followed by that argument.) | |
900 | If the second argument begins with a decimal digit, @value{GDBN} will | |
901 | first attempt to attach to it as a process, and if that fails, attempt | |
902 | to open it as a corefile. If you have a corefile whose name begins with | |
b383017d | 903 | a digit, you can prevent @value{GDBN} from treating it as a pid by |
c1468174 | 904 | prefixing it with @file{./}, e.g.@: @file{./12345}. |
7a292a7a SS |
905 | |
906 | If @value{GDBN} has not been configured to included core file support, | |
907 | such as for most embedded targets, then it will complain about a second | |
908 | argument and ignore it. | |
c906108c SS |
909 | |
910 | Many options have both long and short forms; both are shown in the | |
911 | following list. @value{GDBN} also recognizes the long forms if you truncate | |
912 | them, so long as enough of the option is present to be unambiguous. | |
913 | (If you prefer, you can flag option arguments with @samp{--} rather | |
914 | than @samp{-}, though we illustrate the more usual convention.) | |
915 | ||
d700128c EZ |
916 | @c NOTE: the @cindex entries here use double dashes ON PURPOSE. This |
917 | @c way, both those who look for -foo and --foo in the index, will find | |
918 | @c it. | |
919 | ||
c906108c SS |
920 | @table @code |
921 | @item -symbols @var{file} | |
922 | @itemx -s @var{file} | |
d700128c EZ |
923 | @cindex @code{--symbols} |
924 | @cindex @code{-s} | |
c906108c SS |
925 | Read symbol table from file @var{file}. |
926 | ||
927 | @item -exec @var{file} | |
928 | @itemx -e @var{file} | |
d700128c EZ |
929 | @cindex @code{--exec} |
930 | @cindex @code{-e} | |
7a292a7a SS |
931 | Use file @var{file} as the executable file to execute when appropriate, |
932 | and for examining pure data in conjunction with a core dump. | |
c906108c SS |
933 | |
934 | @item -se @var{file} | |
d700128c | 935 | @cindex @code{--se} |
c906108c SS |
936 | Read symbol table from file @var{file} and use it as the executable |
937 | file. | |
938 | ||
c906108c SS |
939 | @item -core @var{file} |
940 | @itemx -c @var{file} | |
d700128c EZ |
941 | @cindex @code{--core} |
942 | @cindex @code{-c} | |
b383017d | 943 | Use file @var{file} as a core dump to examine. |
c906108c | 944 | |
19837790 MS |
945 | @item -pid @var{number} |
946 | @itemx -p @var{number} | |
947 | @cindex @code{--pid} | |
948 | @cindex @code{-p} | |
949 | Connect to process ID @var{number}, as with the @code{attach} command. | |
c906108c SS |
950 | |
951 | @item -command @var{file} | |
952 | @itemx -x @var{file} | |
d700128c EZ |
953 | @cindex @code{--command} |
954 | @cindex @code{-x} | |
c906108c SS |
955 | Execute @value{GDBN} commands from file @var{file}. @xref{Command |
956 | Files,, Command files}. | |
957 | ||
8a5a3c82 AS |
958 | @item -eval-command @var{command} |
959 | @itemx -ex @var{command} | |
960 | @cindex @code{--eval-command} | |
961 | @cindex @code{-ex} | |
962 | Execute a single @value{GDBN} command. | |
963 | ||
964 | This option may be used multiple times to call multiple commands. It may | |
965 | also be interleaved with @samp{-command} as required. | |
966 | ||
967 | @smallexample | |
968 | @value{GDBP} -ex 'target sim' -ex 'load' \ | |
969 | -x setbreakpoints -ex 'run' a.out | |
970 | @end smallexample | |
971 | ||
c906108c SS |
972 | @item -directory @var{directory} |
973 | @itemx -d @var{directory} | |
d700128c EZ |
974 | @cindex @code{--directory} |
975 | @cindex @code{-d} | |
4b505b12 | 976 | Add @var{directory} to the path to search for source and script files. |
c906108c | 977 | |
c906108c SS |
978 | @item -r |
979 | @itemx -readnow | |
d700128c EZ |
980 | @cindex @code{--readnow} |
981 | @cindex @code{-r} | |
c906108c SS |
982 | Read each symbol file's entire symbol table immediately, rather than |
983 | the default, which is to read it incrementally as it is needed. | |
984 | This makes startup slower, but makes future operations faster. | |
53a5351d | 985 | |
c906108c SS |
986 | @end table |
987 | ||
6d2ebf8b | 988 | @node Mode Options |
79a6e687 | 989 | @subsection Choosing Modes |
c906108c SS |
990 | |
991 | You can run @value{GDBN} in various alternative modes---for example, in | |
992 | batch mode or quiet mode. | |
993 | ||
994 | @table @code | |
995 | @item -nx | |
996 | @itemx -n | |
d700128c EZ |
997 | @cindex @code{--nx} |
998 | @cindex @code{-n} | |
96565e91 | 999 | Do not execute commands found in any initialization files. Normally, |
2df3850c JM |
1000 | @value{GDBN} executes the commands in these files after all the command |
1001 | options and arguments have been processed. @xref{Command Files,,Command | |
79a6e687 | 1002 | Files}. |
c906108c SS |
1003 | |
1004 | @item -quiet | |
d700128c | 1005 | @itemx -silent |
c906108c | 1006 | @itemx -q |
d700128c EZ |
1007 | @cindex @code{--quiet} |
1008 | @cindex @code{--silent} | |
1009 | @cindex @code{-q} | |
c906108c SS |
1010 | ``Quiet''. Do not print the introductory and copyright messages. These |
1011 | messages are also suppressed in batch mode. | |
1012 | ||
1013 | @item -batch | |
d700128c | 1014 | @cindex @code{--batch} |
c906108c SS |
1015 | Run in batch mode. Exit with status @code{0} after processing all the |
1016 | command files specified with @samp{-x} (and all commands from | |
1017 | initialization files, if not inhibited with @samp{-n}). Exit with | |
1018 | nonzero status if an error occurs in executing the @value{GDBN} commands | |
1019 | in the command files. | |
1020 | ||
2df3850c JM |
1021 | Batch mode may be useful for running @value{GDBN} as a filter, for |
1022 | example to download and run a program on another computer; in order to | |
1023 | make this more useful, the message | |
c906108c | 1024 | |
474c8240 | 1025 | @smallexample |
c906108c | 1026 | Program exited normally. |
474c8240 | 1027 | @end smallexample |
c906108c SS |
1028 | |
1029 | @noindent | |
2df3850c JM |
1030 | (which is ordinarily issued whenever a program running under |
1031 | @value{GDBN} control terminates) is not issued when running in batch | |
1032 | mode. | |
1033 | ||
1a088d06 AS |
1034 | @item -batch-silent |
1035 | @cindex @code{--batch-silent} | |
1036 | Run in batch mode exactly like @samp{-batch}, but totally silently. All | |
1037 | @value{GDBN} output to @code{stdout} is prevented (@code{stderr} is | |
1038 | unaffected). This is much quieter than @samp{-silent} and would be useless | |
1039 | for an interactive session. | |
1040 | ||
1041 | This is particularly useful when using targets that give @samp{Loading section} | |
1042 | messages, for example. | |
1043 | ||
1044 | Note that targets that give their output via @value{GDBN}, as opposed to | |
1045 | writing directly to @code{stdout}, will also be made silent. | |
1046 | ||
4b0ad762 AS |
1047 | @item -return-child-result |
1048 | @cindex @code{--return-child-result} | |
1049 | The return code from @value{GDBN} will be the return code from the child | |
1050 | process (the process being debugged), with the following exceptions: | |
1051 | ||
1052 | @itemize @bullet | |
1053 | @item | |
1054 | @value{GDBN} exits abnormally. E.g., due to an incorrect argument or an | |
1055 | internal error. In this case the exit code is the same as it would have been | |
1056 | without @samp{-return-child-result}. | |
1057 | @item | |
1058 | The user quits with an explicit value. E.g., @samp{quit 1}. | |
1059 | @item | |
1060 | The child process never runs, or is not allowed to terminate, in which case | |
1061 | the exit code will be -1. | |
1062 | @end itemize | |
1063 | ||
1064 | This option is useful in conjunction with @samp{-batch} or @samp{-batch-silent}, | |
1065 | when @value{GDBN} is being used as a remote program loader or simulator | |
1066 | interface. | |
1067 | ||
2df3850c JM |
1068 | @item -nowindows |
1069 | @itemx -nw | |
d700128c EZ |
1070 | @cindex @code{--nowindows} |
1071 | @cindex @code{-nw} | |
2df3850c | 1072 | ``No windows''. If @value{GDBN} comes with a graphical user interface |
96a2c332 | 1073 | (GUI) built in, then this option tells @value{GDBN} to only use the command-line |
2df3850c JM |
1074 | interface. If no GUI is available, this option has no effect. |
1075 | ||
1076 | @item -windows | |
1077 | @itemx -w | |
d700128c EZ |
1078 | @cindex @code{--windows} |
1079 | @cindex @code{-w} | |
2df3850c JM |
1080 | If @value{GDBN} includes a GUI, then this option requires it to be |
1081 | used if possible. | |
c906108c SS |
1082 | |
1083 | @item -cd @var{directory} | |
d700128c | 1084 | @cindex @code{--cd} |
c906108c SS |
1085 | Run @value{GDBN} using @var{directory} as its working directory, |
1086 | instead of the current directory. | |
1087 | ||
c906108c SS |
1088 | @item -fullname |
1089 | @itemx -f | |
d700128c EZ |
1090 | @cindex @code{--fullname} |
1091 | @cindex @code{-f} | |
7a292a7a SS |
1092 | @sc{gnu} Emacs sets this option when it runs @value{GDBN} as a |
1093 | subprocess. It tells @value{GDBN} to output the full file name and line | |
1094 | number in a standard, recognizable fashion each time a stack frame is | |
1095 | displayed (which includes each time your program stops). This | |
1096 | recognizable format looks like two @samp{\032} characters, followed by | |
1097 | the file name, line number and character position separated by colons, | |
1098 | and a newline. The Emacs-to-@value{GDBN} interface program uses the two | |
1099 | @samp{\032} characters as a signal to display the source code for the | |
1100 | frame. | |
c906108c | 1101 | |
d700128c EZ |
1102 | @item -epoch |
1103 | @cindex @code{--epoch} | |
1104 | The Epoch Emacs-@value{GDBN} interface sets this option when it runs | |
1105 | @value{GDBN} as a subprocess. It tells @value{GDBN} to modify its print | |
1106 | routines so as to allow Epoch to display values of expressions in a | |
1107 | separate window. | |
1108 | ||
1109 | @item -annotate @var{level} | |
1110 | @cindex @code{--annotate} | |
1111 | This option sets the @dfn{annotation level} inside @value{GDBN}. Its | |
1112 | effect is identical to using @samp{set annotate @var{level}} | |
086432e2 AC |
1113 | (@pxref{Annotations}). The annotation @var{level} controls how much |
1114 | information @value{GDBN} prints together with its prompt, values of | |
1115 | expressions, source lines, and other types of output. Level 0 is the | |
1116 | normal, level 1 is for use when @value{GDBN} is run as a subprocess of | |
1117 | @sc{gnu} Emacs, level 3 is the maximum annotation suitable for programs | |
1118 | that control @value{GDBN}, and level 2 has been deprecated. | |
1119 | ||
265eeb58 | 1120 | The annotation mechanism has largely been superseded by @sc{gdb/mi} |
086432e2 | 1121 | (@pxref{GDB/MI}). |
d700128c | 1122 | |
aa26fa3a TT |
1123 | @item --args |
1124 | @cindex @code{--args} | |
1125 | Change interpretation of command line so that arguments following the | |
1126 | executable file are passed as command line arguments to the inferior. | |
1127 | This option stops option processing. | |
1128 | ||
2df3850c JM |
1129 | @item -baud @var{bps} |
1130 | @itemx -b @var{bps} | |
d700128c EZ |
1131 | @cindex @code{--baud} |
1132 | @cindex @code{-b} | |
c906108c SS |
1133 | Set the line speed (baud rate or bits per second) of any serial |
1134 | interface used by @value{GDBN} for remote debugging. | |
c906108c | 1135 | |
f47b1503 AS |
1136 | @item -l @var{timeout} |
1137 | @cindex @code{-l} | |
1138 | Set the timeout (in seconds) of any communication used by @value{GDBN} | |
1139 | for remote debugging. | |
1140 | ||
c906108c | 1141 | @item -tty @var{device} |
d700128c EZ |
1142 | @itemx -t @var{device} |
1143 | @cindex @code{--tty} | |
1144 | @cindex @code{-t} | |
c906108c SS |
1145 | Run using @var{device} for your program's standard input and output. |
1146 | @c FIXME: kingdon thinks there is more to -tty. Investigate. | |
c906108c | 1147 | |
53a5351d | 1148 | @c resolve the situation of these eventually |
c4555f82 SC |
1149 | @item -tui |
1150 | @cindex @code{--tui} | |
d0d5df6f AC |
1151 | Activate the @dfn{Text User Interface} when starting. The Text User |
1152 | Interface manages several text windows on the terminal, showing | |
1153 | source, assembly, registers and @value{GDBN} command outputs | |
1154 | (@pxref{TUI, ,@value{GDBN} Text User Interface}). Alternatively, the | |
1155 | Text User Interface can be enabled by invoking the program | |
46ba6afa | 1156 | @samp{@value{GDBTUI}}. Do not use this option if you run @value{GDBN} from |
d0d5df6f | 1157 | Emacs (@pxref{Emacs, ,Using @value{GDBN} under @sc{gnu} Emacs}). |
53a5351d JM |
1158 | |
1159 | @c @item -xdb | |
d700128c | 1160 | @c @cindex @code{--xdb} |
53a5351d JM |
1161 | @c Run in XDB compatibility mode, allowing the use of certain XDB commands. |
1162 | @c For information, see the file @file{xdb_trans.html}, which is usually | |
1163 | @c installed in the directory @code{/opt/langtools/wdb/doc} on HP-UX | |
1164 | @c systems. | |
1165 | ||
d700128c EZ |
1166 | @item -interpreter @var{interp} |
1167 | @cindex @code{--interpreter} | |
1168 | Use the interpreter @var{interp} for interface with the controlling | |
1169 | program or device. This option is meant to be set by programs which | |
94bbb2c0 | 1170 | communicate with @value{GDBN} using it as a back end. |
21c294e6 | 1171 | @xref{Interpreters, , Command Interpreters}. |
94bbb2c0 | 1172 | |
da0f9dcd | 1173 | @samp{--interpreter=mi} (or @samp{--interpreter=mi2}) causes |
2fcf52f0 | 1174 | @value{GDBN} to use the @dfn{@sc{gdb/mi} interface} (@pxref{GDB/MI, , |
6b5e8c01 | 1175 | The @sc{gdb/mi} Interface}) included since @value{GDBN} version 6.0. The |
6c74ac8b AC |
1176 | previous @sc{gdb/mi} interface, included in @value{GDBN} version 5.3 and |
1177 | selected with @samp{--interpreter=mi1}, is deprecated. Earlier | |
1178 | @sc{gdb/mi} interfaces are no longer supported. | |
d700128c EZ |
1179 | |
1180 | @item -write | |
1181 | @cindex @code{--write} | |
1182 | Open the executable and core files for both reading and writing. This | |
1183 | is equivalent to the @samp{set write on} command inside @value{GDBN} | |
1184 | (@pxref{Patching}). | |
1185 | ||
1186 | @item -statistics | |
1187 | @cindex @code{--statistics} | |
1188 | This option causes @value{GDBN} to print statistics about time and | |
1189 | memory usage after it completes each command and returns to the prompt. | |
1190 | ||
1191 | @item -version | |
1192 | @cindex @code{--version} | |
1193 | This option causes @value{GDBN} to print its version number and | |
1194 | no-warranty blurb, and exit. | |
1195 | ||
c906108c SS |
1196 | @end table |
1197 | ||
6fc08d32 | 1198 | @node Startup |
79a6e687 | 1199 | @subsection What @value{GDBN} Does During Startup |
6fc08d32 EZ |
1200 | @cindex @value{GDBN} startup |
1201 | ||
1202 | Here's the description of what @value{GDBN} does during session startup: | |
1203 | ||
1204 | @enumerate | |
1205 | @item | |
1206 | Sets up the command interpreter as specified by the command line | |
1207 | (@pxref{Mode Options, interpreter}). | |
1208 | ||
1209 | @item | |
1210 | @cindex init file | |
1211 | Reads the @dfn{init file} (if any) in your home directory@footnote{On | |
1212 | DOS/Windows systems, the home directory is the one pointed to by the | |
1213 | @code{HOME} environment variable.} and executes all the commands in | |
1214 | that file. | |
1215 | ||
1216 | @item | |
1217 | Processes command line options and operands. | |
1218 | ||
1219 | @item | |
1220 | Reads and executes the commands from init file (if any) in the current | |
119b882a EZ |
1221 | working directory. This is only done if the current directory is |
1222 | different from your home directory. Thus, you can have more than one | |
1223 | init file, one generic in your home directory, and another, specific | |
1224 | to the program you are debugging, in the directory where you invoke | |
6fc08d32 EZ |
1225 | @value{GDBN}. |
1226 | ||
1227 | @item | |
1228 | Reads command files specified by the @samp{-x} option. @xref{Command | |
1229 | Files}, for more details about @value{GDBN} command files. | |
1230 | ||
1231 | @item | |
1232 | Reads the command history recorded in the @dfn{history file}. | |
d620b259 | 1233 | @xref{Command History}, for more details about the command history and the |
6fc08d32 EZ |
1234 | files where @value{GDBN} records it. |
1235 | @end enumerate | |
1236 | ||
1237 | Init files use the same syntax as @dfn{command files} (@pxref{Command | |
1238 | Files}) and are processed by @value{GDBN} in the same way. The init | |
1239 | file in your home directory can set options (such as @samp{set | |
1240 | complaints}) that affect subsequent processing of command line options | |
1241 | and operands. Init files are not executed if you use the @samp{-nx} | |
79a6e687 | 1242 | option (@pxref{Mode Options, ,Choosing Modes}). |
6fc08d32 EZ |
1243 | |
1244 | @cindex init file name | |
1245 | @cindex @file{.gdbinit} | |
119b882a | 1246 | @cindex @file{gdb.ini} |
8807d78b | 1247 | The @value{GDBN} init files are normally called @file{.gdbinit}. |
119b882a EZ |
1248 | The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to |
1249 | the limitations of file names imposed by DOS filesystems. The Windows | |
1250 | ports of @value{GDBN} use the standard name, but if they find a | |
1251 | @file{gdb.ini} file, they warn you about that and suggest to rename | |
1252 | the file to the standard name. | |
1253 | ||
6fc08d32 | 1254 | |
6d2ebf8b | 1255 | @node Quitting GDB |
c906108c SS |
1256 | @section Quitting @value{GDBN} |
1257 | @cindex exiting @value{GDBN} | |
1258 | @cindex leaving @value{GDBN} | |
1259 | ||
1260 | @table @code | |
1261 | @kindex quit @r{[}@var{expression}@r{]} | |
41afff9a | 1262 | @kindex q @r{(@code{quit})} |
96a2c332 SS |
1263 | @item quit @r{[}@var{expression}@r{]} |
1264 | @itemx q | |
1265 | To exit @value{GDBN}, use the @code{quit} command (abbreviated | |
c8aa23ab | 1266 | @code{q}), or type an end-of-file character (usually @kbd{Ctrl-d}). If you |
96a2c332 SS |
1267 | do not supply @var{expression}, @value{GDBN} will terminate normally; |
1268 | otherwise it will terminate using the result of @var{expression} as the | |
1269 | error code. | |
c906108c SS |
1270 | @end table |
1271 | ||
1272 | @cindex interrupt | |
c8aa23ab | 1273 | An interrupt (often @kbd{Ctrl-c}) does not exit from @value{GDBN}, but rather |
c906108c SS |
1274 | terminates the action of any @value{GDBN} command that is in progress and |
1275 | returns to @value{GDBN} command level. It is safe to type the interrupt | |
1276 | character at any time because @value{GDBN} does not allow it to take effect | |
1277 | until a time when it is safe. | |
1278 | ||
c906108c SS |
1279 | If you have been using @value{GDBN} to control an attached process or |
1280 | device, you can release it with the @code{detach} command | |
79a6e687 | 1281 | (@pxref{Attach, ,Debugging an Already-running Process}). |
c906108c | 1282 | |
6d2ebf8b | 1283 | @node Shell Commands |
79a6e687 | 1284 | @section Shell Commands |
c906108c SS |
1285 | |
1286 | If you need to execute occasional shell commands during your | |
1287 | debugging session, there is no need to leave or suspend @value{GDBN}; you can | |
1288 | just use the @code{shell} command. | |
1289 | ||
1290 | @table @code | |
1291 | @kindex shell | |
1292 | @cindex shell escape | |
1293 | @item shell @var{command string} | |
1294 | Invoke a standard shell to execute @var{command string}. | |
c906108c | 1295 | If it exists, the environment variable @code{SHELL} determines which |
d4f3574e SS |
1296 | shell to run. Otherwise @value{GDBN} uses the default shell |
1297 | (@file{/bin/sh} on Unix systems, @file{COMMAND.COM} on MS-DOS, etc.). | |
c906108c SS |
1298 | @end table |
1299 | ||
1300 | The utility @code{make} is often needed in development environments. | |
1301 | You do not have to use the @code{shell} command for this purpose in | |
1302 | @value{GDBN}: | |
1303 | ||
1304 | @table @code | |
1305 | @kindex make | |
1306 | @cindex calling make | |
1307 | @item make @var{make-args} | |
1308 | Execute the @code{make} program with the specified | |
1309 | arguments. This is equivalent to @samp{shell make @var{make-args}}. | |
1310 | @end table | |
1311 | ||
79a6e687 BW |
1312 | @node Logging Output |
1313 | @section Logging Output | |
0fac0b41 | 1314 | @cindex logging @value{GDBN} output |
9c16f35a | 1315 | @cindex save @value{GDBN} output to a file |
0fac0b41 DJ |
1316 | |
1317 | You may want to save the output of @value{GDBN} commands to a file. | |
1318 | There are several commands to control @value{GDBN}'s logging. | |
1319 | ||
1320 | @table @code | |
1321 | @kindex set logging | |
1322 | @item set logging on | |
1323 | Enable logging. | |
1324 | @item set logging off | |
1325 | Disable logging. | |
9c16f35a | 1326 | @cindex logging file name |
0fac0b41 DJ |
1327 | @item set logging file @var{file} |
1328 | Change the name of the current logfile. The default logfile is @file{gdb.txt}. | |
1329 | @item set logging overwrite [on|off] | |
1330 | By default, @value{GDBN} will append to the logfile. Set @code{overwrite} if | |
1331 | you want @code{set logging on} to overwrite the logfile instead. | |
1332 | @item set logging redirect [on|off] | |
1333 | By default, @value{GDBN} output will go to both the terminal and the logfile. | |
1334 | Set @code{redirect} if you want output to go only to the log file. | |
1335 | @kindex show logging | |
1336 | @item show logging | |
1337 | Show the current values of the logging settings. | |
1338 | @end table | |
1339 | ||
6d2ebf8b | 1340 | @node Commands |
c906108c SS |
1341 | @chapter @value{GDBN} Commands |
1342 | ||
1343 | You can abbreviate a @value{GDBN} command to the first few letters of the command | |
1344 | name, if that abbreviation is unambiguous; and you can repeat certain | |
1345 | @value{GDBN} commands by typing just @key{RET}. You can also use the @key{TAB} | |
1346 | key to get @value{GDBN} to fill out the rest of a word in a command (or to | |
1347 | show you the alternatives available, if there is more than one possibility). | |
1348 | ||
1349 | @menu | |
1350 | * Command Syntax:: How to give commands to @value{GDBN} | |
1351 | * Completion:: Command completion | |
1352 | * Help:: How to ask @value{GDBN} for help | |
1353 | @end menu | |
1354 | ||
6d2ebf8b | 1355 | @node Command Syntax |
79a6e687 | 1356 | @section Command Syntax |
c906108c SS |
1357 | |
1358 | A @value{GDBN} command is a single line of input. There is no limit on | |
1359 | how long it can be. It starts with a command name, which is followed by | |
1360 | arguments whose meaning depends on the command name. For example, the | |
1361 | command @code{step} accepts an argument which is the number of times to | |
1362 | step, as in @samp{step 5}. You can also use the @code{step} command | |
96a2c332 | 1363 | with no arguments. Some commands do not allow any arguments. |
c906108c SS |
1364 | |
1365 | @cindex abbreviation | |
1366 | @value{GDBN} command names may always be truncated if that abbreviation is | |
1367 | unambiguous. Other possible command abbreviations are listed in the | |
1368 | documentation for individual commands. In some cases, even ambiguous | |
1369 | abbreviations are allowed; for example, @code{s} is specially defined as | |
1370 | equivalent to @code{step} even though there are other commands whose | |
1371 | names start with @code{s}. You can test abbreviations by using them as | |
1372 | arguments to the @code{help} command. | |
1373 | ||
1374 | @cindex repeating commands | |
41afff9a | 1375 | @kindex RET @r{(repeat last command)} |
c906108c | 1376 | A blank line as input to @value{GDBN} (typing just @key{RET}) means to |
96a2c332 | 1377 | repeat the previous command. Certain commands (for example, @code{run}) |
c906108c SS |
1378 | will not repeat this way; these are commands whose unintentional |
1379 | repetition might cause trouble and which you are unlikely to want to | |
c45da7e6 EZ |
1380 | repeat. User-defined commands can disable this feature; see |
1381 | @ref{Define, dont-repeat}. | |
c906108c SS |
1382 | |
1383 | The @code{list} and @code{x} commands, when you repeat them with | |
1384 | @key{RET}, construct new arguments rather than repeating | |
1385 | exactly as typed. This permits easy scanning of source or memory. | |
1386 | ||
1387 | @value{GDBN} can also use @key{RET} in another way: to partition lengthy | |
1388 | output, in a way similar to the common utility @code{more} | |
79a6e687 | 1389 | (@pxref{Screen Size,,Screen Size}). Since it is easy to press one |
c906108c SS |
1390 | @key{RET} too many in this situation, @value{GDBN} disables command |
1391 | repetition after any command that generates this sort of display. | |
1392 | ||
41afff9a | 1393 | @kindex # @r{(a comment)} |
c906108c SS |
1394 | @cindex comment |
1395 | Any text from a @kbd{#} to the end of the line is a comment; it does | |
1396 | nothing. This is useful mainly in command files (@pxref{Command | |
79a6e687 | 1397 | Files,,Command Files}). |
c906108c | 1398 | |
88118b3a | 1399 | @cindex repeating command sequences |
c8aa23ab EZ |
1400 | @kindex Ctrl-o @r{(operate-and-get-next)} |
1401 | The @kbd{Ctrl-o} binding is useful for repeating a complex sequence of | |
7f9087cb | 1402 | commands. This command accepts the current line, like @key{RET}, and |
88118b3a TT |
1403 | then fetches the next line relative to the current line from the history |
1404 | for editing. | |
1405 | ||
6d2ebf8b | 1406 | @node Completion |
79a6e687 | 1407 | @section Command Completion |
c906108c SS |
1408 | |
1409 | @cindex completion | |
1410 | @cindex word completion | |
1411 | @value{GDBN} can fill in the rest of a word in a command for you, if there is | |
1412 | only one possibility; it can also show you what the valid possibilities | |
1413 | are for the next word in a command, at any time. This works for @value{GDBN} | |
1414 | commands, @value{GDBN} subcommands, and the names of symbols in your program. | |
1415 | ||
1416 | Press the @key{TAB} key whenever you want @value{GDBN} to fill out the rest | |
1417 | of a word. If there is only one possibility, @value{GDBN} fills in the | |
1418 | word, and waits for you to finish the command (or press @key{RET} to | |
1419 | enter it). For example, if you type | |
1420 | ||
1421 | @c FIXME "@key" does not distinguish its argument sufficiently to permit | |
1422 | @c complete accuracy in these examples; space introduced for clarity. | |
1423 | @c If texinfo enhancements make it unnecessary, it would be nice to | |
1424 | @c replace " @key" by "@key" in the following... | |
474c8240 | 1425 | @smallexample |
c906108c | 1426 | (@value{GDBP}) info bre @key{TAB} |
474c8240 | 1427 | @end smallexample |
c906108c SS |
1428 | |
1429 | @noindent | |
1430 | @value{GDBN} fills in the rest of the word @samp{breakpoints}, since that is | |
1431 | the only @code{info} subcommand beginning with @samp{bre}: | |
1432 | ||
474c8240 | 1433 | @smallexample |
c906108c | 1434 | (@value{GDBP}) info breakpoints |
474c8240 | 1435 | @end smallexample |
c906108c SS |
1436 | |
1437 | @noindent | |
1438 | You can either press @key{RET} at this point, to run the @code{info | |
1439 | breakpoints} command, or backspace and enter something else, if | |
1440 | @samp{breakpoints} does not look like the command you expected. (If you | |
1441 | were sure you wanted @code{info breakpoints} in the first place, you | |
1442 | might as well just type @key{RET} immediately after @samp{info bre}, | |
1443 | to exploit command abbreviations rather than command completion). | |
1444 | ||
1445 | If there is more than one possibility for the next word when you press | |
1446 | @key{TAB}, @value{GDBN} sounds a bell. You can either supply more | |
1447 | characters and try again, or just press @key{TAB} a second time; | |
1448 | @value{GDBN} displays all the possible completions for that word. For | |
1449 | example, you might want to set a breakpoint on a subroutine whose name | |
1450 | begins with @samp{make_}, but when you type @kbd{b make_@key{TAB}} @value{GDBN} | |
1451 | just sounds the bell. Typing @key{TAB} again displays all the | |
1452 | function names in your program that begin with those characters, for | |
1453 | example: | |
1454 | ||
474c8240 | 1455 | @smallexample |
c906108c SS |
1456 | (@value{GDBP}) b make_ @key{TAB} |
1457 | @exdent @value{GDBN} sounds bell; press @key{TAB} again, to see: | |
5d161b24 DB |
1458 | make_a_section_from_file make_environ |
1459 | make_abs_section make_function_type | |
1460 | make_blockvector make_pointer_type | |
1461 | make_cleanup make_reference_type | |
c906108c SS |
1462 | make_command make_symbol_completion_list |
1463 | (@value{GDBP}) b make_ | |
474c8240 | 1464 | @end smallexample |
c906108c SS |
1465 | |
1466 | @noindent | |
1467 | After displaying the available possibilities, @value{GDBN} copies your | |
1468 | partial input (@samp{b make_} in the example) so you can finish the | |
1469 | command. | |
1470 | ||
1471 | If you just want to see the list of alternatives in the first place, you | |
b37052ae | 1472 | can press @kbd{M-?} rather than pressing @key{TAB} twice. @kbd{M-?} |
7a292a7a | 1473 | means @kbd{@key{META} ?}. You can type this either by holding down a |
c906108c | 1474 | key designated as the @key{META} shift on your keyboard (if there is |
7a292a7a | 1475 | one) while typing @kbd{?}, or as @key{ESC} followed by @kbd{?}. |
c906108c SS |
1476 | |
1477 | @cindex quotes in commands | |
1478 | @cindex completion of quoted strings | |
1479 | Sometimes the string you need, while logically a ``word'', may contain | |
7a292a7a SS |
1480 | parentheses or other characters that @value{GDBN} normally excludes from |
1481 | its notion of a word. To permit word completion to work in this | |
1482 | situation, you may enclose words in @code{'} (single quote marks) in | |
1483 | @value{GDBN} commands. | |
c906108c | 1484 | |
c906108c | 1485 | The most likely situation where you might need this is in typing the |
b37052ae EZ |
1486 | name of a C@t{++} function. This is because C@t{++} allows function |
1487 | overloading (multiple definitions of the same function, distinguished | |
1488 | by argument type). For example, when you want to set a breakpoint you | |
1489 | may need to distinguish whether you mean the version of @code{name} | |
1490 | that takes an @code{int} parameter, @code{name(int)}, or the version | |
1491 | that takes a @code{float} parameter, @code{name(float)}. To use the | |
1492 | word-completion facilities in this situation, type a single quote | |
1493 | @code{'} at the beginning of the function name. This alerts | |
1494 | @value{GDBN} that it may need to consider more information than usual | |
1495 | when you press @key{TAB} or @kbd{M-?} to request word completion: | |
c906108c | 1496 | |
474c8240 | 1497 | @smallexample |
96a2c332 | 1498 | (@value{GDBP}) b 'bubble( @kbd{M-?} |
c906108c SS |
1499 | bubble(double,double) bubble(int,int) |
1500 | (@value{GDBP}) b 'bubble( | |
474c8240 | 1501 | @end smallexample |
c906108c SS |
1502 | |
1503 | In some cases, @value{GDBN} can tell that completing a name requires using | |
1504 | quotes. When this happens, @value{GDBN} inserts the quote for you (while | |
1505 | completing as much as it can) if you do not type the quote in the first | |
1506 | place: | |
1507 | ||
474c8240 | 1508 | @smallexample |
c906108c SS |
1509 | (@value{GDBP}) b bub @key{TAB} |
1510 | @exdent @value{GDBN} alters your input line to the following, and rings a bell: | |
1511 | (@value{GDBP}) b 'bubble( | |
474c8240 | 1512 | @end smallexample |
c906108c SS |
1513 | |
1514 | @noindent | |
1515 | In general, @value{GDBN} can tell that a quote is needed (and inserts it) if | |
1516 | you have not yet started typing the argument list when you ask for | |
1517 | completion on an overloaded symbol. | |
1518 | ||
79a6e687 BW |
1519 | For more information about overloaded functions, see @ref{C Plus Plus |
1520 | Expressions, ,C@t{++} Expressions}. You can use the command @code{set | |
c906108c | 1521 | overload-resolution off} to disable overload resolution; |
79a6e687 | 1522 | see @ref{Debugging C Plus Plus, ,@value{GDBN} Features for C@t{++}}. |
c906108c SS |
1523 | |
1524 | ||
6d2ebf8b | 1525 | @node Help |
79a6e687 | 1526 | @section Getting Help |
c906108c SS |
1527 | @cindex online documentation |
1528 | @kindex help | |
1529 | ||
5d161b24 | 1530 | You can always ask @value{GDBN} itself for information on its commands, |
c906108c SS |
1531 | using the command @code{help}. |
1532 | ||
1533 | @table @code | |
41afff9a | 1534 | @kindex h @r{(@code{help})} |
c906108c SS |
1535 | @item help |
1536 | @itemx h | |
1537 | You can use @code{help} (abbreviated @code{h}) with no arguments to | |
1538 | display a short list of named classes of commands: | |
1539 | ||
1540 | @smallexample | |
1541 | (@value{GDBP}) help | |
1542 | List of classes of commands: | |
1543 | ||
2df3850c | 1544 | aliases -- Aliases of other commands |
c906108c | 1545 | breakpoints -- Making program stop at certain points |
2df3850c | 1546 | data -- Examining data |
c906108c | 1547 | files -- Specifying and examining files |
2df3850c JM |
1548 | internals -- Maintenance commands |
1549 | obscure -- Obscure features | |
1550 | running -- Running the program | |
1551 | stack -- Examining the stack | |
c906108c SS |
1552 | status -- Status inquiries |
1553 | support -- Support facilities | |
12c27660 | 1554 | tracepoints -- Tracing of program execution without |
96a2c332 | 1555 | stopping the program |
c906108c | 1556 | user-defined -- User-defined commands |
c906108c | 1557 | |
5d161b24 | 1558 | Type "help" followed by a class name for a list of |
c906108c | 1559 | commands in that class. |
5d161b24 | 1560 | Type "help" followed by command name for full |
c906108c SS |
1561 | documentation. |
1562 | Command name abbreviations are allowed if unambiguous. | |
1563 | (@value{GDBP}) | |
1564 | @end smallexample | |
96a2c332 | 1565 | @c the above line break eliminates huge line overfull... |
c906108c SS |
1566 | |
1567 | @item help @var{class} | |
1568 | Using one of the general help classes as an argument, you can get a | |
1569 | list of the individual commands in that class. For example, here is the | |
1570 | help display for the class @code{status}: | |
1571 | ||
1572 | @smallexample | |
1573 | (@value{GDBP}) help status | |
1574 | Status inquiries. | |
1575 | ||
1576 | List of commands: | |
1577 | ||
1578 | @c Line break in "show" line falsifies real output, but needed | |
1579 | @c to fit in smallbook page size. | |
2df3850c | 1580 | info -- Generic command for showing things |
12c27660 | 1581 | about the program being debugged |
2df3850c | 1582 | show -- Generic command for showing things |
12c27660 | 1583 | about the debugger |
c906108c | 1584 | |
5d161b24 | 1585 | Type "help" followed by command name for full |
c906108c SS |
1586 | documentation. |
1587 | Command name abbreviations are allowed if unambiguous. | |
1588 | (@value{GDBP}) | |
1589 | @end smallexample | |
1590 | ||
1591 | @item help @var{command} | |
1592 | With a command name as @code{help} argument, @value{GDBN} displays a | |
1593 | short paragraph on how to use that command. | |
1594 | ||
6837a0a2 DB |
1595 | @kindex apropos |
1596 | @item apropos @var{args} | |
09d4efe1 | 1597 | The @code{apropos} command searches through all of the @value{GDBN} |
6837a0a2 DB |
1598 | commands, and their documentation, for the regular expression specified in |
1599 | @var{args}. It prints out all matches found. For example: | |
1600 | ||
1601 | @smallexample | |
1602 | apropos reload | |
1603 | @end smallexample | |
1604 | ||
b37052ae EZ |
1605 | @noindent |
1606 | results in: | |
6837a0a2 DB |
1607 | |
1608 | @smallexample | |
6d2ebf8b SS |
1609 | @c @group |
1610 | set symbol-reloading -- Set dynamic symbol table reloading | |
12c27660 | 1611 | multiple times in one run |
6d2ebf8b | 1612 | show symbol-reloading -- Show dynamic symbol table reloading |
12c27660 | 1613 | multiple times in one run |
6d2ebf8b | 1614 | @c @end group |
6837a0a2 DB |
1615 | @end smallexample |
1616 | ||
c906108c SS |
1617 | @kindex complete |
1618 | @item complete @var{args} | |
1619 | The @code{complete @var{args}} command lists all the possible completions | |
1620 | for the beginning of a command. Use @var{args} to specify the beginning of the | |
1621 | command you want completed. For example: | |
1622 | ||
1623 | @smallexample | |
1624 | complete i | |
1625 | @end smallexample | |
1626 | ||
1627 | @noindent results in: | |
1628 | ||
1629 | @smallexample | |
1630 | @group | |
2df3850c JM |
1631 | if |
1632 | ignore | |
c906108c SS |
1633 | info |
1634 | inspect | |
c906108c SS |
1635 | @end group |
1636 | @end smallexample | |
1637 | ||
1638 | @noindent This is intended for use by @sc{gnu} Emacs. | |
1639 | @end table | |
1640 | ||
1641 | In addition to @code{help}, you can use the @value{GDBN} commands @code{info} | |
1642 | and @code{show} to inquire about the state of your program, or the state | |
1643 | of @value{GDBN} itself. Each command supports many topics of inquiry; this | |
1644 | manual introduces each of them in the appropriate context. The listings | |
1645 | under @code{info} and under @code{show} in the Index point to | |
1646 | all the sub-commands. @xref{Index}. | |
1647 | ||
1648 | @c @group | |
1649 | @table @code | |
1650 | @kindex info | |
41afff9a | 1651 | @kindex i @r{(@code{info})} |
c906108c SS |
1652 | @item info |
1653 | This command (abbreviated @code{i}) is for describing the state of your | |
cda4ce5a | 1654 | program. For example, you can show the arguments passed to a function |
c906108c SS |
1655 | with @code{info args}, list the registers currently in use with @code{info |
1656 | registers}, or list the breakpoints you have set with @code{info breakpoints}. | |
1657 | You can get a complete list of the @code{info} sub-commands with | |
1658 | @w{@code{help info}}. | |
1659 | ||
1660 | @kindex set | |
1661 | @item set | |
5d161b24 | 1662 | You can assign the result of an expression to an environment variable with |
c906108c SS |
1663 | @code{set}. For example, you can set the @value{GDBN} prompt to a $-sign with |
1664 | @code{set prompt $}. | |
1665 | ||
1666 | @kindex show | |
1667 | @item show | |
5d161b24 | 1668 | In contrast to @code{info}, @code{show} is for describing the state of |
c906108c SS |
1669 | @value{GDBN} itself. |
1670 | You can change most of the things you can @code{show}, by using the | |
1671 | related command @code{set}; for example, you can control what number | |
1672 | system is used for displays with @code{set radix}, or simply inquire | |
1673 | which is currently in use with @code{show radix}. | |
1674 | ||
1675 | @kindex info set | |
1676 | To display all the settable parameters and their current | |
1677 | values, you can use @code{show} with no arguments; you may also use | |
1678 | @code{info set}. Both commands produce the same display. | |
1679 | @c FIXME: "info set" violates the rule that "info" is for state of | |
1680 | @c FIXME...program. Ck w/ GNU: "info set" to be called something else, | |
1681 | @c FIXME...or change desc of rule---eg "state of prog and debugging session"? | |
1682 | @end table | |
1683 | @c @end group | |
1684 | ||
1685 | Here are three miscellaneous @code{show} subcommands, all of which are | |
1686 | exceptional in lacking corresponding @code{set} commands: | |
1687 | ||
1688 | @table @code | |
1689 | @kindex show version | |
9c16f35a | 1690 | @cindex @value{GDBN} version number |
c906108c SS |
1691 | @item show version |
1692 | Show what version of @value{GDBN} is running. You should include this | |
2df3850c JM |
1693 | information in @value{GDBN} bug-reports. If multiple versions of |
1694 | @value{GDBN} are in use at your site, you may need to determine which | |
1695 | version of @value{GDBN} you are running; as @value{GDBN} evolves, new | |
1696 | commands are introduced, and old ones may wither away. Also, many | |
1697 | system vendors ship variant versions of @value{GDBN}, and there are | |
96a2c332 | 1698 | variant versions of @value{GDBN} in @sc{gnu}/Linux distributions as well. |
2df3850c JM |
1699 | The version number is the same as the one announced when you start |
1700 | @value{GDBN}. | |
c906108c SS |
1701 | |
1702 | @kindex show copying | |
09d4efe1 | 1703 | @kindex info copying |
9c16f35a | 1704 | @cindex display @value{GDBN} copyright |
c906108c | 1705 | @item show copying |
09d4efe1 | 1706 | @itemx info copying |
c906108c SS |
1707 | Display information about permission for copying @value{GDBN}. |
1708 | ||
1709 | @kindex show warranty | |
09d4efe1 | 1710 | @kindex info warranty |
c906108c | 1711 | @item show warranty |
09d4efe1 | 1712 | @itemx info warranty |
2df3850c | 1713 | Display the @sc{gnu} ``NO WARRANTY'' statement, or a warranty, |
96a2c332 | 1714 | if your version of @value{GDBN} comes with one. |
2df3850c | 1715 | |
c906108c SS |
1716 | @end table |
1717 | ||
6d2ebf8b | 1718 | @node Running |
c906108c SS |
1719 | @chapter Running Programs Under @value{GDBN} |
1720 | ||
1721 | When you run a program under @value{GDBN}, you must first generate | |
1722 | debugging information when you compile it. | |
7a292a7a SS |
1723 | |
1724 | You may start @value{GDBN} with its arguments, if any, in an environment | |
1725 | of your choice. If you are doing native debugging, you may redirect | |
1726 | your program's input and output, debug an already running process, or | |
1727 | kill a child process. | |
c906108c SS |
1728 | |
1729 | @menu | |
1730 | * Compilation:: Compiling for debugging | |
1731 | * Starting:: Starting your program | |
c906108c SS |
1732 | * Arguments:: Your program's arguments |
1733 | * Environment:: Your program's environment | |
c906108c SS |
1734 | |
1735 | * Working Directory:: Your program's working directory | |
1736 | * Input/Output:: Your program's input and output | |
1737 | * Attach:: Debugging an already-running process | |
1738 | * Kill Process:: Killing the child process | |
c906108c SS |
1739 | |
1740 | * Threads:: Debugging programs with multiple threads | |
1741 | * Processes:: Debugging programs with multiple processes | |
5c95884b | 1742 | * Checkpoint/Restart:: Setting a @emph{bookmark} to return to later |
c906108c SS |
1743 | @end menu |
1744 | ||
6d2ebf8b | 1745 | @node Compilation |
79a6e687 | 1746 | @section Compiling for Debugging |
c906108c SS |
1747 | |
1748 | In order to debug a program effectively, you need to generate | |
1749 | debugging information when you compile it. This debugging information | |
1750 | is stored in the object file; it describes the data type of each | |
1751 | variable or function and the correspondence between source line numbers | |
1752 | and addresses in the executable code. | |
1753 | ||
1754 | To request debugging information, specify the @samp{-g} option when you run | |
1755 | the compiler. | |
1756 | ||
514c4d71 EZ |
1757 | Programs that are to be shipped to your customers are compiled with |
1758 | optimizations, using the @samp{-O} compiler option. However, many | |
1759 | compilers are unable to handle the @samp{-g} and @samp{-O} options | |
1760 | together. Using those compilers, you cannot generate optimized | |
c906108c SS |
1761 | executables containing debugging information. |
1762 | ||
514c4d71 | 1763 | @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, supports @samp{-g} with or |
53a5351d JM |
1764 | without @samp{-O}, making it possible to debug optimized code. We |
1765 | recommend that you @emph{always} use @samp{-g} whenever you compile a | |
1766 | program. You may think your program is correct, but there is no sense | |
1767 | in pushing your luck. | |
c906108c SS |
1768 | |
1769 | @cindex optimized code, debugging | |
1770 | @cindex debugging optimized code | |
1771 | When you debug a program compiled with @samp{-g -O}, remember that the | |
1772 | optimizer is rearranging your code; the debugger shows you what is | |
1773 | really there. Do not be too surprised when the execution path does not | |
1774 | exactly match your source file! An extreme example: if you define a | |
1775 | variable, but never use it, @value{GDBN} never sees that | |
1776 | variable---because the compiler optimizes it out of existence. | |
1777 | ||
1778 | Some things do not work as well with @samp{-g -O} as with just | |
1779 | @samp{-g}, particularly on machines with instruction scheduling. If in | |
1780 | doubt, recompile with @samp{-g} alone, and if this fixes the problem, | |
1781 | please report it to us as a bug (including a test case!). | |
15387254 | 1782 | @xref{Variables}, for more information about debugging optimized code. |
c906108c SS |
1783 | |
1784 | Older versions of the @sc{gnu} C compiler permitted a variant option | |
1785 | @w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this | |
1786 | format; if your @sc{gnu} C compiler has this option, do not use it. | |
1787 | ||
514c4d71 EZ |
1788 | @value{GDBN} knows about preprocessor macros and can show you their |
1789 | expansion (@pxref{Macros}). Most compilers do not include information | |
1790 | about preprocessor macros in the debugging information if you specify | |
1791 | the @option{-g} flag alone, because this information is rather large. | |
1792 | Version 3.1 and later of @value{NGCC}, the @sc{gnu} C compiler, | |
1793 | provides macro information if you specify the options | |
1794 | @option{-gdwarf-2} and @option{-g3}; the former option requests | |
1795 | debugging information in the Dwarf 2 format, and the latter requests | |
1796 | ``extra information''. In the future, we hope to find more compact | |
1797 | ways to represent macro information, so that it can be included with | |
1798 | @option{-g} alone. | |
1799 | ||
c906108c | 1800 | @need 2000 |
6d2ebf8b | 1801 | @node Starting |
79a6e687 | 1802 | @section Starting your Program |
c906108c SS |
1803 | @cindex starting |
1804 | @cindex running | |
1805 | ||
1806 | @table @code | |
1807 | @kindex run | |
41afff9a | 1808 | @kindex r @r{(@code{run})} |
c906108c SS |
1809 | @item run |
1810 | @itemx r | |
7a292a7a SS |
1811 | Use the @code{run} command to start your program under @value{GDBN}. |
1812 | You must first specify the program name (except on VxWorks) with an | |
1813 | argument to @value{GDBN} (@pxref{Invocation, ,Getting In and Out of | |
1814 | @value{GDBN}}), or by using the @code{file} or @code{exec-file} command | |
79a6e687 | 1815 | (@pxref{Files, ,Commands to Specify Files}). |
c906108c SS |
1816 | |
1817 | @end table | |
1818 | ||
c906108c SS |
1819 | If you are running your program in an execution environment that |
1820 | supports processes, @code{run} creates an inferior process and makes | |
8edfe269 DJ |
1821 | that process run your program. In some environments without processes, |
1822 | @code{run} jumps to the start of your program. Other targets, | |
1823 | like @samp{remote}, are always running. If you get an error | |
1824 | message like this one: | |
1825 | ||
1826 | @smallexample | |
1827 | The "remote" target does not support "run". | |
1828 | Try "help target" or "continue". | |
1829 | @end smallexample | |
1830 | ||
1831 | @noindent | |
1832 | then use @code{continue} to run your program. You may need @code{load} | |
1833 | first (@pxref{load}). | |
c906108c SS |
1834 | |
1835 | The execution of a program is affected by certain information it | |
1836 | receives from its superior. @value{GDBN} provides ways to specify this | |
1837 | information, which you must do @emph{before} starting your program. (You | |
1838 | can change it after starting your program, but such changes only affect | |
1839 | your program the next time you start it.) This information may be | |
1840 | divided into four categories: | |
1841 | ||
1842 | @table @asis | |
1843 | @item The @emph{arguments.} | |
1844 | Specify the arguments to give your program as the arguments of the | |
1845 | @code{run} command. If a shell is available on your target, the shell | |
1846 | is used to pass the arguments, so that you may use normal conventions | |
1847 | (such as wildcard expansion or variable substitution) in describing | |
1848 | the arguments. | |
1849 | In Unix systems, you can control which shell is used with the | |
1850 | @code{SHELL} environment variable. | |
79a6e687 | 1851 | @xref{Arguments, ,Your Program's Arguments}. |
c906108c SS |
1852 | |
1853 | @item The @emph{environment.} | |
1854 | Your program normally inherits its environment from @value{GDBN}, but you can | |
1855 | use the @value{GDBN} commands @code{set environment} and @code{unset | |
1856 | environment} to change parts of the environment that affect | |
79a6e687 | 1857 | your program. @xref{Environment, ,Your Program's Environment}. |
c906108c SS |
1858 | |
1859 | @item The @emph{working directory.} | |
1860 | Your program inherits its working directory from @value{GDBN}. You can set | |
1861 | the @value{GDBN} working directory with the @code{cd} command in @value{GDBN}. | |
79a6e687 | 1862 | @xref{Working Directory, ,Your Program's Working Directory}. |
c906108c SS |
1863 | |
1864 | @item The @emph{standard input and output.} | |
1865 | Your program normally uses the same device for standard input and | |
1866 | standard output as @value{GDBN} is using. You can redirect input and output | |
1867 | in the @code{run} command line, or you can use the @code{tty} command to | |
1868 | set a different device for your program. | |
79a6e687 | 1869 | @xref{Input/Output, ,Your Program's Input and Output}. |
c906108c SS |
1870 | |
1871 | @cindex pipes | |
1872 | @emph{Warning:} While input and output redirection work, you cannot use | |
1873 | pipes to pass the output of the program you are debugging to another | |
1874 | program; if you attempt this, @value{GDBN} is likely to wind up debugging the | |
1875 | wrong program. | |
1876 | @end table | |
c906108c SS |
1877 | |
1878 | When you issue the @code{run} command, your program begins to execute | |
79a6e687 | 1879 | immediately. @xref{Stopping, ,Stopping and Continuing}, for discussion |
c906108c SS |
1880 | of how to arrange for your program to stop. Once your program has |
1881 | stopped, you may call functions in your program, using the @code{print} | |
1882 | or @code{call} commands. @xref{Data, ,Examining Data}. | |
1883 | ||
1884 | If the modification time of your symbol file has changed since the last | |
1885 | time @value{GDBN} read its symbols, @value{GDBN} discards its symbol | |
1886 | table, and reads it again. When it does this, @value{GDBN} tries to retain | |
1887 | your current breakpoints. | |
1888 | ||
4e8b0763 JB |
1889 | @table @code |
1890 | @kindex start | |
1891 | @item start | |
1892 | @cindex run to main procedure | |
1893 | The name of the main procedure can vary from language to language. | |
1894 | With C or C@t{++}, the main procedure name is always @code{main}, but | |
1895 | other languages such as Ada do not require a specific name for their | |
1896 | main procedure. The debugger provides a convenient way to start the | |
1897 | execution of the program and to stop at the beginning of the main | |
1898 | procedure, depending on the language used. | |
1899 | ||
1900 | The @samp{start} command does the equivalent of setting a temporary | |
1901 | breakpoint at the beginning of the main procedure and then invoking | |
1902 | the @samp{run} command. | |
1903 | ||
f018e82f EZ |
1904 | @cindex elaboration phase |
1905 | Some programs contain an @dfn{elaboration} phase where some startup code is | |
1906 | executed before the main procedure is called. This depends on the | |
1907 | languages used to write your program. In C@t{++}, for instance, | |
4e8b0763 JB |
1908 | constructors for static and global objects are executed before |
1909 | @code{main} is called. It is therefore possible that the debugger stops | |
1910 | before reaching the main procedure. However, the temporary breakpoint | |
1911 | will remain to halt execution. | |
1912 | ||
1913 | Specify the arguments to give to your program as arguments to the | |
1914 | @samp{start} command. These arguments will be given verbatim to the | |
1915 | underlying @samp{run} command. Note that the same arguments will be | |
1916 | reused if no argument is provided during subsequent calls to | |
1917 | @samp{start} or @samp{run}. | |
1918 | ||
1919 | It is sometimes necessary to debug the program during elaboration. In | |
1920 | these cases, using the @code{start} command would stop the execution of | |
1921 | your program too late, as the program would have already completed the | |
1922 | elaboration phase. Under these circumstances, insert breakpoints in your | |
1923 | elaboration code before running your program. | |
ccd213ac DJ |
1924 | |
1925 | @kindex set exec-wrapper | |
1926 | @item set exec-wrapper @var{wrapper} | |
1927 | @itemx show exec-wrapper | |
1928 | @itemx unset exec-wrapper | |
1929 | When @samp{exec-wrapper} is set, the specified wrapper is used to | |
1930 | launch programs for debugging. @value{GDBN} starts your program | |
1931 | with a shell command of the form @kbd{exec @var{wrapper} | |
1932 | @var{program}}. Quoting is added to @var{program} and its | |
1933 | arguments, but not to @var{wrapper}, so you should add quotes if | |
1934 | appropriate for your shell. The wrapper runs until it executes | |
1935 | your program, and then @value{GDBN} takes control. | |
1936 | ||
1937 | You can use any program that eventually calls @code{execve} with | |
1938 | its arguments as a wrapper. Several standard Unix utilities do | |
1939 | this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending | |
1940 | with @code{exec "$@@"} will also work. | |
1941 | ||
1942 | For example, you can use @code{env} to pass an environment variable to | |
1943 | the debugged program, without setting the variable in your shell's | |
1944 | environment: | |
1945 | ||
1946 | @smallexample | |
1947 | (@value{GDBP}) set exec-wrapper env 'LD_PRELOAD=libtest.so' | |
1948 | (@value{GDBP}) run | |
1949 | @end smallexample | |
1950 | ||
1951 | This command is available when debugging locally on most targets, excluding | |
1952 | @sc{djgpp}, Cygwin, MS Windows, and QNX Neutrino. | |
1953 | ||
4e8b0763 JB |
1954 | @end table |
1955 | ||
6d2ebf8b | 1956 | @node Arguments |
79a6e687 | 1957 | @section Your Program's Arguments |
c906108c SS |
1958 | |
1959 | @cindex arguments (to your program) | |
1960 | The arguments to your program can be specified by the arguments of the | |
5d161b24 | 1961 | @code{run} command. |
c906108c SS |
1962 | They are passed to a shell, which expands wildcard characters and |
1963 | performs redirection of I/O, and thence to your program. Your | |
1964 | @code{SHELL} environment variable (if it exists) specifies what shell | |
1965 | @value{GDBN} uses. If you do not define @code{SHELL}, @value{GDBN} uses | |
d4f3574e SS |
1966 | the default shell (@file{/bin/sh} on Unix). |
1967 | ||
1968 | On non-Unix systems, the program is usually invoked directly by | |
1969 | @value{GDBN}, which emulates I/O redirection via the appropriate system | |
1970 | calls, and the wildcard characters are expanded by the startup code of | |
1971 | the program, not by the shell. | |
c906108c SS |
1972 | |
1973 | @code{run} with no arguments uses the same arguments used by the previous | |
1974 | @code{run}, or those set by the @code{set args} command. | |
1975 | ||
c906108c | 1976 | @table @code |
41afff9a | 1977 | @kindex set args |
c906108c SS |
1978 | @item set args |
1979 | Specify the arguments to be used the next time your program is run. If | |
1980 | @code{set args} has no arguments, @code{run} executes your program | |
1981 | with no arguments. Once you have run your program with arguments, | |
1982 | using @code{set args} before the next @code{run} is the only way to run | |
1983 | it again without arguments. | |
1984 | ||
1985 | @kindex show args | |
1986 | @item show args | |
1987 | Show the arguments to give your program when it is started. | |
1988 | @end table | |
1989 | ||
6d2ebf8b | 1990 | @node Environment |
79a6e687 | 1991 | @section Your Program's Environment |
c906108c SS |
1992 | |
1993 | @cindex environment (of your program) | |
1994 | The @dfn{environment} consists of a set of environment variables and | |
1995 | their values. Environment variables conventionally record such things as | |
1996 | your user name, your home directory, your terminal type, and your search | |
1997 | path for programs to run. Usually you set up environment variables with | |
1998 | the shell and they are inherited by all the other programs you run. When | |
1999 | debugging, it can be useful to try running your program with a modified | |
2000 | environment without having to start @value{GDBN} over again. | |
2001 | ||
2002 | @table @code | |
2003 | @kindex path | |
2004 | @item path @var{directory} | |
2005 | Add @var{directory} to the front of the @code{PATH} environment variable | |
17cc6a06 EZ |
2006 | (the search path for executables) that will be passed to your program. |
2007 | The value of @code{PATH} used by @value{GDBN} does not change. | |
d4f3574e SS |
2008 | You may specify several directory names, separated by whitespace or by a |
2009 | system-dependent separator character (@samp{:} on Unix, @samp{;} on | |
2010 | MS-DOS and MS-Windows). If @var{directory} is already in the path, it | |
2011 | is moved to the front, so it is searched sooner. | |
c906108c SS |
2012 | |
2013 | You can use the string @samp{$cwd} to refer to whatever is the current | |
2014 | working directory at the time @value{GDBN} searches the path. If you | |
2015 | use @samp{.} instead, it refers to the directory where you executed the | |
2016 | @code{path} command. @value{GDBN} replaces @samp{.} in the | |
2017 | @var{directory} argument (with the current path) before adding | |
2018 | @var{directory} to the search path. | |
2019 | @c 'path' is explicitly nonrepeatable, but RMS points out it is silly to | |
2020 | @c document that, since repeating it would be a no-op. | |
2021 | ||
2022 | @kindex show paths | |
2023 | @item show paths | |
2024 | Display the list of search paths for executables (the @code{PATH} | |
2025 | environment variable). | |
2026 | ||
2027 | @kindex show environment | |
2028 | @item show environment @r{[}@var{varname}@r{]} | |
2029 | Print the value of environment variable @var{varname} to be given to | |
2030 | your program when it starts. If you do not supply @var{varname}, | |
2031 | print the names and values of all environment variables to be given to | |
2032 | your program. You can abbreviate @code{environment} as @code{env}. | |
2033 | ||
2034 | @kindex set environment | |
53a5351d | 2035 | @item set environment @var{varname} @r{[}=@var{value}@r{]} |
c906108c SS |
2036 | Set environment variable @var{varname} to @var{value}. The value |
2037 | changes for your program only, not for @value{GDBN} itself. @var{value} may | |
2038 | be any string; the values of environment variables are just strings, and | |
2039 | any interpretation is supplied by your program itself. The @var{value} | |
2040 | parameter is optional; if it is eliminated, the variable is set to a | |
2041 | null value. | |
2042 | @c "any string" here does not include leading, trailing | |
2043 | @c blanks. Gnu asks: does anyone care? | |
2044 | ||
2045 | For example, this command: | |
2046 | ||
474c8240 | 2047 | @smallexample |
c906108c | 2048 | set env USER = foo |
474c8240 | 2049 | @end smallexample |
c906108c SS |
2050 | |
2051 | @noindent | |
d4f3574e | 2052 | tells the debugged program, when subsequently run, that its user is named |
c906108c SS |
2053 | @samp{foo}. (The spaces around @samp{=} are used for clarity here; they |
2054 | are not actually required.) | |
2055 | ||
2056 | @kindex unset environment | |
2057 | @item unset environment @var{varname} | |
2058 | Remove variable @var{varname} from the environment to be passed to your | |
2059 | program. This is different from @samp{set env @var{varname} =}; | |
2060 | @code{unset environment} removes the variable from the environment, | |
2061 | rather than assigning it an empty value. | |
2062 | @end table | |
2063 | ||
d4f3574e SS |
2064 | @emph{Warning:} On Unix systems, @value{GDBN} runs your program using |
2065 | the shell indicated | |
c906108c SS |
2066 | by your @code{SHELL} environment variable if it exists (or |
2067 | @code{/bin/sh} if not). If your @code{SHELL} variable names a shell | |
2068 | that runs an initialization file---such as @file{.cshrc} for C-shell, or | |
2069 | @file{.bashrc} for BASH---any variables you set in that file affect | |
2070 | your program. You may wish to move setting of environment variables to | |
2071 | files that are only run when you sign on, such as @file{.login} or | |
2072 | @file{.profile}. | |
2073 | ||
6d2ebf8b | 2074 | @node Working Directory |
79a6e687 | 2075 | @section Your Program's Working Directory |
c906108c SS |
2076 | |
2077 | @cindex working directory (of your program) | |
2078 | Each time you start your program with @code{run}, it inherits its | |
2079 | working directory from the current working directory of @value{GDBN}. | |
2080 | The @value{GDBN} working directory is initially whatever it inherited | |
2081 | from its parent process (typically the shell), but you can specify a new | |
2082 | working directory in @value{GDBN} with the @code{cd} command. | |
2083 | ||
2084 | The @value{GDBN} working directory also serves as a default for the commands | |
2085 | that specify files for @value{GDBN} to operate on. @xref{Files, ,Commands to | |
79a6e687 | 2086 | Specify Files}. |
c906108c SS |
2087 | |
2088 | @table @code | |
2089 | @kindex cd | |
721c2651 | 2090 | @cindex change working directory |
c906108c SS |
2091 | @item cd @var{directory} |
2092 | Set the @value{GDBN} working directory to @var{directory}. | |
2093 | ||
2094 | @kindex pwd | |
2095 | @item pwd | |
2096 | Print the @value{GDBN} working directory. | |
2097 | @end table | |
2098 | ||
60bf7e09 EZ |
2099 | It is generally impossible to find the current working directory of |
2100 | the process being debugged (since a program can change its directory | |
2101 | during its run). If you work on a system where @value{GDBN} is | |
2102 | configured with the @file{/proc} support, you can use the @code{info | |
2103 | proc} command (@pxref{SVR4 Process Information}) to find out the | |
2104 | current working directory of the debuggee. | |
2105 | ||
6d2ebf8b | 2106 | @node Input/Output |
79a6e687 | 2107 | @section Your Program's Input and Output |
c906108c SS |
2108 | |
2109 | @cindex redirection | |
2110 | @cindex i/o | |
2111 | @cindex terminal | |
2112 | By default, the program you run under @value{GDBN} does input and output to | |
5d161b24 | 2113 | the same terminal that @value{GDBN} uses. @value{GDBN} switches the terminal |
c906108c SS |
2114 | to its own terminal modes to interact with you, but it records the terminal |
2115 | modes your program was using and switches back to them when you continue | |
2116 | running your program. | |
2117 | ||
2118 | @table @code | |
2119 | @kindex info terminal | |
2120 | @item info terminal | |
2121 | Displays information recorded by @value{GDBN} about the terminal modes your | |
2122 | program is using. | |
2123 | @end table | |
2124 | ||
2125 | You can redirect your program's input and/or output using shell | |
2126 | redirection with the @code{run} command. For example, | |
2127 | ||
474c8240 | 2128 | @smallexample |
c906108c | 2129 | run > outfile |
474c8240 | 2130 | @end smallexample |
c906108c SS |
2131 | |
2132 | @noindent | |
2133 | starts your program, diverting its output to the file @file{outfile}. | |
2134 | ||
2135 | @kindex tty | |
2136 | @cindex controlling terminal | |
2137 | Another way to specify where your program should do input and output is | |
2138 | with the @code{tty} command. This command accepts a file name as | |
2139 | argument, and causes this file to be the default for future @code{run} | |
2140 | commands. It also resets the controlling terminal for the child | |
2141 | process, for future @code{run} commands. For example, | |
2142 | ||
474c8240 | 2143 | @smallexample |
c906108c | 2144 | tty /dev/ttyb |
474c8240 | 2145 | @end smallexample |
c906108c SS |
2146 | |
2147 | @noindent | |
2148 | directs that processes started with subsequent @code{run} commands | |
2149 | default to do input and output on the terminal @file{/dev/ttyb} and have | |
2150 | that as their controlling terminal. | |
2151 | ||
2152 | An explicit redirection in @code{run} overrides the @code{tty} command's | |
2153 | effect on the input/output device, but not its effect on the controlling | |
2154 | terminal. | |
2155 | ||
2156 | When you use the @code{tty} command or redirect input in the @code{run} | |
2157 | command, only the input @emph{for your program} is affected. The input | |
3cb3b8df BR |
2158 | for @value{GDBN} still comes from your terminal. @code{tty} is an alias |
2159 | for @code{set inferior-tty}. | |
2160 | ||
2161 | @cindex inferior tty | |
2162 | @cindex set inferior controlling terminal | |
2163 | You can use the @code{show inferior-tty} command to tell @value{GDBN} to | |
2164 | display the name of the terminal that will be used for future runs of your | |
2165 | program. | |
2166 | ||
2167 | @table @code | |
2168 | @item set inferior-tty /dev/ttyb | |
2169 | @kindex set inferior-tty | |
2170 | Set the tty for the program being debugged to /dev/ttyb. | |
2171 | ||
2172 | @item show inferior-tty | |
2173 | @kindex show inferior-tty | |
2174 | Show the current tty for the program being debugged. | |
2175 | @end table | |
c906108c | 2176 | |
6d2ebf8b | 2177 | @node Attach |
79a6e687 | 2178 | @section Debugging an Already-running Process |
c906108c SS |
2179 | @kindex attach |
2180 | @cindex attach | |
2181 | ||
2182 | @table @code | |
2183 | @item attach @var{process-id} | |
2184 | This command attaches to a running process---one that was started | |
2185 | outside @value{GDBN}. (@code{info files} shows your active | |
2186 | targets.) The command takes as argument a process ID. The usual way to | |
09d4efe1 | 2187 | find out the @var{process-id} of a Unix process is with the @code{ps} utility, |
c906108c SS |
2188 | or with the @samp{jobs -l} shell command. |
2189 | ||
2190 | @code{attach} does not repeat if you press @key{RET} a second time after | |
2191 | executing the command. | |
2192 | @end table | |
2193 | ||
2194 | To use @code{attach}, your program must be running in an environment | |
2195 | which supports processes; for example, @code{attach} does not work for | |
2196 | programs on bare-board targets that lack an operating system. You must | |
2197 | also have permission to send the process a signal. | |
2198 | ||
2199 | When you use @code{attach}, the debugger finds the program running in | |
2200 | the process first by looking in the current working directory, then (if | |
2201 | the program is not found) by using the source file search path | |
79a6e687 | 2202 | (@pxref{Source Path, ,Specifying Source Directories}). You can also use |
c906108c SS |
2203 | the @code{file} command to load the program. @xref{Files, ,Commands to |
2204 | Specify Files}. | |
2205 | ||
2206 | The first thing @value{GDBN} does after arranging to debug the specified | |
2207 | process is to stop it. You can examine and modify an attached process | |
53a5351d JM |
2208 | with all the @value{GDBN} commands that are ordinarily available when |
2209 | you start processes with @code{run}. You can insert breakpoints; you | |
2210 | can step and continue; you can modify storage. If you would rather the | |
2211 | process continue running, you may use the @code{continue} command after | |
c906108c SS |
2212 | attaching @value{GDBN} to the process. |
2213 | ||
2214 | @table @code | |
2215 | @kindex detach | |
2216 | @item detach | |
2217 | When you have finished debugging the attached process, you can use the | |
2218 | @code{detach} command to release it from @value{GDBN} control. Detaching | |
2219 | the process continues its execution. After the @code{detach} command, | |
2220 | that process and @value{GDBN} become completely independent once more, and you | |
2221 | are ready to @code{attach} another process or start one with @code{run}. | |
2222 | @code{detach} does not repeat if you press @key{RET} again after | |
2223 | executing the command. | |
2224 | @end table | |
2225 | ||
159fcc13 JK |
2226 | If you exit @value{GDBN} while you have an attached process, you detach |
2227 | that process. If you use the @code{run} command, you kill that process. | |
2228 | By default, @value{GDBN} asks for confirmation if you try to do either of these | |
2229 | things; you can control whether or not you need to confirm by using the | |
2230 | @code{set confirm} command (@pxref{Messages/Warnings, ,Optional Warnings and | |
79a6e687 | 2231 | Messages}). |
c906108c | 2232 | |
6d2ebf8b | 2233 | @node Kill Process |
79a6e687 | 2234 | @section Killing the Child Process |
c906108c SS |
2235 | |
2236 | @table @code | |
2237 | @kindex kill | |
2238 | @item kill | |
2239 | Kill the child process in which your program is running under @value{GDBN}. | |
2240 | @end table | |
2241 | ||
2242 | This command is useful if you wish to debug a core dump instead of a | |
2243 | running process. @value{GDBN} ignores any core dump file while your program | |
2244 | is running. | |
2245 | ||
2246 | On some operating systems, a program cannot be executed outside @value{GDBN} | |
2247 | while you have breakpoints set on it inside @value{GDBN}. You can use the | |
2248 | @code{kill} command in this situation to permit running your program | |
2249 | outside the debugger. | |
2250 | ||
2251 | The @code{kill} command is also useful if you wish to recompile and | |
2252 | relink your program, since on many systems it is impossible to modify an | |
2253 | executable file while it is running in a process. In this case, when you | |
2254 | next type @code{run}, @value{GDBN} notices that the file has changed, and | |
2255 | reads the symbol table again (while trying to preserve your current | |
2256 | breakpoint settings). | |
2257 | ||
6d2ebf8b | 2258 | @node Threads |
79a6e687 | 2259 | @section Debugging Programs with Multiple Threads |
c906108c SS |
2260 | |
2261 | @cindex threads of execution | |
2262 | @cindex multiple threads | |
2263 | @cindex switching threads | |
2264 | In some operating systems, such as HP-UX and Solaris, a single program | |
2265 | may have more than one @dfn{thread} of execution. The precise semantics | |
2266 | of threads differ from one operating system to another, but in general | |
2267 | the threads of a single program are akin to multiple processes---except | |
2268 | that they share one address space (that is, they can all examine and | |
2269 | modify the same variables). On the other hand, each thread has its own | |
2270 | registers and execution stack, and perhaps private memory. | |
2271 | ||
2272 | @value{GDBN} provides these facilities for debugging multi-thread | |
2273 | programs: | |
2274 | ||
2275 | @itemize @bullet | |
2276 | @item automatic notification of new threads | |
2277 | @item @samp{thread @var{threadno}}, a command to switch among threads | |
2278 | @item @samp{info threads}, a command to inquire about existing threads | |
5d161b24 | 2279 | @item @samp{thread apply [@var{threadno}] [@var{all}] @var{args}}, |
c906108c SS |
2280 | a command to apply a command to a list of threads |
2281 | @item thread-specific breakpoints | |
93815fbf VP |
2282 | @item @samp{set print thread-events}, which controls printing of |
2283 | messages on thread start and exit. | |
c906108c SS |
2284 | @end itemize |
2285 | ||
c906108c SS |
2286 | @quotation |
2287 | @emph{Warning:} These facilities are not yet available on every | |
2288 | @value{GDBN} configuration where the operating system supports threads. | |
2289 | If your @value{GDBN} does not support threads, these commands have no | |
2290 | effect. For example, a system without thread support shows no output | |
2291 | from @samp{info threads}, and always rejects the @code{thread} command, | |
2292 | like this: | |
2293 | ||
2294 | @smallexample | |
2295 | (@value{GDBP}) info threads | |
2296 | (@value{GDBP}) thread 1 | |
2297 | Thread ID 1 not known. Use the "info threads" command to | |
2298 | see the IDs of currently known threads. | |
2299 | @end smallexample | |
2300 | @c FIXME to implementors: how hard would it be to say "sorry, this GDB | |
2301 | @c doesn't support threads"? | |
2302 | @end quotation | |
c906108c SS |
2303 | |
2304 | @cindex focus of debugging | |
2305 | @cindex current thread | |
2306 | The @value{GDBN} thread debugging facility allows you to observe all | |
2307 | threads while your program runs---but whenever @value{GDBN} takes | |
2308 | control, one thread in particular is always the focus of debugging. | |
2309 | This thread is called the @dfn{current thread}. Debugging commands show | |
2310 | program information from the perspective of the current thread. | |
2311 | ||
41afff9a | 2312 | @cindex @code{New} @var{systag} message |
c906108c SS |
2313 | @cindex thread identifier (system) |
2314 | @c FIXME-implementors!! It would be more helpful if the [New...] message | |
2315 | @c included GDB's numeric thread handle, so you could just go to that | |
2316 | @c thread without first checking `info threads'. | |
2317 | Whenever @value{GDBN} detects a new thread in your program, it displays | |
2318 | the target system's identification for the thread with a message in the | |
2319 | form @samp{[New @var{systag}]}. @var{systag} is a thread identifier | |
2320 | whose form varies depending on the particular system. For example, on | |
8807d78b | 2321 | @sc{gnu}/Linux, you might see |
c906108c | 2322 | |
474c8240 | 2323 | @smallexample |
8807d78b | 2324 | [New Thread 46912507313328 (LWP 25582)] |
474c8240 | 2325 | @end smallexample |
c906108c SS |
2326 | |
2327 | @noindent | |
2328 | when @value{GDBN} notices a new thread. In contrast, on an SGI system, | |
2329 | the @var{systag} is simply something like @samp{process 368}, with no | |
2330 | further qualifier. | |
2331 | ||
2332 | @c FIXME!! (1) Does the [New...] message appear even for the very first | |
2333 | @c thread of a program, or does it only appear for the | |
6ca652b0 | 2334 | @c second---i.e.@: when it becomes obvious we have a multithread |
c906108c SS |
2335 | @c program? |
2336 | @c (2) *Is* there necessarily a first thread always? Or do some | |
2337 | @c multithread systems permit starting a program with multiple | |
5d161b24 | 2338 | @c threads ab initio? |
c906108c SS |
2339 | |
2340 | @cindex thread number | |
2341 | @cindex thread identifier (GDB) | |
2342 | For debugging purposes, @value{GDBN} associates its own thread | |
2343 | number---always a single integer---with each thread in your program. | |
2344 | ||
2345 | @table @code | |
2346 | @kindex info threads | |
2347 | @item info threads | |
2348 | Display a summary of all threads currently in your | |
2349 | program. @value{GDBN} displays for each thread (in this order): | |
2350 | ||
2351 | @enumerate | |
09d4efe1 EZ |
2352 | @item |
2353 | the thread number assigned by @value{GDBN} | |
c906108c | 2354 | |
09d4efe1 EZ |
2355 | @item |
2356 | the target system's thread identifier (@var{systag}) | |
c906108c | 2357 | |
09d4efe1 EZ |
2358 | @item |
2359 | the current stack frame summary for that thread | |
c906108c SS |
2360 | @end enumerate |
2361 | ||
2362 | @noindent | |
2363 | An asterisk @samp{*} to the left of the @value{GDBN} thread number | |
2364 | indicates the current thread. | |
2365 | ||
5d161b24 | 2366 | For example, |
c906108c SS |
2367 | @end table |
2368 | @c end table here to get a little more width for example | |
2369 | ||
2370 | @smallexample | |
2371 | (@value{GDBP}) info threads | |
2372 | 3 process 35 thread 27 0x34e5 in sigpause () | |
2373 | 2 process 35 thread 23 0x34e5 in sigpause () | |
2374 | * 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8) | |
2375 | at threadtest.c:68 | |
2376 | @end smallexample | |
53a5351d JM |
2377 | |
2378 | On HP-UX systems: | |
c906108c | 2379 | |
4644b6e3 EZ |
2380 | @cindex debugging multithreaded programs (on HP-UX) |
2381 | @cindex thread identifier (GDB), on HP-UX | |
c906108c SS |
2382 | For debugging purposes, @value{GDBN} associates its own thread |
2383 | number---a small integer assigned in thread-creation order---with each | |
2384 | thread in your program. | |
2385 | ||
41afff9a EZ |
2386 | @cindex @code{New} @var{systag} message, on HP-UX |
2387 | @cindex thread identifier (system), on HP-UX | |
c906108c SS |
2388 | @c FIXME-implementors!! It would be more helpful if the [New...] message |
2389 | @c included GDB's numeric thread handle, so you could just go to that | |
2390 | @c thread without first checking `info threads'. | |
2391 | Whenever @value{GDBN} detects a new thread in your program, it displays | |
2392 | both @value{GDBN}'s thread number and the target system's identification for the thread with a message in the | |
2393 | form @samp{[New @var{systag}]}. @var{systag} is a thread identifier | |
2394 | whose form varies depending on the particular system. For example, on | |
2395 | HP-UX, you see | |
2396 | ||
474c8240 | 2397 | @smallexample |
c906108c | 2398 | [New thread 2 (system thread 26594)] |
474c8240 | 2399 | @end smallexample |
c906108c SS |
2400 | |
2401 | @noindent | |
5d161b24 | 2402 | when @value{GDBN} notices a new thread. |
c906108c SS |
2403 | |
2404 | @table @code | |
4644b6e3 | 2405 | @kindex info threads (HP-UX) |
c906108c SS |
2406 | @item info threads |
2407 | Display a summary of all threads currently in your | |
2408 | program. @value{GDBN} displays for each thread (in this order): | |
2409 | ||
2410 | @enumerate | |
2411 | @item the thread number assigned by @value{GDBN} | |
2412 | ||
2413 | @item the target system's thread identifier (@var{systag}) | |
2414 | ||
2415 | @item the current stack frame summary for that thread | |
2416 | @end enumerate | |
2417 | ||
2418 | @noindent | |
2419 | An asterisk @samp{*} to the left of the @value{GDBN} thread number | |
2420 | indicates the current thread. | |
2421 | ||
5d161b24 | 2422 | For example, |
c906108c SS |
2423 | @end table |
2424 | @c end table here to get a little more width for example | |
2425 | ||
474c8240 | 2426 | @smallexample |
c906108c | 2427 | (@value{GDBP}) info threads |
6d2ebf8b SS |
2428 | * 3 system thread 26607 worker (wptr=0x7b09c318 "@@") \@* |
2429 | at quicksort.c:137 | |
2430 | 2 system thread 26606 0x7b0030d8 in __ksleep () \@* | |
2431 | from /usr/lib/libc.2 | |
2432 | 1 system thread 27905 0x7b003498 in _brk () \@* | |
2433 | from /usr/lib/libc.2 | |
474c8240 | 2434 | @end smallexample |
c906108c | 2435 | |
c45da7e6 EZ |
2436 | On Solaris, you can display more information about user threads with a |
2437 | Solaris-specific command: | |
2438 | ||
2439 | @table @code | |
2440 | @item maint info sol-threads | |
2441 | @kindex maint info sol-threads | |
2442 | @cindex thread info (Solaris) | |
2443 | Display info on Solaris user threads. | |
2444 | @end table | |
2445 | ||
c906108c SS |
2446 | @table @code |
2447 | @kindex thread @var{threadno} | |
2448 | @item thread @var{threadno} | |
2449 | Make thread number @var{threadno} the current thread. The command | |
2450 | argument @var{threadno} is the internal @value{GDBN} thread number, as | |
2451 | shown in the first field of the @samp{info threads} display. | |
2452 | @value{GDBN} responds by displaying the system identifier of the thread | |
2453 | you selected, and its current stack frame summary: | |
2454 | ||
2455 | @smallexample | |
2456 | @c FIXME!! This example made up; find a @value{GDBN} w/threads and get real one | |
2457 | (@value{GDBP}) thread 2 | |
c906108c | 2458 | [Switching to process 35 thread 23] |
c906108c SS |
2459 | 0x34e5 in sigpause () |
2460 | @end smallexample | |
2461 | ||
2462 | @noindent | |
2463 | As with the @samp{[New @dots{}]} message, the form of the text after | |
2464 | @samp{Switching to} depends on your system's conventions for identifying | |
5d161b24 | 2465 | threads. |
c906108c | 2466 | |
9c16f35a | 2467 | @kindex thread apply |
638ac427 | 2468 | @cindex apply command to several threads |
839c27b7 EZ |
2469 | @item thread apply [@var{threadno}] [@var{all}] @var{command} |
2470 | The @code{thread apply} command allows you to apply the named | |
2471 | @var{command} to one or more threads. Specify the numbers of the | |
2472 | threads that you want affected with the command argument | |
2473 | @var{threadno}. It can be a single thread number, one of the numbers | |
2474 | shown in the first field of the @samp{info threads} display; or it | |
2475 | could be a range of thread numbers, as in @code{2-4}. To apply a | |
2476 | command to all threads, type @kbd{thread apply all @var{command}}. | |
93815fbf VP |
2477 | |
2478 | @kindex set print thread-events | |
2479 | @cindex print messages on thread start and exit | |
2480 | @item set print thread-events | |
2481 | @itemx set print thread-events on | |
2482 | @itemx set print thread-events off | |
2483 | The @code{set print thread-events} command allows you to enable or | |
2484 | disable printing of messages when @value{GDBN} notices that new threads have | |
2485 | started or that threads have exited. By default, these messages will | |
2486 | be printed if detection of these events is supported by the target. | |
2487 | Note that these messages cannot be disabled on all targets. | |
2488 | ||
2489 | @kindex show print thread-events | |
2490 | @item show print thread-events | |
2491 | Show whether messages will be printed when @value{GDBN} detects that threads | |
2492 | have started and exited. | |
c906108c SS |
2493 | @end table |
2494 | ||
2495 | @cindex automatic thread selection | |
2496 | @cindex switching threads automatically | |
2497 | @cindex threads, automatic switching | |
2498 | Whenever @value{GDBN} stops your program, due to a breakpoint or a | |
2499 | signal, it automatically selects the thread where that breakpoint or | |
2500 | signal happened. @value{GDBN} alerts you to the context switch with a | |
2501 | message of the form @samp{[Switching to @var{systag}]} to identify the | |
2502 | thread. | |
2503 | ||
79a6e687 | 2504 | @xref{Thread Stops,,Stopping and Starting Multi-thread Programs}, for |
c906108c SS |
2505 | more information about how @value{GDBN} behaves when you stop and start |
2506 | programs with multiple threads. | |
2507 | ||
79a6e687 | 2508 | @xref{Set Watchpoints,,Setting Watchpoints}, for information about |
c906108c | 2509 | watchpoints in programs with multiple threads. |
c906108c | 2510 | |
6d2ebf8b | 2511 | @node Processes |
79a6e687 | 2512 | @section Debugging Programs with Multiple Processes |
c906108c SS |
2513 | |
2514 | @cindex fork, debugging programs which call | |
2515 | @cindex multiple processes | |
2516 | @cindex processes, multiple | |
53a5351d JM |
2517 | On most systems, @value{GDBN} has no special support for debugging |
2518 | programs which create additional processes using the @code{fork} | |
2519 | function. When a program forks, @value{GDBN} will continue to debug the | |
2520 | parent process and the child process will run unimpeded. If you have | |
2521 | set a breakpoint in any code which the child then executes, the child | |
2522 | will get a @code{SIGTRAP} signal which (unless it catches the signal) | |
2523 | will cause it to terminate. | |
c906108c SS |
2524 | |
2525 | However, if you want to debug the child process there is a workaround | |
2526 | which isn't too painful. Put a call to @code{sleep} in the code which | |
2527 | the child process executes after the fork. It may be useful to sleep | |
2528 | only if a certain environment variable is set, or a certain file exists, | |
2529 | so that the delay need not occur when you don't want to run @value{GDBN} | |
2530 | on the child. While the child is sleeping, use the @code{ps} program to | |
2531 | get its process ID. Then tell @value{GDBN} (a new invocation of | |
2532 | @value{GDBN} if you are also debugging the parent process) to attach to | |
d4f3574e | 2533 | the child process (@pxref{Attach}). From that point on you can debug |
c906108c | 2534 | the child process just like any other process which you attached to. |
c906108c | 2535 | |
b51970ac DJ |
2536 | On some systems, @value{GDBN} provides support for debugging programs that |
2537 | create additional processes using the @code{fork} or @code{vfork} functions. | |
2538 | Currently, the only platforms with this feature are HP-UX (11.x and later | |
a6b151f1 | 2539 | only?) and @sc{gnu}/Linux (kernel version 2.5.60 and later). |
c906108c SS |
2540 | |
2541 | By default, when a program forks, @value{GDBN} will continue to debug | |
2542 | the parent process and the child process will run unimpeded. | |
2543 | ||
2544 | If you want to follow the child process instead of the parent process, | |
2545 | use the command @w{@code{set follow-fork-mode}}. | |
2546 | ||
2547 | @table @code | |
2548 | @kindex set follow-fork-mode | |
2549 | @item set follow-fork-mode @var{mode} | |
2550 | Set the debugger response to a program call of @code{fork} or | |
2551 | @code{vfork}. A call to @code{fork} or @code{vfork} creates a new | |
9c16f35a | 2552 | process. The @var{mode} argument can be: |
c906108c SS |
2553 | |
2554 | @table @code | |
2555 | @item parent | |
2556 | The original process is debugged after a fork. The child process runs | |
2df3850c | 2557 | unimpeded. This is the default. |
c906108c SS |
2558 | |
2559 | @item child | |
2560 | The new process is debugged after a fork. The parent process runs | |
2561 | unimpeded. | |
2562 | ||
c906108c SS |
2563 | @end table |
2564 | ||
9c16f35a | 2565 | @kindex show follow-fork-mode |
c906108c | 2566 | @item show follow-fork-mode |
2df3850c | 2567 | Display the current debugger response to a @code{fork} or @code{vfork} call. |
c906108c SS |
2568 | @end table |
2569 | ||
5c95884b MS |
2570 | @cindex debugging multiple processes |
2571 | On Linux, if you want to debug both the parent and child processes, use the | |
2572 | command @w{@code{set detach-on-fork}}. | |
2573 | ||
2574 | @table @code | |
2575 | @kindex set detach-on-fork | |
2576 | @item set detach-on-fork @var{mode} | |
2577 | Tells gdb whether to detach one of the processes after a fork, or | |
2578 | retain debugger control over them both. | |
2579 | ||
2580 | @table @code | |
2581 | @item on | |
2582 | The child process (or parent process, depending on the value of | |
2583 | @code{follow-fork-mode}) will be detached and allowed to run | |
2584 | independently. This is the default. | |
2585 | ||
2586 | @item off | |
2587 | Both processes will be held under the control of @value{GDBN}. | |
2588 | One process (child or parent, depending on the value of | |
2589 | @code{follow-fork-mode}) is debugged as usual, while the other | |
2590 | is held suspended. | |
2591 | ||
2592 | @end table | |
2593 | ||
11310833 NR |
2594 | @kindex show detach-on-fork |
2595 | @item show detach-on-fork | |
2596 | Show whether detach-on-fork mode is on/off. | |
5c95884b MS |
2597 | @end table |
2598 | ||
11310833 | 2599 | If you choose to set @samp{detach-on-fork} mode off, then |
5c95884b MS |
2600 | @value{GDBN} will retain control of all forked processes (including |
2601 | nested forks). You can list the forked processes under the control of | |
2602 | @value{GDBN} by using the @w{@code{info forks}} command, and switch | |
2603 | from one fork to another by using the @w{@code{fork}} command. | |
2604 | ||
2605 | @table @code | |
2606 | @kindex info forks | |
2607 | @item info forks | |
2608 | Print a list of all forked processes under the control of @value{GDBN}. | |
2609 | The listing will include a fork id, a process id, and the current | |
2610 | position (program counter) of the process. | |
2611 | ||
5c95884b MS |
2612 | @kindex fork @var{fork-id} |
2613 | @item fork @var{fork-id} | |
2614 | Make fork number @var{fork-id} the current process. The argument | |
2615 | @var{fork-id} is the internal fork number assigned by @value{GDBN}, | |
2616 | as shown in the first field of the @samp{info forks} display. | |
2617 | ||
11310833 NR |
2618 | @kindex process @var{process-id} |
2619 | @item process @var{process-id} | |
2620 | Make process number @var{process-id} the current process. The | |
2621 | argument @var{process-id} must be one that is listed in the output of | |
2622 | @samp{info forks}. | |
2623 | ||
5c95884b MS |
2624 | @end table |
2625 | ||
2626 | To quit debugging one of the forked processes, you can either detach | |
f73adfeb | 2627 | from it by using the @w{@code{detach fork}} command (allowing it to |
5c95884b | 2628 | run independently), or delete (and kill) it using the |
b8db102d | 2629 | @w{@code{delete fork}} command. |
5c95884b MS |
2630 | |
2631 | @table @code | |
f73adfeb AS |
2632 | @kindex detach fork @var{fork-id} |
2633 | @item detach fork @var{fork-id} | |
5c95884b MS |
2634 | Detach from the process identified by @value{GDBN} fork number |
2635 | @var{fork-id}, and remove it from the fork list. The process will be | |
2636 | allowed to run independently. | |
2637 | ||
b8db102d MS |
2638 | @kindex delete fork @var{fork-id} |
2639 | @item delete fork @var{fork-id} | |
5c95884b MS |
2640 | Kill the process identified by @value{GDBN} fork number @var{fork-id}, |
2641 | and remove it from the fork list. | |
2642 | ||
2643 | @end table | |
2644 | ||
c906108c SS |
2645 | If you ask to debug a child process and a @code{vfork} is followed by an |
2646 | @code{exec}, @value{GDBN} executes the new target up to the first | |
2647 | breakpoint in the new target. If you have a breakpoint set on | |
2648 | @code{main} in your original program, the breakpoint will also be set on | |
2649 | the child process's @code{main}. | |
2650 | ||
2651 | When a child process is spawned by @code{vfork}, you cannot debug the | |
2652 | child or parent until an @code{exec} call completes. | |
2653 | ||
2654 | If you issue a @code{run} command to @value{GDBN} after an @code{exec} | |
2655 | call executes, the new target restarts. To restart the parent process, | |
2656 | use the @code{file} command with the parent executable name as its | |
2657 | argument. | |
2658 | ||
2659 | You can use the @code{catch} command to make @value{GDBN} stop whenever | |
2660 | a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set | |
79a6e687 | 2661 | Catchpoints, ,Setting Catchpoints}. |
c906108c | 2662 | |
5c95884b | 2663 | @node Checkpoint/Restart |
79a6e687 | 2664 | @section Setting a @emph{Bookmark} to Return to Later |
5c95884b MS |
2665 | |
2666 | @cindex checkpoint | |
2667 | @cindex restart | |
2668 | @cindex bookmark | |
2669 | @cindex snapshot of a process | |
2670 | @cindex rewind program state | |
2671 | ||
2672 | On certain operating systems@footnote{Currently, only | |
2673 | @sc{gnu}/Linux.}, @value{GDBN} is able to save a @dfn{snapshot} of a | |
2674 | program's state, called a @dfn{checkpoint}, and come back to it | |
2675 | later. | |
2676 | ||
2677 | Returning to a checkpoint effectively undoes everything that has | |
2678 | happened in the program since the @code{checkpoint} was saved. This | |
2679 | includes changes in memory, registers, and even (within some limits) | |
2680 | system state. Effectively, it is like going back in time to the | |
2681 | moment when the checkpoint was saved. | |
2682 | ||
2683 | Thus, if you're stepping thru a program and you think you're | |
2684 | getting close to the point where things go wrong, you can save | |
2685 | a checkpoint. Then, if you accidentally go too far and miss | |
2686 | the critical statement, instead of having to restart your program | |
2687 | from the beginning, you can just go back to the checkpoint and | |
2688 | start again from there. | |
2689 | ||
2690 | This can be especially useful if it takes a lot of time or | |
2691 | steps to reach the point where you think the bug occurs. | |
2692 | ||
2693 | To use the @code{checkpoint}/@code{restart} method of debugging: | |
2694 | ||
2695 | @table @code | |
2696 | @kindex checkpoint | |
2697 | @item checkpoint | |
2698 | Save a snapshot of the debugged program's current execution state. | |
2699 | The @code{checkpoint} command takes no arguments, but each checkpoint | |
2700 | is assigned a small integer id, similar to a breakpoint id. | |
2701 | ||
2702 | @kindex info checkpoints | |
2703 | @item info checkpoints | |
2704 | List the checkpoints that have been saved in the current debugging | |
2705 | session. For each checkpoint, the following information will be | |
2706 | listed: | |
2707 | ||
2708 | @table @code | |
2709 | @item Checkpoint ID | |
2710 | @item Process ID | |
2711 | @item Code Address | |
2712 | @item Source line, or label | |
2713 | @end table | |
2714 | ||
2715 | @kindex restart @var{checkpoint-id} | |
2716 | @item restart @var{checkpoint-id} | |
2717 | Restore the program state that was saved as checkpoint number | |
2718 | @var{checkpoint-id}. All program variables, registers, stack frames | |
2719 | etc.@: will be returned to the values that they had when the checkpoint | |
2720 | was saved. In essence, gdb will ``wind back the clock'' to the point | |
2721 | in time when the checkpoint was saved. | |
2722 | ||
2723 | Note that breakpoints, @value{GDBN} variables, command history etc. | |
2724 | are not affected by restoring a checkpoint. In general, a checkpoint | |
2725 | only restores things that reside in the program being debugged, not in | |
2726 | the debugger. | |
2727 | ||
b8db102d MS |
2728 | @kindex delete checkpoint @var{checkpoint-id} |
2729 | @item delete checkpoint @var{checkpoint-id} | |
5c95884b MS |
2730 | Delete the previously-saved checkpoint identified by @var{checkpoint-id}. |
2731 | ||
2732 | @end table | |
2733 | ||
2734 | Returning to a previously saved checkpoint will restore the user state | |
2735 | of the program being debugged, plus a significant subset of the system | |
2736 | (OS) state, including file pointers. It won't ``un-write'' data from | |
2737 | a file, but it will rewind the file pointer to the previous location, | |
2738 | so that the previously written data can be overwritten. For files | |
2739 | opened in read mode, the pointer will also be restored so that the | |
2740 | previously read data can be read again. | |
2741 | ||
2742 | Of course, characters that have been sent to a printer (or other | |
2743 | external device) cannot be ``snatched back'', and characters received | |
2744 | from eg.@: a serial device can be removed from internal program buffers, | |
2745 | but they cannot be ``pushed back'' into the serial pipeline, ready to | |
2746 | be received again. Similarly, the actual contents of files that have | |
2747 | been changed cannot be restored (at this time). | |
2748 | ||
2749 | However, within those constraints, you actually can ``rewind'' your | |
2750 | program to a previously saved point in time, and begin debugging it | |
2751 | again --- and you can change the course of events so as to debug a | |
2752 | different execution path this time. | |
2753 | ||
2754 | @cindex checkpoints and process id | |
2755 | Finally, there is one bit of internal program state that will be | |
2756 | different when you return to a checkpoint --- the program's process | |
2757 | id. Each checkpoint will have a unique process id (or @var{pid}), | |
2758 | and each will be different from the program's original @var{pid}. | |
2759 | If your program has saved a local copy of its process id, this could | |
2760 | potentially pose a problem. | |
2761 | ||
79a6e687 | 2762 | @subsection A Non-obvious Benefit of Using Checkpoints |
5c95884b MS |
2763 | |
2764 | On some systems such as @sc{gnu}/Linux, address space randomization | |
2765 | is performed on new processes for security reasons. This makes it | |
2766 | difficult or impossible to set a breakpoint, or watchpoint, on an | |
2767 | absolute address if you have to restart the program, since the | |
2768 | absolute location of a symbol will change from one execution to the | |
2769 | next. | |
2770 | ||
2771 | A checkpoint, however, is an @emph{identical} copy of a process. | |
2772 | Therefore if you create a checkpoint at (eg.@:) the start of main, | |
2773 | and simply return to that checkpoint instead of restarting the | |
2774 | process, you can avoid the effects of address randomization and | |
2775 | your symbols will all stay in the same place. | |
2776 | ||
6d2ebf8b | 2777 | @node Stopping |
c906108c SS |
2778 | @chapter Stopping and Continuing |
2779 | ||
2780 | The principal purposes of using a debugger are so that you can stop your | |
2781 | program before it terminates; or so that, if your program runs into | |
2782 | trouble, you can investigate and find out why. | |
2783 | ||
7a292a7a SS |
2784 | Inside @value{GDBN}, your program may stop for any of several reasons, |
2785 | such as a signal, a breakpoint, or reaching a new line after a | |
2786 | @value{GDBN} command such as @code{step}. You may then examine and | |
2787 | change variables, set new breakpoints or remove old ones, and then | |
2788 | continue execution. Usually, the messages shown by @value{GDBN} provide | |
2789 | ample explanation of the status of your program---but you can also | |
2790 | explicitly request this information at any time. | |
c906108c SS |
2791 | |
2792 | @table @code | |
2793 | @kindex info program | |
2794 | @item info program | |
2795 | Display information about the status of your program: whether it is | |
7a292a7a | 2796 | running or not, what process it is, and why it stopped. |
c906108c SS |
2797 | @end table |
2798 | ||
2799 | @menu | |
2800 | * Breakpoints:: Breakpoints, watchpoints, and catchpoints | |
2801 | * Continuing and Stepping:: Resuming execution | |
c906108c | 2802 | * Signals:: Signals |
c906108c | 2803 | * Thread Stops:: Stopping and starting multi-thread programs |
c906108c SS |
2804 | @end menu |
2805 | ||
6d2ebf8b | 2806 | @node Breakpoints |
79a6e687 | 2807 | @section Breakpoints, Watchpoints, and Catchpoints |
c906108c SS |
2808 | |
2809 | @cindex breakpoints | |
2810 | A @dfn{breakpoint} makes your program stop whenever a certain point in | |
2811 | the program is reached. For each breakpoint, you can add conditions to | |
2812 | control in finer detail whether your program stops. You can set | |
2813 | breakpoints with the @code{break} command and its variants (@pxref{Set | |
79a6e687 | 2814 | Breaks, ,Setting Breakpoints}), to specify the place where your program |
c906108c SS |
2815 | should stop by line number, function name or exact address in the |
2816 | program. | |
2817 | ||
09d4efe1 EZ |
2818 | On some systems, you can set breakpoints in shared libraries before |
2819 | the executable is run. There is a minor limitation on HP-UX systems: | |
2820 | you must wait until the executable is run in order to set breakpoints | |
2821 | in shared library routines that are not called directly by the program | |
2822 | (for example, routines that are arguments in a @code{pthread_create} | |
2823 | call). | |
c906108c SS |
2824 | |
2825 | @cindex watchpoints | |
fd60e0df | 2826 | @cindex data breakpoints |
c906108c SS |
2827 | @cindex memory tracing |
2828 | @cindex breakpoint on memory address | |
2829 | @cindex breakpoint on variable modification | |
2830 | A @dfn{watchpoint} is a special breakpoint that stops your program | |
fd60e0df | 2831 | when the value of an expression changes. The expression may be a value |
0ced0c34 | 2832 | of a variable, or it could involve values of one or more variables |
fd60e0df EZ |
2833 | combined by operators, such as @samp{a + b}. This is sometimes called |
2834 | @dfn{data breakpoints}. You must use a different command to set | |
79a6e687 | 2835 | watchpoints (@pxref{Set Watchpoints, ,Setting Watchpoints}), but aside |
fd60e0df EZ |
2836 | from that, you can manage a watchpoint like any other breakpoint: you |
2837 | enable, disable, and delete both breakpoints and watchpoints using the | |
2838 | same commands. | |
c906108c SS |
2839 | |
2840 | You can arrange to have values from your program displayed automatically | |
2841 | whenever @value{GDBN} stops at a breakpoint. @xref{Auto Display,, | |
79a6e687 | 2842 | Automatic Display}. |
c906108c SS |
2843 | |
2844 | @cindex catchpoints | |
2845 | @cindex breakpoint on events | |
2846 | A @dfn{catchpoint} is another special breakpoint that stops your program | |
b37052ae | 2847 | when a certain kind of event occurs, such as the throwing of a C@t{++} |
c906108c SS |
2848 | exception or the loading of a library. As with watchpoints, you use a |
2849 | different command to set a catchpoint (@pxref{Set Catchpoints, ,Setting | |
79a6e687 | 2850 | Catchpoints}), but aside from that, you can manage a catchpoint like any |
c906108c | 2851 | other breakpoint. (To stop when your program receives a signal, use the |
d4f3574e | 2852 | @code{handle} command; see @ref{Signals, ,Signals}.) |
c906108c SS |
2853 | |
2854 | @cindex breakpoint numbers | |
2855 | @cindex numbers for breakpoints | |
2856 | @value{GDBN} assigns a number to each breakpoint, watchpoint, or | |
2857 | catchpoint when you create it; these numbers are successive integers | |
2858 | starting with one. In many of the commands for controlling various | |
2859 | features of breakpoints you use the breakpoint number to say which | |
2860 | breakpoint you want to change. Each breakpoint may be @dfn{enabled} or | |
2861 | @dfn{disabled}; if disabled, it has no effect on your program until you | |
2862 | enable it again. | |
2863 | ||
c5394b80 JM |
2864 | @cindex breakpoint ranges |
2865 | @cindex ranges of breakpoints | |
2866 | Some @value{GDBN} commands accept a range of breakpoints on which to | |
2867 | operate. A breakpoint range is either a single breakpoint number, like | |
2868 | @samp{5}, or two such numbers, in increasing order, separated by a | |
2869 | hyphen, like @samp{5-7}. When a breakpoint range is given to a command, | |
d52fb0e9 | 2870 | all breakpoints in that range are operated on. |
c5394b80 | 2871 | |
c906108c SS |
2872 | @menu |
2873 | * Set Breaks:: Setting breakpoints | |
2874 | * Set Watchpoints:: Setting watchpoints | |
2875 | * Set Catchpoints:: Setting catchpoints | |
2876 | * Delete Breaks:: Deleting breakpoints | |
2877 | * Disabling:: Disabling breakpoints | |
2878 | * Conditions:: Break conditions | |
2879 | * Break Commands:: Breakpoint command lists | |
c906108c | 2880 | * Breakpoint Menus:: Breakpoint menus |
d4f3574e | 2881 | * Error in Breakpoints:: ``Cannot insert breakpoints'' |
79a6e687 | 2882 | * Breakpoint-related Warnings:: ``Breakpoint address adjusted...'' |
c906108c SS |
2883 | @end menu |
2884 | ||
6d2ebf8b | 2885 | @node Set Breaks |
79a6e687 | 2886 | @subsection Setting Breakpoints |
c906108c | 2887 | |
5d161b24 | 2888 | @c FIXME LMB what does GDB do if no code on line of breakpt? |
c906108c SS |
2889 | @c consider in particular declaration with/without initialization. |
2890 | @c | |
2891 | @c FIXME 2 is there stuff on this already? break at fun start, already init? | |
2892 | ||
2893 | @kindex break | |
41afff9a EZ |
2894 | @kindex b @r{(@code{break})} |
2895 | @vindex $bpnum@r{, convenience variable} | |
c906108c SS |
2896 | @cindex latest breakpoint |
2897 | Breakpoints are set with the @code{break} command (abbreviated | |
5d161b24 | 2898 | @code{b}). The debugger convenience variable @samp{$bpnum} records the |
f3b28801 | 2899 | number of the breakpoint you've set most recently; see @ref{Convenience |
79a6e687 | 2900 | Vars,, Convenience Variables}, for a discussion of what you can do with |
c906108c SS |
2901 | convenience variables. |
2902 | ||
c906108c | 2903 | @table @code |
2a25a5ba EZ |
2904 | @item break @var{location} |
2905 | Set a breakpoint at the given @var{location}, which can specify a | |
2906 | function name, a line number, or an address of an instruction. | |
2907 | (@xref{Specify Location}, for a list of all the possible ways to | |
2908 | specify a @var{location}.) The breakpoint will stop your program just | |
2909 | before it executes any of the code in the specified @var{location}. | |
2910 | ||
c906108c | 2911 | When using source languages that permit overloading of symbols, such as |
2a25a5ba | 2912 | C@t{++}, a function name may refer to more than one possible place to break. |
79a6e687 | 2913 | @xref{Breakpoint Menus,,Breakpoint Menus}, for a discussion of that situation. |
c906108c | 2914 | |
c906108c SS |
2915 | @item break |
2916 | When called without any arguments, @code{break} sets a breakpoint at | |
2917 | the next instruction to be executed in the selected stack frame | |
2918 | (@pxref{Stack, ,Examining the Stack}). In any selected frame but the | |
2919 | innermost, this makes your program stop as soon as control | |
2920 | returns to that frame. This is similar to the effect of a | |
2921 | @code{finish} command in the frame inside the selected frame---except | |
2922 | that @code{finish} does not leave an active breakpoint. If you use | |
2923 | @code{break} without an argument in the innermost frame, @value{GDBN} stops | |
2924 | the next time it reaches the current location; this may be useful | |
2925 | inside loops. | |
2926 | ||
2927 | @value{GDBN} normally ignores breakpoints when it resumes execution, until at | |
2928 | least one instruction has been executed. If it did not do this, you | |
2929 | would be unable to proceed past a breakpoint without first disabling the | |
2930 | breakpoint. This rule applies whether or not the breakpoint already | |
2931 | existed when your program stopped. | |
2932 | ||
2933 | @item break @dots{} if @var{cond} | |
2934 | Set a breakpoint with condition @var{cond}; evaluate the expression | |
2935 | @var{cond} each time the breakpoint is reached, and stop only if the | |
2936 | value is nonzero---that is, if @var{cond} evaluates as true. | |
2937 | @samp{@dots{}} stands for one of the possible arguments described | |
2938 | above (or no argument) specifying where to break. @xref{Conditions, | |
79a6e687 | 2939 | ,Break Conditions}, for more information on breakpoint conditions. |
c906108c SS |
2940 | |
2941 | @kindex tbreak | |
2942 | @item tbreak @var{args} | |
2943 | Set a breakpoint enabled only for one stop. @var{args} are the | |
2944 | same as for the @code{break} command, and the breakpoint is set in the same | |
2945 | way, but the breakpoint is automatically deleted after the first time your | |
79a6e687 | 2946 | program stops there. @xref{Disabling, ,Disabling Breakpoints}. |
c906108c | 2947 | |
c906108c | 2948 | @kindex hbreak |
ba04e063 | 2949 | @cindex hardware breakpoints |
c906108c | 2950 | @item hbreak @var{args} |
d4f3574e SS |
2951 | Set a hardware-assisted breakpoint. @var{args} are the same as for the |
2952 | @code{break} command and the breakpoint is set in the same way, but the | |
c906108c SS |
2953 | breakpoint requires hardware support and some target hardware may not |
2954 | have this support. The main purpose of this is EPROM/ROM code | |
d4f3574e SS |
2955 | debugging, so you can set a breakpoint at an instruction without |
2956 | changing the instruction. This can be used with the new trap-generation | |
09d4efe1 | 2957 | provided by SPARClite DSU and most x86-based targets. These targets |
d4f3574e SS |
2958 | will generate traps when a program accesses some data or instruction |
2959 | address that is assigned to the debug registers. However the hardware | |
2960 | breakpoint registers can take a limited number of breakpoints. For | |
2961 | example, on the DSU, only two data breakpoints can be set at a time, and | |
2962 | @value{GDBN} will reject this command if more than two are used. Delete | |
2963 | or disable unused hardware breakpoints before setting new ones | |
79a6e687 BW |
2964 | (@pxref{Disabling, ,Disabling Breakpoints}). |
2965 | @xref{Conditions, ,Break Conditions}. | |
9c16f35a EZ |
2966 | For remote targets, you can restrict the number of hardware |
2967 | breakpoints @value{GDBN} will use, see @ref{set remote | |
2968 | hardware-breakpoint-limit}. | |
501eef12 | 2969 | |
c906108c SS |
2970 | @kindex thbreak |
2971 | @item thbreak @var{args} | |
2972 | Set a hardware-assisted breakpoint enabled only for one stop. @var{args} | |
2973 | are the same as for the @code{hbreak} command and the breakpoint is set in | |
5d161b24 | 2974 | the same way. However, like the @code{tbreak} command, |
c906108c SS |
2975 | the breakpoint is automatically deleted after the |
2976 | first time your program stops there. Also, like the @code{hbreak} | |
5d161b24 | 2977 | command, the breakpoint requires hardware support and some target hardware |
79a6e687 BW |
2978 | may not have this support. @xref{Disabling, ,Disabling Breakpoints}. |
2979 | See also @ref{Conditions, ,Break Conditions}. | |
c906108c SS |
2980 | |
2981 | @kindex rbreak | |
2982 | @cindex regular expression | |
c45da7e6 EZ |
2983 | @cindex breakpoints in functions matching a regexp |
2984 | @cindex set breakpoints in many functions | |
c906108c | 2985 | @item rbreak @var{regex} |
c906108c | 2986 | Set breakpoints on all functions matching the regular expression |
11cf8741 JM |
2987 | @var{regex}. This command sets an unconditional breakpoint on all |
2988 | matches, printing a list of all breakpoints it set. Once these | |
2989 | breakpoints are set, they are treated just like the breakpoints set with | |
2990 | the @code{break} command. You can delete them, disable them, or make | |
2991 | them conditional the same way as any other breakpoint. | |
2992 | ||
2993 | The syntax of the regular expression is the standard one used with tools | |
2994 | like @file{grep}. Note that this is different from the syntax used by | |
2995 | shells, so for instance @code{foo*} matches all functions that include | |
2996 | an @code{fo} followed by zero or more @code{o}s. There is an implicit | |
2997 | @code{.*} leading and trailing the regular expression you supply, so to | |
2998 | match only functions that begin with @code{foo}, use @code{^foo}. | |
c906108c | 2999 | |
f7dc1244 | 3000 | @cindex non-member C@t{++} functions, set breakpoint in |
b37052ae | 3001 | When debugging C@t{++} programs, @code{rbreak} is useful for setting |
c906108c SS |
3002 | breakpoints on overloaded functions that are not members of any special |
3003 | classes. | |
c906108c | 3004 | |
f7dc1244 EZ |
3005 | @cindex set breakpoints on all functions |
3006 | The @code{rbreak} command can be used to set breakpoints in | |
3007 | @strong{all} the functions in a program, like this: | |
3008 | ||
3009 | @smallexample | |
3010 | (@value{GDBP}) rbreak . | |
3011 | @end smallexample | |
3012 | ||
c906108c SS |
3013 | @kindex info breakpoints |
3014 | @cindex @code{$_} and @code{info breakpoints} | |
3015 | @item info breakpoints @r{[}@var{n}@r{]} | |
3016 | @itemx info break @r{[}@var{n}@r{]} | |
3017 | @itemx info watchpoints @r{[}@var{n}@r{]} | |
3018 | Print a table of all breakpoints, watchpoints, and catchpoints set and | |
45ac1734 EZ |
3019 | not deleted. Optional argument @var{n} means print information only |
3020 | about the specified breakpoint (or watchpoint or catchpoint). For | |
3021 | each breakpoint, following columns are printed: | |
c906108c SS |
3022 | |
3023 | @table @emph | |
3024 | @item Breakpoint Numbers | |
3025 | @item Type | |
3026 | Breakpoint, watchpoint, or catchpoint. | |
3027 | @item Disposition | |
3028 | Whether the breakpoint is marked to be disabled or deleted when hit. | |
3029 | @item Enabled or Disabled | |
3030 | Enabled breakpoints are marked with @samp{y}. @samp{n} marks breakpoints | |
b3db7447 | 3031 | that are not enabled. |
c906108c | 3032 | @item Address |
fe6fbf8b | 3033 | Where the breakpoint is in your program, as a memory address. For a |
b3db7447 NR |
3034 | pending breakpoint whose address is not yet known, this field will |
3035 | contain @samp{<PENDING>}. Such breakpoint won't fire until a shared | |
3036 | library that has the symbol or line referred by breakpoint is loaded. | |
3037 | See below for details. A breakpoint with several locations will | |
3b784c4f | 3038 | have @samp{<MULTIPLE>} in this field---see below for details. |
c906108c SS |
3039 | @item What |
3040 | Where the breakpoint is in the source for your program, as a file and | |
2650777c JJ |
3041 | line number. For a pending breakpoint, the original string passed to |
3042 | the breakpoint command will be listed as it cannot be resolved until | |
3043 | the appropriate shared library is loaded in the future. | |
c906108c SS |
3044 | @end table |
3045 | ||
3046 | @noindent | |
3047 | If a breakpoint is conditional, @code{info break} shows the condition on | |
3048 | the line following the affected breakpoint; breakpoint commands, if any, | |
2650777c JJ |
3049 | are listed after that. A pending breakpoint is allowed to have a condition |
3050 | specified for it. The condition is not parsed for validity until a shared | |
3051 | library is loaded that allows the pending breakpoint to resolve to a | |
3052 | valid location. | |
c906108c SS |
3053 | |
3054 | @noindent | |
3055 | @code{info break} with a breakpoint | |
3056 | number @var{n} as argument lists only that breakpoint. The | |
3057 | convenience variable @code{$_} and the default examining-address for | |
3058 | the @code{x} command are set to the address of the last breakpoint | |
79a6e687 | 3059 | listed (@pxref{Memory, ,Examining Memory}). |
c906108c SS |
3060 | |
3061 | @noindent | |
3062 | @code{info break} displays a count of the number of times the breakpoint | |
3063 | has been hit. This is especially useful in conjunction with the | |
3064 | @code{ignore} command. You can ignore a large number of breakpoint | |
3065 | hits, look at the breakpoint info to see how many times the breakpoint | |
3066 | was hit, and then run again, ignoring one less than that number. This | |
3067 | will get you quickly to the last hit of that breakpoint. | |
3068 | @end table | |
3069 | ||
3070 | @value{GDBN} allows you to set any number of breakpoints at the same place in | |
3071 | your program. There is nothing silly or meaningless about this. When | |
3072 | the breakpoints are conditional, this is even useful | |
79a6e687 | 3073 | (@pxref{Conditions, ,Break Conditions}). |
c906108c | 3074 | |
fcda367b | 3075 | It is possible that a breakpoint corresponds to several locations |
fe6fbf8b VP |
3076 | in your program. Examples of this situation are: |
3077 | ||
3078 | @itemize @bullet | |
3079 | ||
3080 | @item | |
3081 | For a C@t{++} constructor, the @value{NGCC} compiler generates several | |
3082 | instances of the function body, used in different cases. | |
3083 | ||
3084 | @item | |
3085 | For a C@t{++} template function, a given line in the function can | |
3086 | correspond to any number of instantiations. | |
3087 | ||
3088 | @item | |
3089 | For an inlined function, a given source line can correspond to | |
3090 | several places where that function is inlined. | |
3091 | ||
3092 | @end itemize | |
3093 | ||
3094 | In all those cases, @value{GDBN} will insert a breakpoint at all | |
3095 | the relevant locations. | |
3096 | ||
3b784c4f EZ |
3097 | A breakpoint with multiple locations is displayed in the breakpoint |
3098 | table using several rows---one header row, followed by one row for | |
3099 | each breakpoint location. The header row has @samp{<MULTIPLE>} in the | |
3100 | address column. The rows for individual locations contain the actual | |
3101 | addresses for locations, and show the functions to which those | |
3102 | locations belong. The number column for a location is of the form | |
fe6fbf8b VP |
3103 | @var{breakpoint-number}.@var{location-number}. |
3104 | ||
3105 | For example: | |
3b784c4f | 3106 | |
fe6fbf8b VP |
3107 | @smallexample |
3108 | Num Type Disp Enb Address What | |
3109 | 1 breakpoint keep y <MULTIPLE> | |
3110 | stop only if i==1 | |
3111 | breakpoint already hit 1 time | |
3112 | 1.1 y 0x080486a2 in void foo<int>() at t.cc:8 | |
3113 | 1.2 y 0x080486ca in void foo<double>() at t.cc:8 | |
3114 | @end smallexample | |
3115 | ||
3116 | Each location can be individually enabled or disabled by passing | |
3117 | @var{breakpoint-number}.@var{location-number} as argument to the | |
3b784c4f EZ |
3118 | @code{enable} and @code{disable} commands. Note that you cannot |
3119 | delete the individual locations from the list, you can only delete the | |
16bfc218 | 3120 | entire list of locations that belong to their parent breakpoint (with |
3b784c4f EZ |
3121 | the @kbd{delete @var{num}} command, where @var{num} is the number of |
3122 | the parent breakpoint, 1 in the above example). Disabling or enabling | |
3123 | the parent breakpoint (@pxref{Disabling}) affects all of the locations | |
3124 | that belong to that breakpoint. | |
fe6fbf8b | 3125 | |
2650777c | 3126 | @cindex pending breakpoints |
fe6fbf8b | 3127 | It's quite common to have a breakpoint inside a shared library. |
3b784c4f | 3128 | Shared libraries can be loaded and unloaded explicitly, |
fe6fbf8b VP |
3129 | and possibly repeatedly, as the program is executed. To support |
3130 | this use case, @value{GDBN} updates breakpoint locations whenever | |
3131 | any shared library is loaded or unloaded. Typically, you would | |
fcda367b | 3132 | set a breakpoint in a shared library at the beginning of your |
fe6fbf8b VP |
3133 | debugging session, when the library is not loaded, and when the |
3134 | symbols from the library are not available. When you try to set | |
3135 | breakpoint, @value{GDBN} will ask you if you want to set | |
3b784c4f | 3136 | a so called @dfn{pending breakpoint}---breakpoint whose address |
fe6fbf8b VP |
3137 | is not yet resolved. |
3138 | ||
3139 | After the program is run, whenever a new shared library is loaded, | |
3140 | @value{GDBN} reevaluates all the breakpoints. When a newly loaded | |
3141 | shared library contains the symbol or line referred to by some | |
3142 | pending breakpoint, that breakpoint is resolved and becomes an | |
3143 | ordinary breakpoint. When a library is unloaded, all breakpoints | |
3144 | that refer to its symbols or source lines become pending again. | |
3145 | ||
3146 | This logic works for breakpoints with multiple locations, too. For | |
3147 | example, if you have a breakpoint in a C@t{++} template function, and | |
3148 | a newly loaded shared library has an instantiation of that template, | |
3149 | a new location is added to the list of locations for the breakpoint. | |
3150 | ||
3151 | Except for having unresolved address, pending breakpoints do not | |
3152 | differ from regular breakpoints. You can set conditions or commands, | |
3153 | enable and disable them and perform other breakpoint operations. | |
3154 | ||
3155 | @value{GDBN} provides some additional commands for controlling what | |
3156 | happens when the @samp{break} command cannot resolve breakpoint | |
3157 | address specification to an address: | |
dd79a6cf JJ |
3158 | |
3159 | @kindex set breakpoint pending | |
3160 | @kindex show breakpoint pending | |
3161 | @table @code | |
3162 | @item set breakpoint pending auto | |
3163 | This is the default behavior. When @value{GDBN} cannot find the breakpoint | |
3164 | location, it queries you whether a pending breakpoint should be created. | |
3165 | ||
3166 | @item set breakpoint pending on | |
3167 | This indicates that an unrecognized breakpoint location should automatically | |
3168 | result in a pending breakpoint being created. | |
3169 | ||
3170 | @item set breakpoint pending off | |
3171 | This indicates that pending breakpoints are not to be created. Any | |
3172 | unrecognized breakpoint location results in an error. This setting does | |
3173 | not affect any pending breakpoints previously created. | |
3174 | ||
3175 | @item show breakpoint pending | |
3176 | Show the current behavior setting for creating pending breakpoints. | |
3177 | @end table | |
2650777c | 3178 | |
fe6fbf8b VP |
3179 | The settings above only affect the @code{break} command and its |
3180 | variants. Once breakpoint is set, it will be automatically updated | |
3181 | as shared libraries are loaded and unloaded. | |
2650777c | 3182 | |
765dc015 VP |
3183 | @cindex automatic hardware breakpoints |
3184 | For some targets, @value{GDBN} can automatically decide if hardware or | |
3185 | software breakpoints should be used, depending on whether the | |
3186 | breakpoint address is read-only or read-write. This applies to | |
3187 | breakpoints set with the @code{break} command as well as to internal | |
3188 | breakpoints set by commands like @code{next} and @code{finish}. For | |
fcda367b | 3189 | breakpoints set with @code{hbreak}, @value{GDBN} will always use hardware |
765dc015 VP |
3190 | breakpoints. |
3191 | ||
3192 | You can control this automatic behaviour with the following commands:: | |
3193 | ||
3194 | @kindex set breakpoint auto-hw | |
3195 | @kindex show breakpoint auto-hw | |
3196 | @table @code | |
3197 | @item set breakpoint auto-hw on | |
3198 | This is the default behavior. When @value{GDBN} sets a breakpoint, it | |
3199 | will try to use the target memory map to decide if software or hardware | |
3200 | breakpoint must be used. | |
3201 | ||
3202 | @item set breakpoint auto-hw off | |
3203 | This indicates @value{GDBN} should not automatically select breakpoint | |
3204 | type. If the target provides a memory map, @value{GDBN} will warn when | |
3205 | trying to set software breakpoint at a read-only address. | |
3206 | @end table | |
3207 | ||
3208 | ||
c906108c SS |
3209 | @cindex negative breakpoint numbers |
3210 | @cindex internal @value{GDBN} breakpoints | |
eb12ee30 AC |
3211 | @value{GDBN} itself sometimes sets breakpoints in your program for |
3212 | special purposes, such as proper handling of @code{longjmp} (in C | |
3213 | programs). These internal breakpoints are assigned negative numbers, | |
3214 | starting with @code{-1}; @samp{info breakpoints} does not display them. | |
c906108c | 3215 | You can see these breakpoints with the @value{GDBN} maintenance command |
eb12ee30 | 3216 | @samp{maint info breakpoints} (@pxref{maint info breakpoints}). |
c906108c SS |
3217 | |
3218 | ||
6d2ebf8b | 3219 | @node Set Watchpoints |
79a6e687 | 3220 | @subsection Setting Watchpoints |
c906108c SS |
3221 | |
3222 | @cindex setting watchpoints | |
c906108c SS |
3223 | You can use a watchpoint to stop execution whenever the value of an |
3224 | expression changes, without having to predict a particular place where | |
fd60e0df EZ |
3225 | this may happen. (This is sometimes called a @dfn{data breakpoint}.) |
3226 | The expression may be as simple as the value of a single variable, or | |
3227 | as complex as many variables combined by operators. Examples include: | |
3228 | ||
3229 | @itemize @bullet | |
3230 | @item | |
3231 | A reference to the value of a single variable. | |
3232 | ||
3233 | @item | |
3234 | An address cast to an appropriate data type. For example, | |
3235 | @samp{*(int *)0x12345678} will watch a 4-byte region at the specified | |
3236 | address (assuming an @code{int} occupies 4 bytes). | |
3237 | ||
3238 | @item | |
3239 | An arbitrarily complex expression, such as @samp{a*b + c/d}. The | |
3240 | expression can use any operators valid in the program's native | |
3241 | language (@pxref{Languages}). | |
3242 | @end itemize | |
c906108c | 3243 | |
fa4727a6 DJ |
3244 | You can set a watchpoint on an expression even if the expression can |
3245 | not be evaluated yet. For instance, you can set a watchpoint on | |
3246 | @samp{*global_ptr} before @samp{global_ptr} is initialized. | |
3247 | @value{GDBN} will stop when your program sets @samp{global_ptr} and | |
3248 | the expression produces a valid value. If the expression becomes | |
3249 | valid in some other way than changing a variable (e.g.@: if the memory | |
3250 | pointed to by @samp{*global_ptr} becomes readable as the result of a | |
3251 | @code{malloc} call), @value{GDBN} may not stop until the next time | |
3252 | the expression changes. | |
3253 | ||
82f2d802 EZ |
3254 | @cindex software watchpoints |
3255 | @cindex hardware watchpoints | |
c906108c | 3256 | Depending on your system, watchpoints may be implemented in software or |
2df3850c | 3257 | hardware. @value{GDBN} does software watchpointing by single-stepping your |
c906108c SS |
3258 | program and testing the variable's value each time, which is hundreds of |
3259 | times slower than normal execution. (But this may still be worth it, to | |
3260 | catch errors where you have no clue what part of your program is the | |
3261 | culprit.) | |
3262 | ||
37e4754d | 3263 | On some systems, such as HP-UX, PowerPC, @sc{gnu}/Linux and most other |
82f2d802 EZ |
3264 | x86-based targets, @value{GDBN} includes support for hardware |
3265 | watchpoints, which do not slow down the running of your program. | |
c906108c SS |
3266 | |
3267 | @table @code | |
3268 | @kindex watch | |
d8b2a693 | 3269 | @item watch @var{expr} @r{[}thread @var{threadnum}@r{]} |
fd60e0df EZ |
3270 | Set a watchpoint for an expression. @value{GDBN} will break when the |
3271 | expression @var{expr} is written into by the program and its value | |
3272 | changes. The simplest (and the most popular) use of this command is | |
3273 | to watch the value of a single variable: | |
3274 | ||
3275 | @smallexample | |
3276 | (@value{GDBP}) watch foo | |
3277 | @end smallexample | |
c906108c | 3278 | |
d8b2a693 JB |
3279 | If the command includes a @code{@r{[}thread @var{threadnum}@r{]}} |
3280 | clause, @value{GDBN} breaks only when the thread identified by | |
3281 | @var{threadnum} changes the value of @var{expr}. If any other threads | |
3282 | change the value of @var{expr}, @value{GDBN} will not break. Note | |
3283 | that watchpoints restricted to a single thread in this way only work | |
3284 | with Hardware Watchpoints. | |
3285 | ||
c906108c | 3286 | @kindex rwatch |
d8b2a693 | 3287 | @item rwatch @var{expr} @r{[}thread @var{threadnum}@r{]} |
09d4efe1 EZ |
3288 | Set a watchpoint that will break when the value of @var{expr} is read |
3289 | by the program. | |
c906108c SS |
3290 | |
3291 | @kindex awatch | |
d8b2a693 | 3292 | @item awatch @var{expr} @r{[}thread @var{threadnum}@r{]} |
09d4efe1 EZ |
3293 | Set a watchpoint that will break when @var{expr} is either read from |
3294 | or written into by the program. | |
c906108c | 3295 | |
45ac1734 | 3296 | @kindex info watchpoints @r{[}@var{n}@r{]} |
c906108c SS |
3297 | @item info watchpoints |
3298 | This command prints a list of watchpoints, breakpoints, and catchpoints; | |
09d4efe1 | 3299 | it is the same as @code{info break} (@pxref{Set Breaks}). |
c906108c SS |
3300 | @end table |
3301 | ||
3302 | @value{GDBN} sets a @dfn{hardware watchpoint} if possible. Hardware | |
3303 | watchpoints execute very quickly, and the debugger reports a change in | |
3304 | value at the exact instruction where the change occurs. If @value{GDBN} | |
3305 | cannot set a hardware watchpoint, it sets a software watchpoint, which | |
3306 | executes more slowly and reports the change in value at the next | |
82f2d802 EZ |
3307 | @emph{statement}, not the instruction, after the change occurs. |
3308 | ||
82f2d802 EZ |
3309 | @cindex use only software watchpoints |
3310 | You can force @value{GDBN} to use only software watchpoints with the | |
3311 | @kbd{set can-use-hw-watchpoints 0} command. With this variable set to | |
3312 | zero, @value{GDBN} will never try to use hardware watchpoints, even if | |
3313 | the underlying system supports them. (Note that hardware-assisted | |
3314 | watchpoints that were set @emph{before} setting | |
3315 | @code{can-use-hw-watchpoints} to zero will still use the hardware | |
d3e8051b | 3316 | mechanism of watching expression values.) |
c906108c | 3317 | |
9c16f35a EZ |
3318 | @table @code |
3319 | @item set can-use-hw-watchpoints | |
3320 | @kindex set can-use-hw-watchpoints | |
3321 | Set whether or not to use hardware watchpoints. | |
3322 | ||
3323 | @item show can-use-hw-watchpoints | |
3324 | @kindex show can-use-hw-watchpoints | |
3325 | Show the current mode of using hardware watchpoints. | |
3326 | @end table | |
3327 | ||
3328 | For remote targets, you can restrict the number of hardware | |
3329 | watchpoints @value{GDBN} will use, see @ref{set remote | |
3330 | hardware-breakpoint-limit}. | |
3331 | ||
c906108c SS |
3332 | When you issue the @code{watch} command, @value{GDBN} reports |
3333 | ||
474c8240 | 3334 | @smallexample |
c906108c | 3335 | Hardware watchpoint @var{num}: @var{expr} |
474c8240 | 3336 | @end smallexample |
c906108c SS |
3337 | |
3338 | @noindent | |
3339 | if it was able to set a hardware watchpoint. | |
3340 | ||
7be570e7 JM |
3341 | Currently, the @code{awatch} and @code{rwatch} commands can only set |
3342 | hardware watchpoints, because accesses to data that don't change the | |
3343 | value of the watched expression cannot be detected without examining | |
3344 | every instruction as it is being executed, and @value{GDBN} does not do | |
3345 | that currently. If @value{GDBN} finds that it is unable to set a | |
3346 | hardware breakpoint with the @code{awatch} or @code{rwatch} command, it | |
3347 | will print a message like this: | |
3348 | ||
3349 | @smallexample | |
3350 | Expression cannot be implemented with read/access watchpoint. | |
3351 | @end smallexample | |
3352 | ||
3353 | Sometimes, @value{GDBN} cannot set a hardware watchpoint because the | |
3354 | data type of the watched expression is wider than what a hardware | |
3355 | watchpoint on the target machine can handle. For example, some systems | |
3356 | can only watch regions that are up to 4 bytes wide; on such systems you | |
3357 | cannot set hardware watchpoints for an expression that yields a | |
3358 | double-precision floating-point number (which is typically 8 bytes | |
3359 | wide). As a work-around, it might be possible to break the large region | |
3360 | into a series of smaller ones and watch them with separate watchpoints. | |
3361 | ||
3362 | If you set too many hardware watchpoints, @value{GDBN} might be unable | |
3363 | to insert all of them when you resume the execution of your program. | |
3364 | Since the precise number of active watchpoints is unknown until such | |
3365 | time as the program is about to be resumed, @value{GDBN} might not be | |
3366 | able to warn you about this when you set the watchpoints, and the | |
3367 | warning will be printed only when the program is resumed: | |
3368 | ||
3369 | @smallexample | |
3370 | Hardware watchpoint @var{num}: Could not insert watchpoint | |
3371 | @end smallexample | |
3372 | ||
3373 | @noindent | |
3374 | If this happens, delete or disable some of the watchpoints. | |
3375 | ||
fd60e0df EZ |
3376 | Watching complex expressions that reference many variables can also |
3377 | exhaust the resources available for hardware-assisted watchpoints. | |
3378 | That's because @value{GDBN} needs to watch every variable in the | |
3379 | expression with separately allocated resources. | |
3380 | ||
c906108c | 3381 | If you call a function interactively using @code{print} or @code{call}, |
2df3850c | 3382 | any watchpoints you have set will be inactive until @value{GDBN} reaches another |
c906108c SS |
3383 | kind of breakpoint or the call completes. |
3384 | ||
7be570e7 JM |
3385 | @value{GDBN} automatically deletes watchpoints that watch local |
3386 | (automatic) variables, or expressions that involve such variables, when | |
3387 | they go out of scope, that is, when the execution leaves the block in | |
3388 | which these variables were defined. In particular, when the program | |
3389 | being debugged terminates, @emph{all} local variables go out of scope, | |
3390 | and so only watchpoints that watch global variables remain set. If you | |
3391 | rerun the program, you will need to set all such watchpoints again. One | |
3392 | way of doing that would be to set a code breakpoint at the entry to the | |
3393 | @code{main} function and when it breaks, set all the watchpoints. | |
3394 | ||
c906108c SS |
3395 | @cindex watchpoints and threads |
3396 | @cindex threads and watchpoints | |
d983da9c DJ |
3397 | In multi-threaded programs, watchpoints will detect changes to the |
3398 | watched expression from every thread. | |
3399 | ||
3400 | @quotation | |
3401 | @emph{Warning:} In multi-threaded programs, software watchpoints | |
53a5351d JM |
3402 | have only limited usefulness. If @value{GDBN} creates a software |
3403 | watchpoint, it can only watch the value of an expression @emph{in a | |
3404 | single thread}. If you are confident that the expression can only | |
3405 | change due to the current thread's activity (and if you are also | |
3406 | confident that no other thread can become current), then you can use | |
3407 | software watchpoints as usual. However, @value{GDBN} may not notice | |
3408 | when a non-current thread's activity changes the expression. (Hardware | |
3409 | watchpoints, in contrast, watch an expression in all threads.) | |
c906108c | 3410 | @end quotation |
c906108c | 3411 | |
501eef12 AC |
3412 | @xref{set remote hardware-watchpoint-limit}. |
3413 | ||
6d2ebf8b | 3414 | @node Set Catchpoints |
79a6e687 | 3415 | @subsection Setting Catchpoints |
d4f3574e | 3416 | @cindex catchpoints, setting |
c906108c SS |
3417 | @cindex exception handlers |
3418 | @cindex event handling | |
3419 | ||
3420 | You can use @dfn{catchpoints} to cause the debugger to stop for certain | |
b37052ae | 3421 | kinds of program events, such as C@t{++} exceptions or the loading of a |
c906108c SS |
3422 | shared library. Use the @code{catch} command to set a catchpoint. |
3423 | ||
3424 | @table @code | |
3425 | @kindex catch | |
3426 | @item catch @var{event} | |
3427 | Stop when @var{event} occurs. @var{event} can be any of the following: | |
3428 | @table @code | |
3429 | @item throw | |
4644b6e3 | 3430 | @cindex stop on C@t{++} exceptions |
b37052ae | 3431 | The throwing of a C@t{++} exception. |
c906108c SS |
3432 | |
3433 | @item catch | |
b37052ae | 3434 | The catching of a C@t{++} exception. |
c906108c | 3435 | |
8936fcda JB |
3436 | @item exception |
3437 | @cindex Ada exception catching | |
3438 | @cindex catch Ada exceptions | |
3439 | An Ada exception being raised. If an exception name is specified | |
3440 | at the end of the command (eg @code{catch exception Program_Error}), | |
3441 | the debugger will stop only when this specific exception is raised. | |
3442 | Otherwise, the debugger stops execution when any Ada exception is raised. | |
3443 | ||
3444 | @item exception unhandled | |
3445 | An exception that was raised but is not handled by the program. | |
3446 | ||
3447 | @item assert | |
3448 | A failed Ada assertion. | |
3449 | ||
c906108c | 3450 | @item exec |
4644b6e3 | 3451 | @cindex break on fork/exec |
5ee187d7 DJ |
3452 | A call to @code{exec}. This is currently only available for HP-UX |
3453 | and @sc{gnu}/Linux. | |
c906108c SS |
3454 | |
3455 | @item fork | |
5ee187d7 DJ |
3456 | A call to @code{fork}. This is currently only available for HP-UX |
3457 | and @sc{gnu}/Linux. | |
c906108c SS |
3458 | |
3459 | @item vfork | |
5ee187d7 DJ |
3460 | A call to @code{vfork}. This is currently only available for HP-UX |
3461 | and @sc{gnu}/Linux. | |
c906108c SS |
3462 | |
3463 | @item load | |
3464 | @itemx load @var{libname} | |
4644b6e3 | 3465 | @cindex break on load/unload of shared library |
c906108c SS |
3466 | The dynamic loading of any shared library, or the loading of the library |
3467 | @var{libname}. This is currently only available for HP-UX. | |
3468 | ||
3469 | @item unload | |
3470 | @itemx unload @var{libname} | |
c906108c SS |
3471 | The unloading of any dynamically loaded shared library, or the unloading |
3472 | of the library @var{libname}. This is currently only available for HP-UX. | |
3473 | @end table | |
3474 | ||
3475 | @item tcatch @var{event} | |
3476 | Set a catchpoint that is enabled only for one stop. The catchpoint is | |
3477 | automatically deleted after the first time the event is caught. | |
3478 | ||
3479 | @end table | |
3480 | ||
3481 | Use the @code{info break} command to list the current catchpoints. | |
3482 | ||
b37052ae | 3483 | There are currently some limitations to C@t{++} exception handling |
c906108c SS |
3484 | (@code{catch throw} and @code{catch catch}) in @value{GDBN}: |
3485 | ||
3486 | @itemize @bullet | |
3487 | @item | |
3488 | If you call a function interactively, @value{GDBN} normally returns | |
3489 | control to you when the function has finished executing. If the call | |
3490 | raises an exception, however, the call may bypass the mechanism that | |
3491 | returns control to you and cause your program either to abort or to | |
3492 | simply continue running until it hits a breakpoint, catches a signal | |
3493 | that @value{GDBN} is listening for, or exits. This is the case even if | |
3494 | you set a catchpoint for the exception; catchpoints on exceptions are | |
3495 | disabled within interactive calls. | |
3496 | ||
3497 | @item | |
3498 | You cannot raise an exception interactively. | |
3499 | ||
3500 | @item | |
3501 | You cannot install an exception handler interactively. | |
3502 | @end itemize | |
3503 | ||
3504 | @cindex raise exceptions | |
3505 | Sometimes @code{catch} is not the best way to debug exception handling: | |
3506 | if you need to know exactly where an exception is raised, it is better to | |
3507 | stop @emph{before} the exception handler is called, since that way you | |
3508 | can see the stack before any unwinding takes place. If you set a | |
3509 | breakpoint in an exception handler instead, it may not be easy to find | |
3510 | out where the exception was raised. | |
3511 | ||
3512 | To stop just before an exception handler is called, you need some | |
b37052ae | 3513 | knowledge of the implementation. In the case of @sc{gnu} C@t{++}, exceptions are |
c906108c SS |
3514 | raised by calling a library function named @code{__raise_exception} |
3515 | which has the following ANSI C interface: | |
3516 | ||
474c8240 | 3517 | @smallexample |
c906108c | 3518 | /* @var{addr} is where the exception identifier is stored. |
d4f3574e SS |
3519 | @var{id} is the exception identifier. */ |
3520 | void __raise_exception (void **addr, void *id); | |
474c8240 | 3521 | @end smallexample |
c906108c SS |
3522 | |
3523 | @noindent | |
3524 | To make the debugger catch all exceptions before any stack | |
3525 | unwinding takes place, set a breakpoint on @code{__raise_exception} | |
79a6e687 | 3526 | (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Exceptions}). |
c906108c | 3527 | |
79a6e687 | 3528 | With a conditional breakpoint (@pxref{Conditions, ,Break Conditions}) |
c906108c SS |
3529 | that depends on the value of @var{id}, you can stop your program when |
3530 | a specific exception is raised. You can use multiple conditional | |
3531 | breakpoints to stop your program when any of a number of exceptions are | |
3532 | raised. | |
3533 | ||
3534 | ||
6d2ebf8b | 3535 | @node Delete Breaks |
79a6e687 | 3536 | @subsection Deleting Breakpoints |
c906108c SS |
3537 | |
3538 | @cindex clearing breakpoints, watchpoints, catchpoints | |
3539 | @cindex deleting breakpoints, watchpoints, catchpoints | |
3540 | It is often necessary to eliminate a breakpoint, watchpoint, or | |
3541 | catchpoint once it has done its job and you no longer want your program | |
3542 | to stop there. This is called @dfn{deleting} the breakpoint. A | |
3543 | breakpoint that has been deleted no longer exists; it is forgotten. | |
3544 | ||
3545 | With the @code{clear} command you can delete breakpoints according to | |
3546 | where they are in your program. With the @code{delete} command you can | |
3547 | delete individual breakpoints, watchpoints, or catchpoints by specifying | |
3548 | their breakpoint numbers. | |
3549 | ||
3550 | It is not necessary to delete a breakpoint to proceed past it. @value{GDBN} | |
3551 | automatically ignores breakpoints on the first instruction to be executed | |
3552 | when you continue execution without changing the execution address. | |
3553 | ||
3554 | @table @code | |
3555 | @kindex clear | |
3556 | @item clear | |
3557 | Delete any breakpoints at the next instruction to be executed in the | |
79a6e687 | 3558 | selected stack frame (@pxref{Selection, ,Selecting a Frame}). When |
c906108c SS |
3559 | the innermost frame is selected, this is a good way to delete a |
3560 | breakpoint where your program just stopped. | |
3561 | ||
2a25a5ba EZ |
3562 | @item clear @var{location} |
3563 | Delete any breakpoints set at the specified @var{location}. | |
3564 | @xref{Specify Location}, for the various forms of @var{location}; the | |
3565 | most useful ones are listed below: | |
3566 | ||
3567 | @table @code | |
c906108c SS |
3568 | @item clear @var{function} |
3569 | @itemx clear @var{filename}:@var{function} | |
09d4efe1 | 3570 | Delete any breakpoints set at entry to the named @var{function}. |
c906108c SS |
3571 | |
3572 | @item clear @var{linenum} | |
3573 | @itemx clear @var{filename}:@var{linenum} | |
09d4efe1 EZ |
3574 | Delete any breakpoints set at or within the code of the specified |
3575 | @var{linenum} of the specified @var{filename}. | |
2a25a5ba | 3576 | @end table |
c906108c SS |
3577 | |
3578 | @cindex delete breakpoints | |
3579 | @kindex delete | |
41afff9a | 3580 | @kindex d @r{(@code{delete})} |
c5394b80 JM |
3581 | @item delete @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
3582 | Delete the breakpoints, watchpoints, or catchpoints of the breakpoint | |
3583 | ranges specified as arguments. If no argument is specified, delete all | |
c906108c SS |
3584 | breakpoints (@value{GDBN} asks confirmation, unless you have @code{set |
3585 | confirm off}). You can abbreviate this command as @code{d}. | |
3586 | @end table | |
3587 | ||
6d2ebf8b | 3588 | @node Disabling |
79a6e687 | 3589 | @subsection Disabling Breakpoints |
c906108c | 3590 | |
4644b6e3 | 3591 | @cindex enable/disable a breakpoint |
c906108c SS |
3592 | Rather than deleting a breakpoint, watchpoint, or catchpoint, you might |
3593 | prefer to @dfn{disable} it. This makes the breakpoint inoperative as if | |
3594 | it had been deleted, but remembers the information on the breakpoint so | |
3595 | that you can @dfn{enable} it again later. | |
3596 | ||
3597 | You disable and enable breakpoints, watchpoints, and catchpoints with | |
3598 | the @code{enable} and @code{disable} commands, optionally specifying one | |
3599 | or more breakpoint numbers as arguments. Use @code{info break} or | |
3600 | @code{info watch} to print a list of breakpoints, watchpoints, and | |
3601 | catchpoints if you do not know which numbers to use. | |
3602 | ||
3b784c4f EZ |
3603 | Disabling and enabling a breakpoint that has multiple locations |
3604 | affects all of its locations. | |
3605 | ||
c906108c SS |
3606 | A breakpoint, watchpoint, or catchpoint can have any of four different |
3607 | states of enablement: | |
3608 | ||
3609 | @itemize @bullet | |
3610 | @item | |
3611 | Enabled. The breakpoint stops your program. A breakpoint set | |
3612 | with the @code{break} command starts out in this state. | |
3613 | @item | |
3614 | Disabled. The breakpoint has no effect on your program. | |
3615 | @item | |
3616 | Enabled once. The breakpoint stops your program, but then becomes | |
d4f3574e | 3617 | disabled. |
c906108c SS |
3618 | @item |
3619 | Enabled for deletion. The breakpoint stops your program, but | |
d4f3574e SS |
3620 | immediately after it does so it is deleted permanently. A breakpoint |
3621 | set with the @code{tbreak} command starts out in this state. | |
c906108c SS |
3622 | @end itemize |
3623 | ||
3624 | You can use the following commands to enable or disable breakpoints, | |
3625 | watchpoints, and catchpoints: | |
3626 | ||
3627 | @table @code | |
c906108c | 3628 | @kindex disable |
41afff9a | 3629 | @kindex dis @r{(@code{disable})} |
c5394b80 | 3630 | @item disable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
c906108c SS |
3631 | Disable the specified breakpoints---or all breakpoints, if none are |
3632 | listed. A disabled breakpoint has no effect but is not forgotten. All | |
3633 | options such as ignore-counts, conditions and commands are remembered in | |
3634 | case the breakpoint is enabled again later. You may abbreviate | |
3635 | @code{disable} as @code{dis}. | |
3636 | ||
c906108c | 3637 | @kindex enable |
c5394b80 | 3638 | @item enable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
c906108c SS |
3639 | Enable the specified breakpoints (or all defined breakpoints). They |
3640 | become effective once again in stopping your program. | |
3641 | ||
c5394b80 | 3642 | @item enable @r{[}breakpoints@r{]} once @var{range}@dots{} |
c906108c SS |
3643 | Enable the specified breakpoints temporarily. @value{GDBN} disables any |
3644 | of these breakpoints immediately after stopping your program. | |
3645 | ||
c5394b80 | 3646 | @item enable @r{[}breakpoints@r{]} delete @var{range}@dots{} |
c906108c SS |
3647 | Enable the specified breakpoints to work once, then die. @value{GDBN} |
3648 | deletes any of these breakpoints as soon as your program stops there. | |
09d4efe1 | 3649 | Breakpoints set by the @code{tbreak} command start out in this state. |
c906108c SS |
3650 | @end table |
3651 | ||
d4f3574e SS |
3652 | @c FIXME: I think the following ``Except for [...] @code{tbreak}'' is |
3653 | @c confusing: tbreak is also initially enabled. | |
c906108c | 3654 | Except for a breakpoint set with @code{tbreak} (@pxref{Set Breaks, |
79a6e687 | 3655 | ,Setting Breakpoints}), breakpoints that you set are initially enabled; |
c906108c SS |
3656 | subsequently, they become disabled or enabled only when you use one of |
3657 | the commands above. (The command @code{until} can set and delete a | |
3658 | breakpoint of its own, but it does not change the state of your other | |
3659 | breakpoints; see @ref{Continuing and Stepping, ,Continuing and | |
79a6e687 | 3660 | Stepping}.) |
c906108c | 3661 | |
6d2ebf8b | 3662 | @node Conditions |
79a6e687 | 3663 | @subsection Break Conditions |
c906108c SS |
3664 | @cindex conditional breakpoints |
3665 | @cindex breakpoint conditions | |
3666 | ||
3667 | @c FIXME what is scope of break condition expr? Context where wanted? | |
5d161b24 | 3668 | @c in particular for a watchpoint? |
c906108c SS |
3669 | The simplest sort of breakpoint breaks every time your program reaches a |
3670 | specified place. You can also specify a @dfn{condition} for a | |
3671 | breakpoint. A condition is just a Boolean expression in your | |
3672 | programming language (@pxref{Expressions, ,Expressions}). A breakpoint with | |
3673 | a condition evaluates the expression each time your program reaches it, | |
3674 | and your program stops only if the condition is @emph{true}. | |
3675 | ||
3676 | This is the converse of using assertions for program validation; in that | |
3677 | situation, you want to stop when the assertion is violated---that is, | |
3678 | when the condition is false. In C, if you want to test an assertion expressed | |
3679 | by the condition @var{assert}, you should set the condition | |
3680 | @samp{! @var{assert}} on the appropriate breakpoint. | |
3681 | ||
3682 | Conditions are also accepted for watchpoints; you may not need them, | |
3683 | since a watchpoint is inspecting the value of an expression anyhow---but | |
3684 | it might be simpler, say, to just set a watchpoint on a variable name, | |
3685 | and specify a condition that tests whether the new value is an interesting | |
3686 | one. | |
3687 | ||
3688 | Break conditions can have side effects, and may even call functions in | |
3689 | your program. This can be useful, for example, to activate functions | |
3690 | that log program progress, or to use your own print functions to | |
3691 | format special data structures. The effects are completely predictable | |
3692 | unless there is another enabled breakpoint at the same address. (In | |
3693 | that case, @value{GDBN} might see the other breakpoint first and stop your | |
3694 | program without checking the condition of this one.) Note that | |
d4f3574e SS |
3695 | breakpoint commands are usually more convenient and flexible than break |
3696 | conditions for the | |
c906108c | 3697 | purpose of performing side effects when a breakpoint is reached |
79a6e687 | 3698 | (@pxref{Break Commands, ,Breakpoint Command Lists}). |
c906108c SS |
3699 | |
3700 | Break conditions can be specified when a breakpoint is set, by using | |
3701 | @samp{if} in the arguments to the @code{break} command. @xref{Set | |
79a6e687 | 3702 | Breaks, ,Setting Breakpoints}. They can also be changed at any time |
c906108c | 3703 | with the @code{condition} command. |
53a5351d | 3704 | |
c906108c SS |
3705 | You can also use the @code{if} keyword with the @code{watch} command. |
3706 | The @code{catch} command does not recognize the @code{if} keyword; | |
3707 | @code{condition} is the only way to impose a further condition on a | |
3708 | catchpoint. | |
c906108c SS |
3709 | |
3710 | @table @code | |
3711 | @kindex condition | |
3712 | @item condition @var{bnum} @var{expression} | |
3713 | Specify @var{expression} as the break condition for breakpoint, | |
3714 | watchpoint, or catchpoint number @var{bnum}. After you set a condition, | |
3715 | breakpoint @var{bnum} stops your program only if the value of | |
3716 | @var{expression} is true (nonzero, in C). When you use | |
3717 | @code{condition}, @value{GDBN} checks @var{expression} immediately for | |
3718 | syntactic correctness, and to determine whether symbols in it have | |
d4f3574e SS |
3719 | referents in the context of your breakpoint. If @var{expression} uses |
3720 | symbols not referenced in the context of the breakpoint, @value{GDBN} | |
3721 | prints an error message: | |
3722 | ||
474c8240 | 3723 | @smallexample |
d4f3574e | 3724 | No symbol "foo" in current context. |
474c8240 | 3725 | @end smallexample |
d4f3574e SS |
3726 | |
3727 | @noindent | |
c906108c SS |
3728 | @value{GDBN} does |
3729 | not actually evaluate @var{expression} at the time the @code{condition} | |
d4f3574e SS |
3730 | command (or a command that sets a breakpoint with a condition, like |
3731 | @code{break if @dots{}}) is given, however. @xref{Expressions, ,Expressions}. | |
c906108c SS |
3732 | |
3733 | @item condition @var{bnum} | |
3734 | Remove the condition from breakpoint number @var{bnum}. It becomes | |
3735 | an ordinary unconditional breakpoint. | |
3736 | @end table | |
3737 | ||
3738 | @cindex ignore count (of breakpoint) | |
3739 | A special case of a breakpoint condition is to stop only when the | |
3740 | breakpoint has been reached a certain number of times. This is so | |
3741 | useful that there is a special way to do it, using the @dfn{ignore | |
3742 | count} of the breakpoint. Every breakpoint has an ignore count, which | |
3743 | is an integer. Most of the time, the ignore count is zero, and | |
3744 | therefore has no effect. But if your program reaches a breakpoint whose | |
3745 | ignore count is positive, then instead of stopping, it just decrements | |
3746 | the ignore count by one and continues. As a result, if the ignore count | |
3747 | value is @var{n}, the breakpoint does not stop the next @var{n} times | |
3748 | your program reaches it. | |
3749 | ||
3750 | @table @code | |
3751 | @kindex ignore | |
3752 | @item ignore @var{bnum} @var{count} | |
3753 | Set the ignore count of breakpoint number @var{bnum} to @var{count}. | |
3754 | The next @var{count} times the breakpoint is reached, your program's | |
3755 | execution does not stop; other than to decrement the ignore count, @value{GDBN} | |
3756 | takes no action. | |
3757 | ||
3758 | To make the breakpoint stop the next time it is reached, specify | |
3759 | a count of zero. | |
3760 | ||
3761 | When you use @code{continue} to resume execution of your program from a | |
3762 | breakpoint, you can specify an ignore count directly as an argument to | |
3763 | @code{continue}, rather than using @code{ignore}. @xref{Continuing and | |
79a6e687 | 3764 | Stepping,,Continuing and Stepping}. |
c906108c SS |
3765 | |
3766 | If a breakpoint has a positive ignore count and a condition, the | |
3767 | condition is not checked. Once the ignore count reaches zero, | |
3768 | @value{GDBN} resumes checking the condition. | |
3769 | ||
3770 | You could achieve the effect of the ignore count with a condition such | |
3771 | as @w{@samp{$foo-- <= 0}} using a debugger convenience variable that | |
3772 | is decremented each time. @xref{Convenience Vars, ,Convenience | |
79a6e687 | 3773 | Variables}. |
c906108c SS |
3774 | @end table |
3775 | ||
3776 | Ignore counts apply to breakpoints, watchpoints, and catchpoints. | |
3777 | ||
3778 | ||
6d2ebf8b | 3779 | @node Break Commands |
79a6e687 | 3780 | @subsection Breakpoint Command Lists |
c906108c SS |
3781 | |
3782 | @cindex breakpoint commands | |
3783 | You can give any breakpoint (or watchpoint or catchpoint) a series of | |
3784 | commands to execute when your program stops due to that breakpoint. For | |
3785 | example, you might want to print the values of certain expressions, or | |
3786 | enable other breakpoints. | |
3787 | ||
3788 | @table @code | |
3789 | @kindex commands | |
ca91424e | 3790 | @kindex end@r{ (breakpoint commands)} |
c906108c SS |
3791 | @item commands @r{[}@var{bnum}@r{]} |
3792 | @itemx @dots{} @var{command-list} @dots{} | |
3793 | @itemx end | |
3794 | Specify a list of commands for breakpoint number @var{bnum}. The commands | |
3795 | themselves appear on the following lines. Type a line containing just | |
3796 | @code{end} to terminate the commands. | |
3797 | ||
3798 | To remove all commands from a breakpoint, type @code{commands} and | |
3799 | follow it immediately with @code{end}; that is, give no commands. | |
3800 | ||
3801 | With no @var{bnum} argument, @code{commands} refers to the last | |
3802 | breakpoint, watchpoint, or catchpoint set (not to the breakpoint most | |
3803 | recently encountered). | |
3804 | @end table | |
3805 | ||
3806 | Pressing @key{RET} as a means of repeating the last @value{GDBN} command is | |
3807 | disabled within a @var{command-list}. | |
3808 | ||
3809 | You can use breakpoint commands to start your program up again. Simply | |
3810 | use the @code{continue} command, or @code{step}, or any other command | |
3811 | that resumes execution. | |
3812 | ||
3813 | Any other commands in the command list, after a command that resumes | |
3814 | execution, are ignored. This is because any time you resume execution | |
3815 | (even with a simple @code{next} or @code{step}), you may encounter | |
3816 | another breakpoint---which could have its own command list, leading to | |
3817 | ambiguities about which list to execute. | |
3818 | ||
3819 | @kindex silent | |
3820 | If the first command you specify in a command list is @code{silent}, the | |
3821 | usual message about stopping at a breakpoint is not printed. This may | |
3822 | be desirable for breakpoints that are to print a specific message and | |
3823 | then continue. If none of the remaining commands print anything, you | |
3824 | see no sign that the breakpoint was reached. @code{silent} is | |
3825 | meaningful only at the beginning of a breakpoint command list. | |
3826 | ||
3827 | The commands @code{echo}, @code{output}, and @code{printf} allow you to | |
3828 | print precisely controlled output, and are often useful in silent | |
79a6e687 | 3829 | breakpoints. @xref{Output, ,Commands for Controlled Output}. |
c906108c SS |
3830 | |
3831 | For example, here is how you could use breakpoint commands to print the | |
3832 | value of @code{x} at entry to @code{foo} whenever @code{x} is positive. | |
3833 | ||
474c8240 | 3834 | @smallexample |
c906108c SS |
3835 | break foo if x>0 |
3836 | commands | |
3837 | silent | |
3838 | printf "x is %d\n",x | |
3839 | cont | |
3840 | end | |
474c8240 | 3841 | @end smallexample |
c906108c SS |
3842 | |
3843 | One application for breakpoint commands is to compensate for one bug so | |
3844 | you can test for another. Put a breakpoint just after the erroneous line | |
3845 | of code, give it a condition to detect the case in which something | |
3846 | erroneous has been done, and give it commands to assign correct values | |
3847 | to any variables that need them. End with the @code{continue} command | |
3848 | so that your program does not stop, and start with the @code{silent} | |
3849 | command so that no output is produced. Here is an example: | |
3850 | ||
474c8240 | 3851 | @smallexample |
c906108c SS |
3852 | break 403 |
3853 | commands | |
3854 | silent | |
3855 | set x = y + 4 | |
3856 | cont | |
3857 | end | |
474c8240 | 3858 | @end smallexample |
c906108c | 3859 | |
6d2ebf8b | 3860 | @node Breakpoint Menus |
79a6e687 | 3861 | @subsection Breakpoint Menus |
c906108c SS |
3862 | @cindex overloading |
3863 | @cindex symbol overloading | |
3864 | ||
b383017d | 3865 | Some programming languages (notably C@t{++} and Objective-C) permit a |
b37303ee | 3866 | single function name |
c906108c SS |
3867 | to be defined several times, for application in different contexts. |
3868 | This is called @dfn{overloading}. When a function name is overloaded, | |
3869 | @samp{break @var{function}} is not enough to tell @value{GDBN} where you want | |
3b784c4f EZ |
3870 | a breakpoint. You can use explicit signature of the function, as in |
3871 | @samp{break @var{function}(@var{types})}, to specify which | |
c906108c SS |
3872 | particular version of the function you want. Otherwise, @value{GDBN} offers |
3873 | you a menu of numbered choices for different possible breakpoints, and | |
3874 | waits for your selection with the prompt @samp{>}. The first two | |
3875 | options are always @samp{[0] cancel} and @samp{[1] all}. Typing @kbd{1} | |
3876 | sets a breakpoint at each definition of @var{function}, and typing | |
3877 | @kbd{0} aborts the @code{break} command without setting any new | |
3878 | breakpoints. | |
3879 | ||
3880 | For example, the following session excerpt shows an attempt to set a | |
3881 | breakpoint at the overloaded symbol @code{String::after}. | |
3882 | We choose three particular definitions of that function name: | |
3883 | ||
3884 | @c FIXME! This is likely to change to show arg type lists, at least | |
3885 | @smallexample | |
3886 | @group | |
3887 | (@value{GDBP}) b String::after | |
3888 | [0] cancel | |
3889 | [1] all | |
3890 | [2] file:String.cc; line number:867 | |
3891 | [3] file:String.cc; line number:860 | |
3892 | [4] file:String.cc; line number:875 | |
3893 | [5] file:String.cc; line number:853 | |
3894 | [6] file:String.cc; line number:846 | |
3895 | [7] file:String.cc; line number:735 | |
3896 | > 2 4 6 | |
3897 | Breakpoint 1 at 0xb26c: file String.cc, line 867. | |
3898 | Breakpoint 2 at 0xb344: file String.cc, line 875. | |
3899 | Breakpoint 3 at 0xafcc: file String.cc, line 846. | |
3900 | Multiple breakpoints were set. | |
3901 | Use the "delete" command to delete unwanted | |
3902 | breakpoints. | |
3903 | (@value{GDBP}) | |
3904 | @end group | |
3905 | @end smallexample | |
c906108c SS |
3906 | |
3907 | @c @ifclear BARETARGET | |
6d2ebf8b | 3908 | @node Error in Breakpoints |
d4f3574e | 3909 | @subsection ``Cannot insert breakpoints'' |
c906108c SS |
3910 | @c |
3911 | @c FIXME!! 14/6/95 Is there a real example of this? Let's use it. | |
3912 | @c | |
d4f3574e SS |
3913 | Under some operating systems, breakpoints cannot be used in a program if |
3914 | any other process is running that program. In this situation, | |
5d161b24 | 3915 | attempting to run or continue a program with a breakpoint causes |
d4f3574e SS |
3916 | @value{GDBN} to print an error message: |
3917 | ||
474c8240 | 3918 | @smallexample |
d4f3574e SS |
3919 | Cannot insert breakpoints. |
3920 | The same program may be running in another process. | |
474c8240 | 3921 | @end smallexample |
d4f3574e SS |
3922 | |
3923 | When this happens, you have three ways to proceed: | |
3924 | ||
3925 | @enumerate | |
3926 | @item | |
3927 | Remove or disable the breakpoints, then continue. | |
3928 | ||
3929 | @item | |
5d161b24 | 3930 | Suspend @value{GDBN}, and copy the file containing your program to a new |
d4f3574e | 3931 | name. Resume @value{GDBN} and use the @code{exec-file} command to specify |
5d161b24 | 3932 | that @value{GDBN} should run your program under that name. |
d4f3574e SS |
3933 | Then start your program again. |
3934 | ||
3935 | @item | |
3936 | Relink your program so that the text segment is nonsharable, using the | |
3937 | linker option @samp{-N}. The operating system limitation may not apply | |
3938 | to nonsharable executables. | |
3939 | @end enumerate | |
c906108c SS |
3940 | @c @end ifclear |
3941 | ||
d4f3574e SS |
3942 | A similar message can be printed if you request too many active |
3943 | hardware-assisted breakpoints and watchpoints: | |
3944 | ||
3945 | @c FIXME: the precise wording of this message may change; the relevant | |
3946 | @c source change is not committed yet (Sep 3, 1999). | |
3947 | @smallexample | |
3948 | Stopped; cannot insert breakpoints. | |
3949 | You may have requested too many hardware breakpoints and watchpoints. | |
3950 | @end smallexample | |
3951 | ||
3952 | @noindent | |
3953 | This message is printed when you attempt to resume the program, since | |
3954 | only then @value{GDBN} knows exactly how many hardware breakpoints and | |
3955 | watchpoints it needs to insert. | |
3956 | ||
3957 | When this message is printed, you need to disable or remove some of the | |
3958 | hardware-assisted breakpoints and watchpoints, and then continue. | |
3959 | ||
79a6e687 | 3960 | @node Breakpoint-related Warnings |
1485d690 KB |
3961 | @subsection ``Breakpoint address adjusted...'' |
3962 | @cindex breakpoint address adjusted | |
3963 | ||
3964 | Some processor architectures place constraints on the addresses at | |
3965 | which breakpoints may be placed. For architectures thus constrained, | |
3966 | @value{GDBN} will attempt to adjust the breakpoint's address to comply | |
3967 | with the constraints dictated by the architecture. | |
3968 | ||
3969 | One example of such an architecture is the Fujitsu FR-V. The FR-V is | |
3970 | a VLIW architecture in which a number of RISC-like instructions may be | |
3971 | bundled together for parallel execution. The FR-V architecture | |
3972 | constrains the location of a breakpoint instruction within such a | |
3973 | bundle to the instruction with the lowest address. @value{GDBN} | |
3974 | honors this constraint by adjusting a breakpoint's address to the | |
3975 | first in the bundle. | |
3976 | ||
3977 | It is not uncommon for optimized code to have bundles which contain | |
3978 | instructions from different source statements, thus it may happen that | |
3979 | a breakpoint's address will be adjusted from one source statement to | |
3980 | another. Since this adjustment may significantly alter @value{GDBN}'s | |
3981 | breakpoint related behavior from what the user expects, a warning is | |
3982 | printed when the breakpoint is first set and also when the breakpoint | |
3983 | is hit. | |
3984 | ||
3985 | A warning like the one below is printed when setting a breakpoint | |
3986 | that's been subject to address adjustment: | |
3987 | ||
3988 | @smallexample | |
3989 | warning: Breakpoint address adjusted from 0x00010414 to 0x00010410. | |
3990 | @end smallexample | |
3991 | ||
3992 | Such warnings are printed both for user settable and @value{GDBN}'s | |
3993 | internal breakpoints. If you see one of these warnings, you should | |
3994 | verify that a breakpoint set at the adjusted address will have the | |
3995 | desired affect. If not, the breakpoint in question may be removed and | |
b383017d | 3996 | other breakpoints may be set which will have the desired behavior. |
1485d690 KB |
3997 | E.g., it may be sufficient to place the breakpoint at a later |
3998 | instruction. A conditional breakpoint may also be useful in some | |
3999 | cases to prevent the breakpoint from triggering too often. | |
4000 | ||
4001 | @value{GDBN} will also issue a warning when stopping at one of these | |
4002 | adjusted breakpoints: | |
4003 | ||
4004 | @smallexample | |
4005 | warning: Breakpoint 1 address previously adjusted from 0x00010414 | |
4006 | to 0x00010410. | |
4007 | @end smallexample | |
4008 | ||
4009 | When this warning is encountered, it may be too late to take remedial | |
4010 | action except in cases where the breakpoint is hit earlier or more | |
4011 | frequently than expected. | |
d4f3574e | 4012 | |
6d2ebf8b | 4013 | @node Continuing and Stepping |
79a6e687 | 4014 | @section Continuing and Stepping |
c906108c SS |
4015 | |
4016 | @cindex stepping | |
4017 | @cindex continuing | |
4018 | @cindex resuming execution | |
4019 | @dfn{Continuing} means resuming program execution until your program | |
4020 | completes normally. In contrast, @dfn{stepping} means executing just | |
4021 | one more ``step'' of your program, where ``step'' may mean either one | |
4022 | line of source code, or one machine instruction (depending on what | |
7a292a7a SS |
4023 | particular command you use). Either when continuing or when stepping, |
4024 | your program may stop even sooner, due to a breakpoint or a signal. (If | |
d4f3574e SS |
4025 | it stops due to a signal, you may want to use @code{handle}, or use |
4026 | @samp{signal 0} to resume execution. @xref{Signals, ,Signals}.) | |
c906108c SS |
4027 | |
4028 | @table @code | |
4029 | @kindex continue | |
41afff9a EZ |
4030 | @kindex c @r{(@code{continue})} |
4031 | @kindex fg @r{(resume foreground execution)} | |
c906108c SS |
4032 | @item continue @r{[}@var{ignore-count}@r{]} |
4033 | @itemx c @r{[}@var{ignore-count}@r{]} | |
4034 | @itemx fg @r{[}@var{ignore-count}@r{]} | |
4035 | Resume program execution, at the address where your program last stopped; | |
4036 | any breakpoints set at that address are bypassed. The optional argument | |
4037 | @var{ignore-count} allows you to specify a further number of times to | |
4038 | ignore a breakpoint at this location; its effect is like that of | |
79a6e687 | 4039 | @code{ignore} (@pxref{Conditions, ,Break Conditions}). |
c906108c SS |
4040 | |
4041 | The argument @var{ignore-count} is meaningful only when your program | |
4042 | stopped due to a breakpoint. At other times, the argument to | |
4043 | @code{continue} is ignored. | |
4044 | ||
d4f3574e SS |
4045 | The synonyms @code{c} and @code{fg} (for @dfn{foreground}, as the |
4046 | debugged program is deemed to be the foreground program) are provided | |
4047 | purely for convenience, and have exactly the same behavior as | |
4048 | @code{continue}. | |
c906108c SS |
4049 | @end table |
4050 | ||
4051 | To resume execution at a different place, you can use @code{return} | |
79a6e687 | 4052 | (@pxref{Returning, ,Returning from a Function}) to go back to the |
c906108c | 4053 | calling function; or @code{jump} (@pxref{Jumping, ,Continuing at a |
79a6e687 | 4054 | Different Address}) to go to an arbitrary location in your program. |
c906108c SS |
4055 | |
4056 | A typical technique for using stepping is to set a breakpoint | |
79a6e687 | 4057 | (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Catchpoints}) at the |
c906108c SS |
4058 | beginning of the function or the section of your program where a problem |
4059 | is believed to lie, run your program until it stops at that breakpoint, | |
4060 | and then step through the suspect area, examining the variables that are | |
4061 | interesting, until you see the problem happen. | |
4062 | ||
4063 | @table @code | |
4064 | @kindex step | |
41afff9a | 4065 | @kindex s @r{(@code{step})} |
c906108c SS |
4066 | @item step |
4067 | Continue running your program until control reaches a different source | |
4068 | line, then stop it and return control to @value{GDBN}. This command is | |
4069 | abbreviated @code{s}. | |
4070 | ||
4071 | @quotation | |
4072 | @c "without debugging information" is imprecise; actually "without line | |
4073 | @c numbers in the debugging information". (gcc -g1 has debugging info but | |
4074 | @c not line numbers). But it seems complex to try to make that | |
4075 | @c distinction here. | |
4076 | @emph{Warning:} If you use the @code{step} command while control is | |
4077 | within a function that was compiled without debugging information, | |
4078 | execution proceeds until control reaches a function that does have | |
4079 | debugging information. Likewise, it will not step into a function which | |
4080 | is compiled without debugging information. To step through functions | |
4081 | without debugging information, use the @code{stepi} command, described | |
4082 | below. | |
4083 | @end quotation | |
4084 | ||
4a92d011 EZ |
4085 | The @code{step} command only stops at the first instruction of a source |
4086 | line. This prevents the multiple stops that could otherwise occur in | |
4087 | @code{switch} statements, @code{for} loops, etc. @code{step} continues | |
4088 | to stop if a function that has debugging information is called within | |
4089 | the line. In other words, @code{step} @emph{steps inside} any functions | |
4090 | called within the line. | |
c906108c | 4091 | |
d4f3574e SS |
4092 | Also, the @code{step} command only enters a function if there is line |
4093 | number information for the function. Otherwise it acts like the | |
5d161b24 | 4094 | @code{next} command. This avoids problems when using @code{cc -gl} |
c906108c | 4095 | on MIPS machines. Previously, @code{step} entered subroutines if there |
5d161b24 | 4096 | was any debugging information about the routine. |
c906108c SS |
4097 | |
4098 | @item step @var{count} | |
4099 | Continue running as in @code{step}, but do so @var{count} times. If a | |
7a292a7a SS |
4100 | breakpoint is reached, or a signal not related to stepping occurs before |
4101 | @var{count} steps, stepping stops right away. | |
c906108c SS |
4102 | |
4103 | @kindex next | |
41afff9a | 4104 | @kindex n @r{(@code{next})} |
c906108c SS |
4105 | @item next @r{[}@var{count}@r{]} |
4106 | Continue to the next source line in the current (innermost) stack frame. | |
7a292a7a SS |
4107 | This is similar to @code{step}, but function calls that appear within |
4108 | the line of code are executed without stopping. Execution stops when | |
4109 | control reaches a different line of code at the original stack level | |
4110 | that was executing when you gave the @code{next} command. This command | |
4111 | is abbreviated @code{n}. | |
c906108c SS |
4112 | |
4113 | An argument @var{count} is a repeat count, as for @code{step}. | |
4114 | ||
4115 | ||
4116 | @c FIX ME!! Do we delete this, or is there a way it fits in with | |
4117 | @c the following paragraph? --- Vctoria | |
4118 | @c | |
4119 | @c @code{next} within a function that lacks debugging information acts like | |
4120 | @c @code{step}, but any function calls appearing within the code of the | |
4121 | @c function are executed without stopping. | |
4122 | ||
d4f3574e SS |
4123 | The @code{next} command only stops at the first instruction of a |
4124 | source line. This prevents multiple stops that could otherwise occur in | |
4a92d011 | 4125 | @code{switch} statements, @code{for} loops, etc. |
c906108c | 4126 | |
b90a5f51 CF |
4127 | @kindex set step-mode |
4128 | @item set step-mode | |
4129 | @cindex functions without line info, and stepping | |
4130 | @cindex stepping into functions with no line info | |
4131 | @itemx set step-mode on | |
4a92d011 | 4132 | The @code{set step-mode on} command causes the @code{step} command to |
b90a5f51 CF |
4133 | stop at the first instruction of a function which contains no debug line |
4134 | information rather than stepping over it. | |
4135 | ||
4a92d011 EZ |
4136 | This is useful in cases where you may be interested in inspecting the |
4137 | machine instructions of a function which has no symbolic info and do not | |
4138 | want @value{GDBN} to automatically skip over this function. | |
b90a5f51 CF |
4139 | |
4140 | @item set step-mode off | |
4a92d011 | 4141 | Causes the @code{step} command to step over any functions which contains no |
b90a5f51 CF |
4142 | debug information. This is the default. |
4143 | ||
9c16f35a EZ |
4144 | @item show step-mode |
4145 | Show whether @value{GDBN} will stop in or step over functions without | |
4146 | source line debug information. | |
4147 | ||
c906108c SS |
4148 | @kindex finish |
4149 | @item finish | |
4150 | Continue running until just after function in the selected stack frame | |
4151 | returns. Print the returned value (if any). | |
4152 | ||
4153 | Contrast this with the @code{return} command (@pxref{Returning, | |
79a6e687 | 4154 | ,Returning from a Function}). |
c906108c SS |
4155 | |
4156 | @kindex until | |
41afff9a | 4157 | @kindex u @r{(@code{until})} |
09d4efe1 | 4158 | @cindex run until specified location |
c906108c SS |
4159 | @item until |
4160 | @itemx u | |
4161 | Continue running until a source line past the current line, in the | |
4162 | current stack frame, is reached. This command is used to avoid single | |
4163 | stepping through a loop more than once. It is like the @code{next} | |
4164 | command, except that when @code{until} encounters a jump, it | |
4165 | automatically continues execution until the program counter is greater | |
4166 | than the address of the jump. | |
4167 | ||
4168 | This means that when you reach the end of a loop after single stepping | |
4169 | though it, @code{until} makes your program continue execution until it | |
4170 | exits the loop. In contrast, a @code{next} command at the end of a loop | |
4171 | simply steps back to the beginning of the loop, which forces you to step | |
4172 | through the next iteration. | |
4173 | ||
4174 | @code{until} always stops your program if it attempts to exit the current | |
4175 | stack frame. | |
4176 | ||
4177 | @code{until} may produce somewhat counterintuitive results if the order | |
4178 | of machine code does not match the order of the source lines. For | |
4179 | example, in the following excerpt from a debugging session, the @code{f} | |
4180 | (@code{frame}) command shows that execution is stopped at line | |
4181 | @code{206}; yet when we use @code{until}, we get to line @code{195}: | |
4182 | ||
474c8240 | 4183 | @smallexample |
c906108c SS |
4184 | (@value{GDBP}) f |
4185 | #0 main (argc=4, argv=0xf7fffae8) at m4.c:206 | |
4186 | 206 expand_input(); | |
4187 | (@value{GDBP}) until | |
4188 | 195 for ( ; argc > 0; NEXTARG) @{ | |
474c8240 | 4189 | @end smallexample |
c906108c SS |
4190 | |
4191 | This happened because, for execution efficiency, the compiler had | |
4192 | generated code for the loop closure test at the end, rather than the | |
4193 | start, of the loop---even though the test in a C @code{for}-loop is | |
4194 | written before the body of the loop. The @code{until} command appeared | |
4195 | to step back to the beginning of the loop when it advanced to this | |
4196 | expression; however, it has not really gone to an earlier | |
4197 | statement---not in terms of the actual machine code. | |
4198 | ||
4199 | @code{until} with no argument works by means of single | |
4200 | instruction stepping, and hence is slower than @code{until} with an | |
4201 | argument. | |
4202 | ||
4203 | @item until @var{location} | |
4204 | @itemx u @var{location} | |
4205 | Continue running your program until either the specified location is | |
4206 | reached, or the current stack frame returns. @var{location} is any of | |
2a25a5ba EZ |
4207 | the forms described in @ref{Specify Location}. |
4208 | This form of the command uses temporary breakpoints, and | |
c60eb6f1 EZ |
4209 | hence is quicker than @code{until} without an argument. The specified |
4210 | location is actually reached only if it is in the current frame. This | |
4211 | implies that @code{until} can be used to skip over recursive function | |
4212 | invocations. For instance in the code below, if the current location is | |
4213 | line @code{96}, issuing @code{until 99} will execute the program up to | |
db2e3e2e | 4214 | line @code{99} in the same invocation of factorial, i.e., after the inner |
c60eb6f1 EZ |
4215 | invocations have returned. |
4216 | ||
4217 | @smallexample | |
4218 | 94 int factorial (int value) | |
4219 | 95 @{ | |
4220 | 96 if (value > 1) @{ | |
4221 | 97 value *= factorial (value - 1); | |
4222 | 98 @} | |
4223 | 99 return (value); | |
4224 | 100 @} | |
4225 | @end smallexample | |
4226 | ||
4227 | ||
4228 | @kindex advance @var{location} | |
4229 | @itemx advance @var{location} | |
09d4efe1 | 4230 | Continue running the program up to the given @var{location}. An argument is |
2a25a5ba EZ |
4231 | required, which should be of one of the forms described in |
4232 | @ref{Specify Location}. | |
4233 | Execution will also stop upon exit from the current stack | |
c60eb6f1 EZ |
4234 | frame. This command is similar to @code{until}, but @code{advance} will |
4235 | not skip over recursive function calls, and the target location doesn't | |
4236 | have to be in the same frame as the current one. | |
4237 | ||
c906108c SS |
4238 | |
4239 | @kindex stepi | |
41afff9a | 4240 | @kindex si @r{(@code{stepi})} |
c906108c | 4241 | @item stepi |
96a2c332 | 4242 | @itemx stepi @var{arg} |
c906108c SS |
4243 | @itemx si |
4244 | Execute one machine instruction, then stop and return to the debugger. | |
4245 | ||
4246 | It is often useful to do @samp{display/i $pc} when stepping by machine | |
4247 | instructions. This makes @value{GDBN} automatically display the next | |
4248 | instruction to be executed, each time your program stops. @xref{Auto | |
79a6e687 | 4249 | Display,, Automatic Display}. |
c906108c SS |
4250 | |
4251 | An argument is a repeat count, as in @code{step}. | |
4252 | ||
4253 | @need 750 | |
4254 | @kindex nexti | |
41afff9a | 4255 | @kindex ni @r{(@code{nexti})} |
c906108c | 4256 | @item nexti |
96a2c332 | 4257 | @itemx nexti @var{arg} |
c906108c SS |
4258 | @itemx ni |
4259 | Execute one machine instruction, but if it is a function call, | |
4260 | proceed until the function returns. | |
4261 | ||
4262 | An argument is a repeat count, as in @code{next}. | |
4263 | @end table | |
4264 | ||
6d2ebf8b | 4265 | @node Signals |
c906108c SS |
4266 | @section Signals |
4267 | @cindex signals | |
4268 | ||
4269 | A signal is an asynchronous event that can happen in a program. The | |
4270 | operating system defines the possible kinds of signals, and gives each | |
4271 | kind a name and a number. For example, in Unix @code{SIGINT} is the | |
c8aa23ab | 4272 | signal a program gets when you type an interrupt character (often @kbd{Ctrl-c}); |
c906108c SS |
4273 | @code{SIGSEGV} is the signal a program gets from referencing a place in |
4274 | memory far away from all the areas in use; @code{SIGALRM} occurs when | |
4275 | the alarm clock timer goes off (which happens only if your program has | |
4276 | requested an alarm). | |
4277 | ||
4278 | @cindex fatal signals | |
4279 | Some signals, including @code{SIGALRM}, are a normal part of the | |
4280 | functioning of your program. Others, such as @code{SIGSEGV}, indicate | |
d4f3574e | 4281 | errors; these signals are @dfn{fatal} (they kill your program immediately) if the |
c906108c SS |
4282 | program has not specified in advance some other way to handle the signal. |
4283 | @code{SIGINT} does not indicate an error in your program, but it is normally | |
4284 | fatal so it can carry out the purpose of the interrupt: to kill the program. | |
4285 | ||
4286 | @value{GDBN} has the ability to detect any occurrence of a signal in your | |
4287 | program. You can tell @value{GDBN} in advance what to do for each kind of | |
4288 | signal. | |
4289 | ||
4290 | @cindex handling signals | |
24f93129 EZ |
4291 | Normally, @value{GDBN} is set up to let the non-erroneous signals like |
4292 | @code{SIGALRM} be silently passed to your program | |
4293 | (so as not to interfere with their role in the program's functioning) | |
c906108c SS |
4294 | but to stop your program immediately whenever an error signal happens. |
4295 | You can change these settings with the @code{handle} command. | |
4296 | ||
4297 | @table @code | |
4298 | @kindex info signals | |
09d4efe1 | 4299 | @kindex info handle |
c906108c | 4300 | @item info signals |
96a2c332 | 4301 | @itemx info handle |
c906108c SS |
4302 | Print a table of all the kinds of signals and how @value{GDBN} has been told to |
4303 | handle each one. You can use this to see the signal numbers of all | |
4304 | the defined types of signals. | |
4305 | ||
45ac1734 EZ |
4306 | @item info signals @var{sig} |
4307 | Similar, but print information only about the specified signal number. | |
4308 | ||
d4f3574e | 4309 | @code{info handle} is an alias for @code{info signals}. |
c906108c SS |
4310 | |
4311 | @kindex handle | |
45ac1734 | 4312 | @item handle @var{signal} @r{[}@var{keywords}@dots{}@r{]} |
5ece1a18 EZ |
4313 | Change the way @value{GDBN} handles signal @var{signal}. @var{signal} |
4314 | can be the number of a signal or its name (with or without the | |
24f93129 | 4315 | @samp{SIG} at the beginning); a list of signal numbers of the form |
5ece1a18 | 4316 | @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the |
45ac1734 EZ |
4317 | known signals. Optional arguments @var{keywords}, described below, |
4318 | say what change to make. | |
c906108c SS |
4319 | @end table |
4320 | ||
4321 | @c @group | |
4322 | The keywords allowed by the @code{handle} command can be abbreviated. | |
4323 | Their full names are: | |
4324 | ||
4325 | @table @code | |
4326 | @item nostop | |
4327 | @value{GDBN} should not stop your program when this signal happens. It may | |
4328 | still print a message telling you that the signal has come in. | |
4329 | ||
4330 | @item stop | |
4331 | @value{GDBN} should stop your program when this signal happens. This implies | |
4332 | the @code{print} keyword as well. | |
4333 | ||
4334 | @item print | |
4335 | @value{GDBN} should print a message when this signal happens. | |
4336 | ||
4337 | @item noprint | |
4338 | @value{GDBN} should not mention the occurrence of the signal at all. This | |
4339 | implies the @code{nostop} keyword as well. | |
4340 | ||
4341 | @item pass | |
5ece1a18 | 4342 | @itemx noignore |
c906108c SS |
4343 | @value{GDBN} should allow your program to see this signal; your program |
4344 | can handle the signal, or else it may terminate if the signal is fatal | |
5ece1a18 | 4345 | and not handled. @code{pass} and @code{noignore} are synonyms. |
c906108c SS |
4346 | |
4347 | @item nopass | |
5ece1a18 | 4348 | @itemx ignore |
c906108c | 4349 | @value{GDBN} should not allow your program to see this signal. |
5ece1a18 | 4350 | @code{nopass} and @code{ignore} are synonyms. |
c906108c SS |
4351 | @end table |
4352 | @c @end group | |
4353 | ||
d4f3574e SS |
4354 | When a signal stops your program, the signal is not visible to the |
4355 | program until you | |
c906108c SS |
4356 | continue. Your program sees the signal then, if @code{pass} is in |
4357 | effect for the signal in question @emph{at that time}. In other words, | |
4358 | after @value{GDBN} reports a signal, you can use the @code{handle} | |
4359 | command with @code{pass} or @code{nopass} to control whether your | |
4360 | program sees that signal when you continue. | |
4361 | ||
24f93129 EZ |
4362 | The default is set to @code{nostop}, @code{noprint}, @code{pass} for |
4363 | non-erroneous signals such as @code{SIGALRM}, @code{SIGWINCH} and | |
4364 | @code{SIGCHLD}, and to @code{stop}, @code{print}, @code{pass} for the | |
4365 | erroneous signals. | |
4366 | ||
c906108c SS |
4367 | You can also use the @code{signal} command to prevent your program from |
4368 | seeing a signal, or cause it to see a signal it normally would not see, | |
4369 | or to give it any signal at any time. For example, if your program stopped | |
4370 | due to some sort of memory reference error, you might store correct | |
4371 | values into the erroneous variables and continue, hoping to see more | |
4372 | execution; but your program would probably terminate immediately as | |
4373 | a result of the fatal signal once it saw the signal. To prevent this, | |
4374 | you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your | |
79a6e687 | 4375 | Program a Signal}. |
c906108c | 4376 | |
6d2ebf8b | 4377 | @node Thread Stops |
79a6e687 | 4378 | @section Stopping and Starting Multi-thread Programs |
c906108c SS |
4379 | |
4380 | When your program has multiple threads (@pxref{Threads,, Debugging | |
79a6e687 | 4381 | Programs with Multiple Threads}), you can choose whether to set |
c906108c SS |
4382 | breakpoints on all threads, or on a particular thread. |
4383 | ||
4384 | @table @code | |
4385 | @cindex breakpoints and threads | |
4386 | @cindex thread breakpoints | |
4387 | @kindex break @dots{} thread @var{threadno} | |
4388 | @item break @var{linespec} thread @var{threadno} | |
4389 | @itemx break @var{linespec} thread @var{threadno} if @dots{} | |
4390 | @var{linespec} specifies source lines; there are several ways of | |
2a25a5ba EZ |
4391 | writing them (@pxref{Specify Location}), but the effect is always to |
4392 | specify some source line. | |
c906108c SS |
4393 | |
4394 | Use the qualifier @samp{thread @var{threadno}} with a breakpoint command | |
4395 | to specify that you only want @value{GDBN} to stop the program when a | |
4396 | particular thread reaches this breakpoint. @var{threadno} is one of the | |
4397 | numeric thread identifiers assigned by @value{GDBN}, shown in the first | |
4398 | column of the @samp{info threads} display. | |
4399 | ||
4400 | If you do not specify @samp{thread @var{threadno}} when you set a | |
4401 | breakpoint, the breakpoint applies to @emph{all} threads of your | |
4402 | program. | |
4403 | ||
4404 | You can use the @code{thread} qualifier on conditional breakpoints as | |
4405 | well; in this case, place @samp{thread @var{threadno}} before the | |
4406 | breakpoint condition, like this: | |
4407 | ||
4408 | @smallexample | |
2df3850c | 4409 | (@value{GDBP}) break frik.c:13 thread 28 if bartab > lim |
c906108c SS |
4410 | @end smallexample |
4411 | ||
4412 | @end table | |
4413 | ||
4414 | @cindex stopped threads | |
4415 | @cindex threads, stopped | |
4416 | Whenever your program stops under @value{GDBN} for any reason, | |
4417 | @emph{all} threads of execution stop, not just the current thread. This | |
4418 | allows you to examine the overall state of the program, including | |
4419 | switching between threads, without worrying that things may change | |
4420 | underfoot. | |
4421 | ||
36d86913 MC |
4422 | @cindex thread breakpoints and system calls |
4423 | @cindex system calls and thread breakpoints | |
4424 | @cindex premature return from system calls | |
4425 | There is an unfortunate side effect. If one thread stops for a | |
4426 | breakpoint, or for some other reason, and another thread is blocked in a | |
4427 | system call, then the system call may return prematurely. This is a | |
4428 | consequence of the interaction between multiple threads and the signals | |
4429 | that @value{GDBN} uses to implement breakpoints and other events that | |
4430 | stop execution. | |
4431 | ||
4432 | To handle this problem, your program should check the return value of | |
4433 | each system call and react appropriately. This is good programming | |
4434 | style anyways. | |
4435 | ||
4436 | For example, do not write code like this: | |
4437 | ||
4438 | @smallexample | |
4439 | sleep (10); | |
4440 | @end smallexample | |
4441 | ||
4442 | The call to @code{sleep} will return early if a different thread stops | |
4443 | at a breakpoint or for some other reason. | |
4444 | ||
4445 | Instead, write this: | |
4446 | ||
4447 | @smallexample | |
4448 | int unslept = 10; | |
4449 | while (unslept > 0) | |
4450 | unslept = sleep (unslept); | |
4451 | @end smallexample | |
4452 | ||
4453 | A system call is allowed to return early, so the system is still | |
4454 | conforming to its specification. But @value{GDBN} does cause your | |
4455 | multi-threaded program to behave differently than it would without | |
4456 | @value{GDBN}. | |
4457 | ||
4458 | Also, @value{GDBN} uses internal breakpoints in the thread library to | |
4459 | monitor certain events such as thread creation and thread destruction. | |
4460 | When such an event happens, a system call in another thread may return | |
4461 | prematurely, even though your program does not appear to stop. | |
4462 | ||
c906108c SS |
4463 | @cindex continuing threads |
4464 | @cindex threads, continuing | |
4465 | Conversely, whenever you restart the program, @emph{all} threads start | |
4466 | executing. @emph{This is true even when single-stepping} with commands | |
5d161b24 | 4467 | like @code{step} or @code{next}. |
c906108c SS |
4468 | |
4469 | In particular, @value{GDBN} cannot single-step all threads in lockstep. | |
4470 | Since thread scheduling is up to your debugging target's operating | |
4471 | system (not controlled by @value{GDBN}), other threads may | |
4472 | execute more than one statement while the current thread completes a | |
4473 | single step. Moreover, in general other threads stop in the middle of a | |
4474 | statement, rather than at a clean statement boundary, when the program | |
4475 | stops. | |
4476 | ||
4477 | You might even find your program stopped in another thread after | |
4478 | continuing or even single-stepping. This happens whenever some other | |
4479 | thread runs into a breakpoint, a signal, or an exception before the | |
4480 | first thread completes whatever you requested. | |
4481 | ||
4482 | On some OSes, you can lock the OS scheduler and thus allow only a single | |
4483 | thread to run. | |
4484 | ||
4485 | @table @code | |
4486 | @item set scheduler-locking @var{mode} | |
9c16f35a EZ |
4487 | @cindex scheduler locking mode |
4488 | @cindex lock scheduler | |
c906108c SS |
4489 | Set the scheduler locking mode. If it is @code{off}, then there is no |
4490 | locking and any thread may run at any time. If @code{on}, then only the | |
4491 | current thread may run when the inferior is resumed. The @code{step} | |
4492 | mode optimizes for single-stepping. It stops other threads from | |
4493 | ``seizing the prompt'' by preempting the current thread while you are | |
4494 | stepping. Other threads will only rarely (or never) get a chance to run | |
d4f3574e | 4495 | when you step. They are more likely to run when you @samp{next} over a |
c906108c | 4496 | function call, and they are completely free to run when you use commands |
d4f3574e | 4497 | like @samp{continue}, @samp{until}, or @samp{finish}. However, unless another |
c906108c | 4498 | thread hits a breakpoint during its timeslice, they will never steal the |
2df3850c | 4499 | @value{GDBN} prompt away from the thread that you are debugging. |
c906108c SS |
4500 | |
4501 | @item show scheduler-locking | |
4502 | Display the current scheduler locking mode. | |
4503 | @end table | |
4504 | ||
c906108c | 4505 | |
6d2ebf8b | 4506 | @node Stack |
c906108c SS |
4507 | @chapter Examining the Stack |
4508 | ||
4509 | When your program has stopped, the first thing you need to know is where it | |
4510 | stopped and how it got there. | |
4511 | ||
4512 | @cindex call stack | |
5d161b24 DB |
4513 | Each time your program performs a function call, information about the call |
4514 | is generated. | |
4515 | That information includes the location of the call in your program, | |
4516 | the arguments of the call, | |
c906108c | 4517 | and the local variables of the function being called. |
5d161b24 | 4518 | The information is saved in a block of data called a @dfn{stack frame}. |
c906108c SS |
4519 | The stack frames are allocated in a region of memory called the @dfn{call |
4520 | stack}. | |
4521 | ||
4522 | When your program stops, the @value{GDBN} commands for examining the | |
4523 | stack allow you to see all of this information. | |
4524 | ||
4525 | @cindex selected frame | |
4526 | One of the stack frames is @dfn{selected} by @value{GDBN} and many | |
4527 | @value{GDBN} commands refer implicitly to the selected frame. In | |
4528 | particular, whenever you ask @value{GDBN} for the value of a variable in | |
4529 | your program, the value is found in the selected frame. There are | |
4530 | special @value{GDBN} commands to select whichever frame you are | |
79a6e687 | 4531 | interested in. @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
4532 | |
4533 | When your program stops, @value{GDBN} automatically selects the | |
5d161b24 | 4534 | currently executing frame and describes it briefly, similar to the |
79a6e687 | 4535 | @code{frame} command (@pxref{Frame Info, ,Information about a Frame}). |
c906108c SS |
4536 | |
4537 | @menu | |
4538 | * Frames:: Stack frames | |
4539 | * Backtrace:: Backtraces | |
4540 | * Selection:: Selecting a frame | |
4541 | * Frame Info:: Information on a frame | |
c906108c SS |
4542 | |
4543 | @end menu | |
4544 | ||
6d2ebf8b | 4545 | @node Frames |
79a6e687 | 4546 | @section Stack Frames |
c906108c | 4547 | |
d4f3574e | 4548 | @cindex frame, definition |
c906108c SS |
4549 | @cindex stack frame |
4550 | The call stack is divided up into contiguous pieces called @dfn{stack | |
4551 | frames}, or @dfn{frames} for short; each frame is the data associated | |
4552 | with one call to one function. The frame contains the arguments given | |
4553 | to the function, the function's local variables, and the address at | |
4554 | which the function is executing. | |
4555 | ||
4556 | @cindex initial frame | |
4557 | @cindex outermost frame | |
4558 | @cindex innermost frame | |
4559 | When your program is started, the stack has only one frame, that of the | |
4560 | function @code{main}. This is called the @dfn{initial} frame or the | |
4561 | @dfn{outermost} frame. Each time a function is called, a new frame is | |
4562 | made. Each time a function returns, the frame for that function invocation | |
4563 | is eliminated. If a function is recursive, there can be many frames for | |
4564 | the same function. The frame for the function in which execution is | |
4565 | actually occurring is called the @dfn{innermost} frame. This is the most | |
4566 | recently created of all the stack frames that still exist. | |
4567 | ||
4568 | @cindex frame pointer | |
4569 | Inside your program, stack frames are identified by their addresses. A | |
4570 | stack frame consists of many bytes, each of which has its own address; each | |
4571 | kind of computer has a convention for choosing one byte whose | |
4572 | address serves as the address of the frame. Usually this address is kept | |
e09f16f9 EZ |
4573 | in a register called the @dfn{frame pointer register} |
4574 | (@pxref{Registers, $fp}) while execution is going on in that frame. | |
c906108c SS |
4575 | |
4576 | @cindex frame number | |
4577 | @value{GDBN} assigns numbers to all existing stack frames, starting with | |
4578 | zero for the innermost frame, one for the frame that called it, | |
4579 | and so on upward. These numbers do not really exist in your program; | |
4580 | they are assigned by @value{GDBN} to give you a way of designating stack | |
4581 | frames in @value{GDBN} commands. | |
4582 | ||
6d2ebf8b SS |
4583 | @c The -fomit-frame-pointer below perennially causes hbox overflow |
4584 | @c underflow problems. | |
c906108c SS |
4585 | @cindex frameless execution |
4586 | Some compilers provide a way to compile functions so that they operate | |
e22ea452 | 4587 | without stack frames. (For example, the @value{NGCC} option |
474c8240 | 4588 | @smallexample |
6d2ebf8b | 4589 | @samp{-fomit-frame-pointer} |
474c8240 | 4590 | @end smallexample |
6d2ebf8b | 4591 | generates functions without a frame.) |
c906108c SS |
4592 | This is occasionally done with heavily used library functions to save |
4593 | the frame setup time. @value{GDBN} has limited facilities for dealing | |
4594 | with these function invocations. If the innermost function invocation | |
4595 | has no stack frame, @value{GDBN} nevertheless regards it as though | |
4596 | it had a separate frame, which is numbered zero as usual, allowing | |
4597 | correct tracing of the function call chain. However, @value{GDBN} has | |
4598 | no provision for frameless functions elsewhere in the stack. | |
4599 | ||
4600 | @table @code | |
d4f3574e | 4601 | @kindex frame@r{, command} |
41afff9a | 4602 | @cindex current stack frame |
c906108c | 4603 | @item frame @var{args} |
5d161b24 | 4604 | The @code{frame} command allows you to move from one stack frame to another, |
c906108c | 4605 | and to print the stack frame you select. @var{args} may be either the |
5d161b24 DB |
4606 | address of the frame or the stack frame number. Without an argument, |
4607 | @code{frame} prints the current stack frame. | |
c906108c SS |
4608 | |
4609 | @kindex select-frame | |
41afff9a | 4610 | @cindex selecting frame silently |
c906108c SS |
4611 | @item select-frame |
4612 | The @code{select-frame} command allows you to move from one stack frame | |
4613 | to another without printing the frame. This is the silent version of | |
4614 | @code{frame}. | |
4615 | @end table | |
4616 | ||
6d2ebf8b | 4617 | @node Backtrace |
c906108c SS |
4618 | @section Backtraces |
4619 | ||
09d4efe1 EZ |
4620 | @cindex traceback |
4621 | @cindex call stack traces | |
c906108c SS |
4622 | A backtrace is a summary of how your program got where it is. It shows one |
4623 | line per frame, for many frames, starting with the currently executing | |
4624 | frame (frame zero), followed by its caller (frame one), and on up the | |
4625 | stack. | |
4626 | ||
4627 | @table @code | |
4628 | @kindex backtrace | |
41afff9a | 4629 | @kindex bt @r{(@code{backtrace})} |
c906108c SS |
4630 | @item backtrace |
4631 | @itemx bt | |
4632 | Print a backtrace of the entire stack: one line per frame for all | |
4633 | frames in the stack. | |
4634 | ||
4635 | You can stop the backtrace at any time by typing the system interrupt | |
c8aa23ab | 4636 | character, normally @kbd{Ctrl-c}. |
c906108c SS |
4637 | |
4638 | @item backtrace @var{n} | |
4639 | @itemx bt @var{n} | |
4640 | Similar, but print only the innermost @var{n} frames. | |
4641 | ||
4642 | @item backtrace -@var{n} | |
4643 | @itemx bt -@var{n} | |
4644 | Similar, but print only the outermost @var{n} frames. | |
0f061b69 NR |
4645 | |
4646 | @item backtrace full | |
0f061b69 | 4647 | @itemx bt full |
dd74f6ae NR |
4648 | @itemx bt full @var{n} |
4649 | @itemx bt full -@var{n} | |
e7109c7e | 4650 | Print the values of the local variables also. @var{n} specifies the |
286ba84d | 4651 | number of frames to print, as described above. |
c906108c SS |
4652 | @end table |
4653 | ||
4654 | @kindex where | |
4655 | @kindex info stack | |
c906108c SS |
4656 | The names @code{where} and @code{info stack} (abbreviated @code{info s}) |
4657 | are additional aliases for @code{backtrace}. | |
4658 | ||
839c27b7 EZ |
4659 | @cindex multiple threads, backtrace |
4660 | In a multi-threaded program, @value{GDBN} by default shows the | |
4661 | backtrace only for the current thread. To display the backtrace for | |
4662 | several or all of the threads, use the command @code{thread apply} | |
4663 | (@pxref{Threads, thread apply}). For example, if you type @kbd{thread | |
4664 | apply all backtrace}, @value{GDBN} will display the backtrace for all | |
4665 | the threads; this is handy when you debug a core dump of a | |
4666 | multi-threaded program. | |
4667 | ||
c906108c SS |
4668 | Each line in the backtrace shows the frame number and the function name. |
4669 | The program counter value is also shown---unless you use @code{set | |
4670 | print address off}. The backtrace also shows the source file name and | |
4671 | line number, as well as the arguments to the function. The program | |
4672 | counter value is omitted if it is at the beginning of the code for that | |
4673 | line number. | |
4674 | ||
4675 | Here is an example of a backtrace. It was made with the command | |
4676 | @samp{bt 3}, so it shows the innermost three frames. | |
4677 | ||
4678 | @smallexample | |
4679 | @group | |
5d161b24 | 4680 | #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) |
c906108c SS |
4681 | at builtin.c:993 |
4682 | #1 0x6e38 in expand_macro (sym=0x2b600) at macro.c:242 | |
4683 | #2 0x6840 in expand_token (obs=0x0, t=177664, td=0xf7fffb08) | |
4684 | at macro.c:71 | |
4685 | (More stack frames follow...) | |
4686 | @end group | |
4687 | @end smallexample | |
4688 | ||
4689 | @noindent | |
4690 | The display for frame zero does not begin with a program counter | |
4691 | value, indicating that your program has stopped at the beginning of the | |
4692 | code for line @code{993} of @code{builtin.c}. | |
4693 | ||
18999be5 EZ |
4694 | @cindex value optimized out, in backtrace |
4695 | @cindex function call arguments, optimized out | |
4696 | If your program was compiled with optimizations, some compilers will | |
4697 | optimize away arguments passed to functions if those arguments are | |
4698 | never used after the call. Such optimizations generate code that | |
4699 | passes arguments through registers, but doesn't store those arguments | |
4700 | in the stack frame. @value{GDBN} has no way of displaying such | |
4701 | arguments in stack frames other than the innermost one. Here's what | |
4702 | such a backtrace might look like: | |
4703 | ||
4704 | @smallexample | |
4705 | @group | |
4706 | #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) | |
4707 | at builtin.c:993 | |
4708 | #1 0x6e38 in expand_macro (sym=<value optimized out>) at macro.c:242 | |
4709 | #2 0x6840 in expand_token (obs=0x0, t=<value optimized out>, td=0xf7fffb08) | |
4710 | at macro.c:71 | |
4711 | (More stack frames follow...) | |
4712 | @end group | |
4713 | @end smallexample | |
4714 | ||
4715 | @noindent | |
4716 | The values of arguments that were not saved in their stack frames are | |
4717 | shown as @samp{<value optimized out>}. | |
4718 | ||
4719 | If you need to display the values of such optimized-out arguments, | |
4720 | either deduce that from other variables whose values depend on the one | |
4721 | you are interested in, or recompile without optimizations. | |
4722 | ||
a8f24a35 EZ |
4723 | @cindex backtrace beyond @code{main} function |
4724 | @cindex program entry point | |
4725 | @cindex startup code, and backtrace | |
25d29d70 AC |
4726 | Most programs have a standard user entry point---a place where system |
4727 | libraries and startup code transition into user code. For C this is | |
d416eeec EZ |
4728 | @code{main}@footnote{ |
4729 | Note that embedded programs (the so-called ``free-standing'' | |
4730 | environment) are not required to have a @code{main} function as the | |
4731 | entry point. They could even have multiple entry points.}. | |
4732 | When @value{GDBN} finds the entry function in a backtrace | |
25d29d70 AC |
4733 | it will terminate the backtrace, to avoid tracing into highly |
4734 | system-specific (and generally uninteresting) code. | |
4735 | ||
4736 | If you need to examine the startup code, or limit the number of levels | |
4737 | in a backtrace, you can change this behavior: | |
95f90d25 DJ |
4738 | |
4739 | @table @code | |
25d29d70 AC |
4740 | @item set backtrace past-main |
4741 | @itemx set backtrace past-main on | |
4644b6e3 | 4742 | @kindex set backtrace |
25d29d70 AC |
4743 | Backtraces will continue past the user entry point. |
4744 | ||
4745 | @item set backtrace past-main off | |
95f90d25 DJ |
4746 | Backtraces will stop when they encounter the user entry point. This is the |
4747 | default. | |
4748 | ||
25d29d70 | 4749 | @item show backtrace past-main |
4644b6e3 | 4750 | @kindex show backtrace |
25d29d70 AC |
4751 | Display the current user entry point backtrace policy. |
4752 | ||
2315ffec RC |
4753 | @item set backtrace past-entry |
4754 | @itemx set backtrace past-entry on | |
a8f24a35 | 4755 | Backtraces will continue past the internal entry point of an application. |
2315ffec RC |
4756 | This entry point is encoded by the linker when the application is built, |
4757 | and is likely before the user entry point @code{main} (or equivalent) is called. | |
4758 | ||
4759 | @item set backtrace past-entry off | |
d3e8051b | 4760 | Backtraces will stop when they encounter the internal entry point of an |
2315ffec RC |
4761 | application. This is the default. |
4762 | ||
4763 | @item show backtrace past-entry | |
4764 | Display the current internal entry point backtrace policy. | |
4765 | ||
25d29d70 AC |
4766 | @item set backtrace limit @var{n} |
4767 | @itemx set backtrace limit 0 | |
4768 | @cindex backtrace limit | |
4769 | Limit the backtrace to @var{n} levels. A value of zero means | |
4770 | unlimited. | |
95f90d25 | 4771 | |
25d29d70 AC |
4772 | @item show backtrace limit |
4773 | Display the current limit on backtrace levels. | |
95f90d25 DJ |
4774 | @end table |
4775 | ||
6d2ebf8b | 4776 | @node Selection |
79a6e687 | 4777 | @section Selecting a Frame |
c906108c SS |
4778 | |
4779 | Most commands for examining the stack and other data in your program work on | |
4780 | whichever stack frame is selected at the moment. Here are the commands for | |
4781 | selecting a stack frame; all of them finish by printing a brief description | |
4782 | of the stack frame just selected. | |
4783 | ||
4784 | @table @code | |
d4f3574e | 4785 | @kindex frame@r{, selecting} |
41afff9a | 4786 | @kindex f @r{(@code{frame})} |
c906108c SS |
4787 | @item frame @var{n} |
4788 | @itemx f @var{n} | |
4789 | Select frame number @var{n}. Recall that frame zero is the innermost | |
4790 | (currently executing) frame, frame one is the frame that called the | |
4791 | innermost one, and so on. The highest-numbered frame is the one for | |
4792 | @code{main}. | |
4793 | ||
4794 | @item frame @var{addr} | |
4795 | @itemx f @var{addr} | |
4796 | Select the frame at address @var{addr}. This is useful mainly if the | |
4797 | chaining of stack frames has been damaged by a bug, making it | |
4798 | impossible for @value{GDBN} to assign numbers properly to all frames. In | |
4799 | addition, this can be useful when your program has multiple stacks and | |
4800 | switches between them. | |
4801 | ||
c906108c SS |
4802 | On the SPARC architecture, @code{frame} needs two addresses to |
4803 | select an arbitrary frame: a frame pointer and a stack pointer. | |
4804 | ||
4805 | On the MIPS and Alpha architecture, it needs two addresses: a stack | |
4806 | pointer and a program counter. | |
4807 | ||
4808 | On the 29k architecture, it needs three addresses: a register stack | |
4809 | pointer, a program counter, and a memory stack pointer. | |
c906108c SS |
4810 | |
4811 | @kindex up | |
4812 | @item up @var{n} | |
4813 | Move @var{n} frames up the stack. For positive numbers @var{n}, this | |
4814 | advances toward the outermost frame, to higher frame numbers, to frames | |
4815 | that have existed longer. @var{n} defaults to one. | |
4816 | ||
4817 | @kindex down | |
41afff9a | 4818 | @kindex do @r{(@code{down})} |
c906108c SS |
4819 | @item down @var{n} |
4820 | Move @var{n} frames down the stack. For positive numbers @var{n}, this | |
4821 | advances toward the innermost frame, to lower frame numbers, to frames | |
4822 | that were created more recently. @var{n} defaults to one. You may | |
4823 | abbreviate @code{down} as @code{do}. | |
4824 | @end table | |
4825 | ||
4826 | All of these commands end by printing two lines of output describing the | |
4827 | frame. The first line shows the frame number, the function name, the | |
4828 | arguments, and the source file and line number of execution in that | |
5d161b24 | 4829 | frame. The second line shows the text of that source line. |
c906108c SS |
4830 | |
4831 | @need 1000 | |
4832 | For example: | |
4833 | ||
4834 | @smallexample | |
4835 | @group | |
4836 | (@value{GDBP}) up | |
4837 | #1 0x22f0 in main (argc=1, argv=0xf7fffbf4, env=0xf7fffbfc) | |
4838 | at env.c:10 | |
4839 | 10 read_input_file (argv[i]); | |
4840 | @end group | |
4841 | @end smallexample | |
4842 | ||
4843 | After such a printout, the @code{list} command with no arguments | |
4844 | prints ten lines centered on the point of execution in the frame. | |
87885426 FN |
4845 | You can also edit the program at the point of execution with your favorite |
4846 | editing program by typing @code{edit}. | |
79a6e687 | 4847 | @xref{List, ,Printing Source Lines}, |
87885426 | 4848 | for details. |
c906108c SS |
4849 | |
4850 | @table @code | |
4851 | @kindex down-silently | |
4852 | @kindex up-silently | |
4853 | @item up-silently @var{n} | |
4854 | @itemx down-silently @var{n} | |
4855 | These two commands are variants of @code{up} and @code{down}, | |
4856 | respectively; they differ in that they do their work silently, without | |
4857 | causing display of the new frame. They are intended primarily for use | |
4858 | in @value{GDBN} command scripts, where the output might be unnecessary and | |
4859 | distracting. | |
4860 | @end table | |
4861 | ||
6d2ebf8b | 4862 | @node Frame Info |
79a6e687 | 4863 | @section Information About a Frame |
c906108c SS |
4864 | |
4865 | There are several other commands to print information about the selected | |
4866 | stack frame. | |
4867 | ||
4868 | @table @code | |
4869 | @item frame | |
4870 | @itemx f | |
4871 | When used without any argument, this command does not change which | |
4872 | frame is selected, but prints a brief description of the currently | |
4873 | selected stack frame. It can be abbreviated @code{f}. With an | |
4874 | argument, this command is used to select a stack frame. | |
79a6e687 | 4875 | @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
4876 | |
4877 | @kindex info frame | |
41afff9a | 4878 | @kindex info f @r{(@code{info frame})} |
c906108c SS |
4879 | @item info frame |
4880 | @itemx info f | |
4881 | This command prints a verbose description of the selected stack frame, | |
4882 | including: | |
4883 | ||
4884 | @itemize @bullet | |
5d161b24 DB |
4885 | @item |
4886 | the address of the frame | |
c906108c SS |
4887 | @item |
4888 | the address of the next frame down (called by this frame) | |
4889 | @item | |
4890 | the address of the next frame up (caller of this frame) | |
4891 | @item | |
4892 | the language in which the source code corresponding to this frame is written | |
4893 | @item | |
4894 | the address of the frame's arguments | |
4895 | @item | |
d4f3574e SS |
4896 | the address of the frame's local variables |
4897 | @item | |
c906108c SS |
4898 | the program counter saved in it (the address of execution in the caller frame) |
4899 | @item | |
4900 | which registers were saved in the frame | |
4901 | @end itemize | |
4902 | ||
4903 | @noindent The verbose description is useful when | |
4904 | something has gone wrong that has made the stack format fail to fit | |
4905 | the usual conventions. | |
4906 | ||
4907 | @item info frame @var{addr} | |
4908 | @itemx info f @var{addr} | |
4909 | Print a verbose description of the frame at address @var{addr}, without | |
4910 | selecting that frame. The selected frame remains unchanged by this | |
4911 | command. This requires the same kind of address (more than one for some | |
4912 | architectures) that you specify in the @code{frame} command. | |
79a6e687 | 4913 | @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
4914 | |
4915 | @kindex info args | |
4916 | @item info args | |
4917 | Print the arguments of the selected frame, each on a separate line. | |
4918 | ||
4919 | @item info locals | |
4920 | @kindex info locals | |
4921 | Print the local variables of the selected frame, each on a separate | |
4922 | line. These are all variables (declared either static or automatic) | |
4923 | accessible at the point of execution of the selected frame. | |
4924 | ||
c906108c | 4925 | @kindex info catch |
d4f3574e SS |
4926 | @cindex catch exceptions, list active handlers |
4927 | @cindex exception handlers, how to list | |
c906108c SS |
4928 | @item info catch |
4929 | Print a list of all the exception handlers that are active in the | |
4930 | current stack frame at the current point of execution. To see other | |
4931 | exception handlers, visit the associated frame (using the @code{up}, | |
4932 | @code{down}, or @code{frame} commands); then type @code{info catch}. | |
79a6e687 | 4933 | @xref{Set Catchpoints, , Setting Catchpoints}. |
53a5351d | 4934 | |
c906108c SS |
4935 | @end table |
4936 | ||
c906108c | 4937 | |
6d2ebf8b | 4938 | @node Source |
c906108c SS |
4939 | @chapter Examining Source Files |
4940 | ||
4941 | @value{GDBN} can print parts of your program's source, since the debugging | |
4942 | information recorded in the program tells @value{GDBN} what source files were | |
4943 | used to build it. When your program stops, @value{GDBN} spontaneously prints | |
4944 | the line where it stopped. Likewise, when you select a stack frame | |
79a6e687 | 4945 | (@pxref{Selection, ,Selecting a Frame}), @value{GDBN} prints the line where |
c906108c SS |
4946 | execution in that frame has stopped. You can print other portions of |
4947 | source files by explicit command. | |
4948 | ||
7a292a7a | 4949 | If you use @value{GDBN} through its @sc{gnu} Emacs interface, you may |
d4f3574e | 4950 | prefer to use Emacs facilities to view source; see @ref{Emacs, ,Using |
7a292a7a | 4951 | @value{GDBN} under @sc{gnu} Emacs}. |
c906108c SS |
4952 | |
4953 | @menu | |
4954 | * List:: Printing source lines | |
2a25a5ba | 4955 | * Specify Location:: How to specify code locations |
87885426 | 4956 | * Edit:: Editing source files |
c906108c | 4957 | * Search:: Searching source files |
c906108c SS |
4958 | * Source Path:: Specifying source directories |
4959 | * Machine Code:: Source and machine code | |
4960 | @end menu | |
4961 | ||
6d2ebf8b | 4962 | @node List |
79a6e687 | 4963 | @section Printing Source Lines |
c906108c SS |
4964 | |
4965 | @kindex list | |
41afff9a | 4966 | @kindex l @r{(@code{list})} |
c906108c | 4967 | To print lines from a source file, use the @code{list} command |
5d161b24 | 4968 | (abbreviated @code{l}). By default, ten lines are printed. |
2a25a5ba EZ |
4969 | There are several ways to specify what part of the file you want to |
4970 | print; see @ref{Specify Location}, for the full list. | |
c906108c SS |
4971 | |
4972 | Here are the forms of the @code{list} command most commonly used: | |
4973 | ||
4974 | @table @code | |
4975 | @item list @var{linenum} | |
4976 | Print lines centered around line number @var{linenum} in the | |
4977 | current source file. | |
4978 | ||
4979 | @item list @var{function} | |
4980 | Print lines centered around the beginning of function | |
4981 | @var{function}. | |
4982 | ||
4983 | @item list | |
4984 | Print more lines. If the last lines printed were printed with a | |
4985 | @code{list} command, this prints lines following the last lines | |
4986 | printed; however, if the last line printed was a solitary line printed | |
4987 | as part of displaying a stack frame (@pxref{Stack, ,Examining the | |
4988 | Stack}), this prints lines centered around that line. | |
4989 | ||
4990 | @item list - | |
4991 | Print lines just before the lines last printed. | |
4992 | @end table | |
4993 | ||
9c16f35a | 4994 | @cindex @code{list}, how many lines to display |
c906108c SS |
4995 | By default, @value{GDBN} prints ten source lines with any of these forms of |
4996 | the @code{list} command. You can change this using @code{set listsize}: | |
4997 | ||
4998 | @table @code | |
4999 | @kindex set listsize | |
5000 | @item set listsize @var{count} | |
5001 | Make the @code{list} command display @var{count} source lines (unless | |
5002 | the @code{list} argument explicitly specifies some other number). | |
5003 | ||
5004 | @kindex show listsize | |
5005 | @item show listsize | |
5006 | Display the number of lines that @code{list} prints. | |
5007 | @end table | |
5008 | ||
5009 | Repeating a @code{list} command with @key{RET} discards the argument, | |
5010 | so it is equivalent to typing just @code{list}. This is more useful | |
5011 | than listing the same lines again. An exception is made for an | |
5012 | argument of @samp{-}; that argument is preserved in repetition so that | |
5013 | each repetition moves up in the source file. | |
5014 | ||
c906108c SS |
5015 | In general, the @code{list} command expects you to supply zero, one or two |
5016 | @dfn{linespecs}. Linespecs specify source lines; there are several ways | |
2a25a5ba EZ |
5017 | of writing them (@pxref{Specify Location}), but the effect is always |
5018 | to specify some source line. | |
5019 | ||
c906108c SS |
5020 | Here is a complete description of the possible arguments for @code{list}: |
5021 | ||
5022 | @table @code | |
5023 | @item list @var{linespec} | |
5024 | Print lines centered around the line specified by @var{linespec}. | |
5025 | ||
5026 | @item list @var{first},@var{last} | |
5027 | Print lines from @var{first} to @var{last}. Both arguments are | |
2a25a5ba EZ |
5028 | linespecs. When a @code{list} command has two linespecs, and the |
5029 | source file of the second linespec is omitted, this refers to | |
5030 | the same source file as the first linespec. | |
c906108c SS |
5031 | |
5032 | @item list ,@var{last} | |
5033 | Print lines ending with @var{last}. | |
5034 | ||
5035 | @item list @var{first}, | |
5036 | Print lines starting with @var{first}. | |
5037 | ||
5038 | @item list + | |
5039 | Print lines just after the lines last printed. | |
5040 | ||
5041 | @item list - | |
5042 | Print lines just before the lines last printed. | |
5043 | ||
5044 | @item list | |
5045 | As described in the preceding table. | |
5046 | @end table | |
5047 | ||
2a25a5ba EZ |
5048 | @node Specify Location |
5049 | @section Specifying a Location | |
5050 | @cindex specifying location | |
5051 | @cindex linespec | |
c906108c | 5052 | |
2a25a5ba EZ |
5053 | Several @value{GDBN} commands accept arguments that specify a location |
5054 | of your program's code. Since @value{GDBN} is a source-level | |
5055 | debugger, a location usually specifies some line in the source code; | |
5056 | for that reason, locations are also known as @dfn{linespecs}. | |
c906108c | 5057 | |
2a25a5ba EZ |
5058 | Here are all the different ways of specifying a code location that |
5059 | @value{GDBN} understands: | |
c906108c | 5060 | |
2a25a5ba EZ |
5061 | @table @code |
5062 | @item @var{linenum} | |
5063 | Specifies the line number @var{linenum} of the current source file. | |
c906108c | 5064 | |
2a25a5ba EZ |
5065 | @item -@var{offset} |
5066 | @itemx +@var{offset} | |
5067 | Specifies the line @var{offset} lines before or after the @dfn{current | |
5068 | line}. For the @code{list} command, the current line is the last one | |
5069 | printed; for the breakpoint commands, this is the line at which | |
5070 | execution stopped in the currently selected @dfn{stack frame} | |
5071 | (@pxref{Frames, ,Frames}, for a description of stack frames.) When | |
5072 | used as the second of the two linespecs in a @code{list} command, | |
5073 | this specifies the line @var{offset} lines up or down from the first | |
5074 | linespec. | |
5075 | ||
5076 | @item @var{filename}:@var{linenum} | |
5077 | Specifies the line @var{linenum} in the source file @var{filename}. | |
c906108c SS |
5078 | |
5079 | @item @var{function} | |
5080 | Specifies the line that begins the body of the function @var{function}. | |
2a25a5ba | 5081 | For example, in C, this is the line with the open brace. |
c906108c SS |
5082 | |
5083 | @item @var{filename}:@var{function} | |
2a25a5ba EZ |
5084 | Specifies the line that begins the body of the function @var{function} |
5085 | in the file @var{filename}. You only need the file name with a | |
5086 | function name to avoid ambiguity when there are identically named | |
5087 | functions in different source files. | |
c906108c SS |
5088 | |
5089 | @item *@var{address} | |
2a25a5ba EZ |
5090 | Specifies the program address @var{address}. For line-oriented |
5091 | commands, such as @code{list} and @code{edit}, this specifies a source | |
5092 | line that contains @var{address}. For @code{break} and other | |
5093 | breakpoint oriented commands, this can be used to set breakpoints in | |
5094 | parts of your program which do not have debugging information or | |
5095 | source files. | |
5096 | ||
5097 | Here @var{address} may be any expression valid in the current working | |
5098 | language (@pxref{Languages, working language}) that specifies a code | |
5fa54e5d EZ |
5099 | address. In addition, as a convenience, @value{GDBN} extends the |
5100 | semantics of expressions used in locations to cover the situations | |
5101 | that frequently happen during debugging. Here are the various forms | |
5102 | of @var{address}: | |
2a25a5ba EZ |
5103 | |
5104 | @table @code | |
5105 | @item @var{expression} | |
5106 | Any expression valid in the current working language. | |
5107 | ||
5108 | @item @var{funcaddr} | |
5109 | An address of a function or procedure derived from its name. In C, | |
5110 | C@t{++}, Java, Objective-C, Fortran, minimal, and assembly, this is | |
5111 | simply the function's name @var{function} (and actually a special case | |
5112 | of a valid expression). In Pascal and Modula-2, this is | |
5113 | @code{&@var{function}}. In Ada, this is @code{@var{function}'Address} | |
5114 | (although the Pascal form also works). | |
5115 | ||
5116 | This form specifies the address of the function's first instruction, | |
5117 | before the stack frame and arguments have been set up. | |
5118 | ||
5119 | @item '@var{filename}'::@var{funcaddr} | |
5120 | Like @var{funcaddr} above, but also specifies the name of the source | |
5121 | file explicitly. This is useful if the name of the function does not | |
5122 | specify the function unambiguously, e.g., if there are several | |
5123 | functions with identical names in different source files. | |
c906108c SS |
5124 | @end table |
5125 | ||
2a25a5ba EZ |
5126 | @end table |
5127 | ||
5128 | ||
87885426 | 5129 | @node Edit |
79a6e687 | 5130 | @section Editing Source Files |
87885426 FN |
5131 | @cindex editing source files |
5132 | ||
5133 | @kindex edit | |
5134 | @kindex e @r{(@code{edit})} | |
5135 | To edit the lines in a source file, use the @code{edit} command. | |
5136 | The editing program of your choice | |
5137 | is invoked with the current line set to | |
5138 | the active line in the program. | |
5139 | Alternatively, there are several ways to specify what part of the file you | |
2a25a5ba | 5140 | want to print if you want to see other parts of the program: |
87885426 FN |
5141 | |
5142 | @table @code | |
2a25a5ba EZ |
5143 | @item edit @var{location} |
5144 | Edit the source file specified by @code{location}. Editing starts at | |
5145 | that @var{location}, e.g., at the specified source line of the | |
5146 | specified file. @xref{Specify Location}, for all the possible forms | |
5147 | of the @var{location} argument; here are the forms of the @code{edit} | |
5148 | command most commonly used: | |
87885426 | 5149 | |
2a25a5ba | 5150 | @table @code |
87885426 FN |
5151 | @item edit @var{number} |
5152 | Edit the current source file with @var{number} as the active line number. | |
5153 | ||
5154 | @item edit @var{function} | |
5155 | Edit the file containing @var{function} at the beginning of its definition. | |
2a25a5ba | 5156 | @end table |
87885426 | 5157 | |
87885426 FN |
5158 | @end table |
5159 | ||
79a6e687 | 5160 | @subsection Choosing your Editor |
87885426 FN |
5161 | You can customize @value{GDBN} to use any editor you want |
5162 | @footnote{ | |
5163 | The only restriction is that your editor (say @code{ex}), recognizes the | |
5164 | following command-line syntax: | |
10998722 | 5165 | @smallexample |
87885426 | 5166 | ex +@var{number} file |
10998722 | 5167 | @end smallexample |
15387254 EZ |
5168 | The optional numeric value +@var{number} specifies the number of the line in |
5169 | the file where to start editing.}. | |
5170 | By default, it is @file{@value{EDITOR}}, but you can change this | |
10998722 AC |
5171 | by setting the environment variable @code{EDITOR} before using |
5172 | @value{GDBN}. For example, to configure @value{GDBN} to use the | |
5173 | @code{vi} editor, you could use these commands with the @code{sh} shell: | |
5174 | @smallexample | |
87885426 FN |
5175 | EDITOR=/usr/bin/vi |
5176 | export EDITOR | |
15387254 | 5177 | gdb @dots{} |
10998722 | 5178 | @end smallexample |
87885426 | 5179 | or in the @code{csh} shell, |
10998722 | 5180 | @smallexample |
87885426 | 5181 | setenv EDITOR /usr/bin/vi |
15387254 | 5182 | gdb @dots{} |
10998722 | 5183 | @end smallexample |
87885426 | 5184 | |
6d2ebf8b | 5185 | @node Search |
79a6e687 | 5186 | @section Searching Source Files |
15387254 | 5187 | @cindex searching source files |
c906108c SS |
5188 | |
5189 | There are two commands for searching through the current source file for a | |
5190 | regular expression. | |
5191 | ||
5192 | @table @code | |
5193 | @kindex search | |
5194 | @kindex forward-search | |
5195 | @item forward-search @var{regexp} | |
5196 | @itemx search @var{regexp} | |
5197 | The command @samp{forward-search @var{regexp}} checks each line, | |
5198 | starting with the one following the last line listed, for a match for | |
5d161b24 | 5199 | @var{regexp}. It lists the line that is found. You can use the |
c906108c SS |
5200 | synonym @samp{search @var{regexp}} or abbreviate the command name as |
5201 | @code{fo}. | |
5202 | ||
09d4efe1 | 5203 | @kindex reverse-search |
c906108c SS |
5204 | @item reverse-search @var{regexp} |
5205 | The command @samp{reverse-search @var{regexp}} checks each line, starting | |
5206 | with the one before the last line listed and going backward, for a match | |
5207 | for @var{regexp}. It lists the line that is found. You can abbreviate | |
5208 | this command as @code{rev}. | |
5209 | @end table | |
c906108c | 5210 | |
6d2ebf8b | 5211 | @node Source Path |
79a6e687 | 5212 | @section Specifying Source Directories |
c906108c SS |
5213 | |
5214 | @cindex source path | |
5215 | @cindex directories for source files | |
5216 | Executable programs sometimes do not record the directories of the source | |
5217 | files from which they were compiled, just the names. Even when they do, | |
5218 | the directories could be moved between the compilation and your debugging | |
5219 | session. @value{GDBN} has a list of directories to search for source files; | |
5220 | this is called the @dfn{source path}. Each time @value{GDBN} wants a source file, | |
5221 | it tries all the directories in the list, in the order they are present | |
0b66e38c EZ |
5222 | in the list, until it finds a file with the desired name. |
5223 | ||
5224 | For example, suppose an executable references the file | |
5225 | @file{/usr/src/foo-1.0/lib/foo.c}, and our source path is | |
5226 | @file{/mnt/cross}. The file is first looked up literally; if this | |
5227 | fails, @file{/mnt/cross/usr/src/foo-1.0/lib/foo.c} is tried; if this | |
5228 | fails, @file{/mnt/cross/foo.c} is opened; if this fails, an error | |
5229 | message is printed. @value{GDBN} does not look up the parts of the | |
5230 | source file name, such as @file{/mnt/cross/src/foo-1.0/lib/foo.c}. | |
5231 | Likewise, the subdirectories of the source path are not searched: if | |
5232 | the source path is @file{/mnt/cross}, and the binary refers to | |
5233 | @file{foo.c}, @value{GDBN} would not find it under | |
5234 | @file{/mnt/cross/usr/src/foo-1.0/lib}. | |
5235 | ||
5236 | Plain file names, relative file names with leading directories, file | |
5237 | names containing dots, etc.@: are all treated as described above; for | |
5238 | instance, if the source path is @file{/mnt/cross}, and the source file | |
5239 | is recorded as @file{../lib/foo.c}, @value{GDBN} would first try | |
5240 | @file{../lib/foo.c}, then @file{/mnt/cross/../lib/foo.c}, and after | |
5241 | that---@file{/mnt/cross/foo.c}. | |
5242 | ||
5243 | Note that the executable search path is @emph{not} used to locate the | |
cd852561 | 5244 | source files. |
c906108c SS |
5245 | |
5246 | Whenever you reset or rearrange the source path, @value{GDBN} clears out | |
5247 | any information it has cached about where source files are found and where | |
5248 | each line is in the file. | |
5249 | ||
5250 | @kindex directory | |
5251 | @kindex dir | |
d4f3574e SS |
5252 | When you start @value{GDBN}, its source path includes only @samp{cdir} |
5253 | and @samp{cwd}, in that order. | |
c906108c SS |
5254 | To add other directories, use the @code{directory} command. |
5255 | ||
4b505b12 AS |
5256 | The search path is used to find both program source files and @value{GDBN} |
5257 | script files (read using the @samp{-command} option and @samp{source} command). | |
5258 | ||
30daae6c JB |
5259 | In addition to the source path, @value{GDBN} provides a set of commands |
5260 | that manage a list of source path substitution rules. A @dfn{substitution | |
5261 | rule} specifies how to rewrite source directories stored in the program's | |
5262 | debug information in case the sources were moved to a different | |
5263 | directory between compilation and debugging. A rule is made of | |
5264 | two strings, the first specifying what needs to be rewritten in | |
5265 | the path, and the second specifying how it should be rewritten. | |
5266 | In @ref{set substitute-path}, we name these two parts @var{from} and | |
5267 | @var{to} respectively. @value{GDBN} does a simple string replacement | |
5268 | of @var{from} with @var{to} at the start of the directory part of the | |
5269 | source file name, and uses that result instead of the original file | |
5270 | name to look up the sources. | |
5271 | ||
5272 | Using the previous example, suppose the @file{foo-1.0} tree has been | |
5273 | moved from @file{/usr/src} to @file{/mnt/cross}, then you can tell | |
3f94c067 | 5274 | @value{GDBN} to replace @file{/usr/src} in all source path names with |
30daae6c JB |
5275 | @file{/mnt/cross}. The first lookup will then be |
5276 | @file{/mnt/cross/foo-1.0/lib/foo.c} in place of the original location | |
5277 | of @file{/usr/src/foo-1.0/lib/foo.c}. To define a source path | |
5278 | substitution rule, use the @code{set substitute-path} command | |
5279 | (@pxref{set substitute-path}). | |
5280 | ||
5281 | To avoid unexpected substitution results, a rule is applied only if the | |
5282 | @var{from} part of the directory name ends at a directory separator. | |
5283 | For instance, a rule substituting @file{/usr/source} into | |
5284 | @file{/mnt/cross} will be applied to @file{/usr/source/foo-1.0} but | |
5285 | not to @file{/usr/sourceware/foo-2.0}. And because the substitution | |
d3e8051b | 5286 | is applied only at the beginning of the directory name, this rule will |
30daae6c JB |
5287 | not be applied to @file{/root/usr/source/baz.c} either. |
5288 | ||
5289 | In many cases, you can achieve the same result using the @code{directory} | |
5290 | command. However, @code{set substitute-path} can be more efficient in | |
5291 | the case where the sources are organized in a complex tree with multiple | |
5292 | subdirectories. With the @code{directory} command, you need to add each | |
5293 | subdirectory of your project. If you moved the entire tree while | |
5294 | preserving its internal organization, then @code{set substitute-path} | |
5295 | allows you to direct the debugger to all the sources with one single | |
5296 | command. | |
5297 | ||
5298 | @code{set substitute-path} is also more than just a shortcut command. | |
5299 | The source path is only used if the file at the original location no | |
5300 | longer exists. On the other hand, @code{set substitute-path} modifies | |
5301 | the debugger behavior to look at the rewritten location instead. So, if | |
5302 | for any reason a source file that is not relevant to your executable is | |
5303 | located at the original location, a substitution rule is the only | |
3f94c067 | 5304 | method available to point @value{GDBN} at the new location. |
30daae6c | 5305 | |
c906108c SS |
5306 | @table @code |
5307 | @item directory @var{dirname} @dots{} | |
5308 | @item dir @var{dirname} @dots{} | |
5309 | Add directory @var{dirname} to the front of the source path. Several | |
d4f3574e SS |
5310 | directory names may be given to this command, separated by @samp{:} |
5311 | (@samp{;} on MS-DOS and MS-Windows, where @samp{:} usually appears as | |
5312 | part of absolute file names) or | |
c906108c SS |
5313 | whitespace. You may specify a directory that is already in the source |
5314 | path; this moves it forward, so @value{GDBN} searches it sooner. | |
5315 | ||
5316 | @kindex cdir | |
5317 | @kindex cwd | |
41afff9a | 5318 | @vindex $cdir@r{, convenience variable} |
d3e8051b | 5319 | @vindex $cwd@r{, convenience variable} |
c906108c SS |
5320 | @cindex compilation directory |
5321 | @cindex current directory | |
5322 | @cindex working directory | |
5323 | @cindex directory, current | |
5324 | @cindex directory, compilation | |
5325 | You can use the string @samp{$cdir} to refer to the compilation | |
5326 | directory (if one is recorded), and @samp{$cwd} to refer to the current | |
5327 | working directory. @samp{$cwd} is not the same as @samp{.}---the former | |
5328 | tracks the current working directory as it changes during your @value{GDBN} | |
5329 | session, while the latter is immediately expanded to the current | |
5330 | directory at the time you add an entry to the source path. | |
5331 | ||
5332 | @item directory | |
cd852561 | 5333 | Reset the source path to its default value (@samp{$cdir:$cwd} on Unix systems). This requires confirmation. |
c906108c SS |
5334 | |
5335 | @c RET-repeat for @code{directory} is explicitly disabled, but since | |
5336 | @c repeating it would be a no-op we do not say that. (thanks to RMS) | |
5337 | ||
5338 | @item show directories | |
5339 | @kindex show directories | |
5340 | Print the source path: show which directories it contains. | |
30daae6c JB |
5341 | |
5342 | @anchor{set substitute-path} | |
5343 | @item set substitute-path @var{from} @var{to} | |
5344 | @kindex set substitute-path | |
5345 | Define a source path substitution rule, and add it at the end of the | |
5346 | current list of existing substitution rules. If a rule with the same | |
5347 | @var{from} was already defined, then the old rule is also deleted. | |
5348 | ||
5349 | For example, if the file @file{/foo/bar/baz.c} was moved to | |
5350 | @file{/mnt/cross/baz.c}, then the command | |
5351 | ||
5352 | @smallexample | |
5353 | (@value{GDBP}) set substitute-path /usr/src /mnt/cross | |
5354 | @end smallexample | |
5355 | ||
5356 | @noindent | |
5357 | will tell @value{GDBN} to replace @samp{/usr/src} with | |
5358 | @samp{/mnt/cross}, which will allow @value{GDBN} to find the file | |
5359 | @file{baz.c} even though it was moved. | |
5360 | ||
5361 | In the case when more than one substitution rule have been defined, | |
5362 | the rules are evaluated one by one in the order where they have been | |
5363 | defined. The first one matching, if any, is selected to perform | |
5364 | the substitution. | |
5365 | ||
5366 | For instance, if we had entered the following commands: | |
5367 | ||
5368 | @smallexample | |
5369 | (@value{GDBP}) set substitute-path /usr/src/include /mnt/include | |
5370 | (@value{GDBP}) set substitute-path /usr/src /mnt/src | |
5371 | @end smallexample | |
5372 | ||
5373 | @noindent | |
5374 | @value{GDBN} would then rewrite @file{/usr/src/include/defs.h} into | |
5375 | @file{/mnt/include/defs.h} by using the first rule. However, it would | |
5376 | use the second rule to rewrite @file{/usr/src/lib/foo.c} into | |
5377 | @file{/mnt/src/lib/foo.c}. | |
5378 | ||
5379 | ||
5380 | @item unset substitute-path [path] | |
5381 | @kindex unset substitute-path | |
5382 | If a path is specified, search the current list of substitution rules | |
5383 | for a rule that would rewrite that path. Delete that rule if found. | |
5384 | A warning is emitted by the debugger if no rule could be found. | |
5385 | ||
5386 | If no path is specified, then all substitution rules are deleted. | |
5387 | ||
5388 | @item show substitute-path [path] | |
5389 | @kindex show substitute-path | |
5390 | If a path is specified, then print the source path substitution rule | |
5391 | which would rewrite that path, if any. | |
5392 | ||
5393 | If no path is specified, then print all existing source path substitution | |
5394 | rules. | |
5395 | ||
c906108c SS |
5396 | @end table |
5397 | ||
5398 | If your source path is cluttered with directories that are no longer of | |
5399 | interest, @value{GDBN} may sometimes cause confusion by finding the wrong | |
5400 | versions of source. You can correct the situation as follows: | |
5401 | ||
5402 | @enumerate | |
5403 | @item | |
cd852561 | 5404 | Use @code{directory} with no argument to reset the source path to its default value. |
c906108c SS |
5405 | |
5406 | @item | |
5407 | Use @code{directory} with suitable arguments to reinstall the | |
5408 | directories you want in the source path. You can add all the | |
5409 | directories in one command. | |
5410 | @end enumerate | |
5411 | ||
6d2ebf8b | 5412 | @node Machine Code |
79a6e687 | 5413 | @section Source and Machine Code |
15387254 | 5414 | @cindex source line and its code address |
c906108c SS |
5415 | |
5416 | You can use the command @code{info line} to map source lines to program | |
5417 | addresses (and vice versa), and the command @code{disassemble} to display | |
5418 | a range of addresses as machine instructions. When run under @sc{gnu} Emacs | |
d4f3574e | 5419 | mode, the @code{info line} command causes the arrow to point to the |
5d161b24 | 5420 | line specified. Also, @code{info line} prints addresses in symbolic form as |
c906108c SS |
5421 | well as hex. |
5422 | ||
5423 | @table @code | |
5424 | @kindex info line | |
5425 | @item info line @var{linespec} | |
5426 | Print the starting and ending addresses of the compiled code for | |
5427 | source line @var{linespec}. You can specify source lines in any of | |
2a25a5ba | 5428 | the ways documented in @ref{Specify Location}. |
c906108c SS |
5429 | @end table |
5430 | ||
5431 | For example, we can use @code{info line} to discover the location of | |
5432 | the object code for the first line of function | |
5433 | @code{m4_changequote}: | |
5434 | ||
d4f3574e SS |
5435 | @c FIXME: I think this example should also show the addresses in |
5436 | @c symbolic form, as they usually would be displayed. | |
c906108c | 5437 | @smallexample |
96a2c332 | 5438 | (@value{GDBP}) info line m4_changequote |
c906108c SS |
5439 | Line 895 of "builtin.c" starts at pc 0x634c and ends at 0x6350. |
5440 | @end smallexample | |
5441 | ||
5442 | @noindent | |
15387254 | 5443 | @cindex code address and its source line |
c906108c SS |
5444 | We can also inquire (using @code{*@var{addr}} as the form for |
5445 | @var{linespec}) what source line covers a particular address: | |
5446 | @smallexample | |
5447 | (@value{GDBP}) info line *0x63ff | |
5448 | Line 926 of "builtin.c" starts at pc 0x63e4 and ends at 0x6404. | |
5449 | @end smallexample | |
5450 | ||
5451 | @cindex @code{$_} and @code{info line} | |
15387254 | 5452 | @cindex @code{x} command, default address |
41afff9a | 5453 | @kindex x@r{(examine), and} info line |
c906108c SS |
5454 | After @code{info line}, the default address for the @code{x} command |
5455 | is changed to the starting address of the line, so that @samp{x/i} is | |
5456 | sufficient to begin examining the machine code (@pxref{Memory, | |
79a6e687 | 5457 | ,Examining Memory}). Also, this address is saved as the value of the |
c906108c | 5458 | convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience |
79a6e687 | 5459 | Variables}). |
c906108c SS |
5460 | |
5461 | @table @code | |
5462 | @kindex disassemble | |
5463 | @cindex assembly instructions | |
5464 | @cindex instructions, assembly | |
5465 | @cindex machine instructions | |
5466 | @cindex listing machine instructions | |
5467 | @item disassemble | |
5468 | This specialized command dumps a range of memory as machine | |
5469 | instructions. The default memory range is the function surrounding the | |
5470 | program counter of the selected frame. A single argument to this | |
5471 | command is a program counter value; @value{GDBN} dumps the function | |
5472 | surrounding this value. Two arguments specify a range of addresses | |
5473 | (first inclusive, second exclusive) to dump. | |
5474 | @end table | |
5475 | ||
c906108c SS |
5476 | The following example shows the disassembly of a range of addresses of |
5477 | HP PA-RISC 2.0 code: | |
5478 | ||
5479 | @smallexample | |
5480 | (@value{GDBP}) disas 0x32c4 0x32e4 | |
5481 | Dump of assembler code from 0x32c4 to 0x32e4: | |
5482 | 0x32c4 <main+204>: addil 0,dp | |
5483 | 0x32c8 <main+208>: ldw 0x22c(sr0,r1),r26 | |
5484 | 0x32cc <main+212>: ldil 0x3000,r31 | |
5485 | 0x32d0 <main+216>: ble 0x3f8(sr4,r31) | |
5486 | 0x32d4 <main+220>: ldo 0(r31),rp | |
5487 | 0x32d8 <main+224>: addil -0x800,dp | |
5488 | 0x32dc <main+228>: ldo 0x588(r1),r26 | |
5489 | 0x32e0 <main+232>: ldil 0x3000,r31 | |
5490 | End of assembler dump. | |
5491 | @end smallexample | |
c906108c SS |
5492 | |
5493 | Some architectures have more than one commonly-used set of instruction | |
5494 | mnemonics or other syntax. | |
5495 | ||
76d17f34 EZ |
5496 | For programs that were dynamically linked and use shared libraries, |
5497 | instructions that call functions or branch to locations in the shared | |
5498 | libraries might show a seemingly bogus location---it's actually a | |
5499 | location of the relocation table. On some architectures, @value{GDBN} | |
5500 | might be able to resolve these to actual function names. | |
5501 | ||
c906108c | 5502 | @table @code |
d4f3574e | 5503 | @kindex set disassembly-flavor |
d4f3574e SS |
5504 | @cindex Intel disassembly flavor |
5505 | @cindex AT&T disassembly flavor | |
5506 | @item set disassembly-flavor @var{instruction-set} | |
c906108c SS |
5507 | Select the instruction set to use when disassembling the |
5508 | program via the @code{disassemble} or @code{x/i} commands. | |
5509 | ||
5510 | Currently this command is only defined for the Intel x86 family. You | |
d4f3574e SS |
5511 | can set @var{instruction-set} to either @code{intel} or @code{att}. |
5512 | The default is @code{att}, the AT&T flavor used by default by Unix | |
5513 | assemblers for x86-based targets. | |
9c16f35a EZ |
5514 | |
5515 | @kindex show disassembly-flavor | |
5516 | @item show disassembly-flavor | |
5517 | Show the current setting of the disassembly flavor. | |
c906108c SS |
5518 | @end table |
5519 | ||
5520 | ||
6d2ebf8b | 5521 | @node Data |
c906108c SS |
5522 | @chapter Examining Data |
5523 | ||
5524 | @cindex printing data | |
5525 | @cindex examining data | |
5526 | @kindex print | |
5527 | @kindex inspect | |
5528 | @c "inspect" is not quite a synonym if you are using Epoch, which we do not | |
5529 | @c document because it is nonstandard... Under Epoch it displays in a | |
5530 | @c different window or something like that. | |
5531 | The usual way to examine data in your program is with the @code{print} | |
7a292a7a SS |
5532 | command (abbreviated @code{p}), or its synonym @code{inspect}. It |
5533 | evaluates and prints the value of an expression of the language your | |
5534 | program is written in (@pxref{Languages, ,Using @value{GDBN} with | |
5535 | Different Languages}). | |
c906108c SS |
5536 | |
5537 | @table @code | |
d4f3574e SS |
5538 | @item print @var{expr} |
5539 | @itemx print /@var{f} @var{expr} | |
5540 | @var{expr} is an expression (in the source language). By default the | |
5541 | value of @var{expr} is printed in a format appropriate to its data type; | |
c906108c | 5542 | you can choose a different format by specifying @samp{/@var{f}}, where |
d4f3574e | 5543 | @var{f} is a letter specifying the format; see @ref{Output Formats,,Output |
79a6e687 | 5544 | Formats}. |
c906108c SS |
5545 | |
5546 | @item print | |
5547 | @itemx print /@var{f} | |
15387254 | 5548 | @cindex reprint the last value |
d4f3574e | 5549 | If you omit @var{expr}, @value{GDBN} displays the last value again (from the |
79a6e687 | 5550 | @dfn{value history}; @pxref{Value History, ,Value History}). This allows you to |
c906108c SS |
5551 | conveniently inspect the same value in an alternative format. |
5552 | @end table | |
5553 | ||
5554 | A more low-level way of examining data is with the @code{x} command. | |
5555 | It examines data in memory at a specified address and prints it in a | |
79a6e687 | 5556 | specified format. @xref{Memory, ,Examining Memory}. |
c906108c | 5557 | |
7a292a7a | 5558 | If you are interested in information about types, or about how the |
d4f3574e SS |
5559 | fields of a struct or a class are declared, use the @code{ptype @var{exp}} |
5560 | command rather than @code{print}. @xref{Symbols, ,Examining the Symbol | |
7a292a7a | 5561 | Table}. |
c906108c SS |
5562 | |
5563 | @menu | |
5564 | * Expressions:: Expressions | |
5565 | * Variables:: Program variables | |
5566 | * Arrays:: Artificial arrays | |
5567 | * Output Formats:: Output formats | |
5568 | * Memory:: Examining memory | |
5569 | * Auto Display:: Automatic display | |
5570 | * Print Settings:: Print settings | |
5571 | * Value History:: Value history | |
5572 | * Convenience Vars:: Convenience variables | |
5573 | * Registers:: Registers | |
c906108c | 5574 | * Floating Point Hardware:: Floating point hardware |
53c69bd7 | 5575 | * Vector Unit:: Vector Unit |
721c2651 | 5576 | * OS Information:: Auxiliary data provided by operating system |
29e57380 | 5577 | * Memory Region Attributes:: Memory region attributes |
16d9dec6 | 5578 | * Dump/Restore Files:: Copy between memory and a file |
384ee23f | 5579 | * Core File Generation:: Cause a program dump its core |
a0eb71c5 KB |
5580 | * Character Sets:: Debugging programs that use a different |
5581 | character set than GDB does | |
09d4efe1 | 5582 | * Caching Remote Data:: Data caching for remote targets |
c906108c SS |
5583 | @end menu |
5584 | ||
6d2ebf8b | 5585 | @node Expressions |
c906108c SS |
5586 | @section Expressions |
5587 | ||
5588 | @cindex expressions | |
5589 | @code{print} and many other @value{GDBN} commands accept an expression and | |
5590 | compute its value. Any kind of constant, variable or operator defined | |
5591 | by the programming language you are using is valid in an expression in | |
e2e0bcd1 JB |
5592 | @value{GDBN}. This includes conditional expressions, function calls, |
5593 | casts, and string constants. It also includes preprocessor macros, if | |
5594 | you compiled your program to include this information; see | |
5595 | @ref{Compilation}. | |
c906108c | 5596 | |
15387254 | 5597 | @cindex arrays in expressions |
d4f3574e SS |
5598 | @value{GDBN} supports array constants in expressions input by |
5599 | the user. The syntax is @{@var{element}, @var{element}@dots{}@}. For example, | |
5d161b24 | 5600 | you can use the command @code{print @{1, 2, 3@}} to build up an array in |
d4f3574e | 5601 | memory that is @code{malloc}ed in the target program. |
c906108c | 5602 | |
c906108c SS |
5603 | Because C is so widespread, most of the expressions shown in examples in |
5604 | this manual are in C. @xref{Languages, , Using @value{GDBN} with Different | |
5605 | Languages}, for information on how to use expressions in other | |
5606 | languages. | |
5607 | ||
5608 | In this section, we discuss operators that you can use in @value{GDBN} | |
5609 | expressions regardless of your programming language. | |
5610 | ||
15387254 | 5611 | @cindex casts, in expressions |
c906108c SS |
5612 | Casts are supported in all languages, not just in C, because it is so |
5613 | useful to cast a number into a pointer in order to examine a structure | |
5614 | at that address in memory. | |
5615 | @c FIXME: casts supported---Mod2 true? | |
c906108c SS |
5616 | |
5617 | @value{GDBN} supports these operators, in addition to those common | |
5618 | to programming languages: | |
5619 | ||
5620 | @table @code | |
5621 | @item @@ | |
5622 | @samp{@@} is a binary operator for treating parts of memory as arrays. | |
79a6e687 | 5623 | @xref{Arrays, ,Artificial Arrays}, for more information. |
c906108c SS |
5624 | |
5625 | @item :: | |
5626 | @samp{::} allows you to specify a variable in terms of the file or | |
79a6e687 | 5627 | function where it is defined. @xref{Variables, ,Program Variables}. |
c906108c SS |
5628 | |
5629 | @cindex @{@var{type}@} | |
5630 | @cindex type casting memory | |
5631 | @cindex memory, viewing as typed object | |
5632 | @cindex casts, to view memory | |
5633 | @item @{@var{type}@} @var{addr} | |
5634 | Refers to an object of type @var{type} stored at address @var{addr} in | |
5635 | memory. @var{addr} may be any expression whose value is an integer or | |
5636 | pointer (but parentheses are required around binary operators, just as in | |
5637 | a cast). This construct is allowed regardless of what kind of data is | |
5638 | normally supposed to reside at @var{addr}. | |
5639 | @end table | |
5640 | ||
6d2ebf8b | 5641 | @node Variables |
79a6e687 | 5642 | @section Program Variables |
c906108c SS |
5643 | |
5644 | The most common kind of expression to use is the name of a variable | |
5645 | in your program. | |
5646 | ||
5647 | Variables in expressions are understood in the selected stack frame | |
79a6e687 | 5648 | (@pxref{Selection, ,Selecting a Frame}); they must be either: |
c906108c SS |
5649 | |
5650 | @itemize @bullet | |
5651 | @item | |
5652 | global (or file-static) | |
5653 | @end itemize | |
5654 | ||
5d161b24 | 5655 | @noindent or |
c906108c SS |
5656 | |
5657 | @itemize @bullet | |
5658 | @item | |
5659 | visible according to the scope rules of the | |
5660 | programming language from the point of execution in that frame | |
5d161b24 | 5661 | @end itemize |
c906108c SS |
5662 | |
5663 | @noindent This means that in the function | |
5664 | ||
474c8240 | 5665 | @smallexample |
c906108c SS |
5666 | foo (a) |
5667 | int a; | |
5668 | @{ | |
5669 | bar (a); | |
5670 | @{ | |
5671 | int b = test (); | |
5672 | bar (b); | |
5673 | @} | |
5674 | @} | |
474c8240 | 5675 | @end smallexample |
c906108c SS |
5676 | |
5677 | @noindent | |
5678 | you can examine and use the variable @code{a} whenever your program is | |
5679 | executing within the function @code{foo}, but you can only use or | |
5680 | examine the variable @code{b} while your program is executing inside | |
5681 | the block where @code{b} is declared. | |
5682 | ||
5683 | @cindex variable name conflict | |
5684 | There is an exception: you can refer to a variable or function whose | |
5685 | scope is a single source file even if the current execution point is not | |
5686 | in this file. But it is possible to have more than one such variable or | |
5687 | function with the same name (in different source files). If that | |
5688 | happens, referring to that name has unpredictable effects. If you wish, | |
5689 | you can specify a static variable in a particular function or file, | |
15387254 | 5690 | using the colon-colon (@code{::}) notation: |
c906108c | 5691 | |
d4f3574e | 5692 | @cindex colon-colon, context for variables/functions |
12c27660 | 5693 | @ifnotinfo |
c906108c | 5694 | @c info cannot cope with a :: index entry, but why deprive hard copy readers? |
41afff9a | 5695 | @cindex @code{::}, context for variables/functions |
12c27660 | 5696 | @end ifnotinfo |
474c8240 | 5697 | @smallexample |
c906108c SS |
5698 | @var{file}::@var{variable} |
5699 | @var{function}::@var{variable} | |
474c8240 | 5700 | @end smallexample |
c906108c SS |
5701 | |
5702 | @noindent | |
5703 | Here @var{file} or @var{function} is the name of the context for the | |
5704 | static @var{variable}. In the case of file names, you can use quotes to | |
5705 | make sure @value{GDBN} parses the file name as a single word---for example, | |
5706 | to print a global value of @code{x} defined in @file{f2.c}: | |
5707 | ||
474c8240 | 5708 | @smallexample |
c906108c | 5709 | (@value{GDBP}) p 'f2.c'::x |
474c8240 | 5710 | @end smallexample |
c906108c | 5711 | |
b37052ae | 5712 | @cindex C@t{++} scope resolution |
c906108c | 5713 | This use of @samp{::} is very rarely in conflict with the very similar |
b37052ae | 5714 | use of the same notation in C@t{++}. @value{GDBN} also supports use of the C@t{++} |
c906108c SS |
5715 | scope resolution operator in @value{GDBN} expressions. |
5716 | @c FIXME: Um, so what happens in one of those rare cases where it's in | |
5717 | @c conflict?? --mew | |
c906108c SS |
5718 | |
5719 | @cindex wrong values | |
5720 | @cindex variable values, wrong | |
15387254 EZ |
5721 | @cindex function entry/exit, wrong values of variables |
5722 | @cindex optimized code, wrong values of variables | |
c906108c SS |
5723 | @quotation |
5724 | @emph{Warning:} Occasionally, a local variable may appear to have the | |
5725 | wrong value at certain points in a function---just after entry to a new | |
5726 | scope, and just before exit. | |
5727 | @end quotation | |
5728 | You may see this problem when you are stepping by machine instructions. | |
5729 | This is because, on most machines, it takes more than one instruction to | |
5730 | set up a stack frame (including local variable definitions); if you are | |
5731 | stepping by machine instructions, variables may appear to have the wrong | |
5732 | values until the stack frame is completely built. On exit, it usually | |
5733 | also takes more than one machine instruction to destroy a stack frame; | |
5734 | after you begin stepping through that group of instructions, local | |
5735 | variable definitions may be gone. | |
5736 | ||
5737 | This may also happen when the compiler does significant optimizations. | |
5738 | To be sure of always seeing accurate values, turn off all optimization | |
5739 | when compiling. | |
5740 | ||
d4f3574e SS |
5741 | @cindex ``No symbol "foo" in current context'' |
5742 | Another possible effect of compiler optimizations is to optimize | |
5743 | unused variables out of existence, or assign variables to registers (as | |
5744 | opposed to memory addresses). Depending on the support for such cases | |
5745 | offered by the debug info format used by the compiler, @value{GDBN} | |
5746 | might not be able to display values for such local variables. If that | |
5747 | happens, @value{GDBN} will print a message like this: | |
5748 | ||
474c8240 | 5749 | @smallexample |
d4f3574e | 5750 | No symbol "foo" in current context. |
474c8240 | 5751 | @end smallexample |
d4f3574e SS |
5752 | |
5753 | To solve such problems, either recompile without optimizations, or use a | |
5754 | different debug info format, if the compiler supports several such | |
15387254 | 5755 | formats. For example, @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, |
0179ffac DC |
5756 | usually supports the @option{-gstabs+} option. @option{-gstabs+} |
5757 | produces debug info in a format that is superior to formats such as | |
5758 | COFF. You may be able to use DWARF 2 (@option{-gdwarf-2}), which is also | |
5759 | an effective form for debug info. @xref{Debugging Options,,Options | |
ce9341a1 BW |
5760 | for Debugging Your Program or GCC, gcc.info, Using the @sc{gnu} |
5761 | Compiler Collection (GCC)}. | |
79a6e687 | 5762 | @xref{C, ,C and C@t{++}}, for more information about debug info formats |
15387254 | 5763 | that are best suited to C@t{++} programs. |
d4f3574e | 5764 | |
ab1adacd EZ |
5765 | If you ask to print an object whose contents are unknown to |
5766 | @value{GDBN}, e.g., because its data type is not completely specified | |
5767 | by the debug information, @value{GDBN} will say @samp{<incomplete | |
5768 | type>}. @xref{Symbols, incomplete type}, for more about this. | |
5769 | ||
3a60f64e JK |
5770 | Strings are identified as arrays of @code{char} values without specified |
5771 | signedness. Arrays of either @code{signed char} or @code{unsigned char} get | |
5772 | printed as arrays of 1 byte sized integers. @code{-fsigned-char} or | |
5773 | @code{-funsigned-char} @value{NGCC} options have no effect as @value{GDBN} | |
5774 | defines literal string type @code{"char"} as @code{char} without a sign. | |
5775 | For program code | |
5776 | ||
5777 | @smallexample | |
5778 | char var0[] = "A"; | |
5779 | signed char var1[] = "A"; | |
5780 | @end smallexample | |
5781 | ||
5782 | You get during debugging | |
5783 | @smallexample | |
5784 | (gdb) print var0 | |
5785 | $1 = "A" | |
5786 | (gdb) print var1 | |
5787 | $2 = @{65 'A', 0 '\0'@} | |
5788 | @end smallexample | |
5789 | ||
6d2ebf8b | 5790 | @node Arrays |
79a6e687 | 5791 | @section Artificial Arrays |
c906108c SS |
5792 | |
5793 | @cindex artificial array | |
15387254 | 5794 | @cindex arrays |
41afff9a | 5795 | @kindex @@@r{, referencing memory as an array} |
c906108c SS |
5796 | It is often useful to print out several successive objects of the |
5797 | same type in memory; a section of an array, or an array of | |
5798 | dynamically determined size for which only a pointer exists in the | |
5799 | program. | |
5800 | ||
5801 | You can do this by referring to a contiguous span of memory as an | |
5802 | @dfn{artificial array}, using the binary operator @samp{@@}. The left | |
5803 | operand of @samp{@@} should be the first element of the desired array | |
5804 | and be an individual object. The right operand should be the desired length | |
5805 | of the array. The result is an array value whose elements are all of | |
5806 | the type of the left argument. The first element is actually the left | |
5807 | argument; the second element comes from bytes of memory immediately | |
5808 | following those that hold the first element, and so on. Here is an | |
5809 | example. If a program says | |
5810 | ||
474c8240 | 5811 | @smallexample |
c906108c | 5812 | int *array = (int *) malloc (len * sizeof (int)); |
474c8240 | 5813 | @end smallexample |
c906108c SS |
5814 | |
5815 | @noindent | |
5816 | you can print the contents of @code{array} with | |
5817 | ||
474c8240 | 5818 | @smallexample |
c906108c | 5819 | p *array@@len |
474c8240 | 5820 | @end smallexample |
c906108c SS |
5821 | |
5822 | The left operand of @samp{@@} must reside in memory. Array values made | |
5823 | with @samp{@@} in this way behave just like other arrays in terms of | |
5824 | subscripting, and are coerced to pointers when used in expressions. | |
5825 | Artificial arrays most often appear in expressions via the value history | |
79a6e687 | 5826 | (@pxref{Value History, ,Value History}), after printing one out. |
c906108c SS |
5827 | |
5828 | Another way to create an artificial array is to use a cast. | |
5829 | This re-interprets a value as if it were an array. | |
5830 | The value need not be in memory: | |
474c8240 | 5831 | @smallexample |
c906108c SS |
5832 | (@value{GDBP}) p/x (short[2])0x12345678 |
5833 | $1 = @{0x1234, 0x5678@} | |
474c8240 | 5834 | @end smallexample |
c906108c SS |
5835 | |
5836 | As a convenience, if you leave the array length out (as in | |
c3f6f71d | 5837 | @samp{(@var{type}[])@var{value}}) @value{GDBN} calculates the size to fill |
c906108c | 5838 | the value (as @samp{sizeof(@var{value})/sizeof(@var{type})}: |
474c8240 | 5839 | @smallexample |
c906108c SS |
5840 | (@value{GDBP}) p/x (short[])0x12345678 |
5841 | $2 = @{0x1234, 0x5678@} | |
474c8240 | 5842 | @end smallexample |
c906108c SS |
5843 | |
5844 | Sometimes the artificial array mechanism is not quite enough; in | |
5845 | moderately complex data structures, the elements of interest may not | |
5846 | actually be adjacent---for example, if you are interested in the values | |
5847 | of pointers in an array. One useful work-around in this situation is | |
5848 | to use a convenience variable (@pxref{Convenience Vars, ,Convenience | |
79a6e687 | 5849 | Variables}) as a counter in an expression that prints the first |
c906108c SS |
5850 | interesting value, and then repeat that expression via @key{RET}. For |
5851 | instance, suppose you have an array @code{dtab} of pointers to | |
5852 | structures, and you are interested in the values of a field @code{fv} | |
5853 | in each structure. Here is an example of what you might type: | |
5854 | ||
474c8240 | 5855 | @smallexample |
c906108c SS |
5856 | set $i = 0 |
5857 | p dtab[$i++]->fv | |
5858 | @key{RET} | |
5859 | @key{RET} | |
5860 | @dots{} | |
474c8240 | 5861 | @end smallexample |
c906108c | 5862 | |
6d2ebf8b | 5863 | @node Output Formats |
79a6e687 | 5864 | @section Output Formats |
c906108c SS |
5865 | |
5866 | @cindex formatted output | |
5867 | @cindex output formats | |
5868 | By default, @value{GDBN} prints a value according to its data type. Sometimes | |
5869 | this is not what you want. For example, you might want to print a number | |
5870 | in hex, or a pointer in decimal. Or you might want to view data in memory | |
5871 | at a certain address as a character string or as an instruction. To do | |
5872 | these things, specify an @dfn{output format} when you print a value. | |
5873 | ||
5874 | The simplest use of output formats is to say how to print a value | |
5875 | already computed. This is done by starting the arguments of the | |
5876 | @code{print} command with a slash and a format letter. The format | |
5877 | letters supported are: | |
5878 | ||
5879 | @table @code | |
5880 | @item x | |
5881 | Regard the bits of the value as an integer, and print the integer in | |
5882 | hexadecimal. | |
5883 | ||
5884 | @item d | |
5885 | Print as integer in signed decimal. | |
5886 | ||
5887 | @item u | |
5888 | Print as integer in unsigned decimal. | |
5889 | ||
5890 | @item o | |
5891 | Print as integer in octal. | |
5892 | ||
5893 | @item t | |
5894 | Print as integer in binary. The letter @samp{t} stands for ``two''. | |
5895 | @footnote{@samp{b} cannot be used because these format letters are also | |
5896 | used with the @code{x} command, where @samp{b} stands for ``byte''; | |
79a6e687 | 5897 | see @ref{Memory,,Examining Memory}.} |
c906108c SS |
5898 | |
5899 | @item a | |
5900 | @cindex unknown address, locating | |
3d67e040 | 5901 | @cindex locate address |
c906108c SS |
5902 | Print as an address, both absolute in hexadecimal and as an offset from |
5903 | the nearest preceding symbol. You can use this format used to discover | |
5904 | where (in what function) an unknown address is located: | |
5905 | ||
474c8240 | 5906 | @smallexample |
c906108c SS |
5907 | (@value{GDBP}) p/a 0x54320 |
5908 | $3 = 0x54320 <_initialize_vx+396> | |
474c8240 | 5909 | @end smallexample |
c906108c | 5910 | |
3d67e040 EZ |
5911 | @noindent |
5912 | The command @code{info symbol 0x54320} yields similar results. | |
5913 | @xref{Symbols, info symbol}. | |
5914 | ||
c906108c | 5915 | @item c |
51274035 EZ |
5916 | Regard as an integer and print it as a character constant. This |
5917 | prints both the numerical value and its character representation. The | |
5918 | character representation is replaced with the octal escape @samp{\nnn} | |
5919 | for characters outside the 7-bit @sc{ascii} range. | |
c906108c | 5920 | |
ea37ba09 DJ |
5921 | Without this format, @value{GDBN} displays @code{char}, |
5922 | @w{@code{unsigned char}}, and @w{@code{signed char}} data as character | |
5923 | constants. Single-byte members of vectors are displayed as integer | |
5924 | data. | |
5925 | ||
c906108c SS |
5926 | @item f |
5927 | Regard the bits of the value as a floating point number and print | |
5928 | using typical floating point syntax. | |
ea37ba09 DJ |
5929 | |
5930 | @item s | |
5931 | @cindex printing strings | |
5932 | @cindex printing byte arrays | |
5933 | Regard as a string, if possible. With this format, pointers to single-byte | |
5934 | data are displayed as null-terminated strings and arrays of single-byte data | |
5935 | are displayed as fixed-length strings. Other values are displayed in their | |
5936 | natural types. | |
5937 | ||
5938 | Without this format, @value{GDBN} displays pointers to and arrays of | |
5939 | @code{char}, @w{@code{unsigned char}}, and @w{@code{signed char}} as | |
5940 | strings. Single-byte members of a vector are displayed as an integer | |
5941 | array. | |
c906108c SS |
5942 | @end table |
5943 | ||
5944 | For example, to print the program counter in hex (@pxref{Registers}), type | |
5945 | ||
474c8240 | 5946 | @smallexample |
c906108c | 5947 | p/x $pc |
474c8240 | 5948 | @end smallexample |
c906108c SS |
5949 | |
5950 | @noindent | |
5951 | Note that no space is required before the slash; this is because command | |
5952 | names in @value{GDBN} cannot contain a slash. | |
5953 | ||
5954 | To reprint the last value in the value history with a different format, | |
5955 | you can use the @code{print} command with just a format and no | |
5956 | expression. For example, @samp{p/x} reprints the last value in hex. | |
5957 | ||
6d2ebf8b | 5958 | @node Memory |
79a6e687 | 5959 | @section Examining Memory |
c906108c SS |
5960 | |
5961 | You can use the command @code{x} (for ``examine'') to examine memory in | |
5962 | any of several formats, independently of your program's data types. | |
5963 | ||
5964 | @cindex examining memory | |
5965 | @table @code | |
41afff9a | 5966 | @kindex x @r{(examine memory)} |
c906108c SS |
5967 | @item x/@var{nfu} @var{addr} |
5968 | @itemx x @var{addr} | |
5969 | @itemx x | |
5970 | Use the @code{x} command to examine memory. | |
5971 | @end table | |
5972 | ||
5973 | @var{n}, @var{f}, and @var{u} are all optional parameters that specify how | |
5974 | much memory to display and how to format it; @var{addr} is an | |
5975 | expression giving the address where you want to start displaying memory. | |
5976 | If you use defaults for @var{nfu}, you need not type the slash @samp{/}. | |
5977 | Several commands set convenient defaults for @var{addr}. | |
5978 | ||
5979 | @table @r | |
5980 | @item @var{n}, the repeat count | |
5981 | The repeat count is a decimal integer; the default is 1. It specifies | |
5982 | how much memory (counting by units @var{u}) to display. | |
5983 | @c This really is **decimal**; unaffected by 'set radix' as of GDB | |
5984 | @c 4.1.2. | |
5985 | ||
5986 | @item @var{f}, the display format | |
51274035 EZ |
5987 | The display format is one of the formats used by @code{print} |
5988 | (@samp{x}, @samp{d}, @samp{u}, @samp{o}, @samp{t}, @samp{a}, @samp{c}, | |
ea37ba09 DJ |
5989 | @samp{f}, @samp{s}), and in addition @samp{i} (for machine instructions). |
5990 | The default is @samp{x} (hexadecimal) initially. The default changes | |
5991 | each time you use either @code{x} or @code{print}. | |
c906108c SS |
5992 | |
5993 | @item @var{u}, the unit size | |
5994 | The unit size is any of | |
5995 | ||
5996 | @table @code | |
5997 | @item b | |
5998 | Bytes. | |
5999 | @item h | |
6000 | Halfwords (two bytes). | |
6001 | @item w | |
6002 | Words (four bytes). This is the initial default. | |
6003 | @item g | |
6004 | Giant words (eight bytes). | |
6005 | @end table | |
6006 | ||
6007 | Each time you specify a unit size with @code{x}, that size becomes the | |
6008 | default unit the next time you use @code{x}. (For the @samp{s} and | |
6009 | @samp{i} formats, the unit size is ignored and is normally not written.) | |
6010 | ||
6011 | @item @var{addr}, starting display address | |
6012 | @var{addr} is the address where you want @value{GDBN} to begin displaying | |
6013 | memory. The expression need not have a pointer value (though it may); | |
6014 | it is always interpreted as an integer address of a byte of memory. | |
6015 | @xref{Expressions, ,Expressions}, for more information on expressions. The default for | |
6016 | @var{addr} is usually just after the last address examined---but several | |
6017 | other commands also set the default address: @code{info breakpoints} (to | |
6018 | the address of the last breakpoint listed), @code{info line} (to the | |
6019 | starting address of a line), and @code{print} (if you use it to display | |
6020 | a value from memory). | |
6021 | @end table | |
6022 | ||
6023 | For example, @samp{x/3uh 0x54320} is a request to display three halfwords | |
6024 | (@code{h}) of memory, formatted as unsigned decimal integers (@samp{u}), | |
6025 | starting at address @code{0x54320}. @samp{x/4xw $sp} prints the four | |
6026 | words (@samp{w}) of memory above the stack pointer (here, @samp{$sp}; | |
d4f3574e | 6027 | @pxref{Registers, ,Registers}) in hexadecimal (@samp{x}). |
c906108c SS |
6028 | |
6029 | Since the letters indicating unit sizes are all distinct from the | |
6030 | letters specifying output formats, you do not have to remember whether | |
6031 | unit size or format comes first; either order works. The output | |
6032 | specifications @samp{4xw} and @samp{4wx} mean exactly the same thing. | |
6033 | (However, the count @var{n} must come first; @samp{wx4} does not work.) | |
6034 | ||
6035 | Even though the unit size @var{u} is ignored for the formats @samp{s} | |
6036 | and @samp{i}, you might still want to use a count @var{n}; for example, | |
6037 | @samp{3i} specifies that you want to see three machine instructions, | |
a4642986 MR |
6038 | including any operands. For convenience, especially when used with |
6039 | the @code{display} command, the @samp{i} format also prints branch delay | |
6040 | slot instructions, if any, beyond the count specified, which immediately | |
6041 | follow the last instruction that is within the count. The command | |
6042 | @code{disassemble} gives an alternative way of inspecting machine | |
6043 | instructions; see @ref{Machine Code,,Source and Machine Code}. | |
c906108c SS |
6044 | |
6045 | All the defaults for the arguments to @code{x} are designed to make it | |
6046 | easy to continue scanning memory with minimal specifications each time | |
6047 | you use @code{x}. For example, after you have inspected three machine | |
6048 | instructions with @samp{x/3i @var{addr}}, you can inspect the next seven | |
6049 | with just @samp{x/7}. If you use @key{RET} to repeat the @code{x} command, | |
6050 | the repeat count @var{n} is used again; the other arguments default as | |
6051 | for successive uses of @code{x}. | |
6052 | ||
6053 | @cindex @code{$_}, @code{$__}, and value history | |
6054 | The addresses and contents printed by the @code{x} command are not saved | |
6055 | in the value history because there is often too much of them and they | |
6056 | would get in the way. Instead, @value{GDBN} makes these values available for | |
6057 | subsequent use in expressions as values of the convenience variables | |
6058 | @code{$_} and @code{$__}. After an @code{x} command, the last address | |
6059 | examined is available for use in expressions in the convenience variable | |
6060 | @code{$_}. The contents of that address, as examined, are available in | |
6061 | the convenience variable @code{$__}. | |
6062 | ||
6063 | If the @code{x} command has a repeat count, the address and contents saved | |
6064 | are from the last memory unit printed; this is not the same as the last | |
6065 | address printed if several units were printed on the last line of output. | |
6066 | ||
09d4efe1 EZ |
6067 | @cindex remote memory comparison |
6068 | @cindex verify remote memory image | |
6069 | When you are debugging a program running on a remote target machine | |
ea35711c | 6070 | (@pxref{Remote Debugging}), you may wish to verify the program's image in the |
09d4efe1 EZ |
6071 | remote machine's memory against the executable file you downloaded to |
6072 | the target. The @code{compare-sections} command is provided for such | |
6073 | situations. | |
6074 | ||
6075 | @table @code | |
6076 | @kindex compare-sections | |
6077 | @item compare-sections @r{[}@var{section-name}@r{]} | |
6078 | Compare the data of a loadable section @var{section-name} in the | |
6079 | executable file of the program being debugged with the same section in | |
6080 | the remote machine's memory, and report any mismatches. With no | |
6081 | arguments, compares all loadable sections. This command's | |
6082 | availability depends on the target's support for the @code{"qCRC"} | |
6083 | remote request. | |
6084 | @end table | |
6085 | ||
6d2ebf8b | 6086 | @node Auto Display |
79a6e687 | 6087 | @section Automatic Display |
c906108c SS |
6088 | @cindex automatic display |
6089 | @cindex display of expressions | |
6090 | ||
6091 | If you find that you want to print the value of an expression frequently | |
6092 | (to see how it changes), you might want to add it to the @dfn{automatic | |
6093 | display list} so that @value{GDBN} prints its value each time your program stops. | |
6094 | Each expression added to the list is given a number to identify it; | |
6095 | to remove an expression from the list, you specify that number. | |
6096 | The automatic display looks like this: | |
6097 | ||
474c8240 | 6098 | @smallexample |
c906108c SS |
6099 | 2: foo = 38 |
6100 | 3: bar[5] = (struct hack *) 0x3804 | |
474c8240 | 6101 | @end smallexample |
c906108c SS |
6102 | |
6103 | @noindent | |
6104 | This display shows item numbers, expressions and their current values. As with | |
6105 | displays you request manually using @code{x} or @code{print}, you can | |
6106 | specify the output format you prefer; in fact, @code{display} decides | |
ea37ba09 DJ |
6107 | whether to use @code{print} or @code{x} depending your format |
6108 | specification---it uses @code{x} if you specify either the @samp{i} | |
6109 | or @samp{s} format, or a unit size; otherwise it uses @code{print}. | |
c906108c SS |
6110 | |
6111 | @table @code | |
6112 | @kindex display | |
d4f3574e SS |
6113 | @item display @var{expr} |
6114 | Add the expression @var{expr} to the list of expressions to display | |
c906108c SS |
6115 | each time your program stops. @xref{Expressions, ,Expressions}. |
6116 | ||
6117 | @code{display} does not repeat if you press @key{RET} again after using it. | |
6118 | ||
d4f3574e | 6119 | @item display/@var{fmt} @var{expr} |
c906108c | 6120 | For @var{fmt} specifying only a display format and not a size or |
d4f3574e | 6121 | count, add the expression @var{expr} to the auto-display list but |
c906108c | 6122 | arrange to display it each time in the specified format @var{fmt}. |
79a6e687 | 6123 | @xref{Output Formats,,Output Formats}. |
c906108c SS |
6124 | |
6125 | @item display/@var{fmt} @var{addr} | |
6126 | For @var{fmt} @samp{i} or @samp{s}, or including a unit-size or a | |
6127 | number of units, add the expression @var{addr} as a memory address to | |
6128 | be examined each time your program stops. Examining means in effect | |
79a6e687 | 6129 | doing @samp{x/@var{fmt} @var{addr}}. @xref{Memory, ,Examining Memory}. |
c906108c SS |
6130 | @end table |
6131 | ||
6132 | For example, @samp{display/i $pc} can be helpful, to see the machine | |
6133 | instruction about to be executed each time execution stops (@samp{$pc} | |
d4f3574e | 6134 | is a common name for the program counter; @pxref{Registers, ,Registers}). |
c906108c SS |
6135 | |
6136 | @table @code | |
6137 | @kindex delete display | |
6138 | @kindex undisplay | |
6139 | @item undisplay @var{dnums}@dots{} | |
6140 | @itemx delete display @var{dnums}@dots{} | |
6141 | Remove item numbers @var{dnums} from the list of expressions to display. | |
6142 | ||
6143 | @code{undisplay} does not repeat if you press @key{RET} after using it. | |
6144 | (Otherwise you would just get the error @samp{No display number @dots{}}.) | |
6145 | ||
6146 | @kindex disable display | |
6147 | @item disable display @var{dnums}@dots{} | |
6148 | Disable the display of item numbers @var{dnums}. A disabled display | |
6149 | item is not printed automatically, but is not forgotten. It may be | |
6150 | enabled again later. | |
6151 | ||
6152 | @kindex enable display | |
6153 | @item enable display @var{dnums}@dots{} | |
6154 | Enable display of item numbers @var{dnums}. It becomes effective once | |
6155 | again in auto display of its expression, until you specify otherwise. | |
6156 | ||
6157 | @item display | |
6158 | Display the current values of the expressions on the list, just as is | |
6159 | done when your program stops. | |
6160 | ||
6161 | @kindex info display | |
6162 | @item info display | |
6163 | Print the list of expressions previously set up to display | |
6164 | automatically, each one with its item number, but without showing the | |
6165 | values. This includes disabled expressions, which are marked as such. | |
6166 | It also includes expressions which would not be displayed right now | |
6167 | because they refer to automatic variables not currently available. | |
6168 | @end table | |
6169 | ||
15387254 | 6170 | @cindex display disabled out of scope |
c906108c SS |
6171 | If a display expression refers to local variables, then it does not make |
6172 | sense outside the lexical context for which it was set up. Such an | |
6173 | expression is disabled when execution enters a context where one of its | |
6174 | variables is not defined. For example, if you give the command | |
6175 | @code{display last_char} while inside a function with an argument | |
6176 | @code{last_char}, @value{GDBN} displays this argument while your program | |
6177 | continues to stop inside that function. When it stops elsewhere---where | |
6178 | there is no variable @code{last_char}---the display is disabled | |
6179 | automatically. The next time your program stops where @code{last_char} | |
6180 | is meaningful, you can enable the display expression once again. | |
6181 | ||
6d2ebf8b | 6182 | @node Print Settings |
79a6e687 | 6183 | @section Print Settings |
c906108c SS |
6184 | |
6185 | @cindex format options | |
6186 | @cindex print settings | |
6187 | @value{GDBN} provides the following ways to control how arrays, structures, | |
6188 | and symbols are printed. | |
6189 | ||
6190 | @noindent | |
6191 | These settings are useful for debugging programs in any language: | |
6192 | ||
6193 | @table @code | |
4644b6e3 | 6194 | @kindex set print |
c906108c SS |
6195 | @item set print address |
6196 | @itemx set print address on | |
4644b6e3 | 6197 | @cindex print/don't print memory addresses |
c906108c SS |
6198 | @value{GDBN} prints memory addresses showing the location of stack |
6199 | traces, structure values, pointer values, breakpoints, and so forth, | |
6200 | even when it also displays the contents of those addresses. The default | |
6201 | is @code{on}. For example, this is what a stack frame display looks like with | |
6202 | @code{set print address on}: | |
6203 | ||
6204 | @smallexample | |
6205 | @group | |
6206 | (@value{GDBP}) f | |
6207 | #0 set_quotes (lq=0x34c78 "<<", rq=0x34c88 ">>") | |
6208 | at input.c:530 | |
6209 | 530 if (lquote != def_lquote) | |
6210 | @end group | |
6211 | @end smallexample | |
6212 | ||
6213 | @item set print address off | |
6214 | Do not print addresses when displaying their contents. For example, | |
6215 | this is the same stack frame displayed with @code{set print address off}: | |
6216 | ||
6217 | @smallexample | |
6218 | @group | |
6219 | (@value{GDBP}) set print addr off | |
6220 | (@value{GDBP}) f | |
6221 | #0 set_quotes (lq="<<", rq=">>") at input.c:530 | |
6222 | 530 if (lquote != def_lquote) | |
6223 | @end group | |
6224 | @end smallexample | |
6225 | ||
6226 | You can use @samp{set print address off} to eliminate all machine | |
6227 | dependent displays from the @value{GDBN} interface. For example, with | |
6228 | @code{print address off}, you should get the same text for backtraces on | |
6229 | all machines---whether or not they involve pointer arguments. | |
6230 | ||
4644b6e3 | 6231 | @kindex show print |
c906108c SS |
6232 | @item show print address |
6233 | Show whether or not addresses are to be printed. | |
6234 | @end table | |
6235 | ||
6236 | When @value{GDBN} prints a symbolic address, it normally prints the | |
6237 | closest earlier symbol plus an offset. If that symbol does not uniquely | |
6238 | identify the address (for example, it is a name whose scope is a single | |
6239 | source file), you may need to clarify. One way to do this is with | |
6240 | @code{info line}, for example @samp{info line *0x4537}. Alternately, | |
6241 | you can set @value{GDBN} to print the source file and line number when | |
6242 | it prints a symbolic address: | |
6243 | ||
6244 | @table @code | |
c906108c | 6245 | @item set print symbol-filename on |
9c16f35a EZ |
6246 | @cindex source file and line of a symbol |
6247 | @cindex symbol, source file and line | |
c906108c SS |
6248 | Tell @value{GDBN} to print the source file name and line number of a |
6249 | symbol in the symbolic form of an address. | |
6250 | ||
6251 | @item set print symbol-filename off | |
6252 | Do not print source file name and line number of a symbol. This is the | |
6253 | default. | |
6254 | ||
c906108c SS |
6255 | @item show print symbol-filename |
6256 | Show whether or not @value{GDBN} will print the source file name and | |
6257 | line number of a symbol in the symbolic form of an address. | |
6258 | @end table | |
6259 | ||
6260 | Another situation where it is helpful to show symbol filenames and line | |
6261 | numbers is when disassembling code; @value{GDBN} shows you the line | |
6262 | number and source file that corresponds to each instruction. | |
6263 | ||
6264 | Also, you may wish to see the symbolic form only if the address being | |
6265 | printed is reasonably close to the closest earlier symbol: | |
6266 | ||
6267 | @table @code | |
c906108c | 6268 | @item set print max-symbolic-offset @var{max-offset} |
4644b6e3 | 6269 | @cindex maximum value for offset of closest symbol |
c906108c SS |
6270 | Tell @value{GDBN} to only display the symbolic form of an address if the |
6271 | offset between the closest earlier symbol and the address is less than | |
5d161b24 | 6272 | @var{max-offset}. The default is 0, which tells @value{GDBN} |
c906108c SS |
6273 | to always print the symbolic form of an address if any symbol precedes it. |
6274 | ||
c906108c SS |
6275 | @item show print max-symbolic-offset |
6276 | Ask how large the maximum offset is that @value{GDBN} prints in a | |
6277 | symbolic address. | |
6278 | @end table | |
6279 | ||
6280 | @cindex wild pointer, interpreting | |
6281 | @cindex pointer, finding referent | |
6282 | If you have a pointer and you are not sure where it points, try | |
6283 | @samp{set print symbol-filename on}. Then you can determine the name | |
6284 | and source file location of the variable where it points, using | |
6285 | @samp{p/a @var{pointer}}. This interprets the address in symbolic form. | |
6286 | For example, here @value{GDBN} shows that a variable @code{ptt} points | |
6287 | at another variable @code{t}, defined in @file{hi2.c}: | |
6288 | ||
474c8240 | 6289 | @smallexample |
c906108c SS |
6290 | (@value{GDBP}) set print symbol-filename on |
6291 | (@value{GDBP}) p/a ptt | |
6292 | $4 = 0xe008 <t in hi2.c> | |
474c8240 | 6293 | @end smallexample |
c906108c SS |
6294 | |
6295 | @quotation | |
6296 | @emph{Warning:} For pointers that point to a local variable, @samp{p/a} | |
6297 | does not show the symbol name and filename of the referent, even with | |
6298 | the appropriate @code{set print} options turned on. | |
6299 | @end quotation | |
6300 | ||
6301 | Other settings control how different kinds of objects are printed: | |
6302 | ||
6303 | @table @code | |
c906108c SS |
6304 | @item set print array |
6305 | @itemx set print array on | |
4644b6e3 | 6306 | @cindex pretty print arrays |
c906108c SS |
6307 | Pretty print arrays. This format is more convenient to read, |
6308 | but uses more space. The default is off. | |
6309 | ||
6310 | @item set print array off | |
6311 | Return to compressed format for arrays. | |
6312 | ||
c906108c SS |
6313 | @item show print array |
6314 | Show whether compressed or pretty format is selected for displaying | |
6315 | arrays. | |
6316 | ||
3c9c013a JB |
6317 | @cindex print array indexes |
6318 | @item set print array-indexes | |
6319 | @itemx set print array-indexes on | |
6320 | Print the index of each element when displaying arrays. May be more | |
6321 | convenient to locate a given element in the array or quickly find the | |
6322 | index of a given element in that printed array. The default is off. | |
6323 | ||
6324 | @item set print array-indexes off | |
6325 | Stop printing element indexes when displaying arrays. | |
6326 | ||
6327 | @item show print array-indexes | |
6328 | Show whether the index of each element is printed when displaying | |
6329 | arrays. | |
6330 | ||
c906108c | 6331 | @item set print elements @var{number-of-elements} |
4644b6e3 | 6332 | @cindex number of array elements to print |
9c16f35a | 6333 | @cindex limit on number of printed array elements |
c906108c SS |
6334 | Set a limit on how many elements of an array @value{GDBN} will print. |
6335 | If @value{GDBN} is printing a large array, it stops printing after it has | |
6336 | printed the number of elements set by the @code{set print elements} command. | |
6337 | This limit also applies to the display of strings. | |
d4f3574e | 6338 | When @value{GDBN} starts, this limit is set to 200. |
c906108c SS |
6339 | Setting @var{number-of-elements} to zero means that the printing is unlimited. |
6340 | ||
c906108c SS |
6341 | @item show print elements |
6342 | Display the number of elements of a large array that @value{GDBN} will print. | |
6343 | If the number is 0, then the printing is unlimited. | |
6344 | ||
b4740add JB |
6345 | @item set print frame-arguments @var{value} |
6346 | @cindex printing frame argument values | |
6347 | @cindex print all frame argument values | |
6348 | @cindex print frame argument values for scalars only | |
6349 | @cindex do not print frame argument values | |
6350 | This command allows to control how the values of arguments are printed | |
6351 | when the debugger prints a frame (@pxref{Frames}). The possible | |
6352 | values are: | |
6353 | ||
6354 | @table @code | |
6355 | @item all | |
6356 | The values of all arguments are printed. This is the default. | |
6357 | ||
6358 | @item scalars | |
6359 | Print the value of an argument only if it is a scalar. The value of more | |
6360 | complex arguments such as arrays, structures, unions, etc, is replaced | |
6361 | by @code{@dots{}}. Here is an example where only scalar arguments are shown: | |
6362 | ||
6363 | @smallexample | |
6364 | #1 0x08048361 in call_me (i=3, s=@dots{}, ss=0xbf8d508c, u=@dots{}, e=green) | |
6365 | at frame-args.c:23 | |
6366 | @end smallexample | |
6367 | ||
6368 | @item none | |
6369 | None of the argument values are printed. Instead, the value of each argument | |
6370 | is replaced by @code{@dots{}}. In this case, the example above now becomes: | |
6371 | ||
6372 | @smallexample | |
6373 | #1 0x08048361 in call_me (i=@dots{}, s=@dots{}, ss=@dots{}, u=@dots{}, e=@dots{}) | |
6374 | at frame-args.c:23 | |
6375 | @end smallexample | |
6376 | @end table | |
6377 | ||
6378 | By default, all argument values are always printed. But this command | |
6379 | can be useful in several cases. For instance, it can be used to reduce | |
6380 | the amount of information printed in each frame, making the backtrace | |
6381 | more readable. Also, this command can be used to improve performance | |
6382 | when displaying Ada frames, because the computation of large arguments | |
6383 | can sometimes be CPU-intensive, especiallly in large applications. | |
6384 | Setting @code{print frame-arguments} to @code{scalars} or @code{none} | |
6385 | avoids this computation, thus speeding up the display of each Ada frame. | |
6386 | ||
6387 | @item show print frame-arguments | |
6388 | Show how the value of arguments should be displayed when printing a frame. | |
6389 | ||
9c16f35a EZ |
6390 | @item set print repeats |
6391 | @cindex repeated array elements | |
6392 | Set the threshold for suppressing display of repeated array | |
d3e8051b | 6393 | elements. When the number of consecutive identical elements of an |
9c16f35a EZ |
6394 | array exceeds the threshold, @value{GDBN} prints the string |
6395 | @code{"<repeats @var{n} times>"}, where @var{n} is the number of | |
6396 | identical repetitions, instead of displaying the identical elements | |
6397 | themselves. Setting the threshold to zero will cause all elements to | |
6398 | be individually printed. The default threshold is 10. | |
6399 | ||
6400 | @item show print repeats | |
6401 | Display the current threshold for printing repeated identical | |
6402 | elements. | |
6403 | ||
c906108c | 6404 | @item set print null-stop |
4644b6e3 | 6405 | @cindex @sc{null} elements in arrays |
c906108c | 6406 | Cause @value{GDBN} to stop printing the characters of an array when the first |
d4f3574e | 6407 | @sc{null} is encountered. This is useful when large arrays actually |
c906108c | 6408 | contain only short strings. |
d4f3574e | 6409 | The default is off. |
c906108c | 6410 | |
9c16f35a EZ |
6411 | @item show print null-stop |
6412 | Show whether @value{GDBN} stops printing an array on the first | |
6413 | @sc{null} character. | |
6414 | ||
c906108c | 6415 | @item set print pretty on |
9c16f35a EZ |
6416 | @cindex print structures in indented form |
6417 | @cindex indentation in structure display | |
5d161b24 | 6418 | Cause @value{GDBN} to print structures in an indented format with one member |
c906108c SS |
6419 | per line, like this: |
6420 | ||
6421 | @smallexample | |
6422 | @group | |
6423 | $1 = @{ | |
6424 | next = 0x0, | |
6425 | flags = @{ | |
6426 | sweet = 1, | |
6427 | sour = 1 | |
6428 | @}, | |
6429 | meat = 0x54 "Pork" | |
6430 | @} | |
6431 | @end group | |
6432 | @end smallexample | |
6433 | ||
6434 | @item set print pretty off | |
6435 | Cause @value{GDBN} to print structures in a compact format, like this: | |
6436 | ||
6437 | @smallexample | |
6438 | @group | |
6439 | $1 = @{next = 0x0, flags = @{sweet = 1, sour = 1@}, \ | |
6440 | meat = 0x54 "Pork"@} | |
6441 | @end group | |
6442 | @end smallexample | |
6443 | ||
6444 | @noindent | |
6445 | This is the default format. | |
6446 | ||
c906108c SS |
6447 | @item show print pretty |
6448 | Show which format @value{GDBN} is using to print structures. | |
6449 | ||
c906108c | 6450 | @item set print sevenbit-strings on |
4644b6e3 EZ |
6451 | @cindex eight-bit characters in strings |
6452 | @cindex octal escapes in strings | |
c906108c SS |
6453 | Print using only seven-bit characters; if this option is set, |
6454 | @value{GDBN} displays any eight-bit characters (in strings or | |
6455 | character values) using the notation @code{\}@var{nnn}. This setting is | |
6456 | best if you are working in English (@sc{ascii}) and you use the | |
6457 | high-order bit of characters as a marker or ``meta'' bit. | |
6458 | ||
6459 | @item set print sevenbit-strings off | |
6460 | Print full eight-bit characters. This allows the use of more | |
6461 | international character sets, and is the default. | |
6462 | ||
c906108c SS |
6463 | @item show print sevenbit-strings |
6464 | Show whether or not @value{GDBN} is printing only seven-bit characters. | |
6465 | ||
c906108c | 6466 | @item set print union on |
4644b6e3 | 6467 | @cindex unions in structures, printing |
9c16f35a EZ |
6468 | Tell @value{GDBN} to print unions which are contained in structures |
6469 | and other unions. This is the default setting. | |
c906108c SS |
6470 | |
6471 | @item set print union off | |
9c16f35a EZ |
6472 | Tell @value{GDBN} not to print unions which are contained in |
6473 | structures and other unions. @value{GDBN} will print @code{"@{...@}"} | |
6474 | instead. | |
c906108c | 6475 | |
c906108c SS |
6476 | @item show print union |
6477 | Ask @value{GDBN} whether or not it will print unions which are contained in | |
9c16f35a | 6478 | structures and other unions. |
c906108c SS |
6479 | |
6480 | For example, given the declarations | |
6481 | ||
6482 | @smallexample | |
6483 | typedef enum @{Tree, Bug@} Species; | |
6484 | typedef enum @{Big_tree, Acorn, Seedling@} Tree_forms; | |
5d161b24 | 6485 | typedef enum @{Caterpillar, Cocoon, Butterfly@} |
c906108c SS |
6486 | Bug_forms; |
6487 | ||
6488 | struct thing @{ | |
6489 | Species it; | |
6490 | union @{ | |
6491 | Tree_forms tree; | |
6492 | Bug_forms bug; | |
6493 | @} form; | |
6494 | @}; | |
6495 | ||
6496 | struct thing foo = @{Tree, @{Acorn@}@}; | |
6497 | @end smallexample | |
6498 | ||
6499 | @noindent | |
6500 | with @code{set print union on} in effect @samp{p foo} would print | |
6501 | ||
6502 | @smallexample | |
6503 | $1 = @{it = Tree, form = @{tree = Acorn, bug = Cocoon@}@} | |
6504 | @end smallexample | |
6505 | ||
6506 | @noindent | |
6507 | and with @code{set print union off} in effect it would print | |
6508 | ||
6509 | @smallexample | |
6510 | $1 = @{it = Tree, form = @{...@}@} | |
6511 | @end smallexample | |
9c16f35a EZ |
6512 | |
6513 | @noindent | |
6514 | @code{set print union} affects programs written in C-like languages | |
6515 | and in Pascal. | |
c906108c SS |
6516 | @end table |
6517 | ||
c906108c SS |
6518 | @need 1000 |
6519 | @noindent | |
b37052ae | 6520 | These settings are of interest when debugging C@t{++} programs: |
c906108c SS |
6521 | |
6522 | @table @code | |
4644b6e3 | 6523 | @cindex demangling C@t{++} names |
c906108c SS |
6524 | @item set print demangle |
6525 | @itemx set print demangle on | |
b37052ae | 6526 | Print C@t{++} names in their source form rather than in the encoded |
c906108c | 6527 | (``mangled'') form passed to the assembler and linker for type-safe |
d4f3574e | 6528 | linkage. The default is on. |
c906108c | 6529 | |
c906108c | 6530 | @item show print demangle |
b37052ae | 6531 | Show whether C@t{++} names are printed in mangled or demangled form. |
c906108c | 6532 | |
c906108c SS |
6533 | @item set print asm-demangle |
6534 | @itemx set print asm-demangle on | |
b37052ae | 6535 | Print C@t{++} names in their source form rather than their mangled form, even |
c906108c SS |
6536 | in assembler code printouts such as instruction disassemblies. |
6537 | The default is off. | |
6538 | ||
c906108c | 6539 | @item show print asm-demangle |
b37052ae | 6540 | Show whether C@t{++} names in assembly listings are printed in mangled |
c906108c SS |
6541 | or demangled form. |
6542 | ||
b37052ae EZ |
6543 | @cindex C@t{++} symbol decoding style |
6544 | @cindex symbol decoding style, C@t{++} | |
a8f24a35 | 6545 | @kindex set demangle-style |
c906108c SS |
6546 | @item set demangle-style @var{style} |
6547 | Choose among several encoding schemes used by different compilers to | |
b37052ae | 6548 | represent C@t{++} names. The choices for @var{style} are currently: |
c906108c SS |
6549 | |
6550 | @table @code | |
6551 | @item auto | |
6552 | Allow @value{GDBN} to choose a decoding style by inspecting your program. | |
6553 | ||
6554 | @item gnu | |
b37052ae | 6555 | Decode based on the @sc{gnu} C@t{++} compiler (@code{g++}) encoding algorithm. |
c906108c | 6556 | This is the default. |
c906108c SS |
6557 | |
6558 | @item hp | |
b37052ae | 6559 | Decode based on the HP ANSI C@t{++} (@code{aCC}) encoding algorithm. |
c906108c SS |
6560 | |
6561 | @item lucid | |
b37052ae | 6562 | Decode based on the Lucid C@t{++} compiler (@code{lcc}) encoding algorithm. |
c906108c SS |
6563 | |
6564 | @item arm | |
b37052ae | 6565 | Decode using the algorithm in the @cite{C@t{++} Annotated Reference Manual}. |
c906108c SS |
6566 | @strong{Warning:} this setting alone is not sufficient to allow |
6567 | debugging @code{cfront}-generated executables. @value{GDBN} would | |
6568 | require further enhancement to permit that. | |
6569 | ||
6570 | @end table | |
6571 | If you omit @var{style}, you will see a list of possible formats. | |
6572 | ||
c906108c | 6573 | @item show demangle-style |
b37052ae | 6574 | Display the encoding style currently in use for decoding C@t{++} symbols. |
c906108c | 6575 | |
c906108c SS |
6576 | @item set print object |
6577 | @itemx set print object on | |
4644b6e3 | 6578 | @cindex derived type of an object, printing |
9c16f35a | 6579 | @cindex display derived types |
c906108c SS |
6580 | When displaying a pointer to an object, identify the @emph{actual} |
6581 | (derived) type of the object rather than the @emph{declared} type, using | |
6582 | the virtual function table. | |
6583 | ||
6584 | @item set print object off | |
6585 | Display only the declared type of objects, without reference to the | |
6586 | virtual function table. This is the default setting. | |
6587 | ||
c906108c SS |
6588 | @item show print object |
6589 | Show whether actual, or declared, object types are displayed. | |
6590 | ||
c906108c SS |
6591 | @item set print static-members |
6592 | @itemx set print static-members on | |
4644b6e3 | 6593 | @cindex static members of C@t{++} objects |
b37052ae | 6594 | Print static members when displaying a C@t{++} object. The default is on. |
c906108c SS |
6595 | |
6596 | @item set print static-members off | |
b37052ae | 6597 | Do not print static members when displaying a C@t{++} object. |
c906108c | 6598 | |
c906108c | 6599 | @item show print static-members |
9c16f35a EZ |
6600 | Show whether C@t{++} static members are printed or not. |
6601 | ||
6602 | @item set print pascal_static-members | |
6603 | @itemx set print pascal_static-members on | |
d3e8051b EZ |
6604 | @cindex static members of Pascal objects |
6605 | @cindex Pascal objects, static members display | |
9c16f35a EZ |
6606 | Print static members when displaying a Pascal object. The default is on. |
6607 | ||
6608 | @item set print pascal_static-members off | |
6609 | Do not print static members when displaying a Pascal object. | |
6610 | ||
6611 | @item show print pascal_static-members | |
6612 | Show whether Pascal static members are printed or not. | |
c906108c SS |
6613 | |
6614 | @c These don't work with HP ANSI C++ yet. | |
c906108c SS |
6615 | @item set print vtbl |
6616 | @itemx set print vtbl on | |
4644b6e3 | 6617 | @cindex pretty print C@t{++} virtual function tables |
9c16f35a EZ |
6618 | @cindex virtual functions (C@t{++}) display |
6619 | @cindex VTBL display | |
b37052ae | 6620 | Pretty print C@t{++} virtual function tables. The default is off. |
c906108c | 6621 | (The @code{vtbl} commands do not work on programs compiled with the HP |
b37052ae | 6622 | ANSI C@t{++} compiler (@code{aCC}).) |
c906108c SS |
6623 | |
6624 | @item set print vtbl off | |
b37052ae | 6625 | Do not pretty print C@t{++} virtual function tables. |
c906108c | 6626 | |
c906108c | 6627 | @item show print vtbl |
b37052ae | 6628 | Show whether C@t{++} virtual function tables are pretty printed, or not. |
c906108c | 6629 | @end table |
c906108c | 6630 | |
6d2ebf8b | 6631 | @node Value History |
79a6e687 | 6632 | @section Value History |
c906108c SS |
6633 | |
6634 | @cindex value history | |
9c16f35a | 6635 | @cindex history of values printed by @value{GDBN} |
5d161b24 DB |
6636 | Values printed by the @code{print} command are saved in the @value{GDBN} |
6637 | @dfn{value history}. This allows you to refer to them in other expressions. | |
6638 | Values are kept until the symbol table is re-read or discarded | |
6639 | (for example with the @code{file} or @code{symbol-file} commands). | |
6640 | When the symbol table changes, the value history is discarded, | |
6641 | since the values may contain pointers back to the types defined in the | |
c906108c SS |
6642 | symbol table. |
6643 | ||
6644 | @cindex @code{$} | |
6645 | @cindex @code{$$} | |
6646 | @cindex history number | |
6647 | The values printed are given @dfn{history numbers} by which you can | |
6648 | refer to them. These are successive integers starting with one. | |
6649 | @code{print} shows you the history number assigned to a value by | |
6650 | printing @samp{$@var{num} = } before the value; here @var{num} is the | |
6651 | history number. | |
6652 | ||
6653 | To refer to any previous value, use @samp{$} followed by the value's | |
6654 | history number. The way @code{print} labels its output is designed to | |
6655 | remind you of this. Just @code{$} refers to the most recent value in | |
6656 | the history, and @code{$$} refers to the value before that. | |
6657 | @code{$$@var{n}} refers to the @var{n}th value from the end; @code{$$2} | |
6658 | is the value just prior to @code{$$}, @code{$$1} is equivalent to | |
6659 | @code{$$}, and @code{$$0} is equivalent to @code{$}. | |
6660 | ||
6661 | For example, suppose you have just printed a pointer to a structure and | |
6662 | want to see the contents of the structure. It suffices to type | |
6663 | ||
474c8240 | 6664 | @smallexample |
c906108c | 6665 | p *$ |
474c8240 | 6666 | @end smallexample |
c906108c SS |
6667 | |
6668 | If you have a chain of structures where the component @code{next} points | |
6669 | to the next one, you can print the contents of the next one with this: | |
6670 | ||
474c8240 | 6671 | @smallexample |
c906108c | 6672 | p *$.next |
474c8240 | 6673 | @end smallexample |
c906108c SS |
6674 | |
6675 | @noindent | |
6676 | You can print successive links in the chain by repeating this | |
6677 | command---which you can do by just typing @key{RET}. | |
6678 | ||
6679 | Note that the history records values, not expressions. If the value of | |
6680 | @code{x} is 4 and you type these commands: | |
6681 | ||
474c8240 | 6682 | @smallexample |
c906108c SS |
6683 | print x |
6684 | set x=5 | |
474c8240 | 6685 | @end smallexample |
c906108c SS |
6686 | |
6687 | @noindent | |
6688 | then the value recorded in the value history by the @code{print} command | |
6689 | remains 4 even though the value of @code{x} has changed. | |
6690 | ||
6691 | @table @code | |
6692 | @kindex show values | |
6693 | @item show values | |
6694 | Print the last ten values in the value history, with their item numbers. | |
6695 | This is like @samp{p@ $$9} repeated ten times, except that @code{show | |
6696 | values} does not change the history. | |
6697 | ||
6698 | @item show values @var{n} | |
6699 | Print ten history values centered on history item number @var{n}. | |
6700 | ||
6701 | @item show values + | |
6702 | Print ten history values just after the values last printed. If no more | |
6703 | values are available, @code{show values +} produces no display. | |
6704 | @end table | |
6705 | ||
6706 | Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the | |
6707 | same effect as @samp{show values +}. | |
6708 | ||
6d2ebf8b | 6709 | @node Convenience Vars |
79a6e687 | 6710 | @section Convenience Variables |
c906108c SS |
6711 | |
6712 | @cindex convenience variables | |
9c16f35a | 6713 | @cindex user-defined variables |
c906108c SS |
6714 | @value{GDBN} provides @dfn{convenience variables} that you can use within |
6715 | @value{GDBN} to hold on to a value and refer to it later. These variables | |
6716 | exist entirely within @value{GDBN}; they are not part of your program, and | |
6717 | setting a convenience variable has no direct effect on further execution | |
6718 | of your program. That is why you can use them freely. | |
6719 | ||
6720 | Convenience variables are prefixed with @samp{$}. Any name preceded by | |
6721 | @samp{$} can be used for a convenience variable, unless it is one of | |
d4f3574e | 6722 | the predefined machine-specific register names (@pxref{Registers, ,Registers}). |
c906108c | 6723 | (Value history references, in contrast, are @emph{numbers} preceded |
79a6e687 | 6724 | by @samp{$}. @xref{Value History, ,Value History}.) |
c906108c SS |
6725 | |
6726 | You can save a value in a convenience variable with an assignment | |
6727 | expression, just as you would set a variable in your program. | |
6728 | For example: | |
6729 | ||
474c8240 | 6730 | @smallexample |
c906108c | 6731 | set $foo = *object_ptr |
474c8240 | 6732 | @end smallexample |
c906108c SS |
6733 | |
6734 | @noindent | |
6735 | would save in @code{$foo} the value contained in the object pointed to by | |
6736 | @code{object_ptr}. | |
6737 | ||
6738 | Using a convenience variable for the first time creates it, but its | |
6739 | value is @code{void} until you assign a new value. You can alter the | |
6740 | value with another assignment at any time. | |
6741 | ||
6742 | Convenience variables have no fixed types. You can assign a convenience | |
6743 | variable any type of value, including structures and arrays, even if | |
6744 | that variable already has a value of a different type. The convenience | |
6745 | variable, when used as an expression, has the type of its current value. | |
6746 | ||
6747 | @table @code | |
6748 | @kindex show convenience | |
9c16f35a | 6749 | @cindex show all user variables |
c906108c SS |
6750 | @item show convenience |
6751 | Print a list of convenience variables used so far, and their values. | |
d4f3574e | 6752 | Abbreviated @code{show conv}. |
53e5f3cf AS |
6753 | |
6754 | @kindex init-if-undefined | |
6755 | @cindex convenience variables, initializing | |
6756 | @item init-if-undefined $@var{variable} = @var{expression} | |
6757 | Set a convenience variable if it has not already been set. This is useful | |
6758 | for user-defined commands that keep some state. It is similar, in concept, | |
6759 | to using local static variables with initializers in C (except that | |
6760 | convenience variables are global). It can also be used to allow users to | |
6761 | override default values used in a command script. | |
6762 | ||
6763 | If the variable is already defined then the expression is not evaluated so | |
6764 | any side-effects do not occur. | |
c906108c SS |
6765 | @end table |
6766 | ||
6767 | One of the ways to use a convenience variable is as a counter to be | |
6768 | incremented or a pointer to be advanced. For example, to print | |
6769 | a field from successive elements of an array of structures: | |
6770 | ||
474c8240 | 6771 | @smallexample |
c906108c SS |
6772 | set $i = 0 |
6773 | print bar[$i++]->contents | |
474c8240 | 6774 | @end smallexample |
c906108c | 6775 | |
d4f3574e SS |
6776 | @noindent |
6777 | Repeat that command by typing @key{RET}. | |
c906108c SS |
6778 | |
6779 | Some convenience variables are created automatically by @value{GDBN} and given | |
6780 | values likely to be useful. | |
6781 | ||
6782 | @table @code | |
41afff9a | 6783 | @vindex $_@r{, convenience variable} |
c906108c SS |
6784 | @item $_ |
6785 | The variable @code{$_} is automatically set by the @code{x} command to | |
79a6e687 | 6786 | the last address examined (@pxref{Memory, ,Examining Memory}). Other |
c906108c SS |
6787 | commands which provide a default address for @code{x} to examine also |
6788 | set @code{$_} to that address; these commands include @code{info line} | |
6789 | and @code{info breakpoint}. The type of @code{$_} is @code{void *} | |
6790 | except when set by the @code{x} command, in which case it is a pointer | |
6791 | to the type of @code{$__}. | |
6792 | ||
41afff9a | 6793 | @vindex $__@r{, convenience variable} |
c906108c SS |
6794 | @item $__ |
6795 | The variable @code{$__} is automatically set by the @code{x} command | |
6796 | to the value found in the last address examined. Its type is chosen | |
6797 | to match the format in which the data was printed. | |
6798 | ||
6799 | @item $_exitcode | |
41afff9a | 6800 | @vindex $_exitcode@r{, convenience variable} |
c906108c SS |
6801 | The variable @code{$_exitcode} is automatically set to the exit code when |
6802 | the program being debugged terminates. | |
6803 | @end table | |
6804 | ||
53a5351d JM |
6805 | On HP-UX systems, if you refer to a function or variable name that |
6806 | begins with a dollar sign, @value{GDBN} searches for a user or system | |
6807 | name first, before it searches for a convenience variable. | |
c906108c | 6808 | |
6d2ebf8b | 6809 | @node Registers |
c906108c SS |
6810 | @section Registers |
6811 | ||
6812 | @cindex registers | |
6813 | You can refer to machine register contents, in expressions, as variables | |
6814 | with names starting with @samp{$}. The names of registers are different | |
6815 | for each machine; use @code{info registers} to see the names used on | |
6816 | your machine. | |
6817 | ||
6818 | @table @code | |
6819 | @kindex info registers | |
6820 | @item info registers | |
6821 | Print the names and values of all registers except floating-point | |
c85508ee | 6822 | and vector registers (in the selected stack frame). |
c906108c SS |
6823 | |
6824 | @kindex info all-registers | |
6825 | @cindex floating point registers | |
6826 | @item info all-registers | |
6827 | Print the names and values of all registers, including floating-point | |
c85508ee | 6828 | and vector registers (in the selected stack frame). |
c906108c SS |
6829 | |
6830 | @item info registers @var{regname} @dots{} | |
6831 | Print the @dfn{relativized} value of each specified register @var{regname}. | |
5d161b24 DB |
6832 | As discussed in detail below, register values are normally relative to |
6833 | the selected stack frame. @var{regname} may be any register name valid on | |
c906108c SS |
6834 | the machine you are using, with or without the initial @samp{$}. |
6835 | @end table | |
6836 | ||
e09f16f9 EZ |
6837 | @cindex stack pointer register |
6838 | @cindex program counter register | |
6839 | @cindex process status register | |
6840 | @cindex frame pointer register | |
6841 | @cindex standard registers | |
c906108c SS |
6842 | @value{GDBN} has four ``standard'' register names that are available (in |
6843 | expressions) on most machines---whenever they do not conflict with an | |
6844 | architecture's canonical mnemonics for registers. The register names | |
6845 | @code{$pc} and @code{$sp} are used for the program counter register and | |
6846 | the stack pointer. @code{$fp} is used for a register that contains a | |
6847 | pointer to the current stack frame, and @code{$ps} is used for a | |
6848 | register that contains the processor status. For example, | |
6849 | you could print the program counter in hex with | |
6850 | ||
474c8240 | 6851 | @smallexample |
c906108c | 6852 | p/x $pc |
474c8240 | 6853 | @end smallexample |
c906108c SS |
6854 | |
6855 | @noindent | |
6856 | or print the instruction to be executed next with | |
6857 | ||
474c8240 | 6858 | @smallexample |
c906108c | 6859 | x/i $pc |
474c8240 | 6860 | @end smallexample |
c906108c SS |
6861 | |
6862 | @noindent | |
6863 | or add four to the stack pointer@footnote{This is a way of removing | |
6864 | one word from the stack, on machines where stacks grow downward in | |
6865 | memory (most machines, nowadays). This assumes that the innermost | |
6866 | stack frame is selected; setting @code{$sp} is not allowed when other | |
6867 | stack frames are selected. To pop entire frames off the stack, | |
6868 | regardless of machine architecture, use @code{return}; | |
79a6e687 | 6869 | see @ref{Returning, ,Returning from a Function}.} with |
c906108c | 6870 | |
474c8240 | 6871 | @smallexample |
c906108c | 6872 | set $sp += 4 |
474c8240 | 6873 | @end smallexample |
c906108c SS |
6874 | |
6875 | Whenever possible, these four standard register names are available on | |
6876 | your machine even though the machine has different canonical mnemonics, | |
6877 | so long as there is no conflict. The @code{info registers} command | |
6878 | shows the canonical names. For example, on the SPARC, @code{info | |
6879 | registers} displays the processor status register as @code{$psr} but you | |
d4f3574e SS |
6880 | can also refer to it as @code{$ps}; and on x86-based machines @code{$ps} |
6881 | is an alias for the @sc{eflags} register. | |
c906108c SS |
6882 | |
6883 | @value{GDBN} always considers the contents of an ordinary register as an | |
6884 | integer when the register is examined in this way. Some machines have | |
6885 | special registers which can hold nothing but floating point; these | |
6886 | registers are considered to have floating point values. There is no way | |
6887 | to refer to the contents of an ordinary register as floating point value | |
6888 | (although you can @emph{print} it as a floating point value with | |
6889 | @samp{print/f $@var{regname}}). | |
6890 | ||
6891 | Some registers have distinct ``raw'' and ``virtual'' data formats. This | |
6892 | means that the data format in which the register contents are saved by | |
6893 | the operating system is not the same one that your program normally | |
6894 | sees. For example, the registers of the 68881 floating point | |
6895 | coprocessor are always saved in ``extended'' (raw) format, but all C | |
6896 | programs expect to work with ``double'' (virtual) format. In such | |
5d161b24 | 6897 | cases, @value{GDBN} normally works with the virtual format only (the format |
c906108c SS |
6898 | that makes sense for your program), but the @code{info registers} command |
6899 | prints the data in both formats. | |
6900 | ||
36b80e65 EZ |
6901 | @cindex SSE registers (x86) |
6902 | @cindex MMX registers (x86) | |
6903 | Some machines have special registers whose contents can be interpreted | |
6904 | in several different ways. For example, modern x86-based machines | |
6905 | have SSE and MMX registers that can hold several values packed | |
6906 | together in several different formats. @value{GDBN} refers to such | |
6907 | registers in @code{struct} notation: | |
6908 | ||
6909 | @smallexample | |
6910 | (@value{GDBP}) print $xmm1 | |
6911 | $1 = @{ | |
6912 | v4_float = @{0, 3.43859137e-038, 1.54142831e-044, 1.821688e-044@}, | |
6913 | v2_double = @{9.92129282474342e-303, 2.7585945287983262e-313@}, | |
6914 | v16_int8 = "\000\000\000\000\3706;\001\v\000\000\000\r\000\000", | |
6915 | v8_int16 = @{0, 0, 14072, 315, 11, 0, 13, 0@}, | |
6916 | v4_int32 = @{0, 20657912, 11, 13@}, | |
6917 | v2_int64 = @{88725056443645952, 55834574859@}, | |
6918 | uint128 = 0x0000000d0000000b013b36f800000000 | |
6919 | @} | |
6920 | @end smallexample | |
6921 | ||
6922 | @noindent | |
6923 | To set values of such registers, you need to tell @value{GDBN} which | |
6924 | view of the register you wish to change, as if you were assigning | |
6925 | value to a @code{struct} member: | |
6926 | ||
6927 | @smallexample | |
6928 | (@value{GDBP}) set $xmm1.uint128 = 0x000000000000000000000000FFFFFFFF | |
6929 | @end smallexample | |
6930 | ||
c906108c | 6931 | Normally, register values are relative to the selected stack frame |
79a6e687 | 6932 | (@pxref{Selection, ,Selecting a Frame}). This means that you get the |
c906108c SS |
6933 | value that the register would contain if all stack frames farther in |
6934 | were exited and their saved registers restored. In order to see the | |
6935 | true contents of hardware registers, you must select the innermost | |
6936 | frame (with @samp{frame 0}). | |
6937 | ||
6938 | However, @value{GDBN} must deduce where registers are saved, from the machine | |
6939 | code generated by your compiler. If some registers are not saved, or if | |
6940 | @value{GDBN} is unable to locate the saved registers, the selected stack | |
6941 | frame makes no difference. | |
6942 | ||
6d2ebf8b | 6943 | @node Floating Point Hardware |
79a6e687 | 6944 | @section Floating Point Hardware |
c906108c SS |
6945 | @cindex floating point |
6946 | ||
6947 | Depending on the configuration, @value{GDBN} may be able to give | |
6948 | you more information about the status of the floating point hardware. | |
6949 | ||
6950 | @table @code | |
6951 | @kindex info float | |
6952 | @item info float | |
6953 | Display hardware-dependent information about the floating | |
6954 | point unit. The exact contents and layout vary depending on the | |
6955 | floating point chip. Currently, @samp{info float} is supported on | |
6956 | the ARM and x86 machines. | |
6957 | @end table | |
c906108c | 6958 | |
e76f1f2e AC |
6959 | @node Vector Unit |
6960 | @section Vector Unit | |
6961 | @cindex vector unit | |
6962 | ||
6963 | Depending on the configuration, @value{GDBN} may be able to give you | |
6964 | more information about the status of the vector unit. | |
6965 | ||
6966 | @table @code | |
6967 | @kindex info vector | |
6968 | @item info vector | |
6969 | Display information about the vector unit. The exact contents and | |
6970 | layout vary depending on the hardware. | |
6971 | @end table | |
6972 | ||
721c2651 | 6973 | @node OS Information |
79a6e687 | 6974 | @section Operating System Auxiliary Information |
721c2651 EZ |
6975 | @cindex OS information |
6976 | ||
6977 | @value{GDBN} provides interfaces to useful OS facilities that can help | |
6978 | you debug your program. | |
6979 | ||
6980 | @cindex @code{ptrace} system call | |
6981 | @cindex @code{struct user} contents | |
6982 | When @value{GDBN} runs on a @dfn{Posix system} (such as GNU or Unix | |
6983 | machines), it interfaces with the inferior via the @code{ptrace} | |
6984 | system call. The operating system creates a special sata structure, | |
6985 | called @code{struct user}, for this interface. You can use the | |
6986 | command @code{info udot} to display the contents of this data | |
6987 | structure. | |
6988 | ||
6989 | @table @code | |
6990 | @item info udot | |
6991 | @kindex info udot | |
6992 | Display the contents of the @code{struct user} maintained by the OS | |
6993 | kernel for the program being debugged. @value{GDBN} displays the | |
6994 | contents of @code{struct user} as a list of hex numbers, similar to | |
6995 | the @code{examine} command. | |
6996 | @end table | |
6997 | ||
b383017d RM |
6998 | @cindex auxiliary vector |
6999 | @cindex vector, auxiliary | |
b383017d RM |
7000 | Some operating systems supply an @dfn{auxiliary vector} to programs at |
7001 | startup. This is akin to the arguments and environment that you | |
7002 | specify for a program, but contains a system-dependent variety of | |
7003 | binary values that tell system libraries important details about the | |
7004 | hardware, operating system, and process. Each value's purpose is | |
7005 | identified by an integer tag; the meanings are well-known but system-specific. | |
7006 | Depending on the configuration and operating system facilities, | |
9c16f35a EZ |
7007 | @value{GDBN} may be able to show you this information. For remote |
7008 | targets, this functionality may further depend on the remote stub's | |
427c3a89 DJ |
7009 | support of the @samp{qXfer:auxv:read} packet, see |
7010 | @ref{qXfer auxiliary vector read}. | |
b383017d RM |
7011 | |
7012 | @table @code | |
7013 | @kindex info auxv | |
7014 | @item info auxv | |
7015 | Display the auxiliary vector of the inferior, which can be either a | |
e4937fc1 | 7016 | live process or a core dump file. @value{GDBN} prints each tag value |
b383017d RM |
7017 | numerically, and also shows names and text descriptions for recognized |
7018 | tags. Some values in the vector are numbers, some bit masks, and some | |
e4937fc1 | 7019 | pointers to strings or other data. @value{GDBN} displays each value in the |
b383017d RM |
7020 | most appropriate form for a recognized tag, and in hexadecimal for |
7021 | an unrecognized tag. | |
7022 | @end table | |
7023 | ||
721c2651 | 7024 | |
29e57380 | 7025 | @node Memory Region Attributes |
79a6e687 | 7026 | @section Memory Region Attributes |
29e57380 C |
7027 | @cindex memory region attributes |
7028 | ||
b383017d | 7029 | @dfn{Memory region attributes} allow you to describe special handling |
fd79ecee DJ |
7030 | required by regions of your target's memory. @value{GDBN} uses |
7031 | attributes to determine whether to allow certain types of memory | |
7032 | accesses; whether to use specific width accesses; and whether to cache | |
7033 | target memory. By default the description of memory regions is | |
7034 | fetched from the target (if the current target supports this), but the | |
7035 | user can override the fetched regions. | |
29e57380 C |
7036 | |
7037 | Defined memory regions can be individually enabled and disabled. When a | |
7038 | memory region is disabled, @value{GDBN} uses the default attributes when | |
7039 | accessing memory in that region. Similarly, if no memory regions have | |
7040 | been defined, @value{GDBN} uses the default attributes when accessing | |
7041 | all memory. | |
7042 | ||
b383017d | 7043 | When a memory region is defined, it is given a number to identify it; |
29e57380 C |
7044 | to enable, disable, or remove a memory region, you specify that number. |
7045 | ||
7046 | @table @code | |
7047 | @kindex mem | |
bfac230e | 7048 | @item mem @var{lower} @var{upper} @var{attributes}@dots{} |
09d4efe1 EZ |
7049 | Define a memory region bounded by @var{lower} and @var{upper} with |
7050 | attributes @var{attributes}@dots{}, and add it to the list of regions | |
7051 | monitored by @value{GDBN}. Note that @var{upper} == 0 is a special | |
d3e8051b | 7052 | case: it is treated as the target's maximum memory address. |
bfac230e | 7053 | (0xffff on 16 bit targets, 0xffffffff on 32 bit targets, etc.) |
29e57380 | 7054 | |
fd79ecee DJ |
7055 | @item mem auto |
7056 | Discard any user changes to the memory regions and use target-supplied | |
7057 | regions, if available, or no regions if the target does not support. | |
7058 | ||
29e57380 C |
7059 | @kindex delete mem |
7060 | @item delete mem @var{nums}@dots{} | |
09d4efe1 EZ |
7061 | Remove memory regions @var{nums}@dots{} from the list of regions |
7062 | monitored by @value{GDBN}. | |
29e57380 C |
7063 | |
7064 | @kindex disable mem | |
7065 | @item disable mem @var{nums}@dots{} | |
09d4efe1 | 7066 | Disable monitoring of memory regions @var{nums}@dots{}. |
b383017d | 7067 | A disabled memory region is not forgotten. |
29e57380 C |
7068 | It may be enabled again later. |
7069 | ||
7070 | @kindex enable mem | |
7071 | @item enable mem @var{nums}@dots{} | |
09d4efe1 | 7072 | Enable monitoring of memory regions @var{nums}@dots{}. |
29e57380 C |
7073 | |
7074 | @kindex info mem | |
7075 | @item info mem | |
7076 | Print a table of all defined memory regions, with the following columns | |
09d4efe1 | 7077 | for each region: |
29e57380 C |
7078 | |
7079 | @table @emph | |
7080 | @item Memory Region Number | |
7081 | @item Enabled or Disabled. | |
b383017d | 7082 | Enabled memory regions are marked with @samp{y}. |
29e57380 C |
7083 | Disabled memory regions are marked with @samp{n}. |
7084 | ||
7085 | @item Lo Address | |
7086 | The address defining the inclusive lower bound of the memory region. | |
7087 | ||
7088 | @item Hi Address | |
7089 | The address defining the exclusive upper bound of the memory region. | |
7090 | ||
7091 | @item Attributes | |
7092 | The list of attributes set for this memory region. | |
7093 | @end table | |
7094 | @end table | |
7095 | ||
7096 | ||
7097 | @subsection Attributes | |
7098 | ||
b383017d | 7099 | @subsubsection Memory Access Mode |
29e57380 C |
7100 | The access mode attributes set whether @value{GDBN} may make read or |
7101 | write accesses to a memory region. | |
7102 | ||
7103 | While these attributes prevent @value{GDBN} from performing invalid | |
7104 | memory accesses, they do nothing to prevent the target system, I/O DMA, | |
359df76b | 7105 | etc.@: from accessing memory. |
29e57380 C |
7106 | |
7107 | @table @code | |
7108 | @item ro | |
7109 | Memory is read only. | |
7110 | @item wo | |
7111 | Memory is write only. | |
7112 | @item rw | |
6ca652b0 | 7113 | Memory is read/write. This is the default. |
29e57380 C |
7114 | @end table |
7115 | ||
7116 | @subsubsection Memory Access Size | |
d3e8051b | 7117 | The access size attribute tells @value{GDBN} to use specific sized |
29e57380 C |
7118 | accesses in the memory region. Often memory mapped device registers |
7119 | require specific sized accesses. If no access size attribute is | |
7120 | specified, @value{GDBN} may use accesses of any size. | |
7121 | ||
7122 | @table @code | |
7123 | @item 8 | |
7124 | Use 8 bit memory accesses. | |
7125 | @item 16 | |
7126 | Use 16 bit memory accesses. | |
7127 | @item 32 | |
7128 | Use 32 bit memory accesses. | |
7129 | @item 64 | |
7130 | Use 64 bit memory accesses. | |
7131 | @end table | |
7132 | ||
7133 | @c @subsubsection Hardware/Software Breakpoints | |
7134 | @c The hardware/software breakpoint attributes set whether @value{GDBN} | |
7135 | @c will use hardware or software breakpoints for the internal breakpoints | |
7136 | @c used by the step, next, finish, until, etc. commands. | |
7137 | @c | |
7138 | @c @table @code | |
7139 | @c @item hwbreak | |
b383017d | 7140 | @c Always use hardware breakpoints |
29e57380 C |
7141 | @c @item swbreak (default) |
7142 | @c @end table | |
7143 | ||
7144 | @subsubsection Data Cache | |
7145 | The data cache attributes set whether @value{GDBN} will cache target | |
7146 | memory. While this generally improves performance by reducing debug | |
7147 | protocol overhead, it can lead to incorrect results because @value{GDBN} | |
7148 | does not know about volatile variables or memory mapped device | |
7149 | registers. | |
7150 | ||
7151 | @table @code | |
7152 | @item cache | |
b383017d | 7153 | Enable @value{GDBN} to cache target memory. |
6ca652b0 EZ |
7154 | @item nocache |
7155 | Disable @value{GDBN} from caching target memory. This is the default. | |
29e57380 C |
7156 | @end table |
7157 | ||
4b5752d0 VP |
7158 | @subsection Memory Access Checking |
7159 | @value{GDBN} can be instructed to refuse accesses to memory that is | |
7160 | not explicitly described. This can be useful if accessing such | |
7161 | regions has undesired effects for a specific target, or to provide | |
7162 | better error checking. The following commands control this behaviour. | |
7163 | ||
7164 | @table @code | |
7165 | @kindex set mem inaccessible-by-default | |
7166 | @item set mem inaccessible-by-default [on|off] | |
7167 | If @code{on} is specified, make @value{GDBN} treat memory not | |
7168 | explicitly described by the memory ranges as non-existent and refuse accesses | |
7169 | to such memory. The checks are only performed if there's at least one | |
7170 | memory range defined. If @code{off} is specified, make @value{GDBN} | |
7171 | treat the memory not explicitly described by the memory ranges as RAM. | |
56cf5405 | 7172 | The default value is @code{on}. |
4b5752d0 VP |
7173 | @kindex show mem inaccessible-by-default |
7174 | @item show mem inaccessible-by-default | |
7175 | Show the current handling of accesses to unknown memory. | |
7176 | @end table | |
7177 | ||
7178 | ||
29e57380 | 7179 | @c @subsubsection Memory Write Verification |
b383017d | 7180 | @c The memory write verification attributes set whether @value{GDBN} |
29e57380 C |
7181 | @c will re-reads data after each write to verify the write was successful. |
7182 | @c | |
7183 | @c @table @code | |
7184 | @c @item verify | |
7185 | @c @item noverify (default) | |
7186 | @c @end table | |
7187 | ||
16d9dec6 | 7188 | @node Dump/Restore Files |
79a6e687 | 7189 | @section Copy Between Memory and a File |
16d9dec6 MS |
7190 | @cindex dump/restore files |
7191 | @cindex append data to a file | |
7192 | @cindex dump data to a file | |
7193 | @cindex restore data from a file | |
16d9dec6 | 7194 | |
df5215a6 JB |
7195 | You can use the commands @code{dump}, @code{append}, and |
7196 | @code{restore} to copy data between target memory and a file. The | |
7197 | @code{dump} and @code{append} commands write data to a file, and the | |
7198 | @code{restore} command reads data from a file back into the inferior's | |
7199 | memory. Files may be in binary, Motorola S-record, Intel hex, or | |
7200 | Tektronix Hex format; however, @value{GDBN} can only append to binary | |
7201 | files. | |
7202 | ||
7203 | @table @code | |
7204 | ||
7205 | @kindex dump | |
7206 | @item dump @r{[}@var{format}@r{]} memory @var{filename} @var{start_addr} @var{end_addr} | |
7207 | @itemx dump @r{[}@var{format}@r{]} value @var{filename} @var{expr} | |
7208 | Dump the contents of memory from @var{start_addr} to @var{end_addr}, | |
7209 | or the value of @var{expr}, to @var{filename} in the given format. | |
16d9dec6 | 7210 | |
df5215a6 | 7211 | The @var{format} parameter may be any one of: |
16d9dec6 | 7212 | @table @code |
df5215a6 JB |
7213 | @item binary |
7214 | Raw binary form. | |
7215 | @item ihex | |
7216 | Intel hex format. | |
7217 | @item srec | |
7218 | Motorola S-record format. | |
7219 | @item tekhex | |
7220 | Tektronix Hex format. | |
7221 | @end table | |
7222 | ||
7223 | @value{GDBN} uses the same definitions of these formats as the | |
7224 | @sc{gnu} binary utilities, like @samp{objdump} and @samp{objcopy}. If | |
7225 | @var{format} is omitted, @value{GDBN} dumps the data in raw binary | |
7226 | form. | |
7227 | ||
7228 | @kindex append | |
7229 | @item append @r{[}binary@r{]} memory @var{filename} @var{start_addr} @var{end_addr} | |
7230 | @itemx append @r{[}binary@r{]} value @var{filename} @var{expr} | |
7231 | Append the contents of memory from @var{start_addr} to @var{end_addr}, | |
09d4efe1 | 7232 | or the value of @var{expr}, to the file @var{filename}, in raw binary form. |
df5215a6 JB |
7233 | (@value{GDBN} can only append data to files in raw binary form.) |
7234 | ||
7235 | @kindex restore | |
7236 | @item restore @var{filename} @r{[}binary@r{]} @var{bias} @var{start} @var{end} | |
7237 | Restore the contents of file @var{filename} into memory. The | |
7238 | @code{restore} command can automatically recognize any known @sc{bfd} | |
7239 | file format, except for raw binary. To restore a raw binary file you | |
7240 | must specify the optional keyword @code{binary} after the filename. | |
16d9dec6 | 7241 | |
b383017d | 7242 | If @var{bias} is non-zero, its value will be added to the addresses |
16d9dec6 MS |
7243 | contained in the file. Binary files always start at address zero, so |
7244 | they will be restored at address @var{bias}. Other bfd files have | |
7245 | a built-in location; they will be restored at offset @var{bias} | |
7246 | from that location. | |
7247 | ||
7248 | If @var{start} and/or @var{end} are non-zero, then only data between | |
7249 | file offset @var{start} and file offset @var{end} will be restored. | |
b383017d | 7250 | These offsets are relative to the addresses in the file, before |
16d9dec6 MS |
7251 | the @var{bias} argument is applied. |
7252 | ||
7253 | @end table | |
7254 | ||
384ee23f EZ |
7255 | @node Core File Generation |
7256 | @section How to Produce a Core File from Your Program | |
7257 | @cindex dump core from inferior | |
7258 | ||
7259 | A @dfn{core file} or @dfn{core dump} is a file that records the memory | |
7260 | image of a running process and its process status (register values | |
7261 | etc.). Its primary use is post-mortem debugging of a program that | |
7262 | crashed while it ran outside a debugger. A program that crashes | |
7263 | automatically produces a core file, unless this feature is disabled by | |
7264 | the user. @xref{Files}, for information on invoking @value{GDBN} in | |
7265 | the post-mortem debugging mode. | |
7266 | ||
7267 | Occasionally, you may wish to produce a core file of the program you | |
7268 | are debugging in order to preserve a snapshot of its state. | |
7269 | @value{GDBN} has a special command for that. | |
7270 | ||
7271 | @table @code | |
7272 | @kindex gcore | |
7273 | @kindex generate-core-file | |
7274 | @item generate-core-file [@var{file}] | |
7275 | @itemx gcore [@var{file}] | |
7276 | Produce a core dump of the inferior process. The optional argument | |
7277 | @var{file} specifies the file name where to put the core dump. If not | |
7278 | specified, the file name defaults to @file{core.@var{pid}}, where | |
7279 | @var{pid} is the inferior process ID. | |
7280 | ||
7281 | Note that this command is implemented only for some systems (as of | |
7282 | this writing, @sc{gnu}/Linux, FreeBSD, Solaris, Unixware, and S390). | |
7283 | @end table | |
7284 | ||
a0eb71c5 KB |
7285 | @node Character Sets |
7286 | @section Character Sets | |
7287 | @cindex character sets | |
7288 | @cindex charset | |
7289 | @cindex translating between character sets | |
7290 | @cindex host character set | |
7291 | @cindex target character set | |
7292 | ||
7293 | If the program you are debugging uses a different character set to | |
7294 | represent characters and strings than the one @value{GDBN} uses itself, | |
7295 | @value{GDBN} can automatically translate between the character sets for | |
7296 | you. The character set @value{GDBN} uses we call the @dfn{host | |
7297 | character set}; the one the inferior program uses we call the | |
7298 | @dfn{target character set}. | |
7299 | ||
7300 | For example, if you are running @value{GDBN} on a @sc{gnu}/Linux system, which | |
7301 | uses the ISO Latin 1 character set, but you are using @value{GDBN}'s | |
ea35711c | 7302 | remote protocol (@pxref{Remote Debugging}) to debug a program |
a0eb71c5 KB |
7303 | running on an IBM mainframe, which uses the @sc{ebcdic} character set, |
7304 | then the host character set is Latin-1, and the target character set is | |
7305 | @sc{ebcdic}. If you give @value{GDBN} the command @code{set | |
e33d66ec | 7306 | target-charset EBCDIC-US}, then @value{GDBN} translates between |
a0eb71c5 KB |
7307 | @sc{ebcdic} and Latin 1 as you print character or string values, or use |
7308 | character and string literals in expressions. | |
7309 | ||
7310 | @value{GDBN} has no way to automatically recognize which character set | |
7311 | the inferior program uses; you must tell it, using the @code{set | |
7312 | target-charset} command, described below. | |
7313 | ||
7314 | Here are the commands for controlling @value{GDBN}'s character set | |
7315 | support: | |
7316 | ||
7317 | @table @code | |
7318 | @item set target-charset @var{charset} | |
7319 | @kindex set target-charset | |
7320 | Set the current target character set to @var{charset}. We list the | |
e33d66ec EZ |
7321 | character set names @value{GDBN} recognizes below, but if you type |
7322 | @code{set target-charset} followed by @key{TAB}@key{TAB}, @value{GDBN} will | |
7323 | list the target character sets it supports. | |
a0eb71c5 KB |
7324 | @end table |
7325 | ||
7326 | @table @code | |
7327 | @item set host-charset @var{charset} | |
7328 | @kindex set host-charset | |
7329 | Set the current host character set to @var{charset}. | |
7330 | ||
7331 | By default, @value{GDBN} uses a host character set appropriate to the | |
7332 | system it is running on; you can override that default using the | |
7333 | @code{set host-charset} command. | |
7334 | ||
7335 | @value{GDBN} can only use certain character sets as its host character | |
7336 | set. We list the character set names @value{GDBN} recognizes below, and | |
e33d66ec EZ |
7337 | indicate which can be host character sets, but if you type |
7338 | @code{set target-charset} followed by @key{TAB}@key{TAB}, @value{GDBN} will | |
7339 | list the host character sets it supports. | |
a0eb71c5 KB |
7340 | |
7341 | @item set charset @var{charset} | |
7342 | @kindex set charset | |
e33d66ec EZ |
7343 | Set the current host and target character sets to @var{charset}. As |
7344 | above, if you type @code{set charset} followed by @key{TAB}@key{TAB}, | |
7345 | @value{GDBN} will list the name of the character sets that can be used | |
7346 | for both host and target. | |
7347 | ||
a0eb71c5 KB |
7348 | |
7349 | @item show charset | |
a0eb71c5 | 7350 | @kindex show charset |
b383017d | 7351 | Show the names of the current host and target charsets. |
e33d66ec EZ |
7352 | |
7353 | @itemx show host-charset | |
a0eb71c5 | 7354 | @kindex show host-charset |
b383017d | 7355 | Show the name of the current host charset. |
e33d66ec EZ |
7356 | |
7357 | @itemx show target-charset | |
a0eb71c5 | 7358 | @kindex show target-charset |
b383017d | 7359 | Show the name of the current target charset. |
a0eb71c5 KB |
7360 | |
7361 | @end table | |
7362 | ||
7363 | @value{GDBN} currently includes support for the following character | |
7364 | sets: | |
7365 | ||
7366 | @table @code | |
7367 | ||
7368 | @item ASCII | |
7369 | @cindex ASCII character set | |
7370 | Seven-bit U.S. @sc{ascii}. @value{GDBN} can use this as its host | |
7371 | character set. | |
7372 | ||
7373 | @item ISO-8859-1 | |
7374 | @cindex ISO 8859-1 character set | |
7375 | @cindex ISO Latin 1 character set | |
e33d66ec | 7376 | The ISO Latin 1 character set. This extends @sc{ascii} with accented |
a0eb71c5 KB |
7377 | characters needed for French, German, and Spanish. @value{GDBN} can use |
7378 | this as its host character set. | |
7379 | ||
7380 | @item EBCDIC-US | |
7381 | @itemx IBM1047 | |
7382 | @cindex EBCDIC character set | |
7383 | @cindex IBM1047 character set | |
7384 | Variants of the @sc{ebcdic} character set, used on some of IBM's | |
7385 | mainframe operating systems. (@sc{gnu}/Linux on the S/390 uses U.S. @sc{ascii}.) | |
7386 | @value{GDBN} cannot use these as its host character set. | |
7387 | ||
7388 | @end table | |
7389 | ||
7390 | Note that these are all single-byte character sets. More work inside | |
3f94c067 | 7391 | @value{GDBN} is needed to support multi-byte or variable-width character |
a0eb71c5 KB |
7392 | encodings, like the UTF-8 and UCS-2 encodings of Unicode. |
7393 | ||
7394 | Here is an example of @value{GDBN}'s character set support in action. | |
7395 | Assume that the following source code has been placed in the file | |
7396 | @file{charset-test.c}: | |
7397 | ||
7398 | @smallexample | |
7399 | #include <stdio.h> | |
7400 | ||
7401 | char ascii_hello[] | |
7402 | = @{72, 101, 108, 108, 111, 44, 32, 119, | |
7403 | 111, 114, 108, 100, 33, 10, 0@}; | |
7404 | char ibm1047_hello[] | |
7405 | = @{200, 133, 147, 147, 150, 107, 64, 166, | |
7406 | 150, 153, 147, 132, 90, 37, 0@}; | |
7407 | ||
7408 | main () | |
7409 | @{ | |
7410 | printf ("Hello, world!\n"); | |
7411 | @} | |
10998722 | 7412 | @end smallexample |
a0eb71c5 KB |
7413 | |
7414 | In this program, @code{ascii_hello} and @code{ibm1047_hello} are arrays | |
7415 | containing the string @samp{Hello, world!} followed by a newline, | |
7416 | encoded in the @sc{ascii} and @sc{ibm1047} character sets. | |
7417 | ||
7418 | We compile the program, and invoke the debugger on it: | |
7419 | ||
7420 | @smallexample | |
7421 | $ gcc -g charset-test.c -o charset-test | |
7422 | $ gdb -nw charset-test | |
7423 | GNU gdb 2001-12-19-cvs | |
7424 | Copyright 2001 Free Software Foundation, Inc. | |
7425 | @dots{} | |
f7dc1244 | 7426 | (@value{GDBP}) |
10998722 | 7427 | @end smallexample |
a0eb71c5 KB |
7428 | |
7429 | We can use the @code{show charset} command to see what character sets | |
7430 | @value{GDBN} is currently using to interpret and display characters and | |
7431 | strings: | |
7432 | ||
7433 | @smallexample | |
f7dc1244 | 7434 | (@value{GDBP}) show charset |
e33d66ec | 7435 | The current host and target character set is `ISO-8859-1'. |
f7dc1244 | 7436 | (@value{GDBP}) |
10998722 | 7437 | @end smallexample |
a0eb71c5 KB |
7438 | |
7439 | For the sake of printing this manual, let's use @sc{ascii} as our | |
7440 | initial character set: | |
7441 | @smallexample | |
f7dc1244 EZ |
7442 | (@value{GDBP}) set charset ASCII |
7443 | (@value{GDBP}) show charset | |
e33d66ec | 7444 | The current host and target character set is `ASCII'. |
f7dc1244 | 7445 | (@value{GDBP}) |
10998722 | 7446 | @end smallexample |
a0eb71c5 KB |
7447 | |
7448 | Let's assume that @sc{ascii} is indeed the correct character set for our | |
7449 | host system --- in other words, let's assume that if @value{GDBN} prints | |
7450 | characters using the @sc{ascii} character set, our terminal will display | |
7451 | them properly. Since our current target character set is also | |
7452 | @sc{ascii}, the contents of @code{ascii_hello} print legibly: | |
7453 | ||
7454 | @smallexample | |
f7dc1244 | 7455 | (@value{GDBP}) print ascii_hello |
a0eb71c5 | 7456 | $1 = 0x401698 "Hello, world!\n" |
f7dc1244 | 7457 | (@value{GDBP}) print ascii_hello[0] |
a0eb71c5 | 7458 | $2 = 72 'H' |
f7dc1244 | 7459 | (@value{GDBP}) |
10998722 | 7460 | @end smallexample |
a0eb71c5 KB |
7461 | |
7462 | @value{GDBN} uses the target character set for character and string | |
7463 | literals you use in expressions: | |
7464 | ||
7465 | @smallexample | |
f7dc1244 | 7466 | (@value{GDBP}) print '+' |
a0eb71c5 | 7467 | $3 = 43 '+' |
f7dc1244 | 7468 | (@value{GDBP}) |
10998722 | 7469 | @end smallexample |
a0eb71c5 KB |
7470 | |
7471 | The @sc{ascii} character set uses the number 43 to encode the @samp{+} | |
7472 | character. | |
7473 | ||
7474 | @value{GDBN} relies on the user to tell it which character set the | |
7475 | target program uses. If we print @code{ibm1047_hello} while our target | |
7476 | character set is still @sc{ascii}, we get jibberish: | |
7477 | ||
7478 | @smallexample | |
f7dc1244 | 7479 | (@value{GDBP}) print ibm1047_hello |
a0eb71c5 | 7480 | $4 = 0x4016a8 "\310\205\223\223\226k@@\246\226\231\223\204Z%" |
f7dc1244 | 7481 | (@value{GDBP}) print ibm1047_hello[0] |
a0eb71c5 | 7482 | $5 = 200 '\310' |
f7dc1244 | 7483 | (@value{GDBP}) |
10998722 | 7484 | @end smallexample |
a0eb71c5 | 7485 | |
e33d66ec | 7486 | If we invoke the @code{set target-charset} followed by @key{TAB}@key{TAB}, |
a0eb71c5 KB |
7487 | @value{GDBN} tells us the character sets it supports: |
7488 | ||
7489 | @smallexample | |
f7dc1244 | 7490 | (@value{GDBP}) set target-charset |
b383017d | 7491 | ASCII EBCDIC-US IBM1047 ISO-8859-1 |
f7dc1244 | 7492 | (@value{GDBP}) set target-charset |
10998722 | 7493 | @end smallexample |
a0eb71c5 KB |
7494 | |
7495 | We can select @sc{ibm1047} as our target character set, and examine the | |
7496 | program's strings again. Now the @sc{ascii} string is wrong, but | |
7497 | @value{GDBN} translates the contents of @code{ibm1047_hello} from the | |
7498 | target character set, @sc{ibm1047}, to the host character set, | |
7499 | @sc{ascii}, and they display correctly: | |
7500 | ||
7501 | @smallexample | |
f7dc1244 EZ |
7502 | (@value{GDBP}) set target-charset IBM1047 |
7503 | (@value{GDBP}) show charset | |
e33d66ec EZ |
7504 | The current host character set is `ASCII'. |
7505 | The current target character set is `IBM1047'. | |
f7dc1244 | 7506 | (@value{GDBP}) print ascii_hello |
a0eb71c5 | 7507 | $6 = 0x401698 "\110\145%%?\054\040\167?\162%\144\041\012" |
f7dc1244 | 7508 | (@value{GDBP}) print ascii_hello[0] |
a0eb71c5 | 7509 | $7 = 72 '\110' |
f7dc1244 | 7510 | (@value{GDBP}) print ibm1047_hello |
a0eb71c5 | 7511 | $8 = 0x4016a8 "Hello, world!\n" |
f7dc1244 | 7512 | (@value{GDBP}) print ibm1047_hello[0] |
a0eb71c5 | 7513 | $9 = 200 'H' |
f7dc1244 | 7514 | (@value{GDBP}) |
10998722 | 7515 | @end smallexample |
a0eb71c5 KB |
7516 | |
7517 | As above, @value{GDBN} uses the target character set for character and | |
7518 | string literals you use in expressions: | |
7519 | ||
7520 | @smallexample | |
f7dc1244 | 7521 | (@value{GDBP}) print '+' |
a0eb71c5 | 7522 | $10 = 78 '+' |
f7dc1244 | 7523 | (@value{GDBP}) |
10998722 | 7524 | @end smallexample |
a0eb71c5 | 7525 | |
e33d66ec | 7526 | The @sc{ibm1047} character set uses the number 78 to encode the @samp{+} |
a0eb71c5 KB |
7527 | character. |
7528 | ||
09d4efe1 EZ |
7529 | @node Caching Remote Data |
7530 | @section Caching Data of Remote Targets | |
7531 | @cindex caching data of remote targets | |
7532 | ||
7533 | @value{GDBN} can cache data exchanged between the debugger and a | |
ea35711c | 7534 | remote target (@pxref{Remote Debugging}). Such caching generally improves |
09d4efe1 EZ |
7535 | performance, because it reduces the overhead of the remote protocol by |
7536 | bundling memory reads and writes into large chunks. Unfortunately, | |
7537 | @value{GDBN} does not currently know anything about volatile | |
7538 | registers, and thus data caching will produce incorrect results when | |
7539 | volatile registers are in use. | |
7540 | ||
7541 | @table @code | |
7542 | @kindex set remotecache | |
7543 | @item set remotecache on | |
7544 | @itemx set remotecache off | |
7545 | Set caching state for remote targets. When @code{ON}, use data | |
7546 | caching. By default, this option is @code{OFF}. | |
7547 | ||
7548 | @kindex show remotecache | |
7549 | @item show remotecache | |
7550 | Show the current state of data caching for remote targets. | |
7551 | ||
7552 | @kindex info dcache | |
7553 | @item info dcache | |
7554 | Print the information about the data cache performance. The | |
7555 | information displayed includes: the dcache width and depth; and for | |
7556 | each cache line, how many times it was referenced, and its data and | |
7557 | state (dirty, bad, ok, etc.). This command is useful for debugging | |
7558 | the data cache operation. | |
7559 | @end table | |
7560 | ||
a0eb71c5 | 7561 | |
e2e0bcd1 JB |
7562 | @node Macros |
7563 | @chapter C Preprocessor Macros | |
7564 | ||
49efadf5 | 7565 | Some languages, such as C and C@t{++}, provide a way to define and invoke |
e2e0bcd1 JB |
7566 | ``preprocessor macros'' which expand into strings of tokens. |
7567 | @value{GDBN} can evaluate expressions containing macro invocations, show | |
7568 | the result of macro expansion, and show a macro's definition, including | |
7569 | where it was defined. | |
7570 | ||
7571 | You may need to compile your program specially to provide @value{GDBN} | |
7572 | with information about preprocessor macros. Most compilers do not | |
7573 | include macros in their debugging information, even when you compile | |
7574 | with the @option{-g} flag. @xref{Compilation}. | |
7575 | ||
7576 | A program may define a macro at one point, remove that definition later, | |
7577 | and then provide a different definition after that. Thus, at different | |
7578 | points in the program, a macro may have different definitions, or have | |
7579 | no definition at all. If there is a current stack frame, @value{GDBN} | |
7580 | uses the macros in scope at that frame's source code line. Otherwise, | |
7581 | @value{GDBN} uses the macros in scope at the current listing location; | |
7582 | see @ref{List}. | |
7583 | ||
7584 | At the moment, @value{GDBN} does not support the @code{##} | |
7585 | token-splicing operator, the @code{#} stringification operator, or | |
7586 | variable-arity macros. | |
7587 | ||
7588 | Whenever @value{GDBN} evaluates an expression, it always expands any | |
7589 | macro invocations present in the expression. @value{GDBN} also provides | |
7590 | the following commands for working with macros explicitly. | |
7591 | ||
7592 | @table @code | |
7593 | ||
7594 | @kindex macro expand | |
7595 | @cindex macro expansion, showing the results of preprocessor | |
7596 | @cindex preprocessor macro expansion, showing the results of | |
7597 | @cindex expanding preprocessor macros | |
7598 | @item macro expand @var{expression} | |
7599 | @itemx macro exp @var{expression} | |
7600 | Show the results of expanding all preprocessor macro invocations in | |
7601 | @var{expression}. Since @value{GDBN} simply expands macros, but does | |
7602 | not parse the result, @var{expression} need not be a valid expression; | |
7603 | it can be any string of tokens. | |
7604 | ||
09d4efe1 | 7605 | @kindex macro exp1 |
e2e0bcd1 JB |
7606 | @item macro expand-once @var{expression} |
7607 | @itemx macro exp1 @var{expression} | |
4644b6e3 | 7608 | @cindex expand macro once |
e2e0bcd1 JB |
7609 | @i{(This command is not yet implemented.)} Show the results of |
7610 | expanding those preprocessor macro invocations that appear explicitly in | |
7611 | @var{expression}. Macro invocations appearing in that expansion are | |
7612 | left unchanged. This command allows you to see the effect of a | |
7613 | particular macro more clearly, without being confused by further | |
7614 | expansions. Since @value{GDBN} simply expands macros, but does not | |
7615 | parse the result, @var{expression} need not be a valid expression; it | |
7616 | can be any string of tokens. | |
7617 | ||
475b0867 | 7618 | @kindex info macro |
e2e0bcd1 JB |
7619 | @cindex macro definition, showing |
7620 | @cindex definition, showing a macro's | |
475b0867 | 7621 | @item info macro @var{macro} |
e2e0bcd1 JB |
7622 | Show the definition of the macro named @var{macro}, and describe the |
7623 | source location where that definition was established. | |
7624 | ||
7625 | @kindex macro define | |
7626 | @cindex user-defined macros | |
7627 | @cindex defining macros interactively | |
7628 | @cindex macros, user-defined | |
7629 | @item macro define @var{macro} @var{replacement-list} | |
7630 | @itemx macro define @var{macro}(@var{arglist}) @var{replacement-list} | |
7631 | @i{(This command is not yet implemented.)} Introduce a definition for a | |
7632 | preprocessor macro named @var{macro}, invocations of which are replaced | |
7633 | by the tokens given in @var{replacement-list}. The first form of this | |
7634 | command defines an ``object-like'' macro, which takes no arguments; the | |
7635 | second form defines a ``function-like'' macro, which takes the arguments | |
7636 | given in @var{arglist}. | |
7637 | ||
7638 | A definition introduced by this command is in scope in every expression | |
7639 | evaluated in @value{GDBN}, until it is removed with the @command{macro | |
7640 | undef} command, described below. The definition overrides all | |
7641 | definitions for @var{macro} present in the program being debugged, as | |
7642 | well as any previous user-supplied definition. | |
7643 | ||
7644 | @kindex macro undef | |
7645 | @item macro undef @var{macro} | |
7646 | @i{(This command is not yet implemented.)} Remove any user-supplied | |
7647 | definition for the macro named @var{macro}. This command only affects | |
7648 | definitions provided with the @command{macro define} command, described | |
7649 | above; it cannot remove definitions present in the program being | |
7650 | debugged. | |
7651 | ||
09d4efe1 EZ |
7652 | @kindex macro list |
7653 | @item macro list | |
7654 | @i{(This command is not yet implemented.)} List all the macros | |
7655 | defined using the @code{macro define} command. | |
e2e0bcd1 JB |
7656 | @end table |
7657 | ||
7658 | @cindex macros, example of debugging with | |
7659 | Here is a transcript showing the above commands in action. First, we | |
7660 | show our source files: | |
7661 | ||
7662 | @smallexample | |
7663 | $ cat sample.c | |
7664 | #include <stdio.h> | |
7665 | #include "sample.h" | |
7666 | ||
7667 | #define M 42 | |
7668 | #define ADD(x) (M + x) | |
7669 | ||
7670 | main () | |
7671 | @{ | |
7672 | #define N 28 | |
7673 | printf ("Hello, world!\n"); | |
7674 | #undef N | |
7675 | printf ("We're so creative.\n"); | |
7676 | #define N 1729 | |
7677 | printf ("Goodbye, world!\n"); | |
7678 | @} | |
7679 | $ cat sample.h | |
7680 | #define Q < | |
7681 | $ | |
7682 | @end smallexample | |
7683 | ||
7684 | Now, we compile the program using the @sc{gnu} C compiler, @value{NGCC}. | |
7685 | We pass the @option{-gdwarf-2} and @option{-g3} flags to ensure the | |
7686 | compiler includes information about preprocessor macros in the debugging | |
7687 | information. | |
7688 | ||
7689 | @smallexample | |
7690 | $ gcc -gdwarf-2 -g3 sample.c -o sample | |
7691 | $ | |
7692 | @end smallexample | |
7693 | ||
7694 | Now, we start @value{GDBN} on our sample program: | |
7695 | ||
7696 | @smallexample | |
7697 | $ gdb -nw sample | |
7698 | GNU gdb 2002-05-06-cvs | |
7699 | Copyright 2002 Free Software Foundation, Inc. | |
7700 | GDB is free software, @dots{} | |
f7dc1244 | 7701 | (@value{GDBP}) |
e2e0bcd1 JB |
7702 | @end smallexample |
7703 | ||
7704 | We can expand macros and examine their definitions, even when the | |
7705 | program is not running. @value{GDBN} uses the current listing position | |
7706 | to decide which macro definitions are in scope: | |
7707 | ||
7708 | @smallexample | |
f7dc1244 | 7709 | (@value{GDBP}) list main |
e2e0bcd1 JB |
7710 | 3 |
7711 | 4 #define M 42 | |
7712 | 5 #define ADD(x) (M + x) | |
7713 | 6 | |
7714 | 7 main () | |
7715 | 8 @{ | |
7716 | 9 #define N 28 | |
7717 | 10 printf ("Hello, world!\n"); | |
7718 | 11 #undef N | |
7719 | 12 printf ("We're so creative.\n"); | |
f7dc1244 | 7720 | (@value{GDBP}) info macro ADD |
e2e0bcd1 JB |
7721 | Defined at /home/jimb/gdb/macros/play/sample.c:5 |
7722 | #define ADD(x) (M + x) | |
f7dc1244 | 7723 | (@value{GDBP}) info macro Q |
e2e0bcd1 JB |
7724 | Defined at /home/jimb/gdb/macros/play/sample.h:1 |
7725 | included at /home/jimb/gdb/macros/play/sample.c:2 | |
7726 | #define Q < | |
f7dc1244 | 7727 | (@value{GDBP}) macro expand ADD(1) |
e2e0bcd1 | 7728 | expands to: (42 + 1) |
f7dc1244 | 7729 | (@value{GDBP}) macro expand-once ADD(1) |
e2e0bcd1 | 7730 | expands to: once (M + 1) |
f7dc1244 | 7731 | (@value{GDBP}) |
e2e0bcd1 JB |
7732 | @end smallexample |
7733 | ||
7734 | In the example above, note that @command{macro expand-once} expands only | |
7735 | the macro invocation explicit in the original text --- the invocation of | |
7736 | @code{ADD} --- but does not expand the invocation of the macro @code{M}, | |
7737 | which was introduced by @code{ADD}. | |
7738 | ||
3f94c067 BW |
7739 | Once the program is running, @value{GDBN} uses the macro definitions in |
7740 | force at the source line of the current stack frame: | |
e2e0bcd1 JB |
7741 | |
7742 | @smallexample | |
f7dc1244 | 7743 | (@value{GDBP}) break main |
e2e0bcd1 | 7744 | Breakpoint 1 at 0x8048370: file sample.c, line 10. |
f7dc1244 | 7745 | (@value{GDBP}) run |
b383017d | 7746 | Starting program: /home/jimb/gdb/macros/play/sample |
e2e0bcd1 JB |
7747 | |
7748 | Breakpoint 1, main () at sample.c:10 | |
7749 | 10 printf ("Hello, world!\n"); | |
f7dc1244 | 7750 | (@value{GDBP}) |
e2e0bcd1 JB |
7751 | @end smallexample |
7752 | ||
7753 | At line 10, the definition of the macro @code{N} at line 9 is in force: | |
7754 | ||
7755 | @smallexample | |
f7dc1244 | 7756 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
7757 | Defined at /home/jimb/gdb/macros/play/sample.c:9 |
7758 | #define N 28 | |
f7dc1244 | 7759 | (@value{GDBP}) macro expand N Q M |
e2e0bcd1 | 7760 | expands to: 28 < 42 |
f7dc1244 | 7761 | (@value{GDBP}) print N Q M |
e2e0bcd1 | 7762 | $1 = 1 |
f7dc1244 | 7763 | (@value{GDBP}) |
e2e0bcd1 JB |
7764 | @end smallexample |
7765 | ||
7766 | As we step over directives that remove @code{N}'s definition, and then | |
7767 | give it a new definition, @value{GDBN} finds the definition (or lack | |
7768 | thereof) in force at each point: | |
7769 | ||
7770 | @smallexample | |
f7dc1244 | 7771 | (@value{GDBP}) next |
e2e0bcd1 JB |
7772 | Hello, world! |
7773 | 12 printf ("We're so creative.\n"); | |
f7dc1244 | 7774 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
7775 | The symbol `N' has no definition as a C/C++ preprocessor macro |
7776 | at /home/jimb/gdb/macros/play/sample.c:12 | |
f7dc1244 | 7777 | (@value{GDBP}) next |
e2e0bcd1 JB |
7778 | We're so creative. |
7779 | 14 printf ("Goodbye, world!\n"); | |
f7dc1244 | 7780 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
7781 | Defined at /home/jimb/gdb/macros/play/sample.c:13 |
7782 | #define N 1729 | |
f7dc1244 | 7783 | (@value{GDBP}) macro expand N Q M |
e2e0bcd1 | 7784 | expands to: 1729 < 42 |
f7dc1244 | 7785 | (@value{GDBP}) print N Q M |
e2e0bcd1 | 7786 | $2 = 0 |
f7dc1244 | 7787 | (@value{GDBP}) |
e2e0bcd1 JB |
7788 | @end smallexample |
7789 | ||
7790 | ||
b37052ae EZ |
7791 | @node Tracepoints |
7792 | @chapter Tracepoints | |
7793 | @c This chapter is based on the documentation written by Michael | |
7794 | @c Snyder, David Taylor, Jim Blandy, and Elena Zannoni. | |
7795 | ||
7796 | @cindex tracepoints | |
7797 | In some applications, it is not feasible for the debugger to interrupt | |
7798 | the program's execution long enough for the developer to learn | |
7799 | anything helpful about its behavior. If the program's correctness | |
7800 | depends on its real-time behavior, delays introduced by a debugger | |
7801 | might cause the program to change its behavior drastically, or perhaps | |
7802 | fail, even when the code itself is correct. It is useful to be able | |
7803 | to observe the program's behavior without interrupting it. | |
7804 | ||
7805 | Using @value{GDBN}'s @code{trace} and @code{collect} commands, you can | |
7806 | specify locations in the program, called @dfn{tracepoints}, and | |
7807 | arbitrary expressions to evaluate when those tracepoints are reached. | |
7808 | Later, using the @code{tfind} command, you can examine the values | |
7809 | those expressions had when the program hit the tracepoints. The | |
7810 | expressions may also denote objects in memory---structures or arrays, | |
7811 | for example---whose values @value{GDBN} should record; while visiting | |
7812 | a particular tracepoint, you may inspect those objects as if they were | |
7813 | in memory at that moment. However, because @value{GDBN} records these | |
7814 | values without interacting with you, it can do so quickly and | |
7815 | unobtrusively, hopefully not disturbing the program's behavior. | |
7816 | ||
7817 | The tracepoint facility is currently available only for remote | |
9d29849a JB |
7818 | targets. @xref{Targets}. In addition, your remote target must know |
7819 | how to collect trace data. This functionality is implemented in the | |
7820 | remote stub; however, none of the stubs distributed with @value{GDBN} | |
7821 | support tracepoints as of this writing. The format of the remote | |
7822 | packets used to implement tracepoints are described in @ref{Tracepoint | |
7823 | Packets}. | |
b37052ae EZ |
7824 | |
7825 | This chapter describes the tracepoint commands and features. | |
7826 | ||
7827 | @menu | |
b383017d RM |
7828 | * Set Tracepoints:: |
7829 | * Analyze Collected Data:: | |
7830 | * Tracepoint Variables:: | |
b37052ae EZ |
7831 | @end menu |
7832 | ||
7833 | @node Set Tracepoints | |
7834 | @section Commands to Set Tracepoints | |
7835 | ||
7836 | Before running such a @dfn{trace experiment}, an arbitrary number of | |
7837 | tracepoints can be set. Like a breakpoint (@pxref{Set Breaks}), a | |
7838 | tracepoint has a number assigned to it by @value{GDBN}. Like with | |
7839 | breakpoints, tracepoint numbers are successive integers starting from | |
7840 | one. Many of the commands associated with tracepoints take the | |
7841 | tracepoint number as their argument, to identify which tracepoint to | |
7842 | work on. | |
7843 | ||
7844 | For each tracepoint, you can specify, in advance, some arbitrary set | |
7845 | of data that you want the target to collect in the trace buffer when | |
7846 | it hits that tracepoint. The collected data can include registers, | |
7847 | local variables, or global data. Later, you can use @value{GDBN} | |
7848 | commands to examine the values these data had at the time the | |
7849 | tracepoint was hit. | |
7850 | ||
7851 | This section describes commands to set tracepoints and associated | |
7852 | conditions and actions. | |
7853 | ||
7854 | @menu | |
b383017d RM |
7855 | * Create and Delete Tracepoints:: |
7856 | * Enable and Disable Tracepoints:: | |
7857 | * Tracepoint Passcounts:: | |
7858 | * Tracepoint Actions:: | |
7859 | * Listing Tracepoints:: | |
79a6e687 | 7860 | * Starting and Stopping Trace Experiments:: |
b37052ae EZ |
7861 | @end menu |
7862 | ||
7863 | @node Create and Delete Tracepoints | |
7864 | @subsection Create and Delete Tracepoints | |
7865 | ||
7866 | @table @code | |
7867 | @cindex set tracepoint | |
7868 | @kindex trace | |
7869 | @item trace | |
7870 | The @code{trace} command is very similar to the @code{break} command. | |
7871 | Its argument can be a source line, a function name, or an address in | |
7872 | the target program. @xref{Set Breaks}. The @code{trace} command | |
7873 | defines a tracepoint, which is a point in the target program where the | |
7874 | debugger will briefly stop, collect some data, and then allow the | |
7875 | program to continue. Setting a tracepoint or changing its commands | |
7876 | doesn't take effect until the next @code{tstart} command; thus, you | |
7877 | cannot change the tracepoint attributes once a trace experiment is | |
7878 | running. | |
7879 | ||
7880 | Here are some examples of using the @code{trace} command: | |
7881 | ||
7882 | @smallexample | |
7883 | (@value{GDBP}) @b{trace foo.c:121} // a source file and line number | |
7884 | ||
7885 | (@value{GDBP}) @b{trace +2} // 2 lines forward | |
7886 | ||
7887 | (@value{GDBP}) @b{trace my_function} // first source line of function | |
7888 | ||
7889 | (@value{GDBP}) @b{trace *my_function} // EXACT start address of function | |
7890 | ||
7891 | (@value{GDBP}) @b{trace *0x2117c4} // an address | |
7892 | @end smallexample | |
7893 | ||
7894 | @noindent | |
7895 | You can abbreviate @code{trace} as @code{tr}. | |
7896 | ||
7897 | @vindex $tpnum | |
7898 | @cindex last tracepoint number | |
7899 | @cindex recent tracepoint number | |
7900 | @cindex tracepoint number | |
7901 | The convenience variable @code{$tpnum} records the tracepoint number | |
7902 | of the most recently set tracepoint. | |
7903 | ||
7904 | @kindex delete tracepoint | |
7905 | @cindex tracepoint deletion | |
7906 | @item delete tracepoint @r{[}@var{num}@r{]} | |
7907 | Permanently delete one or more tracepoints. With no argument, the | |
7908 | default is to delete all tracepoints. | |
7909 | ||
7910 | Examples: | |
7911 | ||
7912 | @smallexample | |
7913 | (@value{GDBP}) @b{delete trace 1 2 3} // remove three tracepoints | |
7914 | ||
7915 | (@value{GDBP}) @b{delete trace} // remove all tracepoints | |
7916 | @end smallexample | |
7917 | ||
7918 | @noindent | |
7919 | You can abbreviate this command as @code{del tr}. | |
7920 | @end table | |
7921 | ||
7922 | @node Enable and Disable Tracepoints | |
7923 | @subsection Enable and Disable Tracepoints | |
7924 | ||
7925 | @table @code | |
7926 | @kindex disable tracepoint | |
7927 | @item disable tracepoint @r{[}@var{num}@r{]} | |
7928 | Disable tracepoint @var{num}, or all tracepoints if no argument | |
7929 | @var{num} is given. A disabled tracepoint will have no effect during | |
7930 | the next trace experiment, but it is not forgotten. You can re-enable | |
7931 | a disabled tracepoint using the @code{enable tracepoint} command. | |
7932 | ||
7933 | @kindex enable tracepoint | |
7934 | @item enable tracepoint @r{[}@var{num}@r{]} | |
7935 | Enable tracepoint @var{num}, or all tracepoints. The enabled | |
7936 | tracepoints will become effective the next time a trace experiment is | |
7937 | run. | |
7938 | @end table | |
7939 | ||
7940 | @node Tracepoint Passcounts | |
7941 | @subsection Tracepoint Passcounts | |
7942 | ||
7943 | @table @code | |
7944 | @kindex passcount | |
7945 | @cindex tracepoint pass count | |
7946 | @item passcount @r{[}@var{n} @r{[}@var{num}@r{]]} | |
7947 | Set the @dfn{passcount} of a tracepoint. The passcount is a way to | |
7948 | automatically stop a trace experiment. If a tracepoint's passcount is | |
7949 | @var{n}, then the trace experiment will be automatically stopped on | |
7950 | the @var{n}'th time that tracepoint is hit. If the tracepoint number | |
7951 | @var{num} is not specified, the @code{passcount} command sets the | |
7952 | passcount of the most recently defined tracepoint. If no passcount is | |
7953 | given, the trace experiment will run until stopped explicitly by the | |
7954 | user. | |
7955 | ||
7956 | Examples: | |
7957 | ||
7958 | @smallexample | |
b383017d | 7959 | (@value{GDBP}) @b{passcount 5 2} // Stop on the 5th execution of |
6826cf00 | 7960 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// tracepoint 2} |
b37052ae EZ |
7961 | |
7962 | (@value{GDBP}) @b{passcount 12} // Stop on the 12th execution of the | |
6826cf00 | 7963 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// most recently defined tracepoint.} |
b37052ae EZ |
7964 | (@value{GDBP}) @b{trace foo} |
7965 | (@value{GDBP}) @b{pass 3} | |
7966 | (@value{GDBP}) @b{trace bar} | |
7967 | (@value{GDBP}) @b{pass 2} | |
7968 | (@value{GDBP}) @b{trace baz} | |
7969 | (@value{GDBP}) @b{pass 1} // Stop tracing when foo has been | |
6826cf00 EZ |
7970 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// executed 3 times OR when bar has} |
7971 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// been executed 2 times} | |
7972 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// OR when baz has been executed 1 time.} | |
b37052ae EZ |
7973 | @end smallexample |
7974 | @end table | |
7975 | ||
7976 | @node Tracepoint Actions | |
7977 | @subsection Tracepoint Action Lists | |
7978 | ||
7979 | @table @code | |
7980 | @kindex actions | |
7981 | @cindex tracepoint actions | |
7982 | @item actions @r{[}@var{num}@r{]} | |
7983 | This command will prompt for a list of actions to be taken when the | |
7984 | tracepoint is hit. If the tracepoint number @var{num} is not | |
7985 | specified, this command sets the actions for the one that was most | |
7986 | recently defined (so that you can define a tracepoint and then say | |
7987 | @code{actions} without bothering about its number). You specify the | |
7988 | actions themselves on the following lines, one action at a time, and | |
7989 | terminate the actions list with a line containing just @code{end}. So | |
7990 | far, the only defined actions are @code{collect} and | |
7991 | @code{while-stepping}. | |
7992 | ||
7993 | @cindex remove actions from a tracepoint | |
7994 | To remove all actions from a tracepoint, type @samp{actions @var{num}} | |
7995 | and follow it immediately with @samp{end}. | |
7996 | ||
7997 | @smallexample | |
7998 | (@value{GDBP}) @b{collect @var{data}} // collect some data | |
7999 | ||
6826cf00 | 8000 | (@value{GDBP}) @b{while-stepping 5} // single-step 5 times, collect data |
b37052ae | 8001 | |
6826cf00 | 8002 | (@value{GDBP}) @b{end} // signals the end of actions. |
b37052ae EZ |
8003 | @end smallexample |
8004 | ||
8005 | In the following example, the action list begins with @code{collect} | |
8006 | commands indicating the things to be collected when the tracepoint is | |
8007 | hit. Then, in order to single-step and collect additional data | |
8008 | following the tracepoint, a @code{while-stepping} command is used, | |
8009 | followed by the list of things to be collected while stepping. The | |
8010 | @code{while-stepping} command is terminated by its own separate | |
8011 | @code{end} command. Lastly, the action list is terminated by an | |
8012 | @code{end} command. | |
8013 | ||
8014 | @smallexample | |
8015 | (@value{GDBP}) @b{trace foo} | |
8016 | (@value{GDBP}) @b{actions} | |
8017 | Enter actions for tracepoint 1, one per line: | |
8018 | > collect bar,baz | |
8019 | > collect $regs | |
8020 | > while-stepping 12 | |
8021 | > collect $fp, $sp | |
8022 | > end | |
8023 | end | |
8024 | @end smallexample | |
8025 | ||
8026 | @kindex collect @r{(tracepoints)} | |
8027 | @item collect @var{expr1}, @var{expr2}, @dots{} | |
8028 | Collect values of the given expressions when the tracepoint is hit. | |
8029 | This command accepts a comma-separated list of any valid expressions. | |
8030 | In addition to global, static, or local variables, the following | |
8031 | special arguments are supported: | |
8032 | ||
8033 | @table @code | |
8034 | @item $regs | |
8035 | collect all registers | |
8036 | ||
8037 | @item $args | |
8038 | collect all function arguments | |
8039 | ||
8040 | @item $locals | |
8041 | collect all local variables. | |
8042 | @end table | |
8043 | ||
8044 | You can give several consecutive @code{collect} commands, each one | |
8045 | with a single argument, or one @code{collect} command with several | |
8046 | arguments separated by commas: the effect is the same. | |
8047 | ||
f5c37c66 EZ |
8048 | The command @code{info scope} (@pxref{Symbols, info scope}) is |
8049 | particularly useful for figuring out what data to collect. | |
8050 | ||
b37052ae EZ |
8051 | @kindex while-stepping @r{(tracepoints)} |
8052 | @item while-stepping @var{n} | |
8053 | Perform @var{n} single-step traces after the tracepoint, collecting | |
8054 | new data at each step. The @code{while-stepping} command is | |
8055 | followed by the list of what to collect while stepping (followed by | |
8056 | its own @code{end} command): | |
8057 | ||
8058 | @smallexample | |
8059 | > while-stepping 12 | |
8060 | > collect $regs, myglobal | |
8061 | > end | |
8062 | > | |
8063 | @end smallexample | |
8064 | ||
8065 | @noindent | |
8066 | You may abbreviate @code{while-stepping} as @code{ws} or | |
8067 | @code{stepping}. | |
8068 | @end table | |
8069 | ||
8070 | @node Listing Tracepoints | |
8071 | @subsection Listing Tracepoints | |
8072 | ||
8073 | @table @code | |
8074 | @kindex info tracepoints | |
09d4efe1 | 8075 | @kindex info tp |
b37052ae EZ |
8076 | @cindex information about tracepoints |
8077 | @item info tracepoints @r{[}@var{num}@r{]} | |
8a037dd7 | 8078 | Display information about the tracepoint @var{num}. If you don't specify |
798c8bc6 | 8079 | a tracepoint number, displays information about all the tracepoints |
b37052ae EZ |
8080 | defined so far. For each tracepoint, the following information is |
8081 | shown: | |
8082 | ||
8083 | @itemize @bullet | |
8084 | @item | |
8085 | its number | |
8086 | @item | |
8087 | whether it is enabled or disabled | |
8088 | @item | |
8089 | its address | |
8090 | @item | |
8091 | its passcount as given by the @code{passcount @var{n}} command | |
8092 | @item | |
8093 | its step count as given by the @code{while-stepping @var{n}} command | |
8094 | @item | |
8095 | where in the source files is the tracepoint set | |
8096 | @item | |
8097 | its action list as given by the @code{actions} command | |
8098 | @end itemize | |
8099 | ||
8100 | @smallexample | |
8101 | (@value{GDBP}) @b{info trace} | |
8102 | Num Enb Address PassC StepC What | |
8103 | 1 y 0x002117c4 0 0 <gdb_asm> | |
6826cf00 EZ |
8104 | 2 y 0x0020dc64 0 0 in g_test at g_test.c:1375 |
8105 | 3 y 0x0020b1f4 0 0 in get_data at ../foo.c:41 | |
b37052ae EZ |
8106 | (@value{GDBP}) |
8107 | @end smallexample | |
8108 | ||
8109 | @noindent | |
8110 | This command can be abbreviated @code{info tp}. | |
8111 | @end table | |
8112 | ||
79a6e687 BW |
8113 | @node Starting and Stopping Trace Experiments |
8114 | @subsection Starting and Stopping Trace Experiments | |
b37052ae EZ |
8115 | |
8116 | @table @code | |
8117 | @kindex tstart | |
8118 | @cindex start a new trace experiment | |
8119 | @cindex collected data discarded | |
8120 | @item tstart | |
8121 | This command takes no arguments. It starts the trace experiment, and | |
8122 | begins collecting data. This has the side effect of discarding all | |
8123 | the data collected in the trace buffer during the previous trace | |
8124 | experiment. | |
8125 | ||
8126 | @kindex tstop | |
8127 | @cindex stop a running trace experiment | |
8128 | @item tstop | |
8129 | This command takes no arguments. It ends the trace experiment, and | |
8130 | stops collecting data. | |
8131 | ||
68c71a2e | 8132 | @strong{Note}: a trace experiment and data collection may stop |
b37052ae EZ |
8133 | automatically if any tracepoint's passcount is reached |
8134 | (@pxref{Tracepoint Passcounts}), or if the trace buffer becomes full. | |
8135 | ||
8136 | @kindex tstatus | |
8137 | @cindex status of trace data collection | |
8138 | @cindex trace experiment, status of | |
8139 | @item tstatus | |
8140 | This command displays the status of the current trace data | |
8141 | collection. | |
8142 | @end table | |
8143 | ||
8144 | Here is an example of the commands we described so far: | |
8145 | ||
8146 | @smallexample | |
8147 | (@value{GDBP}) @b{trace gdb_c_test} | |
8148 | (@value{GDBP}) @b{actions} | |
8149 | Enter actions for tracepoint #1, one per line. | |
8150 | > collect $regs,$locals,$args | |
8151 | > while-stepping 11 | |
8152 | > collect $regs | |
8153 | > end | |
8154 | > end | |
8155 | (@value{GDBP}) @b{tstart} | |
8156 | [time passes @dots{}] | |
8157 | (@value{GDBP}) @b{tstop} | |
8158 | @end smallexample | |
8159 | ||
8160 | ||
8161 | @node Analyze Collected Data | |
79a6e687 | 8162 | @section Using the Collected Data |
b37052ae EZ |
8163 | |
8164 | After the tracepoint experiment ends, you use @value{GDBN} commands | |
8165 | for examining the trace data. The basic idea is that each tracepoint | |
8166 | collects a trace @dfn{snapshot} every time it is hit and another | |
8167 | snapshot every time it single-steps. All these snapshots are | |
8168 | consecutively numbered from zero and go into a buffer, and you can | |
8169 | examine them later. The way you examine them is to @dfn{focus} on a | |
8170 | specific trace snapshot. When the remote stub is focused on a trace | |
8171 | snapshot, it will respond to all @value{GDBN} requests for memory and | |
8172 | registers by reading from the buffer which belongs to that snapshot, | |
8173 | rather than from @emph{real} memory or registers of the program being | |
8174 | debugged. This means that @strong{all} @value{GDBN} commands | |
8175 | (@code{print}, @code{info registers}, @code{backtrace}, etc.) will | |
8176 | behave as if we were currently debugging the program state as it was | |
8177 | when the tracepoint occurred. Any requests for data that are not in | |
8178 | the buffer will fail. | |
8179 | ||
8180 | @menu | |
8181 | * tfind:: How to select a trace snapshot | |
8182 | * tdump:: How to display all data for a snapshot | |
8183 | * save-tracepoints:: How to save tracepoints for a future run | |
8184 | @end menu | |
8185 | ||
8186 | @node tfind | |
8187 | @subsection @code{tfind @var{n}} | |
8188 | ||
8189 | @kindex tfind | |
8190 | @cindex select trace snapshot | |
8191 | @cindex find trace snapshot | |
8192 | The basic command for selecting a trace snapshot from the buffer is | |
8193 | @code{tfind @var{n}}, which finds trace snapshot number @var{n}, | |
8194 | counting from zero. If no argument @var{n} is given, the next | |
8195 | snapshot is selected. | |
8196 | ||
8197 | Here are the various forms of using the @code{tfind} command. | |
8198 | ||
8199 | @table @code | |
8200 | @item tfind start | |
8201 | Find the first snapshot in the buffer. This is a synonym for | |
8202 | @code{tfind 0} (since 0 is the number of the first snapshot). | |
8203 | ||
8204 | @item tfind none | |
8205 | Stop debugging trace snapshots, resume @emph{live} debugging. | |
8206 | ||
8207 | @item tfind end | |
8208 | Same as @samp{tfind none}. | |
8209 | ||
8210 | @item tfind | |
8211 | No argument means find the next trace snapshot. | |
8212 | ||
8213 | @item tfind - | |
8214 | Find the previous trace snapshot before the current one. This permits | |
8215 | retracing earlier steps. | |
8216 | ||
8217 | @item tfind tracepoint @var{num} | |
8218 | Find the next snapshot associated with tracepoint @var{num}. Search | |
8219 | proceeds forward from the last examined trace snapshot. If no | |
8220 | argument @var{num} is given, it means find the next snapshot collected | |
8221 | for the same tracepoint as the current snapshot. | |
8222 | ||
8223 | @item tfind pc @var{addr} | |
8224 | Find the next snapshot associated with the value @var{addr} of the | |
8225 | program counter. Search proceeds forward from the last examined trace | |
8226 | snapshot. If no argument @var{addr} is given, it means find the next | |
8227 | snapshot with the same value of PC as the current snapshot. | |
8228 | ||
8229 | @item tfind outside @var{addr1}, @var{addr2} | |
8230 | Find the next snapshot whose PC is outside the given range of | |
8231 | addresses. | |
8232 | ||
8233 | @item tfind range @var{addr1}, @var{addr2} | |
8234 | Find the next snapshot whose PC is between @var{addr1} and | |
8235 | @var{addr2}. @c FIXME: Is the range inclusive or exclusive? | |
8236 | ||
8237 | @item tfind line @r{[}@var{file}:@r{]}@var{n} | |
8238 | Find the next snapshot associated with the source line @var{n}. If | |
8239 | the optional argument @var{file} is given, refer to line @var{n} in | |
8240 | that source file. Search proceeds forward from the last examined | |
8241 | trace snapshot. If no argument @var{n} is given, it means find the | |
8242 | next line other than the one currently being examined; thus saying | |
8243 | @code{tfind line} repeatedly can appear to have the same effect as | |
8244 | stepping from line to line in a @emph{live} debugging session. | |
8245 | @end table | |
8246 | ||
8247 | The default arguments for the @code{tfind} commands are specifically | |
8248 | designed to make it easy to scan through the trace buffer. For | |
8249 | instance, @code{tfind} with no argument selects the next trace | |
8250 | snapshot, and @code{tfind -} with no argument selects the previous | |
8251 | trace snapshot. So, by giving one @code{tfind} command, and then | |
8252 | simply hitting @key{RET} repeatedly you can examine all the trace | |
8253 | snapshots in order. Or, by saying @code{tfind -} and then hitting | |
8254 | @key{RET} repeatedly you can examine the snapshots in reverse order. | |
8255 | The @code{tfind line} command with no argument selects the snapshot | |
8256 | for the next source line executed. The @code{tfind pc} command with | |
8257 | no argument selects the next snapshot with the same program counter | |
8258 | (PC) as the current frame. The @code{tfind tracepoint} command with | |
8259 | no argument selects the next trace snapshot collected by the same | |
8260 | tracepoint as the current one. | |
8261 | ||
8262 | In addition to letting you scan through the trace buffer manually, | |
8263 | these commands make it easy to construct @value{GDBN} scripts that | |
8264 | scan through the trace buffer and print out whatever collected data | |
8265 | you are interested in. Thus, if we want to examine the PC, FP, and SP | |
8266 | registers from each trace frame in the buffer, we can say this: | |
8267 | ||
8268 | @smallexample | |
8269 | (@value{GDBP}) @b{tfind start} | |
8270 | (@value{GDBP}) @b{while ($trace_frame != -1)} | |
8271 | > printf "Frame %d, PC = %08X, SP = %08X, FP = %08X\n", \ | |
8272 | $trace_frame, $pc, $sp, $fp | |
8273 | > tfind | |
8274 | > end | |
8275 | ||
8276 | Frame 0, PC = 0020DC64, SP = 0030BF3C, FP = 0030BF44 | |
8277 | Frame 1, PC = 0020DC6C, SP = 0030BF38, FP = 0030BF44 | |
8278 | Frame 2, PC = 0020DC70, SP = 0030BF34, FP = 0030BF44 | |
8279 | Frame 3, PC = 0020DC74, SP = 0030BF30, FP = 0030BF44 | |
8280 | Frame 4, PC = 0020DC78, SP = 0030BF2C, FP = 0030BF44 | |
8281 | Frame 5, PC = 0020DC7C, SP = 0030BF28, FP = 0030BF44 | |
8282 | Frame 6, PC = 0020DC80, SP = 0030BF24, FP = 0030BF44 | |
8283 | Frame 7, PC = 0020DC84, SP = 0030BF20, FP = 0030BF44 | |
8284 | Frame 8, PC = 0020DC88, SP = 0030BF1C, FP = 0030BF44 | |
8285 | Frame 9, PC = 0020DC8E, SP = 0030BF18, FP = 0030BF44 | |
8286 | Frame 10, PC = 00203F6C, SP = 0030BE3C, FP = 0030BF14 | |
8287 | @end smallexample | |
8288 | ||
8289 | Or, if we want to examine the variable @code{X} at each source line in | |
8290 | the buffer: | |
8291 | ||
8292 | @smallexample | |
8293 | (@value{GDBP}) @b{tfind start} | |
8294 | (@value{GDBP}) @b{while ($trace_frame != -1)} | |
8295 | > printf "Frame %d, X == %d\n", $trace_frame, X | |
8296 | > tfind line | |
8297 | > end | |
8298 | ||
8299 | Frame 0, X = 1 | |
8300 | Frame 7, X = 2 | |
8301 | Frame 13, X = 255 | |
8302 | @end smallexample | |
8303 | ||
8304 | @node tdump | |
8305 | @subsection @code{tdump} | |
8306 | @kindex tdump | |
8307 | @cindex dump all data collected at tracepoint | |
8308 | @cindex tracepoint data, display | |
8309 | ||
8310 | This command takes no arguments. It prints all the data collected at | |
8311 | the current trace snapshot. | |
8312 | ||
8313 | @smallexample | |
8314 | (@value{GDBP}) @b{trace 444} | |
8315 | (@value{GDBP}) @b{actions} | |
8316 | Enter actions for tracepoint #2, one per line: | |
8317 | > collect $regs, $locals, $args, gdb_long_test | |
8318 | > end | |
8319 | ||
8320 | (@value{GDBP}) @b{tstart} | |
8321 | ||
8322 | (@value{GDBP}) @b{tfind line 444} | |
8323 | #0 gdb_test (p1=0x11, p2=0x22, p3=0x33, p4=0x44, p5=0x55, p6=0x66) | |
8324 | at gdb_test.c:444 | |
8325 | 444 printp( "%s: arguments = 0x%X 0x%X 0x%X 0x%X 0x%X 0x%X\n", ) | |
8326 | ||
8327 | (@value{GDBP}) @b{tdump} | |
8328 | Data collected at tracepoint 2, trace frame 1: | |
8329 | d0 0xc4aa0085 -995491707 | |
8330 | d1 0x18 24 | |
8331 | d2 0x80 128 | |
8332 | d3 0x33 51 | |
8333 | d4 0x71aea3d 119204413 | |
8334 | d5 0x22 34 | |
8335 | d6 0xe0 224 | |
8336 | d7 0x380035 3670069 | |
8337 | a0 0x19e24a 1696330 | |
8338 | a1 0x3000668 50333288 | |
8339 | a2 0x100 256 | |
8340 | a3 0x322000 3284992 | |
8341 | a4 0x3000698 50333336 | |
8342 | a5 0x1ad3cc 1758156 | |
8343 | fp 0x30bf3c 0x30bf3c | |
8344 | sp 0x30bf34 0x30bf34 | |
8345 | ps 0x0 0 | |
8346 | pc 0x20b2c8 0x20b2c8 | |
8347 | fpcontrol 0x0 0 | |
8348 | fpstatus 0x0 0 | |
8349 | fpiaddr 0x0 0 | |
8350 | p = 0x20e5b4 "gdb-test" | |
8351 | p1 = (void *) 0x11 | |
8352 | p2 = (void *) 0x22 | |
8353 | p3 = (void *) 0x33 | |
8354 | p4 = (void *) 0x44 | |
8355 | p5 = (void *) 0x55 | |
8356 | p6 = (void *) 0x66 | |
8357 | gdb_long_test = 17 '\021' | |
8358 | ||
8359 | (@value{GDBP}) | |
8360 | @end smallexample | |
8361 | ||
8362 | @node save-tracepoints | |
8363 | @subsection @code{save-tracepoints @var{filename}} | |
8364 | @kindex save-tracepoints | |
8365 | @cindex save tracepoints for future sessions | |
8366 | ||
8367 | This command saves all current tracepoint definitions together with | |
8368 | their actions and passcounts, into a file @file{@var{filename}} | |
8369 | suitable for use in a later debugging session. To read the saved | |
8370 | tracepoint definitions, use the @code{source} command (@pxref{Command | |
8371 | Files}). | |
8372 | ||
8373 | @node Tracepoint Variables | |
8374 | @section Convenience Variables for Tracepoints | |
8375 | @cindex tracepoint variables | |
8376 | @cindex convenience variables for tracepoints | |
8377 | ||
8378 | @table @code | |
8379 | @vindex $trace_frame | |
8380 | @item (int) $trace_frame | |
8381 | The current trace snapshot (a.k.a.@: @dfn{frame}) number, or -1 if no | |
8382 | snapshot is selected. | |
8383 | ||
8384 | @vindex $tracepoint | |
8385 | @item (int) $tracepoint | |
8386 | The tracepoint for the current trace snapshot. | |
8387 | ||
8388 | @vindex $trace_line | |
8389 | @item (int) $trace_line | |
8390 | The line number for the current trace snapshot. | |
8391 | ||
8392 | @vindex $trace_file | |
8393 | @item (char []) $trace_file | |
8394 | The source file for the current trace snapshot. | |
8395 | ||
8396 | @vindex $trace_func | |
8397 | @item (char []) $trace_func | |
8398 | The name of the function containing @code{$tracepoint}. | |
8399 | @end table | |
8400 | ||
8401 | Note: @code{$trace_file} is not suitable for use in @code{printf}, | |
8402 | use @code{output} instead. | |
8403 | ||
8404 | Here's a simple example of using these convenience variables for | |
8405 | stepping through all the trace snapshots and printing some of their | |
8406 | data. | |
8407 | ||
8408 | @smallexample | |
8409 | (@value{GDBP}) @b{tfind start} | |
8410 | ||
8411 | (@value{GDBP}) @b{while $trace_frame != -1} | |
8412 | > output $trace_file | |
8413 | > printf ", line %d (tracepoint #%d)\n", $trace_line, $tracepoint | |
8414 | > tfind | |
8415 | > end | |
8416 | @end smallexample | |
8417 | ||
df0cd8c5 JB |
8418 | @node Overlays |
8419 | @chapter Debugging Programs That Use Overlays | |
8420 | @cindex overlays | |
8421 | ||
8422 | If your program is too large to fit completely in your target system's | |
8423 | memory, you can sometimes use @dfn{overlays} to work around this | |
8424 | problem. @value{GDBN} provides some support for debugging programs that | |
8425 | use overlays. | |
8426 | ||
8427 | @menu | |
8428 | * How Overlays Work:: A general explanation of overlays. | |
8429 | * Overlay Commands:: Managing overlays in @value{GDBN}. | |
8430 | * Automatic Overlay Debugging:: @value{GDBN} can find out which overlays are | |
8431 | mapped by asking the inferior. | |
8432 | * Overlay Sample Program:: A sample program using overlays. | |
8433 | @end menu | |
8434 | ||
8435 | @node How Overlays Work | |
8436 | @section How Overlays Work | |
8437 | @cindex mapped overlays | |
8438 | @cindex unmapped overlays | |
8439 | @cindex load address, overlay's | |
8440 | @cindex mapped address | |
8441 | @cindex overlay area | |
8442 | ||
8443 | Suppose you have a computer whose instruction address space is only 64 | |
8444 | kilobytes long, but which has much more memory which can be accessed by | |
8445 | other means: special instructions, segment registers, or memory | |
8446 | management hardware, for example. Suppose further that you want to | |
8447 | adapt a program which is larger than 64 kilobytes to run on this system. | |
8448 | ||
8449 | One solution is to identify modules of your program which are relatively | |
8450 | independent, and need not call each other directly; call these modules | |
8451 | @dfn{overlays}. Separate the overlays from the main program, and place | |
8452 | their machine code in the larger memory. Place your main program in | |
8453 | instruction memory, but leave at least enough space there to hold the | |
8454 | largest overlay as well. | |
8455 | ||
8456 | Now, to call a function located in an overlay, you must first copy that | |
8457 | overlay's machine code from the large memory into the space set aside | |
8458 | for it in the instruction memory, and then jump to its entry point | |
8459 | there. | |
8460 | ||
c928edc0 AC |
8461 | @c NB: In the below the mapped area's size is greater or equal to the |
8462 | @c size of all overlays. This is intentional to remind the developer | |
8463 | @c that overlays don't necessarily need to be the same size. | |
8464 | ||
474c8240 | 8465 | @smallexample |
df0cd8c5 | 8466 | @group |
c928edc0 AC |
8467 | Data Instruction Larger |
8468 | Address Space Address Space Address Space | |
8469 | +-----------+ +-----------+ +-----------+ | |
8470 | | | | | | | | |
8471 | +-----------+ +-----------+ +-----------+<-- overlay 1 | |
8472 | | program | | main | .----| overlay 1 | load address | |
8473 | | variables | | program | | +-----------+ | |
8474 | | and heap | | | | | | | |
8475 | +-----------+ | | | +-----------+<-- overlay 2 | |
8476 | | | +-----------+ | | | load address | |
8477 | +-----------+ | | | .-| overlay 2 | | |
8478 | | | | | | | | |
8479 | mapped --->+-----------+ | | +-----------+ | |
8480 | address | | | | | | | |
8481 | | overlay | <-' | | | | |
8482 | | area | <---' +-----------+<-- overlay 3 | |
8483 | | | <---. | | load address | |
8484 | +-----------+ `--| overlay 3 | | |
8485 | | | | | | |
8486 | +-----------+ | | | |
8487 | +-----------+ | |
8488 | | | | |
8489 | +-----------+ | |
8490 | ||
8491 | @anchor{A code overlay}A code overlay | |
df0cd8c5 | 8492 | @end group |
474c8240 | 8493 | @end smallexample |
df0cd8c5 | 8494 | |
c928edc0 AC |
8495 | The diagram (@pxref{A code overlay}) shows a system with separate data |
8496 | and instruction address spaces. To map an overlay, the program copies | |
8497 | its code from the larger address space to the instruction address space. | |
8498 | Since the overlays shown here all use the same mapped address, only one | |
8499 | may be mapped at a time. For a system with a single address space for | |
8500 | data and instructions, the diagram would be similar, except that the | |
8501 | program variables and heap would share an address space with the main | |
8502 | program and the overlay area. | |
df0cd8c5 JB |
8503 | |
8504 | An overlay loaded into instruction memory and ready for use is called a | |
8505 | @dfn{mapped} overlay; its @dfn{mapped address} is its address in the | |
8506 | instruction memory. An overlay not present (or only partially present) | |
8507 | in instruction memory is called @dfn{unmapped}; its @dfn{load address} | |
8508 | is its address in the larger memory. The mapped address is also called | |
8509 | the @dfn{virtual memory address}, or @dfn{VMA}; the load address is also | |
8510 | called the @dfn{load memory address}, or @dfn{LMA}. | |
8511 | ||
8512 | Unfortunately, overlays are not a completely transparent way to adapt a | |
8513 | program to limited instruction memory. They introduce a new set of | |
8514 | global constraints you must keep in mind as you design your program: | |
8515 | ||
8516 | @itemize @bullet | |
8517 | ||
8518 | @item | |
8519 | Before calling or returning to a function in an overlay, your program | |
8520 | must make sure that overlay is actually mapped. Otherwise, the call or | |
8521 | return will transfer control to the right address, but in the wrong | |
8522 | overlay, and your program will probably crash. | |
8523 | ||
8524 | @item | |
8525 | If the process of mapping an overlay is expensive on your system, you | |
8526 | will need to choose your overlays carefully to minimize their effect on | |
8527 | your program's performance. | |
8528 | ||
8529 | @item | |
8530 | The executable file you load onto your system must contain each | |
8531 | overlay's instructions, appearing at the overlay's load address, not its | |
8532 | mapped address. However, each overlay's instructions must be relocated | |
8533 | and its symbols defined as if the overlay were at its mapped address. | |
8534 | You can use GNU linker scripts to specify different load and relocation | |
8535 | addresses for pieces of your program; see @ref{Overlay Description,,, | |
8536 | ld.info, Using ld: the GNU linker}. | |
8537 | ||
8538 | @item | |
8539 | The procedure for loading executable files onto your system must be able | |
8540 | to load their contents into the larger address space as well as the | |
8541 | instruction and data spaces. | |
8542 | ||
8543 | @end itemize | |
8544 | ||
8545 | The overlay system described above is rather simple, and could be | |
8546 | improved in many ways: | |
8547 | ||
8548 | @itemize @bullet | |
8549 | ||
8550 | @item | |
8551 | If your system has suitable bank switch registers or memory management | |
8552 | hardware, you could use those facilities to make an overlay's load area | |
8553 | contents simply appear at their mapped address in instruction space. | |
8554 | This would probably be faster than copying the overlay to its mapped | |
8555 | area in the usual way. | |
8556 | ||
8557 | @item | |
8558 | If your overlays are small enough, you could set aside more than one | |
8559 | overlay area, and have more than one overlay mapped at a time. | |
8560 | ||
8561 | @item | |
8562 | You can use overlays to manage data, as well as instructions. In | |
8563 | general, data overlays are even less transparent to your design than | |
8564 | code overlays: whereas code overlays only require care when you call or | |
8565 | return to functions, data overlays require care every time you access | |
8566 | the data. Also, if you change the contents of a data overlay, you | |
8567 | must copy its contents back out to its load address before you can copy a | |
8568 | different data overlay into the same mapped area. | |
8569 | ||
8570 | @end itemize | |
8571 | ||
8572 | ||
8573 | @node Overlay Commands | |
8574 | @section Overlay Commands | |
8575 | ||
8576 | To use @value{GDBN}'s overlay support, each overlay in your program must | |
8577 | correspond to a separate section of the executable file. The section's | |
8578 | virtual memory address and load memory address must be the overlay's | |
8579 | mapped and load addresses. Identifying overlays with sections allows | |
8580 | @value{GDBN} to determine the appropriate address of a function or | |
8581 | variable, depending on whether the overlay is mapped or not. | |
8582 | ||
8583 | @value{GDBN}'s overlay commands all start with the word @code{overlay}; | |
8584 | you can abbreviate this as @code{ov} or @code{ovly}. The commands are: | |
8585 | ||
8586 | @table @code | |
8587 | @item overlay off | |
4644b6e3 | 8588 | @kindex overlay |
df0cd8c5 JB |
8589 | Disable @value{GDBN}'s overlay support. When overlay support is |
8590 | disabled, @value{GDBN} assumes that all functions and variables are | |
8591 | always present at their mapped addresses. By default, @value{GDBN}'s | |
8592 | overlay support is disabled. | |
8593 | ||
8594 | @item overlay manual | |
df0cd8c5 JB |
8595 | @cindex manual overlay debugging |
8596 | Enable @dfn{manual} overlay debugging. In this mode, @value{GDBN} | |
8597 | relies on you to tell it which overlays are mapped, and which are not, | |
8598 | using the @code{overlay map-overlay} and @code{overlay unmap-overlay} | |
8599 | commands described below. | |
8600 | ||
8601 | @item overlay map-overlay @var{overlay} | |
8602 | @itemx overlay map @var{overlay} | |
df0cd8c5 JB |
8603 | @cindex map an overlay |
8604 | Tell @value{GDBN} that @var{overlay} is now mapped; @var{overlay} must | |
8605 | be the name of the object file section containing the overlay. When an | |
8606 | overlay is mapped, @value{GDBN} assumes it can find the overlay's | |
8607 | functions and variables at their mapped addresses. @value{GDBN} assumes | |
8608 | that any other overlays whose mapped ranges overlap that of | |
8609 | @var{overlay} are now unmapped. | |
8610 | ||
8611 | @item overlay unmap-overlay @var{overlay} | |
8612 | @itemx overlay unmap @var{overlay} | |
df0cd8c5 JB |
8613 | @cindex unmap an overlay |
8614 | Tell @value{GDBN} that @var{overlay} is no longer mapped; @var{overlay} | |
8615 | must be the name of the object file section containing the overlay. | |
8616 | When an overlay is unmapped, @value{GDBN} assumes it can find the | |
8617 | overlay's functions and variables at their load addresses. | |
8618 | ||
8619 | @item overlay auto | |
df0cd8c5 JB |
8620 | Enable @dfn{automatic} overlay debugging. In this mode, @value{GDBN} |
8621 | consults a data structure the overlay manager maintains in the inferior | |
8622 | to see which overlays are mapped. For details, see @ref{Automatic | |
8623 | Overlay Debugging}. | |
8624 | ||
8625 | @item overlay load-target | |
8626 | @itemx overlay load | |
df0cd8c5 JB |
8627 | @cindex reloading the overlay table |
8628 | Re-read the overlay table from the inferior. Normally, @value{GDBN} | |
8629 | re-reads the table @value{GDBN} automatically each time the inferior | |
8630 | stops, so this command should only be necessary if you have changed the | |
8631 | overlay mapping yourself using @value{GDBN}. This command is only | |
8632 | useful when using automatic overlay debugging. | |
8633 | ||
8634 | @item overlay list-overlays | |
8635 | @itemx overlay list | |
8636 | @cindex listing mapped overlays | |
8637 | Display a list of the overlays currently mapped, along with their mapped | |
8638 | addresses, load addresses, and sizes. | |
8639 | ||
8640 | @end table | |
8641 | ||
8642 | Normally, when @value{GDBN} prints a code address, it includes the name | |
8643 | of the function the address falls in: | |
8644 | ||
474c8240 | 8645 | @smallexample |
f7dc1244 | 8646 | (@value{GDBP}) print main |
df0cd8c5 | 8647 | $3 = @{int ()@} 0x11a0 <main> |
474c8240 | 8648 | @end smallexample |
df0cd8c5 JB |
8649 | @noindent |
8650 | When overlay debugging is enabled, @value{GDBN} recognizes code in | |
8651 | unmapped overlays, and prints the names of unmapped functions with | |
8652 | asterisks around them. For example, if @code{foo} is a function in an | |
8653 | unmapped overlay, @value{GDBN} prints it this way: | |
8654 | ||
474c8240 | 8655 | @smallexample |
f7dc1244 | 8656 | (@value{GDBP}) overlay list |
df0cd8c5 | 8657 | No sections are mapped. |
f7dc1244 | 8658 | (@value{GDBP}) print foo |
df0cd8c5 | 8659 | $5 = @{int (int)@} 0x100000 <*foo*> |
474c8240 | 8660 | @end smallexample |
df0cd8c5 JB |
8661 | @noindent |
8662 | When @code{foo}'s overlay is mapped, @value{GDBN} prints the function's | |
8663 | name normally: | |
8664 | ||
474c8240 | 8665 | @smallexample |
f7dc1244 | 8666 | (@value{GDBP}) overlay list |
b383017d | 8667 | Section .ov.foo.text, loaded at 0x100000 - 0x100034, |
df0cd8c5 | 8668 | mapped at 0x1016 - 0x104a |
f7dc1244 | 8669 | (@value{GDBP}) print foo |
df0cd8c5 | 8670 | $6 = @{int (int)@} 0x1016 <foo> |
474c8240 | 8671 | @end smallexample |
df0cd8c5 JB |
8672 | |
8673 | When overlay debugging is enabled, @value{GDBN} can find the correct | |
8674 | address for functions and variables in an overlay, whether or not the | |
8675 | overlay is mapped. This allows most @value{GDBN} commands, like | |
8676 | @code{break} and @code{disassemble}, to work normally, even on unmapped | |
8677 | code. However, @value{GDBN}'s breakpoint support has some limitations: | |
8678 | ||
8679 | @itemize @bullet | |
8680 | @item | |
8681 | @cindex breakpoints in overlays | |
8682 | @cindex overlays, setting breakpoints in | |
8683 | You can set breakpoints in functions in unmapped overlays, as long as | |
8684 | @value{GDBN} can write to the overlay at its load address. | |
8685 | @item | |
8686 | @value{GDBN} can not set hardware or simulator-based breakpoints in | |
8687 | unmapped overlays. However, if you set a breakpoint at the end of your | |
8688 | overlay manager (and tell @value{GDBN} which overlays are now mapped, if | |
8689 | you are using manual overlay management), @value{GDBN} will re-set its | |
8690 | breakpoints properly. | |
8691 | @end itemize | |
8692 | ||
8693 | ||
8694 | @node Automatic Overlay Debugging | |
8695 | @section Automatic Overlay Debugging | |
8696 | @cindex automatic overlay debugging | |
8697 | ||
8698 | @value{GDBN} can automatically track which overlays are mapped and which | |
8699 | are not, given some simple co-operation from the overlay manager in the | |
8700 | inferior. If you enable automatic overlay debugging with the | |
8701 | @code{overlay auto} command (@pxref{Overlay Commands}), @value{GDBN} | |
8702 | looks in the inferior's memory for certain variables describing the | |
8703 | current state of the overlays. | |
8704 | ||
8705 | Here are the variables your overlay manager must define to support | |
8706 | @value{GDBN}'s automatic overlay debugging: | |
8707 | ||
8708 | @table @asis | |
8709 | ||
8710 | @item @code{_ovly_table}: | |
8711 | This variable must be an array of the following structures: | |
8712 | ||
474c8240 | 8713 | @smallexample |
df0cd8c5 JB |
8714 | struct |
8715 | @{ | |
8716 | /* The overlay's mapped address. */ | |
8717 | unsigned long vma; | |
8718 | ||
8719 | /* The size of the overlay, in bytes. */ | |
8720 | unsigned long size; | |
8721 | ||
8722 | /* The overlay's load address. */ | |
8723 | unsigned long lma; | |
8724 | ||
8725 | /* Non-zero if the overlay is currently mapped; | |
8726 | zero otherwise. */ | |
8727 | unsigned long mapped; | |
8728 | @} | |
474c8240 | 8729 | @end smallexample |
df0cd8c5 JB |
8730 | |
8731 | @item @code{_novlys}: | |
8732 | This variable must be a four-byte signed integer, holding the total | |
8733 | number of elements in @code{_ovly_table}. | |
8734 | ||
8735 | @end table | |
8736 | ||
8737 | To decide whether a particular overlay is mapped or not, @value{GDBN} | |
8738 | looks for an entry in @w{@code{_ovly_table}} whose @code{vma} and | |
8739 | @code{lma} members equal the VMA and LMA of the overlay's section in the | |
8740 | executable file. When @value{GDBN} finds a matching entry, it consults | |
8741 | the entry's @code{mapped} member to determine whether the overlay is | |
8742 | currently mapped. | |
8743 | ||
81d46470 | 8744 | In addition, your overlay manager may define a function called |
def71bfa | 8745 | @code{_ovly_debug_event}. If this function is defined, @value{GDBN} |
81d46470 MS |
8746 | will silently set a breakpoint there. If the overlay manager then |
8747 | calls this function whenever it has changed the overlay table, this | |
8748 | will enable @value{GDBN} to accurately keep track of which overlays | |
8749 | are in program memory, and update any breakpoints that may be set | |
b383017d | 8750 | in overlays. This will allow breakpoints to work even if the |
81d46470 MS |
8751 | overlays are kept in ROM or other non-writable memory while they |
8752 | are not being executed. | |
df0cd8c5 JB |
8753 | |
8754 | @node Overlay Sample Program | |
8755 | @section Overlay Sample Program | |
8756 | @cindex overlay example program | |
8757 | ||
8758 | When linking a program which uses overlays, you must place the overlays | |
8759 | at their load addresses, while relocating them to run at their mapped | |
8760 | addresses. To do this, you must write a linker script (@pxref{Overlay | |
8761 | Description,,, ld.info, Using ld: the GNU linker}). Unfortunately, | |
8762 | since linker scripts are specific to a particular host system, target | |
8763 | architecture, and target memory layout, this manual cannot provide | |
8764 | portable sample code demonstrating @value{GDBN}'s overlay support. | |
8765 | ||
8766 | However, the @value{GDBN} source distribution does contain an overlaid | |
8767 | program, with linker scripts for a few systems, as part of its test | |
8768 | suite. The program consists of the following files from | |
8769 | @file{gdb/testsuite/gdb.base}: | |
8770 | ||
8771 | @table @file | |
8772 | @item overlays.c | |
8773 | The main program file. | |
8774 | @item ovlymgr.c | |
8775 | A simple overlay manager, used by @file{overlays.c}. | |
8776 | @item foo.c | |
8777 | @itemx bar.c | |
8778 | @itemx baz.c | |
8779 | @itemx grbx.c | |
8780 | Overlay modules, loaded and used by @file{overlays.c}. | |
8781 | @item d10v.ld | |
8782 | @itemx m32r.ld | |
8783 | Linker scripts for linking the test program on the @code{d10v-elf} | |
8784 | and @code{m32r-elf} targets. | |
8785 | @end table | |
8786 | ||
8787 | You can build the test program using the @code{d10v-elf} GCC | |
8788 | cross-compiler like this: | |
8789 | ||
474c8240 | 8790 | @smallexample |
df0cd8c5 JB |
8791 | $ d10v-elf-gcc -g -c overlays.c |
8792 | $ d10v-elf-gcc -g -c ovlymgr.c | |
8793 | $ d10v-elf-gcc -g -c foo.c | |
8794 | $ d10v-elf-gcc -g -c bar.c | |
8795 | $ d10v-elf-gcc -g -c baz.c | |
8796 | $ d10v-elf-gcc -g -c grbx.c | |
8797 | $ d10v-elf-gcc -g overlays.o ovlymgr.o foo.o bar.o \ | |
8798 | baz.o grbx.o -Wl,-Td10v.ld -o overlays | |
474c8240 | 8799 | @end smallexample |
df0cd8c5 JB |
8800 | |
8801 | The build process is identical for any other architecture, except that | |
8802 | you must substitute the appropriate compiler and linker script for the | |
8803 | target system for @code{d10v-elf-gcc} and @code{d10v.ld}. | |
8804 | ||
8805 | ||
6d2ebf8b | 8806 | @node Languages |
c906108c SS |
8807 | @chapter Using @value{GDBN} with Different Languages |
8808 | @cindex languages | |
8809 | ||
c906108c SS |
8810 | Although programming languages generally have common aspects, they are |
8811 | rarely expressed in the same manner. For instance, in ANSI C, | |
8812 | dereferencing a pointer @code{p} is accomplished by @code{*p}, but in | |
8813 | Modula-2, it is accomplished by @code{p^}. Values can also be | |
5d161b24 | 8814 | represented (and displayed) differently. Hex numbers in C appear as |
c906108c | 8815 | @samp{0x1ae}, while in Modula-2 they appear as @samp{1AEH}. |
c906108c SS |
8816 | |
8817 | @cindex working language | |
8818 | Language-specific information is built into @value{GDBN} for some languages, | |
8819 | allowing you to express operations like the above in your program's | |
8820 | native language, and allowing @value{GDBN} to output values in a manner | |
8821 | consistent with the syntax of your program's native language. The | |
8822 | language you use to build expressions is called the @dfn{working | |
8823 | language}. | |
8824 | ||
8825 | @menu | |
8826 | * Setting:: Switching between source languages | |
8827 | * Show:: Displaying the language | |
c906108c | 8828 | * Checks:: Type and range checks |
79a6e687 BW |
8829 | * Supported Languages:: Supported languages |
8830 | * Unsupported Languages:: Unsupported languages | |
c906108c SS |
8831 | @end menu |
8832 | ||
6d2ebf8b | 8833 | @node Setting |
79a6e687 | 8834 | @section Switching Between Source Languages |
c906108c SS |
8835 | |
8836 | There are two ways to control the working language---either have @value{GDBN} | |
8837 | set it automatically, or select it manually yourself. You can use the | |
8838 | @code{set language} command for either purpose. On startup, @value{GDBN} | |
8839 | defaults to setting the language automatically. The working language is | |
8840 | used to determine how expressions you type are interpreted, how values | |
8841 | are printed, etc. | |
8842 | ||
8843 | In addition to the working language, every source file that | |
8844 | @value{GDBN} knows about has its own working language. For some object | |
8845 | file formats, the compiler might indicate which language a particular | |
8846 | source file is in. However, most of the time @value{GDBN} infers the | |
8847 | language from the name of the file. The language of a source file | |
b37052ae | 8848 | controls whether C@t{++} names are demangled---this way @code{backtrace} can |
c906108c | 8849 | show each frame appropriately for its own language. There is no way to |
d4f3574e SS |
8850 | set the language of a source file from within @value{GDBN}, but you can |
8851 | set the language associated with a filename extension. @xref{Show, , | |
79a6e687 | 8852 | Displaying the Language}. |
c906108c SS |
8853 | |
8854 | This is most commonly a problem when you use a program, such | |
5d161b24 | 8855 | as @code{cfront} or @code{f2c}, that generates C but is written in |
c906108c SS |
8856 | another language. In that case, make the |
8857 | program use @code{#line} directives in its C output; that way | |
8858 | @value{GDBN} will know the correct language of the source code of the original | |
8859 | program, and will display that source code, not the generated C code. | |
8860 | ||
8861 | @menu | |
8862 | * Filenames:: Filename extensions and languages. | |
8863 | * Manually:: Setting the working language manually | |
8864 | * Automatically:: Having @value{GDBN} infer the source language | |
8865 | @end menu | |
8866 | ||
6d2ebf8b | 8867 | @node Filenames |
79a6e687 | 8868 | @subsection List of Filename Extensions and Languages |
c906108c SS |
8869 | |
8870 | If a source file name ends in one of the following extensions, then | |
8871 | @value{GDBN} infers that its language is the one indicated. | |
8872 | ||
8873 | @table @file | |
e07c999f PH |
8874 | @item .ada |
8875 | @itemx .ads | |
8876 | @itemx .adb | |
8877 | @itemx .a | |
8878 | Ada source file. | |
c906108c SS |
8879 | |
8880 | @item .c | |
8881 | C source file | |
8882 | ||
8883 | @item .C | |
8884 | @itemx .cc | |
8885 | @itemx .cp | |
8886 | @itemx .cpp | |
8887 | @itemx .cxx | |
8888 | @itemx .c++ | |
b37052ae | 8889 | C@t{++} source file |
c906108c | 8890 | |
b37303ee AF |
8891 | @item .m |
8892 | Objective-C source file | |
8893 | ||
c906108c SS |
8894 | @item .f |
8895 | @itemx .F | |
8896 | Fortran source file | |
8897 | ||
c906108c SS |
8898 | @item .mod |
8899 | Modula-2 source file | |
c906108c SS |
8900 | |
8901 | @item .s | |
8902 | @itemx .S | |
8903 | Assembler source file. This actually behaves almost like C, but | |
8904 | @value{GDBN} does not skip over function prologues when stepping. | |
8905 | @end table | |
8906 | ||
8907 | In addition, you may set the language associated with a filename | |
79a6e687 | 8908 | extension. @xref{Show, , Displaying the Language}. |
c906108c | 8909 | |
6d2ebf8b | 8910 | @node Manually |
79a6e687 | 8911 | @subsection Setting the Working Language |
c906108c SS |
8912 | |
8913 | If you allow @value{GDBN} to set the language automatically, | |
8914 | expressions are interpreted the same way in your debugging session and | |
8915 | your program. | |
8916 | ||
8917 | @kindex set language | |
8918 | If you wish, you may set the language manually. To do this, issue the | |
8919 | command @samp{set language @var{lang}}, where @var{lang} is the name of | |
5d161b24 | 8920 | a language, such as |
c906108c | 8921 | @code{c} or @code{modula-2}. |
c906108c SS |
8922 | For a list of the supported languages, type @samp{set language}. |
8923 | ||
c906108c SS |
8924 | Setting the language manually prevents @value{GDBN} from updating the working |
8925 | language automatically. This can lead to confusion if you try | |
8926 | to debug a program when the working language is not the same as the | |
8927 | source language, when an expression is acceptable to both | |
8928 | languages---but means different things. For instance, if the current | |
8929 | source file were written in C, and @value{GDBN} was parsing Modula-2, a | |
8930 | command such as: | |
8931 | ||
474c8240 | 8932 | @smallexample |
c906108c | 8933 | print a = b + c |
474c8240 | 8934 | @end smallexample |
c906108c SS |
8935 | |
8936 | @noindent | |
8937 | might not have the effect you intended. In C, this means to add | |
8938 | @code{b} and @code{c} and place the result in @code{a}. The result | |
8939 | printed would be the value of @code{a}. In Modula-2, this means to compare | |
8940 | @code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value. | |
c906108c | 8941 | |
6d2ebf8b | 8942 | @node Automatically |
79a6e687 | 8943 | @subsection Having @value{GDBN} Infer the Source Language |
c906108c SS |
8944 | |
8945 | To have @value{GDBN} set the working language automatically, use | |
8946 | @samp{set language local} or @samp{set language auto}. @value{GDBN} | |
8947 | then infers the working language. That is, when your program stops in a | |
8948 | frame (usually by encountering a breakpoint), @value{GDBN} sets the | |
8949 | working language to the language recorded for the function in that | |
8950 | frame. If the language for a frame is unknown (that is, if the function | |
8951 | or block corresponding to the frame was defined in a source file that | |
8952 | does not have a recognized extension), the current working language is | |
8953 | not changed, and @value{GDBN} issues a warning. | |
8954 | ||
8955 | This may not seem necessary for most programs, which are written | |
8956 | entirely in one source language. However, program modules and libraries | |
8957 | written in one source language can be used by a main program written in | |
8958 | a different source language. Using @samp{set language auto} in this | |
8959 | case frees you from having to set the working language manually. | |
8960 | ||
6d2ebf8b | 8961 | @node Show |
79a6e687 | 8962 | @section Displaying the Language |
c906108c SS |
8963 | |
8964 | The following commands help you find out which language is the | |
8965 | working language, and also what language source files were written in. | |
8966 | ||
c906108c SS |
8967 | @table @code |
8968 | @item show language | |
9c16f35a | 8969 | @kindex show language |
c906108c SS |
8970 | Display the current working language. This is the |
8971 | language you can use with commands such as @code{print} to | |
8972 | build and compute expressions that may involve variables in your program. | |
8973 | ||
8974 | @item info frame | |
4644b6e3 | 8975 | @kindex info frame@r{, show the source language} |
5d161b24 | 8976 | Display the source language for this frame. This language becomes the |
c906108c | 8977 | working language if you use an identifier from this frame. |
79a6e687 | 8978 | @xref{Frame Info, ,Information about a Frame}, to identify the other |
c906108c SS |
8979 | information listed here. |
8980 | ||
8981 | @item info source | |
4644b6e3 | 8982 | @kindex info source@r{, show the source language} |
c906108c | 8983 | Display the source language of this source file. |
5d161b24 | 8984 | @xref{Symbols, ,Examining the Symbol Table}, to identify the other |
c906108c SS |
8985 | information listed here. |
8986 | @end table | |
8987 | ||
8988 | In unusual circumstances, you may have source files with extensions | |
8989 | not in the standard list. You can then set the extension associated | |
8990 | with a language explicitly: | |
8991 | ||
c906108c | 8992 | @table @code |
09d4efe1 | 8993 | @item set extension-language @var{ext} @var{language} |
9c16f35a | 8994 | @kindex set extension-language |
09d4efe1 EZ |
8995 | Tell @value{GDBN} that source files with extension @var{ext} are to be |
8996 | assumed as written in the source language @var{language}. | |
c906108c SS |
8997 | |
8998 | @item info extensions | |
9c16f35a | 8999 | @kindex info extensions |
c906108c SS |
9000 | List all the filename extensions and the associated languages. |
9001 | @end table | |
9002 | ||
6d2ebf8b | 9003 | @node Checks |
79a6e687 | 9004 | @section Type and Range Checking |
c906108c SS |
9005 | |
9006 | @quotation | |
9007 | @emph{Warning:} In this release, the @value{GDBN} commands for type and range | |
9008 | checking are included, but they do not yet have any effect. This | |
9009 | section documents the intended facilities. | |
9010 | @end quotation | |
9011 | @c FIXME remove warning when type/range code added | |
9012 | ||
9013 | Some languages are designed to guard you against making seemingly common | |
9014 | errors through a series of compile- and run-time checks. These include | |
9015 | checking the type of arguments to functions and operators, and making | |
9016 | sure mathematical overflows are caught at run time. Checks such as | |
9017 | these help to ensure a program's correctness once it has been compiled | |
9018 | by eliminating type mismatches, and providing active checks for range | |
9019 | errors when your program is running. | |
9020 | ||
9021 | @value{GDBN} can check for conditions like the above if you wish. | |
9c16f35a EZ |
9022 | Although @value{GDBN} does not check the statements in your program, |
9023 | it can check expressions entered directly into @value{GDBN} for | |
9024 | evaluation via the @code{print} command, for example. As with the | |
9025 | working language, @value{GDBN} can also decide whether or not to check | |
9026 | automatically based on your program's source language. | |
79a6e687 | 9027 | @xref{Supported Languages, ,Supported Languages}, for the default |
9c16f35a | 9028 | settings of supported languages. |
c906108c SS |
9029 | |
9030 | @menu | |
9031 | * Type Checking:: An overview of type checking | |
9032 | * Range Checking:: An overview of range checking | |
9033 | @end menu | |
9034 | ||
9035 | @cindex type checking | |
9036 | @cindex checks, type | |
6d2ebf8b | 9037 | @node Type Checking |
79a6e687 | 9038 | @subsection An Overview of Type Checking |
c906108c SS |
9039 | |
9040 | Some languages, such as Modula-2, are strongly typed, meaning that the | |
9041 | arguments to operators and functions have to be of the correct type, | |
9042 | otherwise an error occurs. These checks prevent type mismatch | |
9043 | errors from ever causing any run-time problems. For example, | |
9044 | ||
9045 | @smallexample | |
9046 | 1 + 2 @result{} 3 | |
9047 | @exdent but | |
9048 | @error{} 1 + 2.3 | |
9049 | @end smallexample | |
9050 | ||
9051 | The second example fails because the @code{CARDINAL} 1 is not | |
9052 | type-compatible with the @code{REAL} 2.3. | |
9053 | ||
5d161b24 DB |
9054 | For the expressions you use in @value{GDBN} commands, you can tell the |
9055 | @value{GDBN} type checker to skip checking; | |
9056 | to treat any mismatches as errors and abandon the expression; | |
9057 | or to only issue warnings when type mismatches occur, | |
c906108c SS |
9058 | but evaluate the expression anyway. When you choose the last of |
9059 | these, @value{GDBN} evaluates expressions like the second example above, but | |
9060 | also issues a warning. | |
9061 | ||
5d161b24 DB |
9062 | Even if you turn type checking off, there may be other reasons |
9063 | related to type that prevent @value{GDBN} from evaluating an expression. | |
9064 | For instance, @value{GDBN} does not know how to add an @code{int} and | |
9065 | a @code{struct foo}. These particular type errors have nothing to do | |
9066 | with the language in use, and usually arise from expressions, such as | |
c906108c SS |
9067 | the one described above, which make little sense to evaluate anyway. |
9068 | ||
9069 | Each language defines to what degree it is strict about type. For | |
9070 | instance, both Modula-2 and C require the arguments to arithmetical | |
9071 | operators to be numbers. In C, enumerated types and pointers can be | |
9072 | represented as numbers, so that they are valid arguments to mathematical | |
79a6e687 | 9073 | operators. @xref{Supported Languages, ,Supported Languages}, for further |
c906108c SS |
9074 | details on specific languages. |
9075 | ||
9076 | @value{GDBN} provides some additional commands for controlling the type checker: | |
9077 | ||
c906108c SS |
9078 | @kindex set check type |
9079 | @kindex show check type | |
9080 | @table @code | |
9081 | @item set check type auto | |
9082 | Set type checking on or off based on the current working language. | |
79a6e687 | 9083 | @xref{Supported Languages, ,Supported Languages}, for the default settings for |
c906108c SS |
9084 | each language. |
9085 | ||
9086 | @item set check type on | |
9087 | @itemx set check type off | |
9088 | Set type checking on or off, overriding the default setting for the | |
9089 | current working language. Issue a warning if the setting does not | |
9090 | match the language default. If any type mismatches occur in | |
d4f3574e | 9091 | evaluating an expression while type checking is on, @value{GDBN} prints a |
c906108c SS |
9092 | message and aborts evaluation of the expression. |
9093 | ||
9094 | @item set check type warn | |
9095 | Cause the type checker to issue warnings, but to always attempt to | |
9096 | evaluate the expression. Evaluating the expression may still | |
9097 | be impossible for other reasons. For example, @value{GDBN} cannot add | |
9098 | numbers and structures. | |
9099 | ||
9100 | @item show type | |
5d161b24 | 9101 | Show the current setting of the type checker, and whether or not @value{GDBN} |
c906108c SS |
9102 | is setting it automatically. |
9103 | @end table | |
9104 | ||
9105 | @cindex range checking | |
9106 | @cindex checks, range | |
6d2ebf8b | 9107 | @node Range Checking |
79a6e687 | 9108 | @subsection An Overview of Range Checking |
c906108c SS |
9109 | |
9110 | In some languages (such as Modula-2), it is an error to exceed the | |
9111 | bounds of a type; this is enforced with run-time checks. Such range | |
9112 | checking is meant to ensure program correctness by making sure | |
9113 | computations do not overflow, or indices on an array element access do | |
9114 | not exceed the bounds of the array. | |
9115 | ||
9116 | For expressions you use in @value{GDBN} commands, you can tell | |
9117 | @value{GDBN} to treat range errors in one of three ways: ignore them, | |
9118 | always treat them as errors and abandon the expression, or issue | |
9119 | warnings but evaluate the expression anyway. | |
9120 | ||
9121 | A range error can result from numerical overflow, from exceeding an | |
9122 | array index bound, or when you type a constant that is not a member | |
9123 | of any type. Some languages, however, do not treat overflows as an | |
9124 | error. In many implementations of C, mathematical overflow causes the | |
9125 | result to ``wrap around'' to lower values---for example, if @var{m} is | |
9126 | the largest integer value, and @var{s} is the smallest, then | |
9127 | ||
474c8240 | 9128 | @smallexample |
c906108c | 9129 | @var{m} + 1 @result{} @var{s} |
474c8240 | 9130 | @end smallexample |
c906108c SS |
9131 | |
9132 | This, too, is specific to individual languages, and in some cases | |
79a6e687 BW |
9133 | specific to individual compilers or machines. @xref{Supported Languages, , |
9134 | Supported Languages}, for further details on specific languages. | |
c906108c SS |
9135 | |
9136 | @value{GDBN} provides some additional commands for controlling the range checker: | |
9137 | ||
c906108c SS |
9138 | @kindex set check range |
9139 | @kindex show check range | |
9140 | @table @code | |
9141 | @item set check range auto | |
9142 | Set range checking on or off based on the current working language. | |
79a6e687 | 9143 | @xref{Supported Languages, ,Supported Languages}, for the default settings for |
c906108c SS |
9144 | each language. |
9145 | ||
9146 | @item set check range on | |
9147 | @itemx set check range off | |
9148 | Set range checking on or off, overriding the default setting for the | |
9149 | current working language. A warning is issued if the setting does not | |
c3f6f71d JM |
9150 | match the language default. If a range error occurs and range checking is on, |
9151 | then a message is printed and evaluation of the expression is aborted. | |
c906108c SS |
9152 | |
9153 | @item set check range warn | |
9154 | Output messages when the @value{GDBN} range checker detects a range error, | |
9155 | but attempt to evaluate the expression anyway. Evaluating the | |
9156 | expression may still be impossible for other reasons, such as accessing | |
9157 | memory that the process does not own (a typical example from many Unix | |
9158 | systems). | |
9159 | ||
9160 | @item show range | |
9161 | Show the current setting of the range checker, and whether or not it is | |
9162 | being set automatically by @value{GDBN}. | |
9163 | @end table | |
c906108c | 9164 | |
79a6e687 BW |
9165 | @node Supported Languages |
9166 | @section Supported Languages | |
c906108c | 9167 | |
9c16f35a EZ |
9168 | @value{GDBN} supports C, C@t{++}, Objective-C, Fortran, Java, Pascal, |
9169 | assembly, Modula-2, and Ada. | |
cce74817 | 9170 | @c This is false ... |
c906108c SS |
9171 | Some @value{GDBN} features may be used in expressions regardless of the |
9172 | language you use: the @value{GDBN} @code{@@} and @code{::} operators, | |
9173 | and the @samp{@{type@}addr} construct (@pxref{Expressions, | |
9174 | ,Expressions}) can be used with the constructs of any supported | |
9175 | language. | |
9176 | ||
9177 | The following sections detail to what degree each source language is | |
9178 | supported by @value{GDBN}. These sections are not meant to be language | |
9179 | tutorials or references, but serve only as a reference guide to what the | |
9180 | @value{GDBN} expression parser accepts, and what input and output | |
9181 | formats should look like for different languages. There are many good | |
9182 | books written on each of these languages; please look to these for a | |
9183 | language reference or tutorial. | |
9184 | ||
c906108c | 9185 | @menu |
b37303ee | 9186 | * C:: C and C@t{++} |
b383017d | 9187 | * Objective-C:: Objective-C |
09d4efe1 | 9188 | * Fortran:: Fortran |
9c16f35a | 9189 | * Pascal:: Pascal |
b37303ee | 9190 | * Modula-2:: Modula-2 |
e07c999f | 9191 | * Ada:: Ada |
c906108c SS |
9192 | @end menu |
9193 | ||
6d2ebf8b | 9194 | @node C |
b37052ae | 9195 | @subsection C and C@t{++} |
7a292a7a | 9196 | |
b37052ae EZ |
9197 | @cindex C and C@t{++} |
9198 | @cindex expressions in C or C@t{++} | |
c906108c | 9199 | |
b37052ae | 9200 | Since C and C@t{++} are so closely related, many features of @value{GDBN} apply |
c906108c SS |
9201 | to both languages. Whenever this is the case, we discuss those languages |
9202 | together. | |
9203 | ||
41afff9a EZ |
9204 | @cindex C@t{++} |
9205 | @cindex @code{g++}, @sc{gnu} C@t{++} compiler | |
b37052ae EZ |
9206 | @cindex @sc{gnu} C@t{++} |
9207 | The C@t{++} debugging facilities are jointly implemented by the C@t{++} | |
9208 | compiler and @value{GDBN}. Therefore, to debug your C@t{++} code | |
9209 | effectively, you must compile your C@t{++} programs with a supported | |
9210 | C@t{++} compiler, such as @sc{gnu} @code{g++}, or the HP ANSI C@t{++} | |
c906108c SS |
9211 | compiler (@code{aCC}). |
9212 | ||
0179ffac DC |
9213 | For best results when using @sc{gnu} C@t{++}, use the DWARF 2 debugging |
9214 | format; if it doesn't work on your system, try the stabs+ debugging | |
9215 | format. You can select those formats explicitly with the @code{g++} | |
9216 | command-line options @option{-gdwarf-2} and @option{-gstabs+}. | |
ce9341a1 BW |
9217 | @xref{Debugging Options,,Options for Debugging Your Program or GCC, |
9218 | gcc.info, Using the @sc{gnu} Compiler Collection (GCC)}. | |
c906108c | 9219 | |
c906108c | 9220 | @menu |
b37052ae EZ |
9221 | * C Operators:: C and C@t{++} operators |
9222 | * C Constants:: C and C@t{++} constants | |
79a6e687 | 9223 | * C Plus Plus Expressions:: C@t{++} expressions |
b37052ae EZ |
9224 | * C Defaults:: Default settings for C and C@t{++} |
9225 | * C Checks:: C and C@t{++} type and range checks | |
c906108c | 9226 | * Debugging C:: @value{GDBN} and C |
79a6e687 | 9227 | * Debugging C Plus Plus:: @value{GDBN} features for C@t{++} |
febe4383 | 9228 | * Decimal Floating Point:: Numbers in Decimal Floating Point format |
c906108c | 9229 | @end menu |
c906108c | 9230 | |
6d2ebf8b | 9231 | @node C Operators |
79a6e687 | 9232 | @subsubsection C and C@t{++} Operators |
7a292a7a | 9233 | |
b37052ae | 9234 | @cindex C and C@t{++} operators |
c906108c SS |
9235 | |
9236 | Operators must be defined on values of specific types. For instance, | |
9237 | @code{+} is defined on numbers, but not on structures. Operators are | |
5d161b24 | 9238 | often defined on groups of types. |
c906108c | 9239 | |
b37052ae | 9240 | For the purposes of C and C@t{++}, the following definitions hold: |
c906108c SS |
9241 | |
9242 | @itemize @bullet | |
53a5351d | 9243 | |
c906108c | 9244 | @item |
c906108c | 9245 | @emph{Integral types} include @code{int} with any of its storage-class |
b37052ae | 9246 | specifiers; @code{char}; @code{enum}; and, for C@t{++}, @code{bool}. |
c906108c SS |
9247 | |
9248 | @item | |
d4f3574e SS |
9249 | @emph{Floating-point types} include @code{float}, @code{double}, and |
9250 | @code{long double} (if supported by the target platform). | |
c906108c SS |
9251 | |
9252 | @item | |
53a5351d | 9253 | @emph{Pointer types} include all types defined as @code{(@var{type} *)}. |
c906108c SS |
9254 | |
9255 | @item | |
9256 | @emph{Scalar types} include all of the above. | |
53a5351d | 9257 | |
c906108c SS |
9258 | @end itemize |
9259 | ||
9260 | @noindent | |
9261 | The following operators are supported. They are listed here | |
9262 | in order of increasing precedence: | |
9263 | ||
9264 | @table @code | |
9265 | @item , | |
9266 | The comma or sequencing operator. Expressions in a comma-separated list | |
9267 | are evaluated from left to right, with the result of the entire | |
9268 | expression being the last expression evaluated. | |
9269 | ||
9270 | @item = | |
9271 | Assignment. The value of an assignment expression is the value | |
9272 | assigned. Defined on scalar types. | |
9273 | ||
9274 | @item @var{op}= | |
9275 | Used in an expression of the form @w{@code{@var{a} @var{op}= @var{b}}}, | |
9276 | and translated to @w{@code{@var{a} = @var{a op b}}}. | |
d4f3574e | 9277 | @w{@code{@var{op}=}} and @code{=} have the same precedence. |
c906108c SS |
9278 | @var{op} is any one of the operators @code{|}, @code{^}, @code{&}, |
9279 | @code{<<}, @code{>>}, @code{+}, @code{-}, @code{*}, @code{/}, @code{%}. | |
9280 | ||
9281 | @item ?: | |
9282 | The ternary operator. @code{@var{a} ? @var{b} : @var{c}} can be thought | |
9283 | of as: if @var{a} then @var{b} else @var{c}. @var{a} should be of an | |
9284 | integral type. | |
9285 | ||
9286 | @item || | |
9287 | Logical @sc{or}. Defined on integral types. | |
9288 | ||
9289 | @item && | |
9290 | Logical @sc{and}. Defined on integral types. | |
9291 | ||
9292 | @item | | |
9293 | Bitwise @sc{or}. Defined on integral types. | |
9294 | ||
9295 | @item ^ | |
9296 | Bitwise exclusive-@sc{or}. Defined on integral types. | |
9297 | ||
9298 | @item & | |
9299 | Bitwise @sc{and}. Defined on integral types. | |
9300 | ||
9301 | @item ==@r{, }!= | |
9302 | Equality and inequality. Defined on scalar types. The value of these | |
9303 | expressions is 0 for false and non-zero for true. | |
9304 | ||
9305 | @item <@r{, }>@r{, }<=@r{, }>= | |
9306 | Less than, greater than, less than or equal, greater than or equal. | |
9307 | Defined on scalar types. The value of these expressions is 0 for false | |
9308 | and non-zero for true. | |
9309 | ||
9310 | @item <<@r{, }>> | |
9311 | left shift, and right shift. Defined on integral types. | |
9312 | ||
9313 | @item @@ | |
9314 | The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}). | |
9315 | ||
9316 | @item +@r{, }- | |
9317 | Addition and subtraction. Defined on integral types, floating-point types and | |
9318 | pointer types. | |
9319 | ||
9320 | @item *@r{, }/@r{, }% | |
9321 | Multiplication, division, and modulus. Multiplication and division are | |
9322 | defined on integral and floating-point types. Modulus is defined on | |
9323 | integral types. | |
9324 | ||
9325 | @item ++@r{, }-- | |
9326 | Increment and decrement. When appearing before a variable, the | |
9327 | operation is performed before the variable is used in an expression; | |
9328 | when appearing after it, the variable's value is used before the | |
9329 | operation takes place. | |
9330 | ||
9331 | @item * | |
9332 | Pointer dereferencing. Defined on pointer types. Same precedence as | |
9333 | @code{++}. | |
9334 | ||
9335 | @item & | |
9336 | Address operator. Defined on variables. Same precedence as @code{++}. | |
9337 | ||
b37052ae EZ |
9338 | For debugging C@t{++}, @value{GDBN} implements a use of @samp{&} beyond what is |
9339 | allowed in the C@t{++} language itself: you can use @samp{&(&@var{ref})} | |
b17828ca | 9340 | to examine the address |
b37052ae | 9341 | where a C@t{++} reference variable (declared with @samp{&@var{ref}}) is |
c906108c | 9342 | stored. |
c906108c SS |
9343 | |
9344 | @item - | |
9345 | Negative. Defined on integral and floating-point types. Same | |
9346 | precedence as @code{++}. | |
9347 | ||
9348 | @item ! | |
9349 | Logical negation. Defined on integral types. Same precedence as | |
9350 | @code{++}. | |
9351 | ||
9352 | @item ~ | |
9353 | Bitwise complement operator. Defined on integral types. Same precedence as | |
9354 | @code{++}. | |
9355 | ||
9356 | ||
9357 | @item .@r{, }-> | |
9358 | Structure member, and pointer-to-structure member. For convenience, | |
9359 | @value{GDBN} regards the two as equivalent, choosing whether to dereference a | |
9360 | pointer based on the stored type information. | |
9361 | Defined on @code{struct} and @code{union} data. | |
9362 | ||
c906108c SS |
9363 | @item .*@r{, }->* |
9364 | Dereferences of pointers to members. | |
c906108c SS |
9365 | |
9366 | @item [] | |
9367 | Array indexing. @code{@var{a}[@var{i}]} is defined as | |
9368 | @code{*(@var{a}+@var{i})}. Same precedence as @code{->}. | |
9369 | ||
9370 | @item () | |
9371 | Function parameter list. Same precedence as @code{->}. | |
9372 | ||
c906108c | 9373 | @item :: |
b37052ae | 9374 | C@t{++} scope resolution operator. Defined on @code{struct}, @code{union}, |
7a292a7a | 9375 | and @code{class} types. |
c906108c SS |
9376 | |
9377 | @item :: | |
7a292a7a SS |
9378 | Doubled colons also represent the @value{GDBN} scope operator |
9379 | (@pxref{Expressions, ,Expressions}). Same precedence as @code{::}, | |
9380 | above. | |
c906108c SS |
9381 | @end table |
9382 | ||
c906108c SS |
9383 | If an operator is redefined in the user code, @value{GDBN} usually |
9384 | attempts to invoke the redefined version instead of using the operator's | |
9385 | predefined meaning. | |
c906108c | 9386 | |
6d2ebf8b | 9387 | @node C Constants |
79a6e687 | 9388 | @subsubsection C and C@t{++} Constants |
c906108c | 9389 | |
b37052ae | 9390 | @cindex C and C@t{++} constants |
c906108c | 9391 | |
b37052ae | 9392 | @value{GDBN} allows you to express the constants of C and C@t{++} in the |
c906108c | 9393 | following ways: |
c906108c SS |
9394 | |
9395 | @itemize @bullet | |
9396 | @item | |
9397 | Integer constants are a sequence of digits. Octal constants are | |
6ca652b0 EZ |
9398 | specified by a leading @samp{0} (i.e.@: zero), and hexadecimal constants |
9399 | by a leading @samp{0x} or @samp{0X}. Constants may also end with a letter | |
c906108c SS |
9400 | @samp{l}, specifying that the constant should be treated as a |
9401 | @code{long} value. | |
9402 | ||
9403 | @item | |
9404 | Floating point constants are a sequence of digits, followed by a decimal | |
9405 | point, followed by a sequence of digits, and optionally followed by an | |
9406 | exponent. An exponent is of the form: | |
9407 | @samp{@w{e@r{[[}+@r{]|}-@r{]}@var{nnn}}}, where @var{nnn} is another | |
9408 | sequence of digits. The @samp{+} is optional for positive exponents. | |
d4f3574e SS |
9409 | A floating-point constant may also end with a letter @samp{f} or |
9410 | @samp{F}, specifying that the constant should be treated as being of | |
9411 | the @code{float} (as opposed to the default @code{double}) type; or with | |
9412 | a letter @samp{l} or @samp{L}, which specifies a @code{long double} | |
9413 | constant. | |
c906108c SS |
9414 | |
9415 | @item | |
9416 | Enumerated constants consist of enumerated identifiers, or their | |
9417 | integral equivalents. | |
9418 | ||
9419 | @item | |
9420 | Character constants are a single character surrounded by single quotes | |
9421 | (@code{'}), or a number---the ordinal value of the corresponding character | |
d4f3574e | 9422 | (usually its @sc{ascii} value). Within quotes, the single character may |
c906108c SS |
9423 | be represented by a letter or by @dfn{escape sequences}, which are of |
9424 | the form @samp{\@var{nnn}}, where @var{nnn} is the octal representation | |
9425 | of the character's ordinal value; or of the form @samp{\@var{x}}, where | |
9426 | @samp{@var{x}} is a predefined special character---for example, | |
9427 | @samp{\n} for newline. | |
9428 | ||
9429 | @item | |
96a2c332 SS |
9430 | String constants are a sequence of character constants surrounded by |
9431 | double quotes (@code{"}). Any valid character constant (as described | |
9432 | above) may appear. Double quotes within the string must be preceded by | |
9433 | a backslash, so for instance @samp{"a\"b'c"} is a string of five | |
9434 | characters. | |
c906108c SS |
9435 | |
9436 | @item | |
9437 | Pointer constants are an integral value. You can also write pointers | |
9438 | to constants using the C operator @samp{&}. | |
9439 | ||
9440 | @item | |
9441 | Array constants are comma-separated lists surrounded by braces @samp{@{} | |
9442 | and @samp{@}}; for example, @samp{@{1,2,3@}} is a three-element array of | |
9443 | integers, @samp{@{@{1,2@}, @{3,4@}, @{5,6@}@}} is a three-by-two array, | |
9444 | and @samp{@{&"hi", &"there", &"fred"@}} is a three-element array of pointers. | |
9445 | @end itemize | |
9446 | ||
79a6e687 BW |
9447 | @node C Plus Plus Expressions |
9448 | @subsubsection C@t{++} Expressions | |
b37052ae EZ |
9449 | |
9450 | @cindex expressions in C@t{++} | |
9451 | @value{GDBN} expression handling can interpret most C@t{++} expressions. | |
9452 | ||
0179ffac DC |
9453 | @cindex debugging C@t{++} programs |
9454 | @cindex C@t{++} compilers | |
9455 | @cindex debug formats and C@t{++} | |
9456 | @cindex @value{NGCC} and C@t{++} | |
c906108c | 9457 | @quotation |
b37052ae | 9458 | @emph{Warning:} @value{GDBN} can only debug C@t{++} code if you use the |
0179ffac DC |
9459 | proper compiler and the proper debug format. Currently, @value{GDBN} |
9460 | works best when debugging C@t{++} code that is compiled with | |
9461 | @value{NGCC} 2.95.3 or with @value{NGCC} 3.1 or newer, using the options | |
9462 | @option{-gdwarf-2} or @option{-gstabs+}. DWARF 2 is preferred over | |
9463 | stabs+. Most configurations of @value{NGCC} emit either DWARF 2 or | |
9464 | stabs+ as their default debug format, so you usually don't need to | |
9465 | specify a debug format explicitly. Other compilers and/or debug formats | |
9466 | are likely to work badly or not at all when using @value{GDBN} to debug | |
9467 | C@t{++} code. | |
c906108c | 9468 | @end quotation |
c906108c SS |
9469 | |
9470 | @enumerate | |
9471 | ||
9472 | @cindex member functions | |
9473 | @item | |
9474 | Member function calls are allowed; you can use expressions like | |
9475 | ||
474c8240 | 9476 | @smallexample |
c906108c | 9477 | count = aml->GetOriginal(x, y) |
474c8240 | 9478 | @end smallexample |
c906108c | 9479 | |
41afff9a | 9480 | @vindex this@r{, inside C@t{++} member functions} |
b37052ae | 9481 | @cindex namespace in C@t{++} |
c906108c SS |
9482 | @item |
9483 | While a member function is active (in the selected stack frame), your | |
9484 | expressions have the same namespace available as the member function; | |
9485 | that is, @value{GDBN} allows implicit references to the class instance | |
b37052ae | 9486 | pointer @code{this} following the same rules as C@t{++}. |
c906108c | 9487 | |
c906108c | 9488 | @cindex call overloaded functions |
d4f3574e | 9489 | @cindex overloaded functions, calling |
b37052ae | 9490 | @cindex type conversions in C@t{++} |
c906108c SS |
9491 | @item |
9492 | You can call overloaded functions; @value{GDBN} resolves the function | |
d4f3574e | 9493 | call to the right definition, with some restrictions. @value{GDBN} does not |
c906108c SS |
9494 | perform overload resolution involving user-defined type conversions, |
9495 | calls to constructors, or instantiations of templates that do not exist | |
9496 | in the program. It also cannot handle ellipsis argument lists or | |
9497 | default arguments. | |
9498 | ||
9499 | It does perform integral conversions and promotions, floating-point | |
9500 | promotions, arithmetic conversions, pointer conversions, conversions of | |
9501 | class objects to base classes, and standard conversions such as those of | |
9502 | functions or arrays to pointers; it requires an exact match on the | |
9503 | number of function arguments. | |
9504 | ||
9505 | Overload resolution is always performed, unless you have specified | |
79a6e687 BW |
9506 | @code{set overload-resolution off}. @xref{Debugging C Plus Plus, |
9507 | ,@value{GDBN} Features for C@t{++}}. | |
c906108c | 9508 | |
d4f3574e | 9509 | You must specify @code{set overload-resolution off} in order to use an |
c906108c SS |
9510 | explicit function signature to call an overloaded function, as in |
9511 | @smallexample | |
9512 | p 'foo(char,int)'('x', 13) | |
9513 | @end smallexample | |
d4f3574e | 9514 | |
c906108c | 9515 | The @value{GDBN} command-completion facility can simplify this; |
79a6e687 | 9516 | see @ref{Completion, ,Command Completion}. |
c906108c | 9517 | |
c906108c SS |
9518 | @cindex reference declarations |
9519 | @item | |
b37052ae EZ |
9520 | @value{GDBN} understands variables declared as C@t{++} references; you can use |
9521 | them in expressions just as you do in C@t{++} source---they are automatically | |
c906108c SS |
9522 | dereferenced. |
9523 | ||
9524 | In the parameter list shown when @value{GDBN} displays a frame, the values of | |
9525 | reference variables are not displayed (unlike other variables); this | |
9526 | avoids clutter, since references are often used for large structures. | |
9527 | The @emph{address} of a reference variable is always shown, unless | |
9528 | you have specified @samp{set print address off}. | |
9529 | ||
9530 | @item | |
b37052ae | 9531 | @value{GDBN} supports the C@t{++} name resolution operator @code{::}---your |
c906108c SS |
9532 | expressions can use it just as expressions in your program do. Since |
9533 | one scope may be defined in another, you can use @code{::} repeatedly if | |
9534 | necessary, for example in an expression like | |
9535 | @samp{@var{scope1}::@var{scope2}::@var{name}}. @value{GDBN} also allows | |
b37052ae | 9536 | resolving name scope by reference to source files, in both C and C@t{++} |
79a6e687 | 9537 | debugging (@pxref{Variables, ,Program Variables}). |
c906108c SS |
9538 | @end enumerate |
9539 | ||
b37052ae | 9540 | In addition, when used with HP's C@t{++} compiler, @value{GDBN} supports |
53a5351d JM |
9541 | calling virtual functions correctly, printing out virtual bases of |
9542 | objects, calling functions in a base subobject, casting objects, and | |
9543 | invoking user-defined operators. | |
c906108c | 9544 | |
6d2ebf8b | 9545 | @node C Defaults |
79a6e687 | 9546 | @subsubsection C and C@t{++} Defaults |
7a292a7a | 9547 | |
b37052ae | 9548 | @cindex C and C@t{++} defaults |
c906108c | 9549 | |
c906108c SS |
9550 | If you allow @value{GDBN} to set type and range checking automatically, they |
9551 | both default to @code{off} whenever the working language changes to | |
b37052ae | 9552 | C or C@t{++}. This happens regardless of whether you or @value{GDBN} |
c906108c | 9553 | selects the working language. |
c906108c SS |
9554 | |
9555 | If you allow @value{GDBN} to set the language automatically, it | |
9556 | recognizes source files whose names end with @file{.c}, @file{.C}, or | |
9557 | @file{.cc}, etc, and when @value{GDBN} enters code compiled from one of | |
b37052ae | 9558 | these files, it sets the working language to C or C@t{++}. |
79a6e687 | 9559 | @xref{Automatically, ,Having @value{GDBN} Infer the Source Language}, |
c906108c SS |
9560 | for further details. |
9561 | ||
c906108c SS |
9562 | @c Type checking is (a) primarily motivated by Modula-2, and (b) |
9563 | @c unimplemented. If (b) changes, it might make sense to let this node | |
9564 | @c appear even if Mod-2 does not, but meanwhile ignore it. roland 16jul93. | |
7a292a7a | 9565 | |
6d2ebf8b | 9566 | @node C Checks |
79a6e687 | 9567 | @subsubsection C and C@t{++} Type and Range Checks |
7a292a7a | 9568 | |
b37052ae | 9569 | @cindex C and C@t{++} checks |
c906108c | 9570 | |
b37052ae | 9571 | By default, when @value{GDBN} parses C or C@t{++} expressions, type checking |
c906108c SS |
9572 | is not used. However, if you turn type checking on, @value{GDBN} |
9573 | considers two variables type equivalent if: | |
9574 | ||
9575 | @itemize @bullet | |
9576 | @item | |
9577 | The two variables are structured and have the same structure, union, or | |
9578 | enumerated tag. | |
9579 | ||
9580 | @item | |
9581 | The two variables have the same type name, or types that have been | |
9582 | declared equivalent through @code{typedef}. | |
9583 | ||
9584 | @ignore | |
9585 | @c leaving this out because neither J Gilmore nor R Pesch understand it. | |
9586 | @c FIXME--beers? | |
9587 | @item | |
9588 | The two @code{struct}, @code{union}, or @code{enum} variables are | |
9589 | declared in the same declaration. (Note: this may not be true for all C | |
9590 | compilers.) | |
9591 | @end ignore | |
9592 | @end itemize | |
9593 | ||
9594 | Range checking, if turned on, is done on mathematical operations. Array | |
9595 | indices are not checked, since they are often used to index a pointer | |
9596 | that is not itself an array. | |
c906108c | 9597 | |
6d2ebf8b | 9598 | @node Debugging C |
c906108c | 9599 | @subsubsection @value{GDBN} and C |
c906108c SS |
9600 | |
9601 | The @code{set print union} and @code{show print union} commands apply to | |
9602 | the @code{union} type. When set to @samp{on}, any @code{union} that is | |
7a292a7a SS |
9603 | inside a @code{struct} or @code{class} is also printed. Otherwise, it |
9604 | appears as @samp{@{...@}}. | |
c906108c SS |
9605 | |
9606 | The @code{@@} operator aids in the debugging of dynamic arrays, formed | |
9607 | with pointers and a memory allocation function. @xref{Expressions, | |
9608 | ,Expressions}. | |
9609 | ||
79a6e687 BW |
9610 | @node Debugging C Plus Plus |
9611 | @subsubsection @value{GDBN} Features for C@t{++} | |
c906108c | 9612 | |
b37052ae | 9613 | @cindex commands for C@t{++} |
7a292a7a | 9614 | |
b37052ae EZ |
9615 | Some @value{GDBN} commands are particularly useful with C@t{++}, and some are |
9616 | designed specifically for use with C@t{++}. Here is a summary: | |
c906108c SS |
9617 | |
9618 | @table @code | |
9619 | @cindex break in overloaded functions | |
9620 | @item @r{breakpoint menus} | |
9621 | When you want a breakpoint in a function whose name is overloaded, | |
9622 | @value{GDBN} breakpoint menus help you specify which function definition | |
79a6e687 | 9623 | you want. @xref{Breakpoint Menus,,Breakpoint Menus}. |
c906108c | 9624 | |
b37052ae | 9625 | @cindex overloading in C@t{++} |
c906108c SS |
9626 | @item rbreak @var{regex} |
9627 | Setting breakpoints using regular expressions is helpful for setting | |
9628 | breakpoints on overloaded functions that are not members of any special | |
9629 | classes. | |
79a6e687 | 9630 | @xref{Set Breaks, ,Setting Breakpoints}. |
c906108c | 9631 | |
b37052ae | 9632 | @cindex C@t{++} exception handling |
c906108c SS |
9633 | @item catch throw |
9634 | @itemx catch catch | |
b37052ae | 9635 | Debug C@t{++} exception handling using these commands. @xref{Set |
79a6e687 | 9636 | Catchpoints, , Setting Catchpoints}. |
c906108c SS |
9637 | |
9638 | @cindex inheritance | |
9639 | @item ptype @var{typename} | |
9640 | Print inheritance relationships as well as other information for type | |
9641 | @var{typename}. | |
9642 | @xref{Symbols, ,Examining the Symbol Table}. | |
9643 | ||
b37052ae | 9644 | @cindex C@t{++} symbol display |
c906108c SS |
9645 | @item set print demangle |
9646 | @itemx show print demangle | |
9647 | @itemx set print asm-demangle | |
9648 | @itemx show print asm-demangle | |
b37052ae EZ |
9649 | Control whether C@t{++} symbols display in their source form, both when |
9650 | displaying code as C@t{++} source and when displaying disassemblies. | |
79a6e687 | 9651 | @xref{Print Settings, ,Print Settings}. |
c906108c SS |
9652 | |
9653 | @item set print object | |
9654 | @itemx show print object | |
9655 | Choose whether to print derived (actual) or declared types of objects. | |
79a6e687 | 9656 | @xref{Print Settings, ,Print Settings}. |
c906108c SS |
9657 | |
9658 | @item set print vtbl | |
9659 | @itemx show print vtbl | |
9660 | Control the format for printing virtual function tables. | |
79a6e687 | 9661 | @xref{Print Settings, ,Print Settings}. |
c906108c | 9662 | (The @code{vtbl} commands do not work on programs compiled with the HP |
b37052ae | 9663 | ANSI C@t{++} compiler (@code{aCC}).) |
c906108c SS |
9664 | |
9665 | @kindex set overload-resolution | |
d4f3574e | 9666 | @cindex overloaded functions, overload resolution |
c906108c | 9667 | @item set overload-resolution on |
b37052ae | 9668 | Enable overload resolution for C@t{++} expression evaluation. The default |
c906108c SS |
9669 | is on. For overloaded functions, @value{GDBN} evaluates the arguments |
9670 | and searches for a function whose signature matches the argument types, | |
79a6e687 BW |
9671 | using the standard C@t{++} conversion rules (see @ref{C Plus Plus |
9672 | Expressions, ,C@t{++} Expressions}, for details). | |
9673 | If it cannot find a match, it emits a message. | |
c906108c SS |
9674 | |
9675 | @item set overload-resolution off | |
b37052ae | 9676 | Disable overload resolution for C@t{++} expression evaluation. For |
c906108c SS |
9677 | overloaded functions that are not class member functions, @value{GDBN} |
9678 | chooses the first function of the specified name that it finds in the | |
9679 | symbol table, whether or not its arguments are of the correct type. For | |
9680 | overloaded functions that are class member functions, @value{GDBN} | |
9681 | searches for a function whose signature @emph{exactly} matches the | |
9682 | argument types. | |
c906108c | 9683 | |
9c16f35a EZ |
9684 | @kindex show overload-resolution |
9685 | @item show overload-resolution | |
9686 | Show the current setting of overload resolution. | |
9687 | ||
c906108c SS |
9688 | @item @r{Overloaded symbol names} |
9689 | You can specify a particular definition of an overloaded symbol, using | |
b37052ae | 9690 | the same notation that is used to declare such symbols in C@t{++}: type |
c906108c SS |
9691 | @code{@var{symbol}(@var{types})} rather than just @var{symbol}. You can |
9692 | also use the @value{GDBN} command-line word completion facilities to list the | |
9693 | available choices, or to finish the type list for you. | |
79a6e687 | 9694 | @xref{Completion,, Command Completion}, for details on how to do this. |
c906108c | 9695 | @end table |
c906108c | 9696 | |
febe4383 TJB |
9697 | @node Decimal Floating Point |
9698 | @subsubsection Decimal Floating Point format | |
9699 | @cindex decimal floating point format | |
9700 | ||
9701 | @value{GDBN} can examine, set and perform computations with numbers in | |
9702 | decimal floating point format, which in the C language correspond to the | |
9703 | @code{_Decimal32}, @code{_Decimal64} and @code{_Decimal128} types as | |
9704 | specified by the extension to support decimal floating-point arithmetic. | |
9705 | ||
9706 | There are two encodings in use, depending on the architecture: BID (Binary | |
9707 | Integer Decimal) for x86 and x86-64, and DPD (Densely Packed Decimal) for | |
9708 | PowerPC. @value{GDBN} will use the appropriate encoding for the configured | |
9709 | target. | |
9710 | ||
9711 | Because of a limitation in @file{libdecnumber}, the library used by @value{GDBN} | |
9712 | to manipulate decimal floating point numbers, it is not possible to convert | |
9713 | (using a cast, for example) integers wider than 32-bit to decimal float. | |
9714 | ||
9715 | In addition, in order to imitate @value{GDBN}'s behaviour with binary floating | |
9716 | point computations, error checking in decimal float operations ignores | |
9717 | underflow, overflow and divide by zero exceptions. | |
9718 | ||
4acd40f3 TJB |
9719 | In the PowerPC architecture, @value{GDBN} provides a set of pseudo-registers |
9720 | to inspect @code{_Decimal128} values stored in floating point registers. See | |
9721 | @ref{PowerPC,,PowerPC} for more details. | |
9722 | ||
b37303ee AF |
9723 | @node Objective-C |
9724 | @subsection Objective-C | |
9725 | ||
9726 | @cindex Objective-C | |
9727 | This section provides information about some commands and command | |
721c2651 EZ |
9728 | options that are useful for debugging Objective-C code. See also |
9729 | @ref{Symbols, info classes}, and @ref{Symbols, info selectors}, for a | |
9730 | few more commands specific to Objective-C support. | |
b37303ee AF |
9731 | |
9732 | @menu | |
b383017d RM |
9733 | * Method Names in Commands:: |
9734 | * The Print Command with Objective-C:: | |
b37303ee AF |
9735 | @end menu |
9736 | ||
c8f4133a | 9737 | @node Method Names in Commands |
b37303ee AF |
9738 | @subsubsection Method Names in Commands |
9739 | ||
9740 | The following commands have been extended to accept Objective-C method | |
9741 | names as line specifications: | |
9742 | ||
9743 | @kindex clear@r{, and Objective-C} | |
9744 | @kindex break@r{, and Objective-C} | |
9745 | @kindex info line@r{, and Objective-C} | |
9746 | @kindex jump@r{, and Objective-C} | |
9747 | @kindex list@r{, and Objective-C} | |
9748 | @itemize | |
9749 | @item @code{clear} | |
9750 | @item @code{break} | |
9751 | @item @code{info line} | |
9752 | @item @code{jump} | |
9753 | @item @code{list} | |
9754 | @end itemize | |
9755 | ||
9756 | A fully qualified Objective-C method name is specified as | |
9757 | ||
9758 | @smallexample | |
9759 | -[@var{Class} @var{methodName}] | |
9760 | @end smallexample | |
9761 | ||
c552b3bb JM |
9762 | where the minus sign is used to indicate an instance method and a |
9763 | plus sign (not shown) is used to indicate a class method. The class | |
9764 | name @var{Class} and method name @var{methodName} are enclosed in | |
9765 | brackets, similar to the way messages are specified in Objective-C | |
9766 | source code. For example, to set a breakpoint at the @code{create} | |
9767 | instance method of class @code{Fruit} in the program currently being | |
9768 | debugged, enter: | |
b37303ee AF |
9769 | |
9770 | @smallexample | |
9771 | break -[Fruit create] | |
9772 | @end smallexample | |
9773 | ||
9774 | To list ten program lines around the @code{initialize} class method, | |
9775 | enter: | |
9776 | ||
9777 | @smallexample | |
9778 | list +[NSText initialize] | |
9779 | @end smallexample | |
9780 | ||
c552b3bb JM |
9781 | In the current version of @value{GDBN}, the plus or minus sign is |
9782 | required. In future versions of @value{GDBN}, the plus or minus | |
9783 | sign will be optional, but you can use it to narrow the search. It | |
9784 | is also possible to specify just a method name: | |
b37303ee AF |
9785 | |
9786 | @smallexample | |
9787 | break create | |
9788 | @end smallexample | |
9789 | ||
9790 | You must specify the complete method name, including any colons. If | |
9791 | your program's source files contain more than one @code{create} method, | |
9792 | you'll be presented with a numbered list of classes that implement that | |
9793 | method. Indicate your choice by number, or type @samp{0} to exit if | |
9794 | none apply. | |
9795 | ||
9796 | As another example, to clear a breakpoint established at the | |
9797 | @code{makeKeyAndOrderFront:} method of the @code{NSWindow} class, enter: | |
9798 | ||
9799 | @smallexample | |
9800 | clear -[NSWindow makeKeyAndOrderFront:] | |
9801 | @end smallexample | |
9802 | ||
9803 | @node The Print Command with Objective-C | |
9804 | @subsubsection The Print Command With Objective-C | |
721c2651 | 9805 | @cindex Objective-C, print objects |
c552b3bb JM |
9806 | @kindex print-object |
9807 | @kindex po @r{(@code{print-object})} | |
b37303ee | 9808 | |
c552b3bb | 9809 | The print command has also been extended to accept methods. For example: |
b37303ee AF |
9810 | |
9811 | @smallexample | |
c552b3bb | 9812 | print -[@var{object} hash] |
b37303ee AF |
9813 | @end smallexample |
9814 | ||
9815 | @cindex print an Objective-C object description | |
c552b3bb JM |
9816 | @cindex @code{_NSPrintForDebugger}, and printing Objective-C objects |
9817 | @noindent | |
9818 | will tell @value{GDBN} to send the @code{hash} message to @var{object} | |
9819 | and print the result. Also, an additional command has been added, | |
9820 | @code{print-object} or @code{po} for short, which is meant to print | |
9821 | the description of an object. However, this command may only work | |
9822 | with certain Objective-C libraries that have a particular hook | |
9823 | function, @code{_NSPrintForDebugger}, defined. | |
b37303ee | 9824 | |
09d4efe1 EZ |
9825 | @node Fortran |
9826 | @subsection Fortran | |
9827 | @cindex Fortran-specific support in @value{GDBN} | |
9828 | ||
814e32d7 WZ |
9829 | @value{GDBN} can be used to debug programs written in Fortran, but it |
9830 | currently supports only the features of Fortran 77 language. | |
9831 | ||
9832 | @cindex trailing underscore, in Fortran symbols | |
9833 | Some Fortran compilers (@sc{gnu} Fortran 77 and Fortran 95 compilers | |
9834 | among them) append an underscore to the names of variables and | |
9835 | functions. When you debug programs compiled by those compilers, you | |
9836 | will need to refer to variables and functions with a trailing | |
9837 | underscore. | |
9838 | ||
9839 | @menu | |
9840 | * Fortran Operators:: Fortran operators and expressions | |
9841 | * Fortran Defaults:: Default settings for Fortran | |
79a6e687 | 9842 | * Special Fortran Commands:: Special @value{GDBN} commands for Fortran |
814e32d7 WZ |
9843 | @end menu |
9844 | ||
9845 | @node Fortran Operators | |
79a6e687 | 9846 | @subsubsection Fortran Operators and Expressions |
814e32d7 WZ |
9847 | |
9848 | @cindex Fortran operators and expressions | |
9849 | ||
9850 | Operators must be defined on values of specific types. For instance, | |
9851 | @code{+} is defined on numbers, but not on characters or other non- | |
ff2587ec | 9852 | arithmetic types. Operators are often defined on groups of types. |
814e32d7 WZ |
9853 | |
9854 | @table @code | |
9855 | @item ** | |
9856 | The exponentiation operator. It raises the first operand to the power | |
9857 | of the second one. | |
9858 | ||
9859 | @item : | |
9860 | The range operator. Normally used in the form of array(low:high) to | |
9861 | represent a section of array. | |
9862 | @end table | |
9863 | ||
9864 | @node Fortran Defaults | |
9865 | @subsubsection Fortran Defaults | |
9866 | ||
9867 | @cindex Fortran Defaults | |
9868 | ||
9869 | Fortran symbols are usually case-insensitive, so @value{GDBN} by | |
9870 | default uses case-insensitive matches for Fortran symbols. You can | |
9871 | change that with the @samp{set case-insensitive} command, see | |
9872 | @ref{Symbols}, for the details. | |
9873 | ||
79a6e687 BW |
9874 | @node Special Fortran Commands |
9875 | @subsubsection Special Fortran Commands | |
814e32d7 WZ |
9876 | |
9877 | @cindex Special Fortran commands | |
9878 | ||
db2e3e2e BW |
9879 | @value{GDBN} has some commands to support Fortran-specific features, |
9880 | such as displaying common blocks. | |
814e32d7 | 9881 | |
09d4efe1 EZ |
9882 | @table @code |
9883 | @cindex @code{COMMON} blocks, Fortran | |
9884 | @kindex info common | |
9885 | @item info common @r{[}@var{common-name}@r{]} | |
9886 | This command prints the values contained in the Fortran @code{COMMON} | |
9887 | block whose name is @var{common-name}. With no argument, the names of | |
d52fb0e9 | 9888 | all @code{COMMON} blocks visible at the current program location are |
09d4efe1 EZ |
9889 | printed. |
9890 | @end table | |
9891 | ||
9c16f35a EZ |
9892 | @node Pascal |
9893 | @subsection Pascal | |
9894 | ||
9895 | @cindex Pascal support in @value{GDBN}, limitations | |
9896 | Debugging Pascal programs which use sets, subranges, file variables, or | |
9897 | nested functions does not currently work. @value{GDBN} does not support | |
9898 | entering expressions, printing values, or similar features using Pascal | |
9899 | syntax. | |
9900 | ||
9901 | The Pascal-specific command @code{set print pascal_static-members} | |
9902 | controls whether static members of Pascal objects are displayed. | |
9903 | @xref{Print Settings, pascal_static-members}. | |
9904 | ||
09d4efe1 | 9905 | @node Modula-2 |
c906108c | 9906 | @subsection Modula-2 |
7a292a7a | 9907 | |
d4f3574e | 9908 | @cindex Modula-2, @value{GDBN} support |
c906108c SS |
9909 | |
9910 | The extensions made to @value{GDBN} to support Modula-2 only support | |
9911 | output from the @sc{gnu} Modula-2 compiler (which is currently being | |
9912 | developed). Other Modula-2 compilers are not currently supported, and | |
9913 | attempting to debug executables produced by them is most likely | |
9914 | to give an error as @value{GDBN} reads in the executable's symbol | |
9915 | table. | |
9916 | ||
9917 | @cindex expressions in Modula-2 | |
9918 | @menu | |
9919 | * M2 Operators:: Built-in operators | |
9920 | * Built-In Func/Proc:: Built-in functions and procedures | |
9921 | * M2 Constants:: Modula-2 constants | |
72019c9c | 9922 | * M2 Types:: Modula-2 types |
c906108c SS |
9923 | * M2 Defaults:: Default settings for Modula-2 |
9924 | * Deviations:: Deviations from standard Modula-2 | |
9925 | * M2 Checks:: Modula-2 type and range checks | |
9926 | * M2 Scope:: The scope operators @code{::} and @code{.} | |
9927 | * GDB/M2:: @value{GDBN} and Modula-2 | |
9928 | @end menu | |
9929 | ||
6d2ebf8b | 9930 | @node M2 Operators |
c906108c SS |
9931 | @subsubsection Operators |
9932 | @cindex Modula-2 operators | |
9933 | ||
9934 | Operators must be defined on values of specific types. For instance, | |
9935 | @code{+} is defined on numbers, but not on structures. Operators are | |
9936 | often defined on groups of types. For the purposes of Modula-2, the | |
9937 | following definitions hold: | |
9938 | ||
9939 | @itemize @bullet | |
9940 | ||
9941 | @item | |
9942 | @emph{Integral types} consist of @code{INTEGER}, @code{CARDINAL}, and | |
9943 | their subranges. | |
9944 | ||
9945 | @item | |
9946 | @emph{Character types} consist of @code{CHAR} and its subranges. | |
9947 | ||
9948 | @item | |
9949 | @emph{Floating-point types} consist of @code{REAL}. | |
9950 | ||
9951 | @item | |
9952 | @emph{Pointer types} consist of anything declared as @code{POINTER TO | |
9953 | @var{type}}. | |
9954 | ||
9955 | @item | |
9956 | @emph{Scalar types} consist of all of the above. | |
9957 | ||
9958 | @item | |
9959 | @emph{Set types} consist of @code{SET} and @code{BITSET} types. | |
9960 | ||
9961 | @item | |
9962 | @emph{Boolean types} consist of @code{BOOLEAN}. | |
9963 | @end itemize | |
9964 | ||
9965 | @noindent | |
9966 | The following operators are supported, and appear in order of | |
9967 | increasing precedence: | |
9968 | ||
9969 | @table @code | |
9970 | @item , | |
9971 | Function argument or array index separator. | |
9972 | ||
9973 | @item := | |
9974 | Assignment. The value of @var{var} @code{:=} @var{value} is | |
9975 | @var{value}. | |
9976 | ||
9977 | @item <@r{, }> | |
9978 | Less than, greater than on integral, floating-point, or enumerated | |
9979 | types. | |
9980 | ||
9981 | @item <=@r{, }>= | |
96a2c332 | 9982 | Less than or equal to, greater than or equal to |
c906108c SS |
9983 | on integral, floating-point and enumerated types, or set inclusion on |
9984 | set types. Same precedence as @code{<}. | |
9985 | ||
9986 | @item =@r{, }<>@r{, }# | |
9987 | Equality and two ways of expressing inequality, valid on scalar types. | |
9988 | Same precedence as @code{<}. In @value{GDBN} scripts, only @code{<>} is | |
9989 | available for inequality, since @code{#} conflicts with the script | |
9990 | comment character. | |
9991 | ||
9992 | @item IN | |
9993 | Set membership. Defined on set types and the types of their members. | |
9994 | Same precedence as @code{<}. | |
9995 | ||
9996 | @item OR | |
9997 | Boolean disjunction. Defined on boolean types. | |
9998 | ||
9999 | @item AND@r{, }& | |
d4f3574e | 10000 | Boolean conjunction. Defined on boolean types. |
c906108c SS |
10001 | |
10002 | @item @@ | |
10003 | The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}). | |
10004 | ||
10005 | @item +@r{, }- | |
10006 | Addition and subtraction on integral and floating-point types, or union | |
10007 | and difference on set types. | |
10008 | ||
10009 | @item * | |
10010 | Multiplication on integral and floating-point types, or set intersection | |
10011 | on set types. | |
10012 | ||
10013 | @item / | |
10014 | Division on floating-point types, or symmetric set difference on set | |
10015 | types. Same precedence as @code{*}. | |
10016 | ||
10017 | @item DIV@r{, }MOD | |
10018 | Integer division and remainder. Defined on integral types. Same | |
10019 | precedence as @code{*}. | |
10020 | ||
10021 | @item - | |
10022 | Negative. Defined on @code{INTEGER} and @code{REAL} data. | |
10023 | ||
10024 | @item ^ | |
10025 | Pointer dereferencing. Defined on pointer types. | |
10026 | ||
10027 | @item NOT | |
10028 | Boolean negation. Defined on boolean types. Same precedence as | |
10029 | @code{^}. | |
10030 | ||
10031 | @item . | |
10032 | @code{RECORD} field selector. Defined on @code{RECORD} data. Same | |
10033 | precedence as @code{^}. | |
10034 | ||
10035 | @item [] | |
10036 | Array indexing. Defined on @code{ARRAY} data. Same precedence as @code{^}. | |
10037 | ||
10038 | @item () | |
10039 | Procedure argument list. Defined on @code{PROCEDURE} objects. Same precedence | |
10040 | as @code{^}. | |
10041 | ||
10042 | @item ::@r{, }. | |
10043 | @value{GDBN} and Modula-2 scope operators. | |
10044 | @end table | |
10045 | ||
10046 | @quotation | |
72019c9c | 10047 | @emph{Warning:} Set expressions and their operations are not yet supported, so @value{GDBN} |
c906108c SS |
10048 | treats the use of the operator @code{IN}, or the use of operators |
10049 | @code{+}, @code{-}, @code{*}, @code{/}, @code{=}, , @code{<>}, @code{#}, | |
10050 | @code{<=}, and @code{>=} on sets as an error. | |
10051 | @end quotation | |
10052 | ||
cb51c4e0 | 10053 | |
6d2ebf8b | 10054 | @node Built-In Func/Proc |
79a6e687 | 10055 | @subsubsection Built-in Functions and Procedures |
cb51c4e0 | 10056 | @cindex Modula-2 built-ins |
c906108c SS |
10057 | |
10058 | Modula-2 also makes available several built-in procedures and functions. | |
10059 | In describing these, the following metavariables are used: | |
10060 | ||
10061 | @table @var | |
10062 | ||
10063 | @item a | |
10064 | represents an @code{ARRAY} variable. | |
10065 | ||
10066 | @item c | |
10067 | represents a @code{CHAR} constant or variable. | |
10068 | ||
10069 | @item i | |
10070 | represents a variable or constant of integral type. | |
10071 | ||
10072 | @item m | |
10073 | represents an identifier that belongs to a set. Generally used in the | |
10074 | same function with the metavariable @var{s}. The type of @var{s} should | |
10075 | be @code{SET OF @var{mtype}} (where @var{mtype} is the type of @var{m}). | |
10076 | ||
10077 | @item n | |
10078 | represents a variable or constant of integral or floating-point type. | |
10079 | ||
10080 | @item r | |
10081 | represents a variable or constant of floating-point type. | |
10082 | ||
10083 | @item t | |
10084 | represents a type. | |
10085 | ||
10086 | @item v | |
10087 | represents a variable. | |
10088 | ||
10089 | @item x | |
10090 | represents a variable or constant of one of many types. See the | |
10091 | explanation of the function for details. | |
10092 | @end table | |
10093 | ||
10094 | All Modula-2 built-in procedures also return a result, described below. | |
10095 | ||
10096 | @table @code | |
10097 | @item ABS(@var{n}) | |
10098 | Returns the absolute value of @var{n}. | |
10099 | ||
10100 | @item CAP(@var{c}) | |
10101 | If @var{c} is a lower case letter, it returns its upper case | |
c3f6f71d | 10102 | equivalent, otherwise it returns its argument. |
c906108c SS |
10103 | |
10104 | @item CHR(@var{i}) | |
10105 | Returns the character whose ordinal value is @var{i}. | |
10106 | ||
10107 | @item DEC(@var{v}) | |
c3f6f71d | 10108 | Decrements the value in the variable @var{v} by one. Returns the new value. |
c906108c SS |
10109 | |
10110 | @item DEC(@var{v},@var{i}) | |
10111 | Decrements the value in the variable @var{v} by @var{i}. Returns the | |
10112 | new value. | |
10113 | ||
10114 | @item EXCL(@var{m},@var{s}) | |
10115 | Removes the element @var{m} from the set @var{s}. Returns the new | |
10116 | set. | |
10117 | ||
10118 | @item FLOAT(@var{i}) | |
10119 | Returns the floating point equivalent of the integer @var{i}. | |
10120 | ||
10121 | @item HIGH(@var{a}) | |
10122 | Returns the index of the last member of @var{a}. | |
10123 | ||
10124 | @item INC(@var{v}) | |
c3f6f71d | 10125 | Increments the value in the variable @var{v} by one. Returns the new value. |
c906108c SS |
10126 | |
10127 | @item INC(@var{v},@var{i}) | |
10128 | Increments the value in the variable @var{v} by @var{i}. Returns the | |
10129 | new value. | |
10130 | ||
10131 | @item INCL(@var{m},@var{s}) | |
10132 | Adds the element @var{m} to the set @var{s} if it is not already | |
10133 | there. Returns the new set. | |
10134 | ||
10135 | @item MAX(@var{t}) | |
10136 | Returns the maximum value of the type @var{t}. | |
10137 | ||
10138 | @item MIN(@var{t}) | |
10139 | Returns the minimum value of the type @var{t}. | |
10140 | ||
10141 | @item ODD(@var{i}) | |
10142 | Returns boolean TRUE if @var{i} is an odd number. | |
10143 | ||
10144 | @item ORD(@var{x}) | |
10145 | Returns the ordinal value of its argument. For example, the ordinal | |
c3f6f71d JM |
10146 | value of a character is its @sc{ascii} value (on machines supporting the |
10147 | @sc{ascii} character set). @var{x} must be of an ordered type, which include | |
c906108c SS |
10148 | integral, character and enumerated types. |
10149 | ||
10150 | @item SIZE(@var{x}) | |
10151 | Returns the size of its argument. @var{x} can be a variable or a type. | |
10152 | ||
10153 | @item TRUNC(@var{r}) | |
10154 | Returns the integral part of @var{r}. | |
10155 | ||
844781a1 GM |
10156 | @item TSIZE(@var{x}) |
10157 | Returns the size of its argument. @var{x} can be a variable or a type. | |
10158 | ||
c906108c SS |
10159 | @item VAL(@var{t},@var{i}) |
10160 | Returns the member of the type @var{t} whose ordinal value is @var{i}. | |
10161 | @end table | |
10162 | ||
10163 | @quotation | |
10164 | @emph{Warning:} Sets and their operations are not yet supported, so | |
10165 | @value{GDBN} treats the use of procedures @code{INCL} and @code{EXCL} as | |
10166 | an error. | |
10167 | @end quotation | |
10168 | ||
10169 | @cindex Modula-2 constants | |
6d2ebf8b | 10170 | @node M2 Constants |
c906108c SS |
10171 | @subsubsection Constants |
10172 | ||
10173 | @value{GDBN} allows you to express the constants of Modula-2 in the following | |
10174 | ways: | |
10175 | ||
10176 | @itemize @bullet | |
10177 | ||
10178 | @item | |
10179 | Integer constants are simply a sequence of digits. When used in an | |
10180 | expression, a constant is interpreted to be type-compatible with the | |
10181 | rest of the expression. Hexadecimal integers are specified by a | |
10182 | trailing @samp{H}, and octal integers by a trailing @samp{B}. | |
10183 | ||
10184 | @item | |
10185 | Floating point constants appear as a sequence of digits, followed by a | |
10186 | decimal point and another sequence of digits. An optional exponent can | |
10187 | then be specified, in the form @samp{E@r{[}+@r{|}-@r{]}@var{nnn}}, where | |
10188 | @samp{@r{[}+@r{|}-@r{]}@var{nnn}} is the desired exponent. All of the | |
10189 | digits of the floating point constant must be valid decimal (base 10) | |
10190 | digits. | |
10191 | ||
10192 | @item | |
10193 | Character constants consist of a single character enclosed by a pair of | |
10194 | like quotes, either single (@code{'}) or double (@code{"}). They may | |
c3f6f71d | 10195 | also be expressed by their ordinal value (their @sc{ascii} value, usually) |
c906108c SS |
10196 | followed by a @samp{C}. |
10197 | ||
10198 | @item | |
10199 | String constants consist of a sequence of characters enclosed by a | |
10200 | pair of like quotes, either single (@code{'}) or double (@code{"}). | |
10201 | Escape sequences in the style of C are also allowed. @xref{C | |
79a6e687 | 10202 | Constants, ,C and C@t{++} Constants}, for a brief explanation of escape |
c906108c SS |
10203 | sequences. |
10204 | ||
10205 | @item | |
10206 | Enumerated constants consist of an enumerated identifier. | |
10207 | ||
10208 | @item | |
10209 | Boolean constants consist of the identifiers @code{TRUE} and | |
10210 | @code{FALSE}. | |
10211 | ||
10212 | @item | |
10213 | Pointer constants consist of integral values only. | |
10214 | ||
10215 | @item | |
10216 | Set constants are not yet supported. | |
10217 | @end itemize | |
10218 | ||
72019c9c GM |
10219 | @node M2 Types |
10220 | @subsubsection Modula-2 Types | |
10221 | @cindex Modula-2 types | |
10222 | ||
10223 | Currently @value{GDBN} can print the following data types in Modula-2 | |
10224 | syntax: array types, record types, set types, pointer types, procedure | |
10225 | types, enumerated types, subrange types and base types. You can also | |
10226 | print the contents of variables declared using these type. | |
10227 | This section gives a number of simple source code examples together with | |
10228 | sample @value{GDBN} sessions. | |
10229 | ||
10230 | The first example contains the following section of code: | |
10231 | ||
10232 | @smallexample | |
10233 | VAR | |
10234 | s: SET OF CHAR ; | |
10235 | r: [20..40] ; | |
10236 | @end smallexample | |
10237 | ||
10238 | @noindent | |
10239 | and you can request @value{GDBN} to interrogate the type and value of | |
10240 | @code{r} and @code{s}. | |
10241 | ||
10242 | @smallexample | |
10243 | (@value{GDBP}) print s | |
10244 | @{'A'..'C', 'Z'@} | |
10245 | (@value{GDBP}) ptype s | |
10246 | SET OF CHAR | |
10247 | (@value{GDBP}) print r | |
10248 | 21 | |
10249 | (@value{GDBP}) ptype r | |
10250 | [20..40] | |
10251 | @end smallexample | |
10252 | ||
10253 | @noindent | |
10254 | Likewise if your source code declares @code{s} as: | |
10255 | ||
10256 | @smallexample | |
10257 | VAR | |
10258 | s: SET ['A'..'Z'] ; | |
10259 | @end smallexample | |
10260 | ||
10261 | @noindent | |
10262 | then you may query the type of @code{s} by: | |
10263 | ||
10264 | @smallexample | |
10265 | (@value{GDBP}) ptype s | |
10266 | type = SET ['A'..'Z'] | |
10267 | @end smallexample | |
10268 | ||
10269 | @noindent | |
10270 | Note that at present you cannot interactively manipulate set | |
10271 | expressions using the debugger. | |
10272 | ||
10273 | The following example shows how you might declare an array in Modula-2 | |
10274 | and how you can interact with @value{GDBN} to print its type and contents: | |
10275 | ||
10276 | @smallexample | |
10277 | VAR | |
10278 | s: ARRAY [-10..10] OF CHAR ; | |
10279 | @end smallexample | |
10280 | ||
10281 | @smallexample | |
10282 | (@value{GDBP}) ptype s | |
10283 | ARRAY [-10..10] OF CHAR | |
10284 | @end smallexample | |
10285 | ||
10286 | Note that the array handling is not yet complete and although the type | |
10287 | is printed correctly, expression handling still assumes that all | |
10288 | arrays have a lower bound of zero and not @code{-10} as in the example | |
844781a1 | 10289 | above. |
72019c9c GM |
10290 | |
10291 | Here are some more type related Modula-2 examples: | |
10292 | ||
10293 | @smallexample | |
10294 | TYPE | |
10295 | colour = (blue, red, yellow, green) ; | |
10296 | t = [blue..yellow] ; | |
10297 | VAR | |
10298 | s: t ; | |
10299 | BEGIN | |
10300 | s := blue ; | |
10301 | @end smallexample | |
10302 | ||
10303 | @noindent | |
10304 | The @value{GDBN} interaction shows how you can query the data type | |
10305 | and value of a variable. | |
10306 | ||
10307 | @smallexample | |
10308 | (@value{GDBP}) print s | |
10309 | $1 = blue | |
10310 | (@value{GDBP}) ptype t | |
10311 | type = [blue..yellow] | |
10312 | @end smallexample | |
10313 | ||
10314 | @noindent | |
10315 | In this example a Modula-2 array is declared and its contents | |
10316 | displayed. Observe that the contents are written in the same way as | |
10317 | their @code{C} counterparts. | |
10318 | ||
10319 | @smallexample | |
10320 | VAR | |
10321 | s: ARRAY [1..5] OF CARDINAL ; | |
10322 | BEGIN | |
10323 | s[1] := 1 ; | |
10324 | @end smallexample | |
10325 | ||
10326 | @smallexample | |
10327 | (@value{GDBP}) print s | |
10328 | $1 = @{1, 0, 0, 0, 0@} | |
10329 | (@value{GDBP}) ptype s | |
10330 | type = ARRAY [1..5] OF CARDINAL | |
10331 | @end smallexample | |
10332 | ||
10333 | The Modula-2 language interface to @value{GDBN} also understands | |
10334 | pointer types as shown in this example: | |
10335 | ||
10336 | @smallexample | |
10337 | VAR | |
10338 | s: POINTER TO ARRAY [1..5] OF CARDINAL ; | |
10339 | BEGIN | |
10340 | NEW(s) ; | |
10341 | s^[1] := 1 ; | |
10342 | @end smallexample | |
10343 | ||
10344 | @noindent | |
10345 | and you can request that @value{GDBN} describes the type of @code{s}. | |
10346 | ||
10347 | @smallexample | |
10348 | (@value{GDBP}) ptype s | |
10349 | type = POINTER TO ARRAY [1..5] OF CARDINAL | |
10350 | @end smallexample | |
10351 | ||
10352 | @value{GDBN} handles compound types as we can see in this example. | |
10353 | Here we combine array types, record types, pointer types and subrange | |
10354 | types: | |
10355 | ||
10356 | @smallexample | |
10357 | TYPE | |
10358 | foo = RECORD | |
10359 | f1: CARDINAL ; | |
10360 | f2: CHAR ; | |
10361 | f3: myarray ; | |
10362 | END ; | |
10363 | ||
10364 | myarray = ARRAY myrange OF CARDINAL ; | |
10365 | myrange = [-2..2] ; | |
10366 | VAR | |
10367 | s: POINTER TO ARRAY myrange OF foo ; | |
10368 | @end smallexample | |
10369 | ||
10370 | @noindent | |
10371 | and you can ask @value{GDBN} to describe the type of @code{s} as shown | |
10372 | below. | |
10373 | ||
10374 | @smallexample | |
10375 | (@value{GDBP}) ptype s | |
10376 | type = POINTER TO ARRAY [-2..2] OF foo = RECORD | |
10377 | f1 : CARDINAL; | |
10378 | f2 : CHAR; | |
10379 | f3 : ARRAY [-2..2] OF CARDINAL; | |
10380 | END | |
10381 | @end smallexample | |
10382 | ||
6d2ebf8b | 10383 | @node M2 Defaults |
79a6e687 | 10384 | @subsubsection Modula-2 Defaults |
c906108c SS |
10385 | @cindex Modula-2 defaults |
10386 | ||
10387 | If type and range checking are set automatically by @value{GDBN}, they | |
10388 | both default to @code{on} whenever the working language changes to | |
d4f3574e | 10389 | Modula-2. This happens regardless of whether you or @value{GDBN} |
c906108c SS |
10390 | selected the working language. |
10391 | ||
10392 | If you allow @value{GDBN} to set the language automatically, then entering | |
10393 | code compiled from a file whose name ends with @file{.mod} sets the | |
79a6e687 BW |
10394 | working language to Modula-2. @xref{Automatically, ,Having @value{GDBN} |
10395 | Infer the Source Language}, for further details. | |
c906108c | 10396 | |
6d2ebf8b | 10397 | @node Deviations |
79a6e687 | 10398 | @subsubsection Deviations from Standard Modula-2 |
c906108c SS |
10399 | @cindex Modula-2, deviations from |
10400 | ||
10401 | A few changes have been made to make Modula-2 programs easier to debug. | |
10402 | This is done primarily via loosening its type strictness: | |
10403 | ||
10404 | @itemize @bullet | |
10405 | @item | |
10406 | Unlike in standard Modula-2, pointer constants can be formed by | |
10407 | integers. This allows you to modify pointer variables during | |
10408 | debugging. (In standard Modula-2, the actual address contained in a | |
10409 | pointer variable is hidden from you; it can only be modified | |
10410 | through direct assignment to another pointer variable or expression that | |
10411 | returned a pointer.) | |
10412 | ||
10413 | @item | |
10414 | C escape sequences can be used in strings and characters to represent | |
10415 | non-printable characters. @value{GDBN} prints out strings with these | |
10416 | escape sequences embedded. Single non-printable characters are | |
10417 | printed using the @samp{CHR(@var{nnn})} format. | |
10418 | ||
10419 | @item | |
10420 | The assignment operator (@code{:=}) returns the value of its right-hand | |
10421 | argument. | |
10422 | ||
10423 | @item | |
10424 | All built-in procedures both modify @emph{and} return their argument. | |
10425 | @end itemize | |
10426 | ||
6d2ebf8b | 10427 | @node M2 Checks |
79a6e687 | 10428 | @subsubsection Modula-2 Type and Range Checks |
c906108c SS |
10429 | @cindex Modula-2 checks |
10430 | ||
10431 | @quotation | |
10432 | @emph{Warning:} in this release, @value{GDBN} does not yet perform type or | |
10433 | range checking. | |
10434 | @end quotation | |
10435 | @c FIXME remove warning when type/range checks added | |
10436 | ||
10437 | @value{GDBN} considers two Modula-2 variables type equivalent if: | |
10438 | ||
10439 | @itemize @bullet | |
10440 | @item | |
10441 | They are of types that have been declared equivalent via a @code{TYPE | |
10442 | @var{t1} = @var{t2}} statement | |
10443 | ||
10444 | @item | |
10445 | They have been declared on the same line. (Note: This is true of the | |
10446 | @sc{gnu} Modula-2 compiler, but it may not be true of other compilers.) | |
10447 | @end itemize | |
10448 | ||
10449 | As long as type checking is enabled, any attempt to combine variables | |
10450 | whose types are not equivalent is an error. | |
10451 | ||
10452 | Range checking is done on all mathematical operations, assignment, array | |
10453 | index bounds, and all built-in functions and procedures. | |
10454 | ||
6d2ebf8b | 10455 | @node M2 Scope |
79a6e687 | 10456 | @subsubsection The Scope Operators @code{::} and @code{.} |
c906108c | 10457 | @cindex scope |
41afff9a | 10458 | @cindex @code{.}, Modula-2 scope operator |
c906108c SS |
10459 | @cindex colon, doubled as scope operator |
10460 | @ifinfo | |
41afff9a | 10461 | @vindex colon-colon@r{, in Modula-2} |
c906108c SS |
10462 | @c Info cannot handle :: but TeX can. |
10463 | @end ifinfo | |
10464 | @iftex | |
41afff9a | 10465 | @vindex ::@r{, in Modula-2} |
c906108c SS |
10466 | @end iftex |
10467 | ||
10468 | There are a few subtle differences between the Modula-2 scope operator | |
10469 | (@code{.}) and the @value{GDBN} scope operator (@code{::}). The two have | |
10470 | similar syntax: | |
10471 | ||
474c8240 | 10472 | @smallexample |
c906108c SS |
10473 | |
10474 | @var{module} . @var{id} | |
10475 | @var{scope} :: @var{id} | |
474c8240 | 10476 | @end smallexample |
c906108c SS |
10477 | |
10478 | @noindent | |
10479 | where @var{scope} is the name of a module or a procedure, | |
10480 | @var{module} the name of a module, and @var{id} is any declared | |
10481 | identifier within your program, except another module. | |
10482 | ||
10483 | Using the @code{::} operator makes @value{GDBN} search the scope | |
10484 | specified by @var{scope} for the identifier @var{id}. If it is not | |
10485 | found in the specified scope, then @value{GDBN} searches all scopes | |
10486 | enclosing the one specified by @var{scope}. | |
10487 | ||
10488 | Using the @code{.} operator makes @value{GDBN} search the current scope for | |
10489 | the identifier specified by @var{id} that was imported from the | |
10490 | definition module specified by @var{module}. With this operator, it is | |
10491 | an error if the identifier @var{id} was not imported from definition | |
10492 | module @var{module}, or if @var{id} is not an identifier in | |
10493 | @var{module}. | |
10494 | ||
6d2ebf8b | 10495 | @node GDB/M2 |
c906108c SS |
10496 | @subsubsection @value{GDBN} and Modula-2 |
10497 | ||
10498 | Some @value{GDBN} commands have little use when debugging Modula-2 programs. | |
10499 | Five subcommands of @code{set print} and @code{show print} apply | |
b37052ae | 10500 | specifically to C and C@t{++}: @samp{vtbl}, @samp{demangle}, |
c906108c | 10501 | @samp{asm-demangle}, @samp{object}, and @samp{union}. The first four |
b37052ae | 10502 | apply to C@t{++}, and the last to the C @code{union} type, which has no direct |
c906108c SS |
10503 | analogue in Modula-2. |
10504 | ||
10505 | The @code{@@} operator (@pxref{Expressions, ,Expressions}), while available | |
d4f3574e | 10506 | with any language, is not useful with Modula-2. Its |
c906108c | 10507 | intent is to aid the debugging of @dfn{dynamic arrays}, which cannot be |
b37052ae | 10508 | created in Modula-2 as they can in C or C@t{++}. However, because an |
c906108c | 10509 | address can be specified by an integral constant, the construct |
d4f3574e | 10510 | @samp{@{@var{type}@}@var{adrexp}} is still useful. |
c906108c SS |
10511 | |
10512 | @cindex @code{#} in Modula-2 | |
10513 | In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is | |
10514 | interpreted as the beginning of a comment. Use @code{<>} instead. | |
c906108c | 10515 | |
e07c999f PH |
10516 | @node Ada |
10517 | @subsection Ada | |
10518 | @cindex Ada | |
10519 | ||
10520 | The extensions made to @value{GDBN} for Ada only support | |
10521 | output from the @sc{gnu} Ada (GNAT) compiler. | |
10522 | Other Ada compilers are not currently supported, and | |
10523 | attempting to debug executables produced by them is most likely | |
10524 | to be difficult. | |
10525 | ||
10526 | ||
10527 | @cindex expressions in Ada | |
10528 | @menu | |
10529 | * Ada Mode Intro:: General remarks on the Ada syntax | |
10530 | and semantics supported by Ada mode | |
10531 | in @value{GDBN}. | |
10532 | * Omissions from Ada:: Restrictions on the Ada expression syntax. | |
10533 | * Additions to Ada:: Extensions of the Ada expression syntax. | |
10534 | * Stopping Before Main Program:: Debugging the program during elaboration. | |
10535 | * Ada Glitches:: Known peculiarities of Ada mode. | |
10536 | @end menu | |
10537 | ||
10538 | @node Ada Mode Intro | |
10539 | @subsubsection Introduction | |
10540 | @cindex Ada mode, general | |
10541 | ||
10542 | The Ada mode of @value{GDBN} supports a fairly large subset of Ada expression | |
10543 | syntax, with some extensions. | |
10544 | The philosophy behind the design of this subset is | |
10545 | ||
10546 | @itemize @bullet | |
10547 | @item | |
10548 | That @value{GDBN} should provide basic literals and access to operations for | |
10549 | arithmetic, dereferencing, field selection, indexing, and subprogram calls, | |
10550 | leaving more sophisticated computations to subprograms written into the | |
10551 | program (which therefore may be called from @value{GDBN}). | |
10552 | ||
10553 | @item | |
10554 | That type safety and strict adherence to Ada language restrictions | |
10555 | are not particularly important to the @value{GDBN} user. | |
10556 | ||
10557 | @item | |
10558 | That brevity is important to the @value{GDBN} user. | |
10559 | @end itemize | |
10560 | ||
10561 | Thus, for brevity, the debugger acts as if there were | |
10562 | implicit @code{with} and @code{use} clauses in effect for all user-written | |
10563 | packages, making it unnecessary to fully qualify most names with | |
10564 | their packages, regardless of context. Where this causes ambiguity, | |
10565 | @value{GDBN} asks the user's intent. | |
10566 | ||
10567 | The debugger will start in Ada mode if it detects an Ada main program. | |
10568 | As for other languages, it will enter Ada mode when stopped in a program that | |
10569 | was translated from an Ada source file. | |
10570 | ||
10571 | While in Ada mode, you may use `@t{--}' for comments. This is useful | |
10572 | mostly for documenting command files. The standard @value{GDBN} comment | |
10573 | (@samp{#}) still works at the beginning of a line in Ada mode, but not in the | |
10574 | middle (to allow based literals). | |
10575 | ||
10576 | The debugger supports limited overloading. Given a subprogram call in which | |
10577 | the function symbol has multiple definitions, it will use the number of | |
10578 | actual parameters and some information about their types to attempt to narrow | |
10579 | the set of definitions. It also makes very limited use of context, preferring | |
10580 | procedures to functions in the context of the @code{call} command, and | |
10581 | functions to procedures elsewhere. | |
10582 | ||
10583 | @node Omissions from Ada | |
10584 | @subsubsection Omissions from Ada | |
10585 | @cindex Ada, omissions from | |
10586 | ||
10587 | Here are the notable omissions from the subset: | |
10588 | ||
10589 | @itemize @bullet | |
10590 | @item | |
10591 | Only a subset of the attributes are supported: | |
10592 | ||
10593 | @itemize @minus | |
10594 | @item | |
10595 | @t{'First}, @t{'Last}, and @t{'Length} | |
10596 | on array objects (not on types and subtypes). | |
10597 | ||
10598 | @item | |
10599 | @t{'Min} and @t{'Max}. | |
10600 | ||
10601 | @item | |
10602 | @t{'Pos} and @t{'Val}. | |
10603 | ||
10604 | @item | |
10605 | @t{'Tag}. | |
10606 | ||
10607 | @item | |
10608 | @t{'Range} on array objects (not subtypes), but only as the right | |
10609 | operand of the membership (@code{in}) operator. | |
10610 | ||
10611 | @item | |
10612 | @t{'Access}, @t{'Unchecked_Access}, and | |
10613 | @t{'Unrestricted_Access} (a GNAT extension). | |
10614 | ||
10615 | @item | |
10616 | @t{'Address}. | |
10617 | @end itemize | |
10618 | ||
10619 | @item | |
10620 | The names in | |
10621 | @code{Characters.Latin_1} are not available and | |
10622 | concatenation is not implemented. Thus, escape characters in strings are | |
10623 | not currently available. | |
10624 | ||
10625 | @item | |
10626 | Equality tests (@samp{=} and @samp{/=}) on arrays test for bitwise | |
10627 | equality of representations. They will generally work correctly | |
10628 | for strings and arrays whose elements have integer or enumeration types. | |
10629 | They may not work correctly for arrays whose element | |
10630 | types have user-defined equality, for arrays of real values | |
10631 | (in particular, IEEE-conformant floating point, because of negative | |
10632 | zeroes and NaNs), and for arrays whose elements contain unused bits with | |
10633 | indeterminate values. | |
10634 | ||
10635 | @item | |
10636 | The other component-by-component array operations (@code{and}, @code{or}, | |
10637 | @code{xor}, @code{not}, and relational tests other than equality) | |
10638 | are not implemented. | |
10639 | ||
10640 | @item | |
860701dc PH |
10641 | @cindex array aggregates (Ada) |
10642 | @cindex record aggregates (Ada) | |
10643 | @cindex aggregates (Ada) | |
10644 | There is limited support for array and record aggregates. They are | |
10645 | permitted only on the right sides of assignments, as in these examples: | |
10646 | ||
10647 | @smallexample | |
10648 | set An_Array := (1, 2, 3, 4, 5, 6) | |
10649 | set An_Array := (1, others => 0) | |
10650 | set An_Array := (0|4 => 1, 1..3 => 2, 5 => 6) | |
10651 | set A_2D_Array := ((1, 2, 3), (4, 5, 6), (7, 8, 9)) | |
10652 | set A_Record := (1, "Peter", True); | |
10653 | set A_Record := (Name => "Peter", Id => 1, Alive => True) | |
10654 | @end smallexample | |
10655 | ||
10656 | Changing a | |
10657 | discriminant's value by assigning an aggregate has an | |
10658 | undefined effect if that discriminant is used within the record. | |
10659 | However, you can first modify discriminants by directly assigning to | |
10660 | them (which normally would not be allowed in Ada), and then performing an | |
10661 | aggregate assignment. For example, given a variable @code{A_Rec} | |
10662 | declared to have a type such as: | |
10663 | ||
10664 | @smallexample | |
10665 | type Rec (Len : Small_Integer := 0) is record | |
10666 | Id : Integer; | |
10667 | Vals : IntArray (1 .. Len); | |
10668 | end record; | |
10669 | @end smallexample | |
10670 | ||
10671 | you can assign a value with a different size of @code{Vals} with two | |
10672 | assignments: | |
10673 | ||
10674 | @smallexample | |
10675 | set A_Rec.Len := 4 | |
10676 | set A_Rec := (Id => 42, Vals => (1, 2, 3, 4)) | |
10677 | @end smallexample | |
10678 | ||
10679 | As this example also illustrates, @value{GDBN} is very loose about the usual | |
10680 | rules concerning aggregates. You may leave out some of the | |
10681 | components of an array or record aggregate (such as the @code{Len} | |
10682 | component in the assignment to @code{A_Rec} above); they will retain their | |
10683 | original values upon assignment. You may freely use dynamic values as | |
10684 | indices in component associations. You may even use overlapping or | |
10685 | redundant component associations, although which component values are | |
10686 | assigned in such cases is not defined. | |
e07c999f PH |
10687 | |
10688 | @item | |
10689 | Calls to dispatching subprograms are not implemented. | |
10690 | ||
10691 | @item | |
10692 | The overloading algorithm is much more limited (i.e., less selective) | |
ae21e955 BW |
10693 | than that of real Ada. It makes only limited use of the context in |
10694 | which a subexpression appears to resolve its meaning, and it is much | |
10695 | looser in its rules for allowing type matches. As a result, some | |
10696 | function calls will be ambiguous, and the user will be asked to choose | |
10697 | the proper resolution. | |
e07c999f PH |
10698 | |
10699 | @item | |
10700 | The @code{new} operator is not implemented. | |
10701 | ||
10702 | @item | |
10703 | Entry calls are not implemented. | |
10704 | ||
10705 | @item | |
10706 | Aside from printing, arithmetic operations on the native VAX floating-point | |
10707 | formats are not supported. | |
10708 | ||
10709 | @item | |
10710 | It is not possible to slice a packed array. | |
10711 | @end itemize | |
10712 | ||
10713 | @node Additions to Ada | |
10714 | @subsubsection Additions to Ada | |
10715 | @cindex Ada, deviations from | |
10716 | ||
10717 | As it does for other languages, @value{GDBN} makes certain generic | |
10718 | extensions to Ada (@pxref{Expressions}): | |
10719 | ||
10720 | @itemize @bullet | |
10721 | @item | |
ae21e955 BW |
10722 | If the expression @var{E} is a variable residing in memory (typically |
10723 | a local variable or array element) and @var{N} is a positive integer, | |
10724 | then @code{@var{E}@@@var{N}} displays the values of @var{E} and the | |
10725 | @var{N}-1 adjacent variables following it in memory as an array. In | |
10726 | Ada, this operator is generally not necessary, since its prime use is | |
10727 | in displaying parts of an array, and slicing will usually do this in | |
10728 | Ada. However, there are occasional uses when debugging programs in | |
10729 | which certain debugging information has been optimized away. | |
e07c999f PH |
10730 | |
10731 | @item | |
ae21e955 BW |
10732 | @code{@var{B}::@var{var}} means ``the variable named @var{var} that |
10733 | appears in function or file @var{B}.'' When @var{B} is a file name, | |
10734 | you must typically surround it in single quotes. | |
e07c999f PH |
10735 | |
10736 | @item | |
10737 | The expression @code{@{@var{type}@} @var{addr}} means ``the variable of type | |
10738 | @var{type} that appears at address @var{addr}.'' | |
10739 | ||
10740 | @item | |
10741 | A name starting with @samp{$} is a convenience variable | |
10742 | (@pxref{Convenience Vars}) or a machine register (@pxref{Registers}). | |
10743 | @end itemize | |
10744 | ||
ae21e955 BW |
10745 | In addition, @value{GDBN} provides a few other shortcuts and outright |
10746 | additions specific to Ada: | |
e07c999f PH |
10747 | |
10748 | @itemize @bullet | |
10749 | @item | |
10750 | The assignment statement is allowed as an expression, returning | |
10751 | its right-hand operand as its value. Thus, you may enter | |
10752 | ||
10753 | @smallexample | |
10754 | set x := y + 3 | |
10755 | print A(tmp := y + 1) | |
10756 | @end smallexample | |
10757 | ||
10758 | @item | |
10759 | The semicolon is allowed as an ``operator,'' returning as its value | |
10760 | the value of its right-hand operand. | |
10761 | This allows, for example, | |
10762 | complex conditional breaks: | |
10763 | ||
10764 | @smallexample | |
10765 | break f | |
10766 | condition 1 (report(i); k += 1; A(k) > 100) | |
10767 | @end smallexample | |
10768 | ||
10769 | @item | |
10770 | Rather than use catenation and symbolic character names to introduce special | |
10771 | characters into strings, one may instead use a special bracket notation, | |
10772 | which is also used to print strings. A sequence of characters of the form | |
10773 | @samp{["@var{XX}"]} within a string or character literal denotes the | |
10774 | (single) character whose numeric encoding is @var{XX} in hexadecimal. The | |
10775 | sequence of characters @samp{["""]} also denotes a single quotation mark | |
10776 | in strings. For example, | |
10777 | @smallexample | |
10778 | "One line.["0a"]Next line.["0a"]" | |
10779 | @end smallexample | |
10780 | @noindent | |
ae21e955 BW |
10781 | contains an ASCII newline character (@code{Ada.Characters.Latin_1.LF}) |
10782 | after each period. | |
e07c999f PH |
10783 | |
10784 | @item | |
10785 | The subtype used as a prefix for the attributes @t{'Pos}, @t{'Min}, and | |
10786 | @t{'Max} is optional (and is ignored in any case). For example, it is valid | |
10787 | to write | |
10788 | ||
10789 | @smallexample | |
10790 | print 'max(x, y) | |
10791 | @end smallexample | |
10792 | ||
10793 | @item | |
10794 | When printing arrays, @value{GDBN} uses positional notation when the | |
10795 | array has a lower bound of 1, and uses a modified named notation otherwise. | |
ae21e955 BW |
10796 | For example, a one-dimensional array of three integers with a lower bound |
10797 | of 3 might print as | |
e07c999f PH |
10798 | |
10799 | @smallexample | |
10800 | (3 => 10, 17, 1) | |
10801 | @end smallexample | |
10802 | ||
10803 | @noindent | |
10804 | That is, in contrast to valid Ada, only the first component has a @code{=>} | |
10805 | clause. | |
10806 | ||
10807 | @item | |
10808 | You may abbreviate attributes in expressions with any unique, | |
10809 | multi-character subsequence of | |
10810 | their names (an exact match gets preference). | |
10811 | For example, you may use @t{a'len}, @t{a'gth}, or @t{a'lh} | |
10812 | in place of @t{a'length}. | |
10813 | ||
10814 | @item | |
10815 | @cindex quoting Ada internal identifiers | |
10816 | Since Ada is case-insensitive, the debugger normally maps identifiers you type | |
10817 | to lower case. The GNAT compiler uses upper-case characters for | |
10818 | some of its internal identifiers, which are normally of no interest to users. | |
10819 | For the rare occasions when you actually have to look at them, | |
10820 | enclose them in angle brackets to avoid the lower-case mapping. | |
10821 | For example, | |
10822 | @smallexample | |
10823 | @value{GDBP} print <JMPBUF_SAVE>[0] | |
10824 | @end smallexample | |
10825 | ||
10826 | @item | |
10827 | Printing an object of class-wide type or dereferencing an | |
10828 | access-to-class-wide value will display all the components of the object's | |
10829 | specific type (as indicated by its run-time tag). Likewise, component | |
10830 | selection on such a value will operate on the specific type of the | |
10831 | object. | |
10832 | ||
10833 | @end itemize | |
10834 | ||
10835 | @node Stopping Before Main Program | |
10836 | @subsubsection Stopping at the Very Beginning | |
10837 | ||
10838 | @cindex breakpointing Ada elaboration code | |
10839 | It is sometimes necessary to debug the program during elaboration, and | |
10840 | before reaching the main procedure. | |
10841 | As defined in the Ada Reference | |
10842 | Manual, the elaboration code is invoked from a procedure called | |
10843 | @code{adainit}. To run your program up to the beginning of | |
10844 | elaboration, simply use the following two commands: | |
10845 | @code{tbreak adainit} and @code{run}. | |
10846 | ||
10847 | @node Ada Glitches | |
10848 | @subsubsection Known Peculiarities of Ada Mode | |
10849 | @cindex Ada, problems | |
10850 | ||
10851 | Besides the omissions listed previously (@pxref{Omissions from Ada}), | |
10852 | we know of several problems with and limitations of Ada mode in | |
10853 | @value{GDBN}, | |
10854 | some of which will be fixed with planned future releases of the debugger | |
10855 | and the GNU Ada compiler. | |
10856 | ||
10857 | @itemize @bullet | |
10858 | @item | |
10859 | Currently, the debugger | |
10860 | has insufficient information to determine whether certain pointers represent | |
10861 | pointers to objects or the objects themselves. | |
10862 | Thus, the user may have to tack an extra @code{.all} after an expression | |
10863 | to get it printed properly. | |
10864 | ||
10865 | @item | |
10866 | Static constants that the compiler chooses not to materialize as objects in | |
10867 | storage are invisible to the debugger. | |
10868 | ||
10869 | @item | |
10870 | Named parameter associations in function argument lists are ignored (the | |
10871 | argument lists are treated as positional). | |
10872 | ||
10873 | @item | |
10874 | Many useful library packages are currently invisible to the debugger. | |
10875 | ||
10876 | @item | |
10877 | Fixed-point arithmetic, conversions, input, and output is carried out using | |
10878 | floating-point arithmetic, and may give results that only approximate those on | |
10879 | the host machine. | |
10880 | ||
10881 | @item | |
10882 | The type of the @t{'Address} attribute may not be @code{System.Address}. | |
10883 | ||
10884 | @item | |
10885 | The GNAT compiler never generates the prefix @code{Standard} for any of | |
10886 | the standard symbols defined by the Ada language. @value{GDBN} knows about | |
10887 | this: it will strip the prefix from names when you use it, and will never | |
10888 | look for a name you have so qualified among local symbols, nor match against | |
10889 | symbols in other packages or subprograms. If you have | |
10890 | defined entities anywhere in your program other than parameters and | |
10891 | local variables whose simple names match names in @code{Standard}, | |
10892 | GNAT's lack of qualification here can cause confusion. When this happens, | |
10893 | you can usually resolve the confusion | |
10894 | by qualifying the problematic names with package | |
10895 | @code{Standard} explicitly. | |
10896 | @end itemize | |
10897 | ||
79a6e687 BW |
10898 | @node Unsupported Languages |
10899 | @section Unsupported Languages | |
4e562065 JB |
10900 | |
10901 | @cindex unsupported languages | |
10902 | @cindex minimal language | |
10903 | In addition to the other fully-supported programming languages, | |
10904 | @value{GDBN} also provides a pseudo-language, called @code{minimal}. | |
10905 | It does not represent a real programming language, but provides a set | |
10906 | of capabilities close to what the C or assembly languages provide. | |
10907 | This should allow most simple operations to be performed while debugging | |
10908 | an application that uses a language currently not supported by @value{GDBN}. | |
10909 | ||
10910 | If the language is set to @code{auto}, @value{GDBN} will automatically | |
10911 | select this language if the current frame corresponds to an unsupported | |
10912 | language. | |
10913 | ||
6d2ebf8b | 10914 | @node Symbols |
c906108c SS |
10915 | @chapter Examining the Symbol Table |
10916 | ||
d4f3574e | 10917 | The commands described in this chapter allow you to inquire about the |
c906108c SS |
10918 | symbols (names of variables, functions and types) defined in your |
10919 | program. This information is inherent in the text of your program and | |
10920 | does not change as your program executes. @value{GDBN} finds it in your | |
10921 | program's symbol table, in the file indicated when you started @value{GDBN} | |
79a6e687 BW |
10922 | (@pxref{File Options, ,Choosing Files}), or by one of the |
10923 | file-management commands (@pxref{Files, ,Commands to Specify Files}). | |
c906108c SS |
10924 | |
10925 | @cindex symbol names | |
10926 | @cindex names of symbols | |
10927 | @cindex quoting names | |
10928 | Occasionally, you may need to refer to symbols that contain unusual | |
10929 | characters, which @value{GDBN} ordinarily treats as word delimiters. The | |
10930 | most frequent case is in referring to static variables in other | |
79a6e687 | 10931 | source files (@pxref{Variables,,Program Variables}). File names |
c906108c SS |
10932 | are recorded in object files as debugging symbols, but @value{GDBN} would |
10933 | ordinarily parse a typical file name, like @file{foo.c}, as the three words | |
10934 | @samp{foo} @samp{.} @samp{c}. To allow @value{GDBN} to recognize | |
10935 | @samp{foo.c} as a single symbol, enclose it in single quotes; for example, | |
10936 | ||
474c8240 | 10937 | @smallexample |
c906108c | 10938 | p 'foo.c'::x |
474c8240 | 10939 | @end smallexample |
c906108c SS |
10940 | |
10941 | @noindent | |
10942 | looks up the value of @code{x} in the scope of the file @file{foo.c}. | |
10943 | ||
10944 | @table @code | |
a8f24a35 EZ |
10945 | @cindex case-insensitive symbol names |
10946 | @cindex case sensitivity in symbol names | |
10947 | @kindex set case-sensitive | |
10948 | @item set case-sensitive on | |
10949 | @itemx set case-sensitive off | |
10950 | @itemx set case-sensitive auto | |
10951 | Normally, when @value{GDBN} looks up symbols, it matches their names | |
10952 | with case sensitivity determined by the current source language. | |
10953 | Occasionally, you may wish to control that. The command @code{set | |
10954 | case-sensitive} lets you do that by specifying @code{on} for | |
10955 | case-sensitive matches or @code{off} for case-insensitive ones. If | |
10956 | you specify @code{auto}, case sensitivity is reset to the default | |
10957 | suitable for the source language. The default is case-sensitive | |
10958 | matches for all languages except for Fortran, for which the default is | |
10959 | case-insensitive matches. | |
10960 | ||
9c16f35a EZ |
10961 | @kindex show case-sensitive |
10962 | @item show case-sensitive | |
a8f24a35 EZ |
10963 | This command shows the current setting of case sensitivity for symbols |
10964 | lookups. | |
10965 | ||
c906108c | 10966 | @kindex info address |
b37052ae | 10967 | @cindex address of a symbol |
c906108c SS |
10968 | @item info address @var{symbol} |
10969 | Describe where the data for @var{symbol} is stored. For a register | |
10970 | variable, this says which register it is kept in. For a non-register | |
10971 | local variable, this prints the stack-frame offset at which the variable | |
10972 | is always stored. | |
10973 | ||
10974 | Note the contrast with @samp{print &@var{symbol}}, which does not work | |
10975 | at all for a register variable, and for a stack local variable prints | |
10976 | the exact address of the current instantiation of the variable. | |
10977 | ||
3d67e040 | 10978 | @kindex info symbol |
b37052ae | 10979 | @cindex symbol from address |
9c16f35a | 10980 | @cindex closest symbol and offset for an address |
3d67e040 EZ |
10981 | @item info symbol @var{addr} |
10982 | Print the name of a symbol which is stored at the address @var{addr}. | |
10983 | If no symbol is stored exactly at @var{addr}, @value{GDBN} prints the | |
10984 | nearest symbol and an offset from it: | |
10985 | ||
474c8240 | 10986 | @smallexample |
3d67e040 EZ |
10987 | (@value{GDBP}) info symbol 0x54320 |
10988 | _initialize_vx + 396 in section .text | |
474c8240 | 10989 | @end smallexample |
3d67e040 EZ |
10990 | |
10991 | @noindent | |
10992 | This is the opposite of the @code{info address} command. You can use | |
10993 | it to find out the name of a variable or a function given its address. | |
10994 | ||
c906108c | 10995 | @kindex whatis |
62f3a2ba FF |
10996 | @item whatis [@var{arg}] |
10997 | Print the data type of @var{arg}, which can be either an expression or | |
10998 | a data type. With no argument, print the data type of @code{$}, the | |
10999 | last value in the value history. If @var{arg} is an expression, it is | |
11000 | not actually evaluated, and any side-effecting operations (such as | |
11001 | assignments or function calls) inside it do not take place. If | |
11002 | @var{arg} is a type name, it may be the name of a type or typedef, or | |
11003 | for C code it may have the form @samp{class @var{class-name}}, | |
11004 | @samp{struct @var{struct-tag}}, @samp{union @var{union-tag}} or | |
11005 | @samp{enum @var{enum-tag}}. | |
c906108c SS |
11006 | @xref{Expressions, ,Expressions}. |
11007 | ||
c906108c | 11008 | @kindex ptype |
62f3a2ba FF |
11009 | @item ptype [@var{arg}] |
11010 | @code{ptype} accepts the same arguments as @code{whatis}, but prints a | |
11011 | detailed description of the type, instead of just the name of the type. | |
11012 | @xref{Expressions, ,Expressions}. | |
c906108c SS |
11013 | |
11014 | For example, for this variable declaration: | |
11015 | ||
474c8240 | 11016 | @smallexample |
c906108c | 11017 | struct complex @{double real; double imag;@} v; |
474c8240 | 11018 | @end smallexample |
c906108c SS |
11019 | |
11020 | @noindent | |
11021 | the two commands give this output: | |
11022 | ||
474c8240 | 11023 | @smallexample |
c906108c SS |
11024 | @group |
11025 | (@value{GDBP}) whatis v | |
11026 | type = struct complex | |
11027 | (@value{GDBP}) ptype v | |
11028 | type = struct complex @{ | |
11029 | double real; | |
11030 | double imag; | |
11031 | @} | |
11032 | @end group | |
474c8240 | 11033 | @end smallexample |
c906108c SS |
11034 | |
11035 | @noindent | |
11036 | As with @code{whatis}, using @code{ptype} without an argument refers to | |
11037 | the type of @code{$}, the last value in the value history. | |
11038 | ||
ab1adacd EZ |
11039 | @cindex incomplete type |
11040 | Sometimes, programs use opaque data types or incomplete specifications | |
11041 | of complex data structure. If the debug information included in the | |
11042 | program does not allow @value{GDBN} to display a full declaration of | |
11043 | the data type, it will say @samp{<incomplete type>}. For example, | |
11044 | given these declarations: | |
11045 | ||
11046 | @smallexample | |
11047 | struct foo; | |
11048 | struct foo *fooptr; | |
11049 | @end smallexample | |
11050 | ||
11051 | @noindent | |
11052 | but no definition for @code{struct foo} itself, @value{GDBN} will say: | |
11053 | ||
11054 | @smallexample | |
ddb50cd7 | 11055 | (@value{GDBP}) ptype foo |
ab1adacd EZ |
11056 | $1 = <incomplete type> |
11057 | @end smallexample | |
11058 | ||
11059 | @noindent | |
11060 | ``Incomplete type'' is C terminology for data types that are not | |
11061 | completely specified. | |
11062 | ||
c906108c SS |
11063 | @kindex info types |
11064 | @item info types @var{regexp} | |
11065 | @itemx info types | |
09d4efe1 EZ |
11066 | Print a brief description of all types whose names match the regular |
11067 | expression @var{regexp} (or all types in your program, if you supply | |
11068 | no argument). Each complete typename is matched as though it were a | |
11069 | complete line; thus, @samp{i type value} gives information on all | |
11070 | types in your program whose names include the string @code{value}, but | |
11071 | @samp{i type ^value$} gives information only on types whose complete | |
11072 | name is @code{value}. | |
c906108c SS |
11073 | |
11074 | This command differs from @code{ptype} in two ways: first, like | |
11075 | @code{whatis}, it does not print a detailed description; second, it | |
11076 | lists all source files where a type is defined. | |
11077 | ||
b37052ae EZ |
11078 | @kindex info scope |
11079 | @cindex local variables | |
09d4efe1 | 11080 | @item info scope @var{location} |
b37052ae | 11081 | List all the variables local to a particular scope. This command |
09d4efe1 EZ |
11082 | accepts a @var{location} argument---a function name, a source line, or |
11083 | an address preceded by a @samp{*}, and prints all the variables local | |
2a25a5ba EZ |
11084 | to the scope defined by that location. (@xref{Specify Location}, for |
11085 | details about supported forms of @var{location}.) For example: | |
b37052ae EZ |
11086 | |
11087 | @smallexample | |
11088 | (@value{GDBP}) @b{info scope command_line_handler} | |
11089 | Scope for command_line_handler: | |
11090 | Symbol rl is an argument at stack/frame offset 8, length 4. | |
11091 | Symbol linebuffer is in static storage at address 0x150a18, length 4. | |
11092 | Symbol linelength is in static storage at address 0x150a1c, length 4. | |
11093 | Symbol p is a local variable in register $esi, length 4. | |
11094 | Symbol p1 is a local variable in register $ebx, length 4. | |
11095 | Symbol nline is a local variable in register $edx, length 4. | |
11096 | Symbol repeat is a local variable at frame offset -8, length 4. | |
11097 | @end smallexample | |
11098 | ||
f5c37c66 EZ |
11099 | @noindent |
11100 | This command is especially useful for determining what data to collect | |
11101 | during a @dfn{trace experiment}, see @ref{Tracepoint Actions, | |
11102 | collect}. | |
11103 | ||
c906108c SS |
11104 | @kindex info source |
11105 | @item info source | |
919d772c JB |
11106 | Show information about the current source file---that is, the source file for |
11107 | the function containing the current point of execution: | |
11108 | @itemize @bullet | |
11109 | @item | |
11110 | the name of the source file, and the directory containing it, | |
11111 | @item | |
11112 | the directory it was compiled in, | |
11113 | @item | |
11114 | its length, in lines, | |
11115 | @item | |
11116 | which programming language it is written in, | |
11117 | @item | |
11118 | whether the executable includes debugging information for that file, and | |
11119 | if so, what format the information is in (e.g., STABS, Dwarf 2, etc.), and | |
11120 | @item | |
11121 | whether the debugging information includes information about | |
11122 | preprocessor macros. | |
11123 | @end itemize | |
11124 | ||
c906108c SS |
11125 | |
11126 | @kindex info sources | |
11127 | @item info sources | |
11128 | Print the names of all source files in your program for which there is | |
11129 | debugging information, organized into two lists: files whose symbols | |
11130 | have already been read, and files whose symbols will be read when needed. | |
11131 | ||
11132 | @kindex info functions | |
11133 | @item info functions | |
11134 | Print the names and data types of all defined functions. | |
11135 | ||
11136 | @item info functions @var{regexp} | |
11137 | Print the names and data types of all defined functions | |
11138 | whose names contain a match for regular expression @var{regexp}. | |
11139 | Thus, @samp{info fun step} finds all functions whose names | |
11140 | include @code{step}; @samp{info fun ^step} finds those whose names | |
b383017d | 11141 | start with @code{step}. If a function name contains characters |
c1468174 | 11142 | that conflict with the regular expression language (e.g.@: |
1c5dfdad | 11143 | @samp{operator*()}), they may be quoted with a backslash. |
c906108c SS |
11144 | |
11145 | @kindex info variables | |
11146 | @item info variables | |
11147 | Print the names and data types of all variables that are declared | |
6ca652b0 | 11148 | outside of functions (i.e.@: excluding local variables). |
c906108c SS |
11149 | |
11150 | @item info variables @var{regexp} | |
11151 | Print the names and data types of all variables (except for local | |
11152 | variables) whose names contain a match for regular expression | |
11153 | @var{regexp}. | |
11154 | ||
b37303ee | 11155 | @kindex info classes |
721c2651 | 11156 | @cindex Objective-C, classes and selectors |
b37303ee AF |
11157 | @item info classes |
11158 | @itemx info classes @var{regexp} | |
11159 | Display all Objective-C classes in your program, or | |
11160 | (with the @var{regexp} argument) all those matching a particular regular | |
11161 | expression. | |
11162 | ||
11163 | @kindex info selectors | |
11164 | @item info selectors | |
11165 | @itemx info selectors @var{regexp} | |
11166 | Display all Objective-C selectors in your program, or | |
11167 | (with the @var{regexp} argument) all those matching a particular regular | |
11168 | expression. | |
11169 | ||
c906108c SS |
11170 | @ignore |
11171 | This was never implemented. | |
11172 | @kindex info methods | |
11173 | @item info methods | |
11174 | @itemx info methods @var{regexp} | |
11175 | The @code{info methods} command permits the user to examine all defined | |
b37052ae EZ |
11176 | methods within C@t{++} program, or (with the @var{regexp} argument) a |
11177 | specific set of methods found in the various C@t{++} classes. Many | |
11178 | C@t{++} classes provide a large number of methods. Thus, the output | |
c906108c SS |
11179 | from the @code{ptype} command can be overwhelming and hard to use. The |
11180 | @code{info-methods} command filters the methods, printing only those | |
11181 | which match the regular-expression @var{regexp}. | |
11182 | @end ignore | |
11183 | ||
c906108c SS |
11184 | @cindex reloading symbols |
11185 | Some systems allow individual object files that make up your program to | |
7a292a7a SS |
11186 | be replaced without stopping and restarting your program. For example, |
11187 | in VxWorks you can simply recompile a defective object file and keep on | |
11188 | running. If you are running on one of these systems, you can allow | |
11189 | @value{GDBN} to reload the symbols for automatically relinked modules: | |
c906108c SS |
11190 | |
11191 | @table @code | |
11192 | @kindex set symbol-reloading | |
11193 | @item set symbol-reloading on | |
11194 | Replace symbol definitions for the corresponding source file when an | |
11195 | object file with a particular name is seen again. | |
11196 | ||
11197 | @item set symbol-reloading off | |
6d2ebf8b SS |
11198 | Do not replace symbol definitions when encountering object files of the |
11199 | same name more than once. This is the default state; if you are not | |
11200 | running on a system that permits automatic relinking of modules, you | |
11201 | should leave @code{symbol-reloading} off, since otherwise @value{GDBN} | |
11202 | may discard symbols when linking large programs, that may contain | |
11203 | several modules (from different directories or libraries) with the same | |
11204 | name. | |
c906108c SS |
11205 | |
11206 | @kindex show symbol-reloading | |
11207 | @item show symbol-reloading | |
11208 | Show the current @code{on} or @code{off} setting. | |
11209 | @end table | |
c906108c | 11210 | |
9c16f35a | 11211 | @cindex opaque data types |
c906108c SS |
11212 | @kindex set opaque-type-resolution |
11213 | @item set opaque-type-resolution on | |
11214 | Tell @value{GDBN} to resolve opaque types. An opaque type is a type | |
11215 | declared as a pointer to a @code{struct}, @code{class}, or | |
11216 | @code{union}---for example, @code{struct MyType *}---that is used in one | |
11217 | source file although the full declaration of @code{struct MyType} is in | |
11218 | another source file. The default is on. | |
11219 | ||
11220 | A change in the setting of this subcommand will not take effect until | |
11221 | the next time symbols for a file are loaded. | |
11222 | ||
11223 | @item set opaque-type-resolution off | |
11224 | Tell @value{GDBN} not to resolve opaque types. In this case, the type | |
11225 | is printed as follows: | |
11226 | @smallexample | |
11227 | @{<no data fields>@} | |
11228 | @end smallexample | |
11229 | ||
11230 | @kindex show opaque-type-resolution | |
11231 | @item show opaque-type-resolution | |
11232 | Show whether opaque types are resolved or not. | |
c906108c SS |
11233 | |
11234 | @kindex maint print symbols | |
11235 | @cindex symbol dump | |
11236 | @kindex maint print psymbols | |
11237 | @cindex partial symbol dump | |
11238 | @item maint print symbols @var{filename} | |
11239 | @itemx maint print psymbols @var{filename} | |
11240 | @itemx maint print msymbols @var{filename} | |
11241 | Write a dump of debugging symbol data into the file @var{filename}. | |
11242 | These commands are used to debug the @value{GDBN} symbol-reading code. Only | |
11243 | symbols with debugging data are included. If you use @samp{maint print | |
11244 | symbols}, @value{GDBN} includes all the symbols for which it has already | |
11245 | collected full details: that is, @var{filename} reflects symbols for | |
11246 | only those files whose symbols @value{GDBN} has read. You can use the | |
11247 | command @code{info sources} to find out which files these are. If you | |
11248 | use @samp{maint print psymbols} instead, the dump shows information about | |
11249 | symbols that @value{GDBN} only knows partially---that is, symbols defined in | |
11250 | files that @value{GDBN} has skimmed, but not yet read completely. Finally, | |
11251 | @samp{maint print msymbols} dumps just the minimal symbol information | |
11252 | required for each object file from which @value{GDBN} has read some symbols. | |
79a6e687 | 11253 | @xref{Files, ,Commands to Specify Files}, for a discussion of how |
c906108c | 11254 | @value{GDBN} reads symbols (in the description of @code{symbol-file}). |
44ea7b70 | 11255 | |
5e7b2f39 JB |
11256 | @kindex maint info symtabs |
11257 | @kindex maint info psymtabs | |
44ea7b70 JB |
11258 | @cindex listing @value{GDBN}'s internal symbol tables |
11259 | @cindex symbol tables, listing @value{GDBN}'s internal | |
11260 | @cindex full symbol tables, listing @value{GDBN}'s internal | |
11261 | @cindex partial symbol tables, listing @value{GDBN}'s internal | |
5e7b2f39 JB |
11262 | @item maint info symtabs @r{[} @var{regexp} @r{]} |
11263 | @itemx maint info psymtabs @r{[} @var{regexp} @r{]} | |
44ea7b70 JB |
11264 | |
11265 | List the @code{struct symtab} or @code{struct partial_symtab} | |
11266 | structures whose names match @var{regexp}. If @var{regexp} is not | |
11267 | given, list them all. The output includes expressions which you can | |
11268 | copy into a @value{GDBN} debugging this one to examine a particular | |
11269 | structure in more detail. For example: | |
11270 | ||
11271 | @smallexample | |
5e7b2f39 | 11272 | (@value{GDBP}) maint info psymtabs dwarf2read |
44ea7b70 JB |
11273 | @{ objfile /home/gnu/build/gdb/gdb |
11274 | ((struct objfile *) 0x82e69d0) | |
b383017d | 11275 | @{ psymtab /home/gnu/src/gdb/dwarf2read.c |
44ea7b70 JB |
11276 | ((struct partial_symtab *) 0x8474b10) |
11277 | readin no | |
11278 | fullname (null) | |
11279 | text addresses 0x814d3c8 -- 0x8158074 | |
11280 | globals (* (struct partial_symbol **) 0x8507a08 @@ 9) | |
11281 | statics (* (struct partial_symbol **) 0x40e95b78 @@ 2882) | |
11282 | dependencies (none) | |
11283 | @} | |
11284 | @} | |
5e7b2f39 | 11285 | (@value{GDBP}) maint info symtabs |
44ea7b70 JB |
11286 | (@value{GDBP}) |
11287 | @end smallexample | |
11288 | @noindent | |
11289 | We see that there is one partial symbol table whose filename contains | |
11290 | the string @samp{dwarf2read}, belonging to the @samp{gdb} executable; | |
11291 | and we see that @value{GDBN} has not read in any symtabs yet at all. | |
11292 | If we set a breakpoint on a function, that will cause @value{GDBN} to | |
11293 | read the symtab for the compilation unit containing that function: | |
11294 | ||
11295 | @smallexample | |
11296 | (@value{GDBP}) break dwarf2_psymtab_to_symtab | |
11297 | Breakpoint 1 at 0x814e5da: file /home/gnu/src/gdb/dwarf2read.c, | |
11298 | line 1574. | |
5e7b2f39 | 11299 | (@value{GDBP}) maint info symtabs |
b383017d | 11300 | @{ objfile /home/gnu/build/gdb/gdb |
44ea7b70 | 11301 | ((struct objfile *) 0x82e69d0) |
b383017d | 11302 | @{ symtab /home/gnu/src/gdb/dwarf2read.c |
44ea7b70 JB |
11303 | ((struct symtab *) 0x86c1f38) |
11304 | dirname (null) | |
11305 | fullname (null) | |
11306 | blockvector ((struct blockvector *) 0x86c1bd0) (primary) | |
1b39d5c0 | 11307 | linetable ((struct linetable *) 0x8370fa0) |
44ea7b70 JB |
11308 | debugformat DWARF 2 |
11309 | @} | |
11310 | @} | |
b383017d | 11311 | (@value{GDBP}) |
44ea7b70 | 11312 | @end smallexample |
c906108c SS |
11313 | @end table |
11314 | ||
44ea7b70 | 11315 | |
6d2ebf8b | 11316 | @node Altering |
c906108c SS |
11317 | @chapter Altering Execution |
11318 | ||
11319 | Once you think you have found an error in your program, you might want to | |
11320 | find out for certain whether correcting the apparent error would lead to | |
11321 | correct results in the rest of the run. You can find the answer by | |
11322 | experiment, using the @value{GDBN} features for altering execution of the | |
11323 | program. | |
11324 | ||
11325 | For example, you can store new values into variables or memory | |
7a292a7a SS |
11326 | locations, give your program a signal, restart it at a different |
11327 | address, or even return prematurely from a function. | |
c906108c SS |
11328 | |
11329 | @menu | |
11330 | * Assignment:: Assignment to variables | |
11331 | * Jumping:: Continuing at a different address | |
c906108c | 11332 | * Signaling:: Giving your program a signal |
c906108c SS |
11333 | * Returning:: Returning from a function |
11334 | * Calling:: Calling your program's functions | |
11335 | * Patching:: Patching your program | |
11336 | @end menu | |
11337 | ||
6d2ebf8b | 11338 | @node Assignment |
79a6e687 | 11339 | @section Assignment to Variables |
c906108c SS |
11340 | |
11341 | @cindex assignment | |
11342 | @cindex setting variables | |
11343 | To alter the value of a variable, evaluate an assignment expression. | |
11344 | @xref{Expressions, ,Expressions}. For example, | |
11345 | ||
474c8240 | 11346 | @smallexample |
c906108c | 11347 | print x=4 |
474c8240 | 11348 | @end smallexample |
c906108c SS |
11349 | |
11350 | @noindent | |
11351 | stores the value 4 into the variable @code{x}, and then prints the | |
5d161b24 | 11352 | value of the assignment expression (which is 4). |
c906108c SS |
11353 | @xref{Languages, ,Using @value{GDBN} with Different Languages}, for more |
11354 | information on operators in supported languages. | |
c906108c SS |
11355 | |
11356 | @kindex set variable | |
11357 | @cindex variables, setting | |
11358 | If you are not interested in seeing the value of the assignment, use the | |
11359 | @code{set} command instead of the @code{print} command. @code{set} is | |
11360 | really the same as @code{print} except that the expression's value is | |
11361 | not printed and is not put in the value history (@pxref{Value History, | |
79a6e687 | 11362 | ,Value History}). The expression is evaluated only for its effects. |
c906108c | 11363 | |
c906108c SS |
11364 | If the beginning of the argument string of the @code{set} command |
11365 | appears identical to a @code{set} subcommand, use the @code{set | |
11366 | variable} command instead of just @code{set}. This command is identical | |
11367 | to @code{set} except for its lack of subcommands. For example, if your | |
11368 | program has a variable @code{width}, you get an error if you try to set | |
11369 | a new value with just @samp{set width=13}, because @value{GDBN} has the | |
11370 | command @code{set width}: | |
11371 | ||
474c8240 | 11372 | @smallexample |
c906108c SS |
11373 | (@value{GDBP}) whatis width |
11374 | type = double | |
11375 | (@value{GDBP}) p width | |
11376 | $4 = 13 | |
11377 | (@value{GDBP}) set width=47 | |
11378 | Invalid syntax in expression. | |
474c8240 | 11379 | @end smallexample |
c906108c SS |
11380 | |
11381 | @noindent | |
11382 | The invalid expression, of course, is @samp{=47}. In | |
11383 | order to actually set the program's variable @code{width}, use | |
11384 | ||
474c8240 | 11385 | @smallexample |
c906108c | 11386 | (@value{GDBP}) set var width=47 |
474c8240 | 11387 | @end smallexample |
53a5351d | 11388 | |
c906108c SS |
11389 | Because the @code{set} command has many subcommands that can conflict |
11390 | with the names of program variables, it is a good idea to use the | |
11391 | @code{set variable} command instead of just @code{set}. For example, if | |
11392 | your program has a variable @code{g}, you run into problems if you try | |
11393 | to set a new value with just @samp{set g=4}, because @value{GDBN} has | |
11394 | the command @code{set gnutarget}, abbreviated @code{set g}: | |
11395 | ||
474c8240 | 11396 | @smallexample |
c906108c SS |
11397 | @group |
11398 | (@value{GDBP}) whatis g | |
11399 | type = double | |
11400 | (@value{GDBP}) p g | |
11401 | $1 = 1 | |
11402 | (@value{GDBP}) set g=4 | |
2df3850c | 11403 | (@value{GDBP}) p g |
c906108c SS |
11404 | $2 = 1 |
11405 | (@value{GDBP}) r | |
11406 | The program being debugged has been started already. | |
11407 | Start it from the beginning? (y or n) y | |
11408 | Starting program: /home/smith/cc_progs/a.out | |
6d2ebf8b SS |
11409 | "/home/smith/cc_progs/a.out": can't open to read symbols: |
11410 | Invalid bfd target. | |
c906108c SS |
11411 | (@value{GDBP}) show g |
11412 | The current BFD target is "=4". | |
11413 | @end group | |
474c8240 | 11414 | @end smallexample |
c906108c SS |
11415 | |
11416 | @noindent | |
11417 | The program variable @code{g} did not change, and you silently set the | |
11418 | @code{gnutarget} to an invalid value. In order to set the variable | |
11419 | @code{g}, use | |
11420 | ||
474c8240 | 11421 | @smallexample |
c906108c | 11422 | (@value{GDBP}) set var g=4 |
474c8240 | 11423 | @end smallexample |
c906108c SS |
11424 | |
11425 | @value{GDBN} allows more implicit conversions in assignments than C; you can | |
11426 | freely store an integer value into a pointer variable or vice versa, | |
11427 | and you can convert any structure to any other structure that is the | |
11428 | same length or shorter. | |
11429 | @comment FIXME: how do structs align/pad in these conversions? | |
11430 | @comment /doc@cygnus.com 18dec1990 | |
11431 | ||
11432 | To store values into arbitrary places in memory, use the @samp{@{@dots{}@}} | |
11433 | construct to generate a value of specified type at a specified address | |
11434 | (@pxref{Expressions, ,Expressions}). For example, @code{@{int@}0x83040} refers | |
11435 | to memory location @code{0x83040} as an integer (which implies a certain size | |
11436 | and representation in memory), and | |
11437 | ||
474c8240 | 11438 | @smallexample |
c906108c | 11439 | set @{int@}0x83040 = 4 |
474c8240 | 11440 | @end smallexample |
c906108c SS |
11441 | |
11442 | @noindent | |
11443 | stores the value 4 into that memory location. | |
11444 | ||
6d2ebf8b | 11445 | @node Jumping |
79a6e687 | 11446 | @section Continuing at a Different Address |
c906108c SS |
11447 | |
11448 | Ordinarily, when you continue your program, you do so at the place where | |
11449 | it stopped, with the @code{continue} command. You can instead continue at | |
11450 | an address of your own choosing, with the following commands: | |
11451 | ||
11452 | @table @code | |
11453 | @kindex jump | |
11454 | @item jump @var{linespec} | |
2a25a5ba EZ |
11455 | @itemx jump @var{location} |
11456 | Resume execution at line @var{linespec} or at address given by | |
11457 | @var{location}. Execution stops again immediately if there is a | |
11458 | breakpoint there. @xref{Specify Location}, for a description of the | |
11459 | different forms of @var{linespec} and @var{location}. It is common | |
11460 | practice to use the @code{tbreak} command in conjunction with | |
11461 | @code{jump}. @xref{Set Breaks, ,Setting Breakpoints}. | |
c906108c SS |
11462 | |
11463 | The @code{jump} command does not change the current stack frame, or | |
11464 | the stack pointer, or the contents of any memory location or any | |
11465 | register other than the program counter. If line @var{linespec} is in | |
11466 | a different function from the one currently executing, the results may | |
11467 | be bizarre if the two functions expect different patterns of arguments or | |
11468 | of local variables. For this reason, the @code{jump} command requests | |
11469 | confirmation if the specified line is not in the function currently | |
11470 | executing. However, even bizarre results are predictable if you are | |
11471 | well acquainted with the machine-language code of your program. | |
c906108c SS |
11472 | @end table |
11473 | ||
c906108c | 11474 | @c Doesn't work on HP-UX; have to set $pcoqh and $pcoqt. |
53a5351d JM |
11475 | On many systems, you can get much the same effect as the @code{jump} |
11476 | command by storing a new value into the register @code{$pc}. The | |
11477 | difference is that this does not start your program running; it only | |
11478 | changes the address of where it @emph{will} run when you continue. For | |
11479 | example, | |
c906108c | 11480 | |
474c8240 | 11481 | @smallexample |
c906108c | 11482 | set $pc = 0x485 |
474c8240 | 11483 | @end smallexample |
c906108c SS |
11484 | |
11485 | @noindent | |
11486 | makes the next @code{continue} command or stepping command execute at | |
11487 | address @code{0x485}, rather than at the address where your program stopped. | |
79a6e687 | 11488 | @xref{Continuing and Stepping, ,Continuing and Stepping}. |
c906108c SS |
11489 | |
11490 | The most common occasion to use the @code{jump} command is to back | |
11491 | up---perhaps with more breakpoints set---over a portion of a program | |
11492 | that has already executed, in order to examine its execution in more | |
11493 | detail. | |
11494 | ||
c906108c | 11495 | @c @group |
6d2ebf8b | 11496 | @node Signaling |
79a6e687 | 11497 | @section Giving your Program a Signal |
9c16f35a | 11498 | @cindex deliver a signal to a program |
c906108c SS |
11499 | |
11500 | @table @code | |
11501 | @kindex signal | |
11502 | @item signal @var{signal} | |
11503 | Resume execution where your program stopped, but immediately give it the | |
11504 | signal @var{signal}. @var{signal} can be the name or the number of a | |
11505 | signal. For example, on many systems @code{signal 2} and @code{signal | |
11506 | SIGINT} are both ways of sending an interrupt signal. | |
11507 | ||
11508 | Alternatively, if @var{signal} is zero, continue execution without | |
11509 | giving a signal. This is useful when your program stopped on account of | |
11510 | a signal and would ordinary see the signal when resumed with the | |
11511 | @code{continue} command; @samp{signal 0} causes it to resume without a | |
11512 | signal. | |
11513 | ||
11514 | @code{signal} does not repeat when you press @key{RET} a second time | |
11515 | after executing the command. | |
11516 | @end table | |
11517 | @c @end group | |
11518 | ||
11519 | Invoking the @code{signal} command is not the same as invoking the | |
11520 | @code{kill} utility from the shell. Sending a signal with @code{kill} | |
11521 | causes @value{GDBN} to decide what to do with the signal depending on | |
11522 | the signal handling tables (@pxref{Signals}). The @code{signal} command | |
11523 | passes the signal directly to your program. | |
11524 | ||
c906108c | 11525 | |
6d2ebf8b | 11526 | @node Returning |
79a6e687 | 11527 | @section Returning from a Function |
c906108c SS |
11528 | |
11529 | @table @code | |
11530 | @cindex returning from a function | |
11531 | @kindex return | |
11532 | @item return | |
11533 | @itemx return @var{expression} | |
11534 | You can cancel execution of a function call with the @code{return} | |
11535 | command. If you give an | |
11536 | @var{expression} argument, its value is used as the function's return | |
11537 | value. | |
11538 | @end table | |
11539 | ||
11540 | When you use @code{return}, @value{GDBN} discards the selected stack frame | |
11541 | (and all frames within it). You can think of this as making the | |
11542 | discarded frame return prematurely. If you wish to specify a value to | |
11543 | be returned, give that value as the argument to @code{return}. | |
11544 | ||
11545 | This pops the selected stack frame (@pxref{Selection, ,Selecting a | |
79a6e687 | 11546 | Frame}), and any other frames inside of it, leaving its caller as the |
c906108c SS |
11547 | innermost remaining frame. That frame becomes selected. The |
11548 | specified value is stored in the registers used for returning values | |
11549 | of functions. | |
11550 | ||
11551 | The @code{return} command does not resume execution; it leaves the | |
11552 | program stopped in the state that would exist if the function had just | |
11553 | returned. In contrast, the @code{finish} command (@pxref{Continuing | |
79a6e687 | 11554 | and Stepping, ,Continuing and Stepping}) resumes execution until the |
c906108c SS |
11555 | selected stack frame returns naturally. |
11556 | ||
6d2ebf8b | 11557 | @node Calling |
79a6e687 | 11558 | @section Calling Program Functions |
c906108c | 11559 | |
f8568604 | 11560 | @table @code |
c906108c | 11561 | @cindex calling functions |
f8568604 EZ |
11562 | @cindex inferior functions, calling |
11563 | @item print @var{expr} | |
d3e8051b | 11564 | Evaluate the expression @var{expr} and display the resulting value. |
f8568604 EZ |
11565 | @var{expr} may include calls to functions in the program being |
11566 | debugged. | |
11567 | ||
c906108c | 11568 | @kindex call |
c906108c SS |
11569 | @item call @var{expr} |
11570 | Evaluate the expression @var{expr} without displaying @code{void} | |
11571 | returned values. | |
c906108c SS |
11572 | |
11573 | You can use this variant of the @code{print} command if you want to | |
f8568604 EZ |
11574 | execute a function from your program that does not return anything |
11575 | (a.k.a.@: @dfn{a void function}), but without cluttering the output | |
11576 | with @code{void} returned values that @value{GDBN} will otherwise | |
11577 | print. If the result is not void, it is printed and saved in the | |
11578 | value history. | |
11579 | @end table | |
11580 | ||
9c16f35a EZ |
11581 | It is possible for the function you call via the @code{print} or |
11582 | @code{call} command to generate a signal (e.g., if there's a bug in | |
11583 | the function, or if you passed it incorrect arguments). What happens | |
11584 | in that case is controlled by the @code{set unwindonsignal} command. | |
11585 | ||
11586 | @table @code | |
11587 | @item set unwindonsignal | |
11588 | @kindex set unwindonsignal | |
11589 | @cindex unwind stack in called functions | |
11590 | @cindex call dummy stack unwinding | |
11591 | Set unwinding of the stack if a signal is received while in a function | |
11592 | that @value{GDBN} called in the program being debugged. If set to on, | |
11593 | @value{GDBN} unwinds the stack it created for the call and restores | |
11594 | the context to what it was before the call. If set to off (the | |
11595 | default), @value{GDBN} stops in the frame where the signal was | |
11596 | received. | |
11597 | ||
11598 | @item show unwindonsignal | |
11599 | @kindex show unwindonsignal | |
11600 | Show the current setting of stack unwinding in the functions called by | |
11601 | @value{GDBN}. | |
11602 | @end table | |
11603 | ||
f8568604 EZ |
11604 | @cindex weak alias functions |
11605 | Sometimes, a function you wish to call is actually a @dfn{weak alias} | |
11606 | for another function. In such case, @value{GDBN} might not pick up | |
11607 | the type information, including the types of the function arguments, | |
11608 | which causes @value{GDBN} to call the inferior function incorrectly. | |
11609 | As a result, the called function will function erroneously and may | |
11610 | even crash. A solution to that is to use the name of the aliased | |
11611 | function instead. | |
c906108c | 11612 | |
6d2ebf8b | 11613 | @node Patching |
79a6e687 | 11614 | @section Patching Programs |
7a292a7a | 11615 | |
c906108c SS |
11616 | @cindex patching binaries |
11617 | @cindex writing into executables | |
c906108c | 11618 | @cindex writing into corefiles |
c906108c | 11619 | |
7a292a7a SS |
11620 | By default, @value{GDBN} opens the file containing your program's |
11621 | executable code (or the corefile) read-only. This prevents accidental | |
11622 | alterations to machine code; but it also prevents you from intentionally | |
11623 | patching your program's binary. | |
c906108c SS |
11624 | |
11625 | If you'd like to be able to patch the binary, you can specify that | |
11626 | explicitly with the @code{set write} command. For example, you might | |
11627 | want to turn on internal debugging flags, or even to make emergency | |
11628 | repairs. | |
11629 | ||
11630 | @table @code | |
11631 | @kindex set write | |
11632 | @item set write on | |
11633 | @itemx set write off | |
7a292a7a SS |
11634 | If you specify @samp{set write on}, @value{GDBN} opens executable and |
11635 | core files for both reading and writing; if you specify @samp{set write | |
c906108c SS |
11636 | off} (the default), @value{GDBN} opens them read-only. |
11637 | ||
11638 | If you have already loaded a file, you must load it again (using the | |
7a292a7a SS |
11639 | @code{exec-file} or @code{core-file} command) after changing @code{set |
11640 | write}, for your new setting to take effect. | |
c906108c SS |
11641 | |
11642 | @item show write | |
11643 | @kindex show write | |
7a292a7a SS |
11644 | Display whether executable files and core files are opened for writing |
11645 | as well as reading. | |
c906108c SS |
11646 | @end table |
11647 | ||
6d2ebf8b | 11648 | @node GDB Files |
c906108c SS |
11649 | @chapter @value{GDBN} Files |
11650 | ||
7a292a7a SS |
11651 | @value{GDBN} needs to know the file name of the program to be debugged, |
11652 | both in order to read its symbol table and in order to start your | |
11653 | program. To debug a core dump of a previous run, you must also tell | |
11654 | @value{GDBN} the name of the core dump file. | |
c906108c SS |
11655 | |
11656 | @menu | |
11657 | * Files:: Commands to specify files | |
5b5d99cf | 11658 | * Separate Debug Files:: Debugging information in separate files |
c906108c SS |
11659 | * Symbol Errors:: Errors reading symbol files |
11660 | @end menu | |
11661 | ||
6d2ebf8b | 11662 | @node Files |
79a6e687 | 11663 | @section Commands to Specify Files |
c906108c | 11664 | |
7a292a7a | 11665 | @cindex symbol table |
c906108c | 11666 | @cindex core dump file |
7a292a7a SS |
11667 | |
11668 | You may want to specify executable and core dump file names. The usual | |
11669 | way to do this is at start-up time, using the arguments to | |
11670 | @value{GDBN}'s start-up commands (@pxref{Invocation, , Getting In and | |
11671 | Out of @value{GDBN}}). | |
c906108c SS |
11672 | |
11673 | Occasionally it is necessary to change to a different file during a | |
397ca115 EZ |
11674 | @value{GDBN} session. Or you may run @value{GDBN} and forget to |
11675 | specify a file you want to use. Or you are debugging a remote target | |
79a6e687 BW |
11676 | via @code{gdbserver} (@pxref{Server, file, Using the @code{gdbserver} |
11677 | Program}). In these situations the @value{GDBN} commands to specify | |
0869d01b | 11678 | new files are useful. |
c906108c SS |
11679 | |
11680 | @table @code | |
11681 | @cindex executable file | |
11682 | @kindex file | |
11683 | @item file @var{filename} | |
11684 | Use @var{filename} as the program to be debugged. It is read for its | |
11685 | symbols and for the contents of pure memory. It is also the program | |
11686 | executed when you use the @code{run} command. If you do not specify a | |
5d161b24 DB |
11687 | directory and the file is not found in the @value{GDBN} working directory, |
11688 | @value{GDBN} uses the environment variable @code{PATH} as a list of | |
11689 | directories to search, just as the shell does when looking for a program | |
11690 | to run. You can change the value of this variable, for both @value{GDBN} | |
c906108c SS |
11691 | and your program, using the @code{path} command. |
11692 | ||
fc8be69e EZ |
11693 | @cindex unlinked object files |
11694 | @cindex patching object files | |
11695 | You can load unlinked object @file{.o} files into @value{GDBN} using | |
11696 | the @code{file} command. You will not be able to ``run'' an object | |
11697 | file, but you can disassemble functions and inspect variables. Also, | |
11698 | if the underlying BFD functionality supports it, you could use | |
11699 | @kbd{gdb -write} to patch object files using this technique. Note | |
11700 | that @value{GDBN} can neither interpret nor modify relocations in this | |
11701 | case, so branches and some initialized variables will appear to go to | |
11702 | the wrong place. But this feature is still handy from time to time. | |
11703 | ||
c906108c SS |
11704 | @item file |
11705 | @code{file} with no argument makes @value{GDBN} discard any information it | |
11706 | has on both executable file and the symbol table. | |
11707 | ||
11708 | @kindex exec-file | |
11709 | @item exec-file @r{[} @var{filename} @r{]} | |
11710 | Specify that the program to be run (but not the symbol table) is found | |
11711 | in @var{filename}. @value{GDBN} searches the environment variable @code{PATH} | |
11712 | if necessary to locate your program. Omitting @var{filename} means to | |
11713 | discard information on the executable file. | |
11714 | ||
11715 | @kindex symbol-file | |
11716 | @item symbol-file @r{[} @var{filename} @r{]} | |
11717 | Read symbol table information from file @var{filename}. @code{PATH} is | |
11718 | searched when necessary. Use the @code{file} command to get both symbol | |
11719 | table and program to run from the same file. | |
11720 | ||
11721 | @code{symbol-file} with no argument clears out @value{GDBN} information on your | |
11722 | program's symbol table. | |
11723 | ||
ae5a43e0 DJ |
11724 | The @code{symbol-file} command causes @value{GDBN} to forget the contents of |
11725 | some breakpoints and auto-display expressions. This is because they may | |
11726 | contain pointers to the internal data recording symbols and data types, | |
11727 | which are part of the old symbol table data being discarded inside | |
11728 | @value{GDBN}. | |
c906108c SS |
11729 | |
11730 | @code{symbol-file} does not repeat if you press @key{RET} again after | |
11731 | executing it once. | |
11732 | ||
11733 | When @value{GDBN} is configured for a particular environment, it | |
11734 | understands debugging information in whatever format is the standard | |
11735 | generated for that environment; you may use either a @sc{gnu} compiler, or | |
11736 | other compilers that adhere to the local conventions. | |
c906108c | 11737 | Best results are usually obtained from @sc{gnu} compilers; for example, |
e22ea452 | 11738 | using @code{@value{NGCC}} you can generate debugging information for |
c906108c | 11739 | optimized code. |
c906108c SS |
11740 | |
11741 | For most kinds of object files, with the exception of old SVR3 systems | |
11742 | using COFF, the @code{symbol-file} command does not normally read the | |
11743 | symbol table in full right away. Instead, it scans the symbol table | |
11744 | quickly to find which source files and which symbols are present. The | |
11745 | details are read later, one source file at a time, as they are needed. | |
11746 | ||
11747 | The purpose of this two-stage reading strategy is to make @value{GDBN} | |
11748 | start up faster. For the most part, it is invisible except for | |
11749 | occasional pauses while the symbol table details for a particular source | |
11750 | file are being read. (The @code{set verbose} command can turn these | |
11751 | pauses into messages if desired. @xref{Messages/Warnings, ,Optional | |
79a6e687 | 11752 | Warnings and Messages}.) |
c906108c | 11753 | |
c906108c SS |
11754 | We have not implemented the two-stage strategy for COFF yet. When the |
11755 | symbol table is stored in COFF format, @code{symbol-file} reads the | |
11756 | symbol table data in full right away. Note that ``stabs-in-COFF'' | |
11757 | still does the two-stage strategy, since the debug info is actually | |
11758 | in stabs format. | |
11759 | ||
11760 | @kindex readnow | |
11761 | @cindex reading symbols immediately | |
11762 | @cindex symbols, reading immediately | |
a94ab193 EZ |
11763 | @item symbol-file @var{filename} @r{[} -readnow @r{]} |
11764 | @itemx file @var{filename} @r{[} -readnow @r{]} | |
c906108c SS |
11765 | You can override the @value{GDBN} two-stage strategy for reading symbol |
11766 | tables by using the @samp{-readnow} option with any of the commands that | |
11767 | load symbol table information, if you want to be sure @value{GDBN} has the | |
5d161b24 | 11768 | entire symbol table available. |
c906108c | 11769 | |
c906108c SS |
11770 | @c FIXME: for now no mention of directories, since this seems to be in |
11771 | @c flux. 13mar1992 status is that in theory GDB would look either in | |
11772 | @c current dir or in same dir as myprog; but issues like competing | |
11773 | @c GDB's, or clutter in system dirs, mean that in practice right now | |
11774 | @c only current dir is used. FFish says maybe a special GDB hierarchy | |
11775 | @c (eg rooted in val of env var GDBSYMS) could exist for mappable symbol | |
11776 | @c files. | |
11777 | ||
c906108c | 11778 | @kindex core-file |
09d4efe1 | 11779 | @item core-file @r{[}@var{filename}@r{]} |
4644b6e3 | 11780 | @itemx core |
c906108c SS |
11781 | Specify the whereabouts of a core dump file to be used as the ``contents |
11782 | of memory''. Traditionally, core files contain only some parts of the | |
11783 | address space of the process that generated them; @value{GDBN} can access the | |
11784 | executable file itself for other parts. | |
11785 | ||
11786 | @code{core-file} with no argument specifies that no core file is | |
11787 | to be used. | |
11788 | ||
11789 | Note that the core file is ignored when your program is actually running | |
7a292a7a SS |
11790 | under @value{GDBN}. So, if you have been running your program and you |
11791 | wish to debug a core file instead, you must kill the subprocess in which | |
11792 | the program is running. To do this, use the @code{kill} command | |
79a6e687 | 11793 | (@pxref{Kill Process, ,Killing the Child Process}). |
c906108c | 11794 | |
c906108c SS |
11795 | @kindex add-symbol-file |
11796 | @cindex dynamic linking | |
11797 | @item add-symbol-file @var{filename} @var{address} | |
a94ab193 | 11798 | @itemx add-symbol-file @var{filename} @var{address} @r{[} -readnow @r{]} |
17d9d558 | 11799 | @itemx add-symbol-file @var{filename} @r{-s}@var{section} @var{address} @dots{} |
96a2c332 SS |
11800 | The @code{add-symbol-file} command reads additional symbol table |
11801 | information from the file @var{filename}. You would use this command | |
11802 | when @var{filename} has been dynamically loaded (by some other means) | |
11803 | into the program that is running. @var{address} should be the memory | |
11804 | address at which the file has been loaded; @value{GDBN} cannot figure | |
d167840f EZ |
11805 | this out for itself. You can additionally specify an arbitrary number |
11806 | of @samp{@r{-s}@var{section} @var{address}} pairs, to give an explicit | |
11807 | section name and base address for that section. You can specify any | |
11808 | @var{address} as an expression. | |
c906108c SS |
11809 | |
11810 | The symbol table of the file @var{filename} is added to the symbol table | |
11811 | originally read with the @code{symbol-file} command. You can use the | |
96a2c332 SS |
11812 | @code{add-symbol-file} command any number of times; the new symbol data |
11813 | thus read keeps adding to the old. To discard all old symbol data | |
11814 | instead, use the @code{symbol-file} command without any arguments. | |
c906108c | 11815 | |
17d9d558 JB |
11816 | @cindex relocatable object files, reading symbols from |
11817 | @cindex object files, relocatable, reading symbols from | |
11818 | @cindex reading symbols from relocatable object files | |
11819 | @cindex symbols, reading from relocatable object files | |
11820 | @cindex @file{.o} files, reading symbols from | |
11821 | Although @var{filename} is typically a shared library file, an | |
11822 | executable file, or some other object file which has been fully | |
11823 | relocated for loading into a process, you can also load symbolic | |
11824 | information from relocatable @file{.o} files, as long as: | |
11825 | ||
11826 | @itemize @bullet | |
11827 | @item | |
11828 | the file's symbolic information refers only to linker symbols defined in | |
11829 | that file, not to symbols defined by other object files, | |
11830 | @item | |
11831 | every section the file's symbolic information refers to has actually | |
11832 | been loaded into the inferior, as it appears in the file, and | |
11833 | @item | |
11834 | you can determine the address at which every section was loaded, and | |
11835 | provide these to the @code{add-symbol-file} command. | |
11836 | @end itemize | |
11837 | ||
11838 | @noindent | |
11839 | Some embedded operating systems, like Sun Chorus and VxWorks, can load | |
11840 | relocatable files into an already running program; such systems | |
11841 | typically make the requirements above easy to meet. However, it's | |
11842 | important to recognize that many native systems use complex link | |
49efadf5 | 11843 | procedures (@code{.linkonce} section factoring and C@t{++} constructor table |
17d9d558 JB |
11844 | assembly, for example) that make the requirements difficult to meet. In |
11845 | general, one cannot assume that using @code{add-symbol-file} to read a | |
11846 | relocatable object file's symbolic information will have the same effect | |
11847 | as linking the relocatable object file into the program in the normal | |
11848 | way. | |
11849 | ||
c906108c SS |
11850 | @code{add-symbol-file} does not repeat if you press @key{RET} after using it. |
11851 | ||
c45da7e6 EZ |
11852 | @kindex add-symbol-file-from-memory |
11853 | @cindex @code{syscall DSO} | |
11854 | @cindex load symbols from memory | |
11855 | @item add-symbol-file-from-memory @var{address} | |
11856 | Load symbols from the given @var{address} in a dynamically loaded | |
11857 | object file whose image is mapped directly into the inferior's memory. | |
11858 | For example, the Linux kernel maps a @code{syscall DSO} into each | |
11859 | process's address space; this DSO provides kernel-specific code for | |
11860 | some system calls. The argument can be any expression whose | |
11861 | evaluation yields the address of the file's shared object file header. | |
11862 | For this command to work, you must have used @code{symbol-file} or | |
11863 | @code{exec-file} commands in advance. | |
11864 | ||
09d4efe1 EZ |
11865 | @kindex add-shared-symbol-files |
11866 | @kindex assf | |
11867 | @item add-shared-symbol-files @var{library-file} | |
11868 | @itemx assf @var{library-file} | |
11869 | The @code{add-shared-symbol-files} command can currently be used only | |
11870 | in the Cygwin build of @value{GDBN} on MS-Windows OS, where it is an | |
11871 | alias for the @code{dll-symbols} command (@pxref{Cygwin Native}). | |
11872 | @value{GDBN} automatically looks for shared libraries, however if | |
11873 | @value{GDBN} does not find yours, you can invoke | |
11874 | @code{add-shared-symbol-files}. It takes one argument: the shared | |
11875 | library's file name. @code{assf} is a shorthand alias for | |
11876 | @code{add-shared-symbol-files}. | |
c906108c | 11877 | |
c906108c | 11878 | @kindex section |
09d4efe1 EZ |
11879 | @item section @var{section} @var{addr} |
11880 | The @code{section} command changes the base address of the named | |
11881 | @var{section} of the exec file to @var{addr}. This can be used if the | |
11882 | exec file does not contain section addresses, (such as in the | |
11883 | @code{a.out} format), or when the addresses specified in the file | |
11884 | itself are wrong. Each section must be changed separately. The | |
11885 | @code{info files} command, described below, lists all the sections and | |
11886 | their addresses. | |
c906108c SS |
11887 | |
11888 | @kindex info files | |
11889 | @kindex info target | |
11890 | @item info files | |
11891 | @itemx info target | |
7a292a7a SS |
11892 | @code{info files} and @code{info target} are synonymous; both print the |
11893 | current target (@pxref{Targets, ,Specifying a Debugging Target}), | |
11894 | including the names of the executable and core dump files currently in | |
11895 | use by @value{GDBN}, and the files from which symbols were loaded. The | |
11896 | command @code{help target} lists all possible targets rather than | |
11897 | current ones. | |
11898 | ||
fe95c787 MS |
11899 | @kindex maint info sections |
11900 | @item maint info sections | |
11901 | Another command that can give you extra information about program sections | |
11902 | is @code{maint info sections}. In addition to the section information | |
11903 | displayed by @code{info files}, this command displays the flags and file | |
11904 | offset of each section in the executable and core dump files. In addition, | |
11905 | @code{maint info sections} provides the following command options (which | |
11906 | may be arbitrarily combined): | |
11907 | ||
11908 | @table @code | |
11909 | @item ALLOBJ | |
11910 | Display sections for all loaded object files, including shared libraries. | |
11911 | @item @var{sections} | |
6600abed | 11912 | Display info only for named @var{sections}. |
fe95c787 MS |
11913 | @item @var{section-flags} |
11914 | Display info only for sections for which @var{section-flags} are true. | |
11915 | The section flags that @value{GDBN} currently knows about are: | |
11916 | @table @code | |
11917 | @item ALLOC | |
11918 | Section will have space allocated in the process when loaded. | |
11919 | Set for all sections except those containing debug information. | |
11920 | @item LOAD | |
11921 | Section will be loaded from the file into the child process memory. | |
11922 | Set for pre-initialized code and data, clear for @code{.bss} sections. | |
11923 | @item RELOC | |
11924 | Section needs to be relocated before loading. | |
11925 | @item READONLY | |
11926 | Section cannot be modified by the child process. | |
11927 | @item CODE | |
11928 | Section contains executable code only. | |
6600abed | 11929 | @item DATA |
fe95c787 MS |
11930 | Section contains data only (no executable code). |
11931 | @item ROM | |
11932 | Section will reside in ROM. | |
11933 | @item CONSTRUCTOR | |
11934 | Section contains data for constructor/destructor lists. | |
11935 | @item HAS_CONTENTS | |
11936 | Section is not empty. | |
11937 | @item NEVER_LOAD | |
11938 | An instruction to the linker to not output the section. | |
11939 | @item COFF_SHARED_LIBRARY | |
11940 | A notification to the linker that the section contains | |
11941 | COFF shared library information. | |
11942 | @item IS_COMMON | |
11943 | Section contains common symbols. | |
11944 | @end table | |
11945 | @end table | |
6763aef9 | 11946 | @kindex set trust-readonly-sections |
9c16f35a | 11947 | @cindex read-only sections |
6763aef9 MS |
11948 | @item set trust-readonly-sections on |
11949 | Tell @value{GDBN} that readonly sections in your object file | |
6ca652b0 | 11950 | really are read-only (i.e.@: that their contents will not change). |
6763aef9 MS |
11951 | In that case, @value{GDBN} can fetch values from these sections |
11952 | out of the object file, rather than from the target program. | |
11953 | For some targets (notably embedded ones), this can be a significant | |
11954 | enhancement to debugging performance. | |
11955 | ||
11956 | The default is off. | |
11957 | ||
11958 | @item set trust-readonly-sections off | |
15110bc3 | 11959 | Tell @value{GDBN} not to trust readonly sections. This means that |
6763aef9 MS |
11960 | the contents of the section might change while the program is running, |
11961 | and must therefore be fetched from the target when needed. | |
9c16f35a EZ |
11962 | |
11963 | @item show trust-readonly-sections | |
11964 | Show the current setting of trusting readonly sections. | |
c906108c SS |
11965 | @end table |
11966 | ||
11967 | All file-specifying commands allow both absolute and relative file names | |
11968 | as arguments. @value{GDBN} always converts the file name to an absolute file | |
11969 | name and remembers it that way. | |
11970 | ||
c906108c | 11971 | @cindex shared libraries |
9cceb671 DJ |
11972 | @anchor{Shared Libraries} |
11973 | @value{GDBN} supports @sc{gnu}/Linux, MS-Windows, HP-UX, SunOS, SVr4, Irix, | |
9c16f35a | 11974 | and IBM RS/6000 AIX shared libraries. |
53a5351d | 11975 | |
9cceb671 DJ |
11976 | On MS-Windows @value{GDBN} must be linked with the Expat library to support |
11977 | shared libraries. @xref{Expat}. | |
11978 | ||
c906108c SS |
11979 | @value{GDBN} automatically loads symbol definitions from shared libraries |
11980 | when you use the @code{run} command, or when you examine a core file. | |
11981 | (Before you issue the @code{run} command, @value{GDBN} does not understand | |
11982 | references to a function in a shared library, however---unless you are | |
11983 | debugging a core file). | |
53a5351d JM |
11984 | |
11985 | On HP-UX, if the program loads a library explicitly, @value{GDBN} | |
11986 | automatically loads the symbols at the time of the @code{shl_load} call. | |
11987 | ||
c906108c SS |
11988 | @c FIXME: some @value{GDBN} release may permit some refs to undef |
11989 | @c FIXME...symbols---eg in a break cmd---assuming they are from a shared | |
11990 | @c FIXME...lib; check this from time to time when updating manual | |
11991 | ||
b7209cb4 FF |
11992 | There are times, however, when you may wish to not automatically load |
11993 | symbol definitions from shared libraries, such as when they are | |
11994 | particularly large or there are many of them. | |
11995 | ||
11996 | To control the automatic loading of shared library symbols, use the | |
11997 | commands: | |
11998 | ||
11999 | @table @code | |
12000 | @kindex set auto-solib-add | |
12001 | @item set auto-solib-add @var{mode} | |
12002 | If @var{mode} is @code{on}, symbols from all shared object libraries | |
12003 | will be loaded automatically when the inferior begins execution, you | |
12004 | attach to an independently started inferior, or when the dynamic linker | |
12005 | informs @value{GDBN} that a new library has been loaded. If @var{mode} | |
12006 | is @code{off}, symbols must be loaded manually, using the | |
12007 | @code{sharedlibrary} command. The default value is @code{on}. | |
12008 | ||
dcaf7c2c EZ |
12009 | @cindex memory used for symbol tables |
12010 | If your program uses lots of shared libraries with debug info that | |
12011 | takes large amounts of memory, you can decrease the @value{GDBN} | |
12012 | memory footprint by preventing it from automatically loading the | |
12013 | symbols from shared libraries. To that end, type @kbd{set | |
12014 | auto-solib-add off} before running the inferior, then load each | |
12015 | library whose debug symbols you do need with @kbd{sharedlibrary | |
d3e8051b | 12016 | @var{regexp}}, where @var{regexp} is a regular expression that matches |
dcaf7c2c EZ |
12017 | the libraries whose symbols you want to be loaded. |
12018 | ||
b7209cb4 FF |
12019 | @kindex show auto-solib-add |
12020 | @item show auto-solib-add | |
12021 | Display the current autoloading mode. | |
12022 | @end table | |
12023 | ||
c45da7e6 | 12024 | @cindex load shared library |
b7209cb4 FF |
12025 | To explicitly load shared library symbols, use the @code{sharedlibrary} |
12026 | command: | |
12027 | ||
c906108c SS |
12028 | @table @code |
12029 | @kindex info sharedlibrary | |
12030 | @kindex info share | |
12031 | @item info share | |
12032 | @itemx info sharedlibrary | |
12033 | Print the names of the shared libraries which are currently loaded. | |
12034 | ||
12035 | @kindex sharedlibrary | |
12036 | @kindex share | |
12037 | @item sharedlibrary @var{regex} | |
12038 | @itemx share @var{regex} | |
c906108c SS |
12039 | Load shared object library symbols for files matching a |
12040 | Unix regular expression. | |
12041 | As with files loaded automatically, it only loads shared libraries | |
12042 | required by your program for a core file or after typing @code{run}. If | |
12043 | @var{regex} is omitted all shared libraries required by your program are | |
12044 | loaded. | |
c45da7e6 EZ |
12045 | |
12046 | @item nosharedlibrary | |
12047 | @kindex nosharedlibrary | |
12048 | @cindex unload symbols from shared libraries | |
12049 | Unload all shared object library symbols. This discards all symbols | |
12050 | that have been loaded from all shared libraries. Symbols from shared | |
12051 | libraries that were loaded by explicit user requests are not | |
12052 | discarded. | |
c906108c SS |
12053 | @end table |
12054 | ||
721c2651 EZ |
12055 | Sometimes you may wish that @value{GDBN} stops and gives you control |
12056 | when any of shared library events happen. Use the @code{set | |
12057 | stop-on-solib-events} command for this: | |
12058 | ||
12059 | @table @code | |
12060 | @item set stop-on-solib-events | |
12061 | @kindex set stop-on-solib-events | |
12062 | This command controls whether @value{GDBN} should give you control | |
12063 | when the dynamic linker notifies it about some shared library event. | |
12064 | The most common event of interest is loading or unloading of a new | |
12065 | shared library. | |
12066 | ||
12067 | @item show stop-on-solib-events | |
12068 | @kindex show stop-on-solib-events | |
12069 | Show whether @value{GDBN} stops and gives you control when shared | |
12070 | library events happen. | |
12071 | @end table | |
12072 | ||
f5ebfba0 DJ |
12073 | Shared libraries are also supported in many cross or remote debugging |
12074 | configurations. A copy of the target's libraries need to be present on the | |
12075 | host system; they need to be the same as the target libraries, although the | |
12076 | copies on the target can be stripped as long as the copies on the host are | |
12077 | not. | |
12078 | ||
59b7b46f EZ |
12079 | @cindex where to look for shared libraries |
12080 | For remote debugging, you need to tell @value{GDBN} where the target | |
12081 | libraries are, so that it can load the correct copies---otherwise, it | |
12082 | may try to load the host's libraries. @value{GDBN} has two variables | |
12083 | to specify the search directories for target libraries. | |
f5ebfba0 DJ |
12084 | |
12085 | @table @code | |
59b7b46f | 12086 | @cindex prefix for shared library file names |
f822c95b | 12087 | @cindex system root, alternate |
f5ebfba0 | 12088 | @kindex set solib-absolute-prefix |
f822c95b DJ |
12089 | @kindex set sysroot |
12090 | @item set sysroot @var{path} | |
12091 | Use @var{path} as the system root for the program being debugged. Any | |
12092 | absolute shared library paths will be prefixed with @var{path}; many | |
12093 | runtime loaders store the absolute paths to the shared library in the | |
12094 | target program's memory. If you use @code{set sysroot} to find shared | |
12095 | libraries, they need to be laid out in the same way that they are on | |
12096 | the target, with e.g.@: a @file{/lib} and @file{/usr/lib} hierarchy | |
12097 | under @var{path}. | |
12098 | ||
12099 | The @code{set solib-absolute-prefix} command is an alias for @code{set | |
12100 | sysroot}. | |
12101 | ||
12102 | @cindex default system root | |
59b7b46f | 12103 | @cindex @samp{--with-sysroot} |
f822c95b DJ |
12104 | You can set the default system root by using the configure-time |
12105 | @samp{--with-sysroot} option. If the system root is inside | |
12106 | @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or | |
12107 | @samp{--exec-prefix}), then the default system root will be updated | |
12108 | automatically if the installed @value{GDBN} is moved to a new | |
12109 | location. | |
12110 | ||
12111 | @kindex show sysroot | |
12112 | @item show sysroot | |
f5ebfba0 DJ |
12113 | Display the current shared library prefix. |
12114 | ||
12115 | @kindex set solib-search-path | |
12116 | @item set solib-search-path @var{path} | |
f822c95b DJ |
12117 | If this variable is set, @var{path} is a colon-separated list of |
12118 | directories to search for shared libraries. @samp{solib-search-path} | |
12119 | is used after @samp{sysroot} fails to locate the library, or if the | |
12120 | path to the library is relative instead of absolute. If you want to | |
12121 | use @samp{solib-search-path} instead of @samp{sysroot}, be sure to set | |
d3e8051b | 12122 | @samp{sysroot} to a nonexistent directory to prevent @value{GDBN} from |
f822c95b | 12123 | finding your host's libraries. @samp{sysroot} is preferred; setting |
d3e8051b | 12124 | it to a nonexistent directory may interfere with automatic loading |
f822c95b | 12125 | of shared library symbols. |
f5ebfba0 DJ |
12126 | |
12127 | @kindex show solib-search-path | |
12128 | @item show solib-search-path | |
12129 | Display the current shared library search path. | |
12130 | @end table | |
12131 | ||
5b5d99cf JB |
12132 | |
12133 | @node Separate Debug Files | |
12134 | @section Debugging Information in Separate Files | |
12135 | @cindex separate debugging information files | |
12136 | @cindex debugging information in separate files | |
12137 | @cindex @file{.debug} subdirectories | |
12138 | @cindex debugging information directory, global | |
12139 | @cindex global debugging information directory | |
c7e83d54 EZ |
12140 | @cindex build ID, and separate debugging files |
12141 | @cindex @file{.build-id} directory | |
5b5d99cf JB |
12142 | |
12143 | @value{GDBN} allows you to put a program's debugging information in a | |
12144 | file separate from the executable itself, in a way that allows | |
12145 | @value{GDBN} to find and load the debugging information automatically. | |
c7e83d54 EZ |
12146 | Since debugging information can be very large---sometimes larger |
12147 | than the executable code itself---some systems distribute debugging | |
5b5d99cf JB |
12148 | information for their executables in separate files, which users can |
12149 | install only when they need to debug a problem. | |
12150 | ||
c7e83d54 EZ |
12151 | @value{GDBN} supports two ways of specifying the separate debug info |
12152 | file: | |
5b5d99cf JB |
12153 | |
12154 | @itemize @bullet | |
12155 | @item | |
c7e83d54 EZ |
12156 | The executable contains a @dfn{debug link} that specifies the name of |
12157 | the separate debug info file. The separate debug file's name is | |
12158 | usually @file{@var{executable}.debug}, where @var{executable} is the | |
12159 | name of the corresponding executable file without leading directories | |
12160 | (e.g., @file{ls.debug} for @file{/usr/bin/ls}). In addition, the | |
12161 | debug link specifies a CRC32 checksum for the debug file, which | |
12162 | @value{GDBN} uses to validate that the executable and the debug file | |
12163 | came from the same build. | |
12164 | ||
12165 | @item | |
7e27a47a | 12166 | The executable contains a @dfn{build ID}, a unique bit string that is |
c7e83d54 | 12167 | also present in the corresponding debug info file. (This is supported |
7e27a47a EZ |
12168 | only on some operating systems, notably those which use the ELF format |
12169 | for binary files and the @sc{gnu} Binutils.) For more details about | |
12170 | this feature, see the description of the @option{--build-id} | |
12171 | command-line option in @ref{Options, , Command Line Options, ld.info, | |
12172 | The GNU Linker}. The debug info file's name is not specified | |
12173 | explicitly by the build ID, but can be computed from the build ID, see | |
12174 | below. | |
d3750b24 JK |
12175 | @end itemize |
12176 | ||
c7e83d54 EZ |
12177 | Depending on the way the debug info file is specified, @value{GDBN} |
12178 | uses two different methods of looking for the debug file: | |
d3750b24 JK |
12179 | |
12180 | @itemize @bullet | |
12181 | @item | |
c7e83d54 EZ |
12182 | For the ``debug link'' method, @value{GDBN} looks up the named file in |
12183 | the directory of the executable file, then in a subdirectory of that | |
12184 | directory named @file{.debug}, and finally under the global debug | |
12185 | directory, in a subdirectory whose name is identical to the leading | |
12186 | directories of the executable's absolute file name. | |
12187 | ||
12188 | @item | |
83f83d7f | 12189 | For the ``build ID'' method, @value{GDBN} looks in the |
c7e83d54 EZ |
12190 | @file{.build-id} subdirectory of the global debug directory for a file |
12191 | named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the | |
7e27a47a EZ |
12192 | first 2 hex characters of the build ID bit string, and @var{nnnnnnnn} |
12193 | are the rest of the bit string. (Real build ID strings are 32 or more | |
12194 | hex characters, not 10.) | |
c7e83d54 EZ |
12195 | @end itemize |
12196 | ||
12197 | So, for example, suppose you ask @value{GDBN} to debug | |
7e27a47a EZ |
12198 | @file{/usr/bin/ls}, which has a debug link that specifies the |
12199 | file @file{ls.debug}, and a build ID whose value in hex is | |
c7e83d54 EZ |
12200 | @code{abcdef1234}. If the global debug directory is |
12201 | @file{/usr/lib/debug}, then @value{GDBN} will look for the following | |
12202 | debug information files, in the indicated order: | |
12203 | ||
12204 | @itemize @minus | |
12205 | @item | |
12206 | @file{/usr/lib/debug/.build-id/ab/cdef1234.debug} | |
d3750b24 | 12207 | @item |
c7e83d54 | 12208 | @file{/usr/bin/ls.debug} |
5b5d99cf | 12209 | @item |
c7e83d54 | 12210 | @file{/usr/bin/.debug/ls.debug} |
5b5d99cf | 12211 | @item |
c7e83d54 | 12212 | @file{/usr/lib/debug/usr/bin/ls.debug}. |
5b5d99cf | 12213 | @end itemize |
5b5d99cf JB |
12214 | |
12215 | You can set the global debugging info directory's name, and view the | |
12216 | name @value{GDBN} is currently using. | |
12217 | ||
12218 | @table @code | |
12219 | ||
12220 | @kindex set debug-file-directory | |
12221 | @item set debug-file-directory @var{directory} | |
12222 | Set the directory which @value{GDBN} searches for separate debugging | |
12223 | information files to @var{directory}. | |
12224 | ||
12225 | @kindex show debug-file-directory | |
12226 | @item show debug-file-directory | |
12227 | Show the directory @value{GDBN} searches for separate debugging | |
12228 | information files. | |
12229 | ||
12230 | @end table | |
12231 | ||
12232 | @cindex @code{.gnu_debuglink} sections | |
c7e83d54 | 12233 | @cindex debug link sections |
5b5d99cf JB |
12234 | A debug link is a special section of the executable file named |
12235 | @code{.gnu_debuglink}. The section must contain: | |
12236 | ||
12237 | @itemize | |
12238 | @item | |
12239 | A filename, with any leading directory components removed, followed by | |
12240 | a zero byte, | |
12241 | @item | |
12242 | zero to three bytes of padding, as needed to reach the next four-byte | |
12243 | boundary within the section, and | |
12244 | @item | |
12245 | a four-byte CRC checksum, stored in the same endianness used for the | |
12246 | executable file itself. The checksum is computed on the debugging | |
12247 | information file's full contents by the function given below, passing | |
12248 | zero as the @var{crc} argument. | |
12249 | @end itemize | |
12250 | ||
12251 | Any executable file format can carry a debug link, as long as it can | |
12252 | contain a section named @code{.gnu_debuglink} with the contents | |
12253 | described above. | |
12254 | ||
d3750b24 | 12255 | @cindex @code{.note.gnu.build-id} sections |
c7e83d54 | 12256 | @cindex build ID sections |
7e27a47a EZ |
12257 | The build ID is a special section in the executable file (and in other |
12258 | ELF binary files that @value{GDBN} may consider). This section is | |
12259 | often named @code{.note.gnu.build-id}, but that name is not mandatory. | |
12260 | It contains unique identification for the built files---the ID remains | |
12261 | the same across multiple builds of the same build tree. The default | |
12262 | algorithm SHA1 produces 160 bits (40 hexadecimal characters) of the | |
12263 | content for the build ID string. The same section with an identical | |
12264 | value is present in the original built binary with symbols, in its | |
12265 | stripped variant, and in the separate debugging information file. | |
d3750b24 | 12266 | |
5b5d99cf JB |
12267 | The debugging information file itself should be an ordinary |
12268 | executable, containing a full set of linker symbols, sections, and | |
12269 | debugging information. The sections of the debugging information file | |
c7e83d54 EZ |
12270 | should have the same names, addresses, and sizes as the original file, |
12271 | but they need not contain any data---much like a @code{.bss} section | |
5b5d99cf JB |
12272 | in an ordinary executable. |
12273 | ||
7e27a47a | 12274 | The @sc{gnu} binary utilities (Binutils) package includes the |
c7e83d54 EZ |
12275 | @samp{objcopy} utility that can produce |
12276 | the separated executable / debugging information file pairs using the | |
12277 | following commands: | |
12278 | ||
12279 | @smallexample | |
12280 | @kbd{objcopy --only-keep-debug foo foo.debug} | |
12281 | @kbd{strip -g foo} | |
c7e83d54 EZ |
12282 | @end smallexample |
12283 | ||
12284 | @noindent | |
12285 | These commands remove the debugging | |
83f83d7f JK |
12286 | information from the executable file @file{foo} and place it in the file |
12287 | @file{foo.debug}. You can use the first, second or both methods to link the | |
12288 | two files: | |
12289 | ||
12290 | @itemize @bullet | |
12291 | @item | |
12292 | The debug link method needs the following additional command to also leave | |
12293 | behind a debug link in @file{foo}: | |
12294 | ||
12295 | @smallexample | |
12296 | @kbd{objcopy --add-gnu-debuglink=foo.debug foo} | |
12297 | @end smallexample | |
12298 | ||
12299 | Ulrich Drepper's @file{elfutils} package, starting with version 0.53, contains | |
d3750b24 | 12300 | a version of the @code{strip} command such that the command @kbd{strip foo -f |
83f83d7f JK |
12301 | foo.debug} has the same functionality as the two @code{objcopy} commands and |
12302 | the @code{ln -s} command above, together. | |
12303 | ||
12304 | @item | |
12305 | Build ID gets embedded into the main executable using @code{ld --build-id} or | |
12306 | the @value{NGCC} counterpart @code{gcc -Wl,--build-id}. Build ID support plus | |
12307 | compatibility fixes for debug files separation are present in @sc{gnu} binary | |
7e27a47a | 12308 | utilities (Binutils) package since version 2.18. |
83f83d7f JK |
12309 | @end itemize |
12310 | ||
12311 | @noindent | |
d3750b24 | 12312 | |
c7e83d54 EZ |
12313 | Since there are many different ways to compute CRC's for the debug |
12314 | link (different polynomials, reversals, byte ordering, etc.), the | |
12315 | simplest way to describe the CRC used in @code{.gnu_debuglink} | |
12316 | sections is to give the complete code for a function that computes it: | |
5b5d99cf | 12317 | |
4644b6e3 | 12318 | @kindex gnu_debuglink_crc32 |
5b5d99cf JB |
12319 | @smallexample |
12320 | unsigned long | |
12321 | gnu_debuglink_crc32 (unsigned long crc, | |
12322 | unsigned char *buf, size_t len) | |
12323 | @{ | |
12324 | static const unsigned long crc32_table[256] = | |
12325 | @{ | |
12326 | 0x00000000, 0x77073096, 0xee0e612c, 0x990951ba, 0x076dc419, | |
12327 | 0x706af48f, 0xe963a535, 0x9e6495a3, 0x0edb8832, 0x79dcb8a4, | |
12328 | 0xe0d5e91e, 0x97d2d988, 0x09b64c2b, 0x7eb17cbd, 0xe7b82d07, | |
12329 | 0x90bf1d91, 0x1db71064, 0x6ab020f2, 0xf3b97148, 0x84be41de, | |
12330 | 0x1adad47d, 0x6ddde4eb, 0xf4d4b551, 0x83d385c7, 0x136c9856, | |
12331 | 0x646ba8c0, 0xfd62f97a, 0x8a65c9ec, 0x14015c4f, 0x63066cd9, | |
12332 | 0xfa0f3d63, 0x8d080df5, 0x3b6e20c8, 0x4c69105e, 0xd56041e4, | |
12333 | 0xa2677172, 0x3c03e4d1, 0x4b04d447, 0xd20d85fd, 0xa50ab56b, | |
12334 | 0x35b5a8fa, 0x42b2986c, 0xdbbbc9d6, 0xacbcf940, 0x32d86ce3, | |
12335 | 0x45df5c75, 0xdcd60dcf, 0xabd13d59, 0x26d930ac, 0x51de003a, | |
12336 | 0xc8d75180, 0xbfd06116, 0x21b4f4b5, 0x56b3c423, 0xcfba9599, | |
12337 | 0xb8bda50f, 0x2802b89e, 0x5f058808, 0xc60cd9b2, 0xb10be924, | |
12338 | 0x2f6f7c87, 0x58684c11, 0xc1611dab, 0xb6662d3d, 0x76dc4190, | |
12339 | 0x01db7106, 0x98d220bc, 0xefd5102a, 0x71b18589, 0x06b6b51f, | |
12340 | 0x9fbfe4a5, 0xe8b8d433, 0x7807c9a2, 0x0f00f934, 0x9609a88e, | |
12341 | 0xe10e9818, 0x7f6a0dbb, 0x086d3d2d, 0x91646c97, 0xe6635c01, | |
12342 | 0x6b6b51f4, 0x1c6c6162, 0x856530d8, 0xf262004e, 0x6c0695ed, | |
12343 | 0x1b01a57b, 0x8208f4c1, 0xf50fc457, 0x65b0d9c6, 0x12b7e950, | |
12344 | 0x8bbeb8ea, 0xfcb9887c, 0x62dd1ddf, 0x15da2d49, 0x8cd37cf3, | |
12345 | 0xfbd44c65, 0x4db26158, 0x3ab551ce, 0xa3bc0074, 0xd4bb30e2, | |
12346 | 0x4adfa541, 0x3dd895d7, 0xa4d1c46d, 0xd3d6f4fb, 0x4369e96a, | |
12347 | 0x346ed9fc, 0xad678846, 0xda60b8d0, 0x44042d73, 0x33031de5, | |
12348 | 0xaa0a4c5f, 0xdd0d7cc9, 0x5005713c, 0x270241aa, 0xbe0b1010, | |
12349 | 0xc90c2086, 0x5768b525, 0x206f85b3, 0xb966d409, 0xce61e49f, | |
12350 | 0x5edef90e, 0x29d9c998, 0xb0d09822, 0xc7d7a8b4, 0x59b33d17, | |
12351 | 0x2eb40d81, 0xb7bd5c3b, 0xc0ba6cad, 0xedb88320, 0x9abfb3b6, | |
12352 | 0x03b6e20c, 0x74b1d29a, 0xead54739, 0x9dd277af, 0x04db2615, | |
12353 | 0x73dc1683, 0xe3630b12, 0x94643b84, 0x0d6d6a3e, 0x7a6a5aa8, | |
12354 | 0xe40ecf0b, 0x9309ff9d, 0x0a00ae27, 0x7d079eb1, 0xf00f9344, | |
12355 | 0x8708a3d2, 0x1e01f268, 0x6906c2fe, 0xf762575d, 0x806567cb, | |
12356 | 0x196c3671, 0x6e6b06e7, 0xfed41b76, 0x89d32be0, 0x10da7a5a, | |
12357 | 0x67dd4acc, 0xf9b9df6f, 0x8ebeeff9, 0x17b7be43, 0x60b08ed5, | |
12358 | 0xd6d6a3e8, 0xa1d1937e, 0x38d8c2c4, 0x4fdff252, 0xd1bb67f1, | |
12359 | 0xa6bc5767, 0x3fb506dd, 0x48b2364b, 0xd80d2bda, 0xaf0a1b4c, | |
12360 | 0x36034af6, 0x41047a60, 0xdf60efc3, 0xa867df55, 0x316e8eef, | |
12361 | 0x4669be79, 0xcb61b38c, 0xbc66831a, 0x256fd2a0, 0x5268e236, | |
12362 | 0xcc0c7795, 0xbb0b4703, 0x220216b9, 0x5505262f, 0xc5ba3bbe, | |
12363 | 0xb2bd0b28, 0x2bb45a92, 0x5cb36a04, 0xc2d7ffa7, 0xb5d0cf31, | |
12364 | 0x2cd99e8b, 0x5bdeae1d, 0x9b64c2b0, 0xec63f226, 0x756aa39c, | |
12365 | 0x026d930a, 0x9c0906a9, 0xeb0e363f, 0x72076785, 0x05005713, | |
12366 | 0x95bf4a82, 0xe2b87a14, 0x7bb12bae, 0x0cb61b38, 0x92d28e9b, | |
12367 | 0xe5d5be0d, 0x7cdcefb7, 0x0bdbdf21, 0x86d3d2d4, 0xf1d4e242, | |
12368 | 0x68ddb3f8, 0x1fda836e, 0x81be16cd, 0xf6b9265b, 0x6fb077e1, | |
12369 | 0x18b74777, 0x88085ae6, 0xff0f6a70, 0x66063bca, 0x11010b5c, | |
12370 | 0x8f659eff, 0xf862ae69, 0x616bffd3, 0x166ccf45, 0xa00ae278, | |
12371 | 0xd70dd2ee, 0x4e048354, 0x3903b3c2, 0xa7672661, 0xd06016f7, | |
12372 | 0x4969474d, 0x3e6e77db, 0xaed16a4a, 0xd9d65adc, 0x40df0b66, | |
12373 | 0x37d83bf0, 0xa9bcae53, 0xdebb9ec5, 0x47b2cf7f, 0x30b5ffe9, | |
12374 | 0xbdbdf21c, 0xcabac28a, 0x53b39330, 0x24b4a3a6, 0xbad03605, | |
12375 | 0xcdd70693, 0x54de5729, 0x23d967bf, 0xb3667a2e, 0xc4614ab8, | |
12376 | 0x5d681b02, 0x2a6f2b94, 0xb40bbe37, 0xc30c8ea1, 0x5a05df1b, | |
12377 | 0x2d02ef8d | |
12378 | @}; | |
12379 | unsigned char *end; | |
12380 | ||
12381 | crc = ~crc & 0xffffffff; | |
12382 | for (end = buf + len; buf < end; ++buf) | |
12383 | crc = crc32_table[(crc ^ *buf) & 0xff] ^ (crc >> 8); | |
e7a3abfc | 12384 | return ~crc & 0xffffffff; |
5b5d99cf JB |
12385 | @} |
12386 | @end smallexample | |
12387 | ||
c7e83d54 EZ |
12388 | @noindent |
12389 | This computation does not apply to the ``build ID'' method. | |
12390 | ||
5b5d99cf | 12391 | |
6d2ebf8b | 12392 | @node Symbol Errors |
79a6e687 | 12393 | @section Errors Reading Symbol Files |
c906108c SS |
12394 | |
12395 | While reading a symbol file, @value{GDBN} occasionally encounters problems, | |
12396 | such as symbol types it does not recognize, or known bugs in compiler | |
12397 | output. By default, @value{GDBN} does not notify you of such problems, since | |
12398 | they are relatively common and primarily of interest to people | |
12399 | debugging compilers. If you are interested in seeing information | |
12400 | about ill-constructed symbol tables, you can either ask @value{GDBN} to print | |
12401 | only one message about each such type of problem, no matter how many | |
12402 | times the problem occurs; or you can ask @value{GDBN} to print more messages, | |
12403 | to see how many times the problems occur, with the @code{set | |
79a6e687 BW |
12404 | complaints} command (@pxref{Messages/Warnings, ,Optional Warnings and |
12405 | Messages}). | |
c906108c SS |
12406 | |
12407 | The messages currently printed, and their meanings, include: | |
12408 | ||
12409 | @table @code | |
12410 | @item inner block not inside outer block in @var{symbol} | |
12411 | ||
12412 | The symbol information shows where symbol scopes begin and end | |
12413 | (such as at the start of a function or a block of statements). This | |
12414 | error indicates that an inner scope block is not fully contained | |
12415 | in its outer scope blocks. | |
12416 | ||
12417 | @value{GDBN} circumvents the problem by treating the inner block as if it had | |
12418 | the same scope as the outer block. In the error message, @var{symbol} | |
12419 | may be shown as ``@code{(don't know)}'' if the outer block is not a | |
12420 | function. | |
12421 | ||
12422 | @item block at @var{address} out of order | |
12423 | ||
12424 | The symbol information for symbol scope blocks should occur in | |
12425 | order of increasing addresses. This error indicates that it does not | |
12426 | do so. | |
12427 | ||
12428 | @value{GDBN} does not circumvent this problem, and has trouble | |
12429 | locating symbols in the source file whose symbols it is reading. (You | |
12430 | can often determine what source file is affected by specifying | |
79a6e687 BW |
12431 | @code{set verbose on}. @xref{Messages/Warnings, ,Optional Warnings and |
12432 | Messages}.) | |
c906108c SS |
12433 | |
12434 | @item bad block start address patched | |
12435 | ||
12436 | The symbol information for a symbol scope block has a start address | |
12437 | smaller than the address of the preceding source line. This is known | |
12438 | to occur in the SunOS 4.1.1 (and earlier) C compiler. | |
12439 | ||
12440 | @value{GDBN} circumvents the problem by treating the symbol scope block as | |
12441 | starting on the previous source line. | |
12442 | ||
12443 | @item bad string table offset in symbol @var{n} | |
12444 | ||
12445 | @cindex foo | |
12446 | Symbol number @var{n} contains a pointer into the string table which is | |
12447 | larger than the size of the string table. | |
12448 | ||
12449 | @value{GDBN} circumvents the problem by considering the symbol to have the | |
12450 | name @code{foo}, which may cause other problems if many symbols end up | |
12451 | with this name. | |
12452 | ||
12453 | @item unknown symbol type @code{0x@var{nn}} | |
12454 | ||
7a292a7a SS |
12455 | The symbol information contains new data types that @value{GDBN} does |
12456 | not yet know how to read. @code{0x@var{nn}} is the symbol type of the | |
d4f3574e | 12457 | uncomprehended information, in hexadecimal. |
c906108c | 12458 | |
7a292a7a SS |
12459 | @value{GDBN} circumvents the error by ignoring this symbol information. |
12460 | This usually allows you to debug your program, though certain symbols | |
c906108c | 12461 | are not accessible. If you encounter such a problem and feel like |
7a292a7a SS |
12462 | debugging it, you can debug @code{@value{GDBP}} with itself, breakpoint |
12463 | on @code{complain}, then go up to the function @code{read_dbx_symtab} | |
12464 | and examine @code{*bufp} to see the symbol. | |
c906108c SS |
12465 | |
12466 | @item stub type has NULL name | |
c906108c | 12467 | |
7a292a7a | 12468 | @value{GDBN} could not find the full definition for a struct or class. |
c906108c | 12469 | |
7a292a7a | 12470 | @item const/volatile indicator missing (ok if using g++ v1.x), got@dots{} |
b37052ae | 12471 | The symbol information for a C@t{++} member function is missing some |
7a292a7a SS |
12472 | information that recent versions of the compiler should have output for |
12473 | it. | |
c906108c SS |
12474 | |
12475 | @item info mismatch between compiler and debugger | |
12476 | ||
12477 | @value{GDBN} could not parse a type specification output by the compiler. | |
7a292a7a | 12478 | |
c906108c SS |
12479 | @end table |
12480 | ||
6d2ebf8b | 12481 | @node Targets |
c906108c | 12482 | @chapter Specifying a Debugging Target |
7a292a7a | 12483 | |
c906108c | 12484 | @cindex debugging target |
c906108c | 12485 | A @dfn{target} is the execution environment occupied by your program. |
53a5351d JM |
12486 | |
12487 | Often, @value{GDBN} runs in the same host environment as your program; | |
12488 | in that case, the debugging target is specified as a side effect when | |
12489 | you use the @code{file} or @code{core} commands. When you need more | |
c906108c SS |
12490 | flexibility---for example, running @value{GDBN} on a physically separate |
12491 | host, or controlling a standalone system over a serial port or a | |
53a5351d JM |
12492 | realtime system over a TCP/IP connection---you can use the @code{target} |
12493 | command to specify one of the target types configured for @value{GDBN} | |
79a6e687 | 12494 | (@pxref{Target Commands, ,Commands for Managing Targets}). |
c906108c | 12495 | |
a8f24a35 EZ |
12496 | @cindex target architecture |
12497 | It is possible to build @value{GDBN} for several different @dfn{target | |
12498 | architectures}. When @value{GDBN} is built like that, you can choose | |
12499 | one of the available architectures with the @kbd{set architecture} | |
12500 | command. | |
12501 | ||
12502 | @table @code | |
12503 | @kindex set architecture | |
12504 | @kindex show architecture | |
12505 | @item set architecture @var{arch} | |
12506 | This command sets the current target architecture to @var{arch}. The | |
12507 | value of @var{arch} can be @code{"auto"}, in addition to one of the | |
12508 | supported architectures. | |
12509 | ||
12510 | @item show architecture | |
12511 | Show the current target architecture. | |
9c16f35a EZ |
12512 | |
12513 | @item set processor | |
12514 | @itemx processor | |
12515 | @kindex set processor | |
12516 | @kindex show processor | |
12517 | These are alias commands for, respectively, @code{set architecture} | |
12518 | and @code{show architecture}. | |
a8f24a35 EZ |
12519 | @end table |
12520 | ||
c906108c SS |
12521 | @menu |
12522 | * Active Targets:: Active targets | |
12523 | * Target Commands:: Commands for managing targets | |
c906108c | 12524 | * Byte Order:: Choosing target byte order |
c906108c SS |
12525 | @end menu |
12526 | ||
6d2ebf8b | 12527 | @node Active Targets |
79a6e687 | 12528 | @section Active Targets |
7a292a7a | 12529 | |
c906108c SS |
12530 | @cindex stacking targets |
12531 | @cindex active targets | |
12532 | @cindex multiple targets | |
12533 | ||
c906108c | 12534 | There are three classes of targets: processes, core files, and |
7a292a7a SS |
12535 | executable files. @value{GDBN} can work concurrently on up to three |
12536 | active targets, one in each class. This allows you to (for example) | |
12537 | start a process and inspect its activity without abandoning your work on | |
12538 | a core file. | |
c906108c SS |
12539 | |
12540 | For example, if you execute @samp{gdb a.out}, then the executable file | |
12541 | @code{a.out} is the only active target. If you designate a core file as | |
12542 | well---presumably from a prior run that crashed and coredumped---then | |
12543 | @value{GDBN} has two active targets and uses them in tandem, looking | |
12544 | first in the corefile target, then in the executable file, to satisfy | |
12545 | requests for memory addresses. (Typically, these two classes of target | |
12546 | are complementary, since core files contain only a program's | |
12547 | read-write memory---variables and so on---plus machine status, while | |
12548 | executable files contain only the program text and initialized data.) | |
c906108c SS |
12549 | |
12550 | When you type @code{run}, your executable file becomes an active process | |
7a292a7a SS |
12551 | target as well. When a process target is active, all @value{GDBN} |
12552 | commands requesting memory addresses refer to that target; addresses in | |
12553 | an active core file or executable file target are obscured while the | |
12554 | process target is active. | |
c906108c | 12555 | |
7a292a7a | 12556 | Use the @code{core-file} and @code{exec-file} commands to select a new |
79a6e687 BW |
12557 | core file or executable target (@pxref{Files, ,Commands to Specify |
12558 | Files}). To specify as a target a process that is already running, use | |
12559 | the @code{attach} command (@pxref{Attach, ,Debugging an Already-running | |
12560 | Process}). | |
c906108c | 12561 | |
6d2ebf8b | 12562 | @node Target Commands |
79a6e687 | 12563 | @section Commands for Managing Targets |
c906108c SS |
12564 | |
12565 | @table @code | |
12566 | @item target @var{type} @var{parameters} | |
7a292a7a SS |
12567 | Connects the @value{GDBN} host environment to a target machine or |
12568 | process. A target is typically a protocol for talking to debugging | |
12569 | facilities. You use the argument @var{type} to specify the type or | |
12570 | protocol of the target machine. | |
c906108c SS |
12571 | |
12572 | Further @var{parameters} are interpreted by the target protocol, but | |
12573 | typically include things like device names or host names to connect | |
12574 | with, process numbers, and baud rates. | |
c906108c SS |
12575 | |
12576 | The @code{target} command does not repeat if you press @key{RET} again | |
12577 | after executing the command. | |
12578 | ||
12579 | @kindex help target | |
12580 | @item help target | |
12581 | Displays the names of all targets available. To display targets | |
12582 | currently selected, use either @code{info target} or @code{info files} | |
79a6e687 | 12583 | (@pxref{Files, ,Commands to Specify Files}). |
c906108c SS |
12584 | |
12585 | @item help target @var{name} | |
12586 | Describe a particular target, including any parameters necessary to | |
12587 | select it. | |
12588 | ||
12589 | @kindex set gnutarget | |
12590 | @item set gnutarget @var{args} | |
5d161b24 | 12591 | @value{GDBN} uses its own library BFD to read your files. @value{GDBN} |
c906108c | 12592 | knows whether it is reading an @dfn{executable}, |
5d161b24 DB |
12593 | a @dfn{core}, or a @dfn{.o} file; however, you can specify the file format |
12594 | with the @code{set gnutarget} command. Unlike most @code{target} commands, | |
c906108c SS |
12595 | with @code{gnutarget} the @code{target} refers to a program, not a machine. |
12596 | ||
d4f3574e | 12597 | @quotation |
c906108c SS |
12598 | @emph{Warning:} To specify a file format with @code{set gnutarget}, |
12599 | you must know the actual BFD name. | |
d4f3574e | 12600 | @end quotation |
c906108c | 12601 | |
d4f3574e | 12602 | @noindent |
79a6e687 | 12603 | @xref{Files, , Commands to Specify Files}. |
c906108c | 12604 | |
5d161b24 | 12605 | @kindex show gnutarget |
c906108c SS |
12606 | @item show gnutarget |
12607 | Use the @code{show gnutarget} command to display what file format | |
12608 | @code{gnutarget} is set to read. If you have not set @code{gnutarget}, | |
12609 | @value{GDBN} will determine the file format for each file automatically, | |
12610 | and @code{show gnutarget} displays @samp{The current BDF target is "auto"}. | |
12611 | @end table | |
12612 | ||
4644b6e3 | 12613 | @cindex common targets |
c906108c SS |
12614 | Here are some common targets (available, or not, depending on the GDB |
12615 | configuration): | |
c906108c SS |
12616 | |
12617 | @table @code | |
4644b6e3 | 12618 | @kindex target |
c906108c | 12619 | @item target exec @var{program} |
4644b6e3 | 12620 | @cindex executable file target |
c906108c SS |
12621 | An executable file. @samp{target exec @var{program}} is the same as |
12622 | @samp{exec-file @var{program}}. | |
12623 | ||
c906108c | 12624 | @item target core @var{filename} |
4644b6e3 | 12625 | @cindex core dump file target |
c906108c SS |
12626 | A core dump file. @samp{target core @var{filename}} is the same as |
12627 | @samp{core-file @var{filename}}. | |
c906108c | 12628 | |
1a10341b | 12629 | @item target remote @var{medium} |
4644b6e3 | 12630 | @cindex remote target |
1a10341b JB |
12631 | A remote system connected to @value{GDBN} via a serial line or network |
12632 | connection. This command tells @value{GDBN} to use its own remote | |
12633 | protocol over @var{medium} for debugging. @xref{Remote Debugging}. | |
12634 | ||
12635 | For example, if you have a board connected to @file{/dev/ttya} on the | |
12636 | machine running @value{GDBN}, you could say: | |
12637 | ||
12638 | @smallexample | |
12639 | target remote /dev/ttya | |
12640 | @end smallexample | |
12641 | ||
12642 | @code{target remote} supports the @code{load} command. This is only | |
12643 | useful if you have some other way of getting the stub to the target | |
12644 | system, and you can put it somewhere in memory where it won't get | |
12645 | clobbered by the download. | |
c906108c | 12646 | |
c906108c | 12647 | @item target sim |
4644b6e3 | 12648 | @cindex built-in simulator target |
2df3850c | 12649 | Builtin CPU simulator. @value{GDBN} includes simulators for most architectures. |
104c1213 | 12650 | In general, |
474c8240 | 12651 | @smallexample |
104c1213 JM |
12652 | target sim |
12653 | load | |
12654 | run | |
474c8240 | 12655 | @end smallexample |
d4f3574e | 12656 | @noindent |
104c1213 | 12657 | works; however, you cannot assume that a specific memory map, device |
d4f3574e | 12658 | drivers, or even basic I/O is available, although some simulators do |
104c1213 JM |
12659 | provide these. For info about any processor-specific simulator details, |
12660 | see the appropriate section in @ref{Embedded Processors, ,Embedded | |
12661 | Processors}. | |
12662 | ||
c906108c SS |
12663 | @end table |
12664 | ||
104c1213 | 12665 | Some configurations may include these targets as well: |
c906108c SS |
12666 | |
12667 | @table @code | |
12668 | ||
c906108c | 12669 | @item target nrom @var{dev} |
4644b6e3 | 12670 | @cindex NetROM ROM emulator target |
c906108c SS |
12671 | NetROM ROM emulator. This target only supports downloading. |
12672 | ||
c906108c SS |
12673 | @end table |
12674 | ||
5d161b24 | 12675 | Different targets are available on different configurations of @value{GDBN}; |
c906108c | 12676 | your configuration may have more or fewer targets. |
c906108c | 12677 | |
721c2651 EZ |
12678 | Many remote targets require you to download the executable's code once |
12679 | you've successfully established a connection. You may wish to control | |
3d00d119 DJ |
12680 | various aspects of this process. |
12681 | ||
12682 | @table @code | |
721c2651 EZ |
12683 | |
12684 | @item set hash | |
12685 | @kindex set hash@r{, for remote monitors} | |
12686 | @cindex hash mark while downloading | |
12687 | This command controls whether a hash mark @samp{#} is displayed while | |
12688 | downloading a file to the remote monitor. If on, a hash mark is | |
12689 | displayed after each S-record is successfully downloaded to the | |
12690 | monitor. | |
12691 | ||
12692 | @item show hash | |
12693 | @kindex show hash@r{, for remote monitors} | |
12694 | Show the current status of displaying the hash mark. | |
12695 | ||
12696 | @item set debug monitor | |
12697 | @kindex set debug monitor | |
12698 | @cindex display remote monitor communications | |
12699 | Enable or disable display of communications messages between | |
12700 | @value{GDBN} and the remote monitor. | |
12701 | ||
12702 | @item show debug monitor | |
12703 | @kindex show debug monitor | |
12704 | Show the current status of displaying communications between | |
12705 | @value{GDBN} and the remote monitor. | |
a8f24a35 | 12706 | @end table |
c906108c SS |
12707 | |
12708 | @table @code | |
12709 | ||
12710 | @kindex load @var{filename} | |
12711 | @item load @var{filename} | |
8edfe269 | 12712 | @anchor{load} |
c906108c SS |
12713 | Depending on what remote debugging facilities are configured into |
12714 | @value{GDBN}, the @code{load} command may be available. Where it exists, it | |
12715 | is meant to make @var{filename} (an executable) available for debugging | |
12716 | on the remote system---by downloading, or dynamic linking, for example. | |
12717 | @code{load} also records the @var{filename} symbol table in @value{GDBN}, like | |
12718 | the @code{add-symbol-file} command. | |
12719 | ||
12720 | If your @value{GDBN} does not have a @code{load} command, attempting to | |
12721 | execute it gets the error message ``@code{You can't do that when your | |
12722 | target is @dots{}}'' | |
c906108c SS |
12723 | |
12724 | The file is loaded at whatever address is specified in the executable. | |
12725 | For some object file formats, you can specify the load address when you | |
12726 | link the program; for other formats, like a.out, the object file format | |
12727 | specifies a fixed address. | |
12728 | @c FIXME! This would be a good place for an xref to the GNU linker doc. | |
12729 | ||
68437a39 DJ |
12730 | Depending on the remote side capabilities, @value{GDBN} may be able to |
12731 | load programs into flash memory. | |
12732 | ||
c906108c SS |
12733 | @code{load} does not repeat if you press @key{RET} again after using it. |
12734 | @end table | |
12735 | ||
6d2ebf8b | 12736 | @node Byte Order |
79a6e687 | 12737 | @section Choosing Target Byte Order |
7a292a7a | 12738 | |
c906108c SS |
12739 | @cindex choosing target byte order |
12740 | @cindex target byte order | |
c906108c | 12741 | |
172c2a43 | 12742 | Some types of processors, such as the MIPS, PowerPC, and Renesas SH, |
c906108c SS |
12743 | offer the ability to run either big-endian or little-endian byte |
12744 | orders. Usually the executable or symbol will include a bit to | |
12745 | designate the endian-ness, and you will not need to worry about | |
12746 | which to use. However, you may still find it useful to adjust | |
d4f3574e | 12747 | @value{GDBN}'s idea of processor endian-ness manually. |
c906108c SS |
12748 | |
12749 | @table @code | |
4644b6e3 | 12750 | @kindex set endian |
c906108c SS |
12751 | @item set endian big |
12752 | Instruct @value{GDBN} to assume the target is big-endian. | |
12753 | ||
c906108c SS |
12754 | @item set endian little |
12755 | Instruct @value{GDBN} to assume the target is little-endian. | |
12756 | ||
c906108c SS |
12757 | @item set endian auto |
12758 | Instruct @value{GDBN} to use the byte order associated with the | |
12759 | executable. | |
12760 | ||
12761 | @item show endian | |
12762 | Display @value{GDBN}'s current idea of the target byte order. | |
12763 | ||
12764 | @end table | |
12765 | ||
12766 | Note that these commands merely adjust interpretation of symbolic | |
12767 | data on the host, and that they have absolutely no effect on the | |
12768 | target system. | |
12769 | ||
ea35711c DJ |
12770 | |
12771 | @node Remote Debugging | |
12772 | @chapter Debugging Remote Programs | |
c906108c SS |
12773 | @cindex remote debugging |
12774 | ||
12775 | If you are trying to debug a program running on a machine that cannot run | |
5d161b24 DB |
12776 | @value{GDBN} in the usual way, it is often useful to use remote debugging. |
12777 | For example, you might use remote debugging on an operating system kernel, | |
c906108c SS |
12778 | or on a small system which does not have a general purpose operating system |
12779 | powerful enough to run a full-featured debugger. | |
12780 | ||
12781 | Some configurations of @value{GDBN} have special serial or TCP/IP interfaces | |
12782 | to make this work with particular debugging targets. In addition, | |
5d161b24 | 12783 | @value{GDBN} comes with a generic serial protocol (specific to @value{GDBN}, |
c906108c SS |
12784 | but not specific to any particular target system) which you can use if you |
12785 | write the remote stubs---the code that runs on the remote system to | |
12786 | communicate with @value{GDBN}. | |
12787 | ||
12788 | Other remote targets may be available in your | |
12789 | configuration of @value{GDBN}; use @code{help target} to list them. | |
c906108c | 12790 | |
6b2f586d | 12791 | @menu |
07f31aa6 | 12792 | * Connecting:: Connecting to a remote target |
a6b151f1 | 12793 | * File Transfer:: Sending files to a remote system |
6b2f586d | 12794 | * Server:: Using the gdbserver program |
79a6e687 BW |
12795 | * Remote Configuration:: Remote configuration |
12796 | * Remote Stub:: Implementing a remote stub | |
6b2f586d AC |
12797 | @end menu |
12798 | ||
07f31aa6 | 12799 | @node Connecting |
79a6e687 | 12800 | @section Connecting to a Remote Target |
07f31aa6 DJ |
12801 | |
12802 | On the @value{GDBN} host machine, you will need an unstripped copy of | |
d3e8051b | 12803 | your program, since @value{GDBN} needs symbol and debugging information. |
07f31aa6 DJ |
12804 | Start up @value{GDBN} as usual, using the name of the local copy of your |
12805 | program as the first argument. | |
12806 | ||
86941c27 JB |
12807 | @cindex @code{target remote} |
12808 | @value{GDBN} can communicate with the target over a serial line, or | |
12809 | over an @acronym{IP} network using @acronym{TCP} or @acronym{UDP}. In | |
12810 | each case, @value{GDBN} uses the same protocol for debugging your | |
12811 | program; only the medium carrying the debugging packets varies. The | |
12812 | @code{target remote} command establishes a connection to the target. | |
12813 | Its arguments indicate which medium to use: | |
12814 | ||
12815 | @table @code | |
12816 | ||
12817 | @item target remote @var{serial-device} | |
07f31aa6 | 12818 | @cindex serial line, @code{target remote} |
86941c27 JB |
12819 | Use @var{serial-device} to communicate with the target. For example, |
12820 | to use a serial line connected to the device named @file{/dev/ttyb}: | |
12821 | ||
12822 | @smallexample | |
12823 | target remote /dev/ttyb | |
12824 | @end smallexample | |
12825 | ||
07f31aa6 DJ |
12826 | If you're using a serial line, you may want to give @value{GDBN} the |
12827 | @w{@samp{--baud}} option, or use the @code{set remotebaud} command | |
79a6e687 | 12828 | (@pxref{Remote Configuration, set remotebaud}) before the |
9c16f35a | 12829 | @code{target} command. |
07f31aa6 | 12830 | |
86941c27 JB |
12831 | @item target remote @code{@var{host}:@var{port}} |
12832 | @itemx target remote @code{tcp:@var{host}:@var{port}} | |
12833 | @cindex @acronym{TCP} port, @code{target remote} | |
12834 | Debug using a @acronym{TCP} connection to @var{port} on @var{host}. | |
12835 | The @var{host} may be either a host name or a numeric @acronym{IP} | |
12836 | address; @var{port} must be a decimal number. The @var{host} could be | |
12837 | the target machine itself, if it is directly connected to the net, or | |
12838 | it might be a terminal server which in turn has a serial line to the | |
12839 | target. | |
07f31aa6 | 12840 | |
86941c27 JB |
12841 | For example, to connect to port 2828 on a terminal server named |
12842 | @code{manyfarms}: | |
07f31aa6 DJ |
12843 | |
12844 | @smallexample | |
12845 | target remote manyfarms:2828 | |
12846 | @end smallexample | |
12847 | ||
86941c27 JB |
12848 | If your remote target is actually running on the same machine as your |
12849 | debugger session (e.g.@: a simulator for your target running on the | |
12850 | same host), you can omit the hostname. For example, to connect to | |
12851 | port 1234 on your local machine: | |
07f31aa6 DJ |
12852 | |
12853 | @smallexample | |
12854 | target remote :1234 | |
12855 | @end smallexample | |
12856 | @noindent | |
12857 | ||
12858 | Note that the colon is still required here. | |
12859 | ||
86941c27 JB |
12860 | @item target remote @code{udp:@var{host}:@var{port}} |
12861 | @cindex @acronym{UDP} port, @code{target remote} | |
12862 | Debug using @acronym{UDP} packets to @var{port} on @var{host}. For example, to | |
12863 | connect to @acronym{UDP} port 2828 on a terminal server named @code{manyfarms}: | |
07f31aa6 DJ |
12864 | |
12865 | @smallexample | |
12866 | target remote udp:manyfarms:2828 | |
12867 | @end smallexample | |
12868 | ||
86941c27 JB |
12869 | When using a @acronym{UDP} connection for remote debugging, you should |
12870 | keep in mind that the `U' stands for ``Unreliable''. @acronym{UDP} | |
12871 | can silently drop packets on busy or unreliable networks, which will | |
12872 | cause havoc with your debugging session. | |
12873 | ||
66b8c7f6 JB |
12874 | @item target remote | @var{command} |
12875 | @cindex pipe, @code{target remote} to | |
12876 | Run @var{command} in the background and communicate with it using a | |
12877 | pipe. The @var{command} is a shell command, to be parsed and expanded | |
12878 | by the system's command shell, @code{/bin/sh}; it should expect remote | |
12879 | protocol packets on its standard input, and send replies on its | |
12880 | standard output. You could use this to run a stand-alone simulator | |
12881 | that speaks the remote debugging protocol, to make net connections | |
12882 | using programs like @code{ssh}, or for other similar tricks. | |
12883 | ||
12884 | If @var{command} closes its standard output (perhaps by exiting), | |
12885 | @value{GDBN} will try to send it a @code{SIGTERM} signal. (If the | |
12886 | program has already exited, this will have no effect.) | |
12887 | ||
86941c27 | 12888 | @end table |
07f31aa6 | 12889 | |
86941c27 | 12890 | Once the connection has been established, you can use all the usual |
8edfe269 DJ |
12891 | commands to examine and change data. The remote program is already |
12892 | running; you can use @kbd{step} and @kbd{continue}, and you do not | |
12893 | need to use @kbd{run}. | |
07f31aa6 DJ |
12894 | |
12895 | @cindex interrupting remote programs | |
12896 | @cindex remote programs, interrupting | |
12897 | Whenever @value{GDBN} is waiting for the remote program, if you type the | |
c8aa23ab | 12898 | interrupt character (often @kbd{Ctrl-c}), @value{GDBN} attempts to stop the |
07f31aa6 DJ |
12899 | program. This may or may not succeed, depending in part on the hardware |
12900 | and the serial drivers the remote system uses. If you type the | |
12901 | interrupt character once again, @value{GDBN} displays this prompt: | |
12902 | ||
12903 | @smallexample | |
12904 | Interrupted while waiting for the program. | |
12905 | Give up (and stop debugging it)? (y or n) | |
12906 | @end smallexample | |
12907 | ||
12908 | If you type @kbd{y}, @value{GDBN} abandons the remote debugging session. | |
12909 | (If you decide you want to try again later, you can use @samp{target | |
12910 | remote} again to connect once more.) If you type @kbd{n}, @value{GDBN} | |
12911 | goes back to waiting. | |
12912 | ||
12913 | @table @code | |
12914 | @kindex detach (remote) | |
12915 | @item detach | |
12916 | When you have finished debugging the remote program, you can use the | |
12917 | @code{detach} command to release it from @value{GDBN} control. | |
12918 | Detaching from the target normally resumes its execution, but the results | |
12919 | will depend on your particular remote stub. After the @code{detach} | |
12920 | command, @value{GDBN} is free to connect to another target. | |
12921 | ||
12922 | @kindex disconnect | |
12923 | @item disconnect | |
12924 | The @code{disconnect} command behaves like @code{detach}, except that | |
12925 | the target is generally not resumed. It will wait for @value{GDBN} | |
12926 | (this instance or another one) to connect and continue debugging. After | |
12927 | the @code{disconnect} command, @value{GDBN} is again free to connect to | |
12928 | another target. | |
09d4efe1 EZ |
12929 | |
12930 | @cindex send command to remote monitor | |
fad38dfa EZ |
12931 | @cindex extend @value{GDBN} for remote targets |
12932 | @cindex add new commands for external monitor | |
09d4efe1 EZ |
12933 | @kindex monitor |
12934 | @item monitor @var{cmd} | |
fad38dfa EZ |
12935 | This command allows you to send arbitrary commands directly to the |
12936 | remote monitor. Since @value{GDBN} doesn't care about the commands it | |
12937 | sends like this, this command is the way to extend @value{GDBN}---you | |
12938 | can add new commands that only the external monitor will understand | |
12939 | and implement. | |
07f31aa6 DJ |
12940 | @end table |
12941 | ||
a6b151f1 DJ |
12942 | @node File Transfer |
12943 | @section Sending files to a remote system | |
12944 | @cindex remote target, file transfer | |
12945 | @cindex file transfer | |
12946 | @cindex sending files to remote systems | |
12947 | ||
12948 | Some remote targets offer the ability to transfer files over the same | |
12949 | connection used to communicate with @value{GDBN}. This is convenient | |
12950 | for targets accessible through other means, e.g.@: @sc{gnu}/Linux systems | |
12951 | running @code{gdbserver} over a network interface. For other targets, | |
12952 | e.g.@: embedded devices with only a single serial port, this may be | |
12953 | the only way to upload or download files. | |
12954 | ||
12955 | Not all remote targets support these commands. | |
12956 | ||
12957 | @table @code | |
12958 | @kindex remote put | |
12959 | @item remote put @var{hostfile} @var{targetfile} | |
12960 | Copy file @var{hostfile} from the host system (the machine running | |
12961 | @value{GDBN}) to @var{targetfile} on the target system. | |
12962 | ||
12963 | @kindex remote get | |
12964 | @item remote get @var{targetfile} @var{hostfile} | |
12965 | Copy file @var{targetfile} from the target system to @var{hostfile} | |
12966 | on the host system. | |
12967 | ||
12968 | @kindex remote delete | |
12969 | @item remote delete @var{targetfile} | |
12970 | Delete @var{targetfile} from the target system. | |
12971 | ||
12972 | @end table | |
12973 | ||
6f05cf9f | 12974 | @node Server |
79a6e687 | 12975 | @section Using the @code{gdbserver} Program |
6f05cf9f AC |
12976 | |
12977 | @kindex gdbserver | |
12978 | @cindex remote connection without stubs | |
12979 | @code{gdbserver} is a control program for Unix-like systems, which | |
12980 | allows you to connect your program with a remote @value{GDBN} via | |
12981 | @code{target remote}---but without linking in the usual debugging stub. | |
12982 | ||
12983 | @code{gdbserver} is not a complete replacement for the debugging stubs, | |
12984 | because it requires essentially the same operating-system facilities | |
12985 | that @value{GDBN} itself does. In fact, a system that can run | |
12986 | @code{gdbserver} to connect to a remote @value{GDBN} could also run | |
12987 | @value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless, | |
12988 | because it is a much smaller program than @value{GDBN} itself. It is | |
12989 | also easier to port than all of @value{GDBN}, so you may be able to get | |
12990 | started more quickly on a new system by using @code{gdbserver}. | |
12991 | Finally, if you develop code for real-time systems, you may find that | |
12992 | the tradeoffs involved in real-time operation make it more convenient to | |
12993 | do as much development work as possible on another system, for example | |
12994 | by cross-compiling. You can use @code{gdbserver} to make a similar | |
12995 | choice for debugging. | |
12996 | ||
12997 | @value{GDBN} and @code{gdbserver} communicate via either a serial line | |
12998 | or a TCP connection, using the standard @value{GDBN} remote serial | |
12999 | protocol. | |
13000 | ||
2d717e4f DJ |
13001 | @quotation |
13002 | @emph{Warning:} @code{gdbserver} does not have any built-in security. | |
13003 | Do not run @code{gdbserver} connected to any public network; a | |
13004 | @value{GDBN} connection to @code{gdbserver} provides access to the | |
13005 | target system with the same privileges as the user running | |
13006 | @code{gdbserver}. | |
13007 | @end quotation | |
13008 | ||
13009 | @subsection Running @code{gdbserver} | |
13010 | @cindex arguments, to @code{gdbserver} | |
13011 | ||
13012 | Run @code{gdbserver} on the target system. You need a copy of the | |
13013 | program you want to debug, including any libraries it requires. | |
6f05cf9f AC |
13014 | @code{gdbserver} does not need your program's symbol table, so you can |
13015 | strip the program if necessary to save space. @value{GDBN} on the host | |
13016 | system does all the symbol handling. | |
13017 | ||
13018 | To use the server, you must tell it how to communicate with @value{GDBN}; | |
56460a61 | 13019 | the name of your program; and the arguments for your program. The usual |
6f05cf9f AC |
13020 | syntax is: |
13021 | ||
13022 | @smallexample | |
13023 | target> gdbserver @var{comm} @var{program} [ @var{args} @dots{} ] | |
13024 | @end smallexample | |
13025 | ||
13026 | @var{comm} is either a device name (to use a serial line) or a TCP | |
13027 | hostname and portnumber. For example, to debug Emacs with the argument | |
13028 | @samp{foo.txt} and communicate with @value{GDBN} over the serial port | |
13029 | @file{/dev/com1}: | |
13030 | ||
13031 | @smallexample | |
13032 | target> gdbserver /dev/com1 emacs foo.txt | |
13033 | @end smallexample | |
13034 | ||
13035 | @code{gdbserver} waits passively for the host @value{GDBN} to communicate | |
13036 | with it. | |
13037 | ||
13038 | To use a TCP connection instead of a serial line: | |
13039 | ||
13040 | @smallexample | |
13041 | target> gdbserver host:2345 emacs foo.txt | |
13042 | @end smallexample | |
13043 | ||
13044 | The only difference from the previous example is the first argument, | |
13045 | specifying that you are communicating with the host @value{GDBN} via | |
13046 | TCP. The @samp{host:2345} argument means that @code{gdbserver} is to | |
13047 | expect a TCP connection from machine @samp{host} to local TCP port 2345. | |
13048 | (Currently, the @samp{host} part is ignored.) You can choose any number | |
13049 | you want for the port number as long as it does not conflict with any | |
13050 | TCP ports already in use on the target system (for example, @code{23} is | |
13051 | reserved for @code{telnet}).@footnote{If you choose a port number that | |
13052 | conflicts with another service, @code{gdbserver} prints an error message | |
13053 | and exits.} You must use the same port number with the host @value{GDBN} | |
13054 | @code{target remote} command. | |
13055 | ||
2d717e4f DJ |
13056 | @subsubsection Attaching to a Running Program |
13057 | ||
56460a61 DJ |
13058 | On some targets, @code{gdbserver} can also attach to running programs. |
13059 | This is accomplished via the @code{--attach} argument. The syntax is: | |
13060 | ||
13061 | @smallexample | |
2d717e4f | 13062 | target> gdbserver --attach @var{comm} @var{pid} |
56460a61 DJ |
13063 | @end smallexample |
13064 | ||
13065 | @var{pid} is the process ID of a currently running process. It isn't necessary | |
13066 | to point @code{gdbserver} at a binary for the running process. | |
13067 | ||
b1fe9455 DJ |
13068 | @pindex pidof |
13069 | @cindex attach to a program by name | |
13070 | You can debug processes by name instead of process ID if your target has the | |
13071 | @code{pidof} utility: | |
13072 | ||
13073 | @smallexample | |
2d717e4f | 13074 | target> gdbserver --attach @var{comm} `pidof @var{program}` |
b1fe9455 DJ |
13075 | @end smallexample |
13076 | ||
f822c95b | 13077 | In case more than one copy of @var{program} is running, or @var{program} |
b1fe9455 DJ |
13078 | has multiple threads, most versions of @code{pidof} support the |
13079 | @code{-s} option to only return the first process ID. | |
13080 | ||
2d717e4f DJ |
13081 | @subsubsection Multi-Process Mode for @code{gdbserver} |
13082 | @cindex gdbserver, multiple processes | |
13083 | @cindex multiple processes with gdbserver | |
13084 | ||
13085 | When you connect to @code{gdbserver} using @code{target remote}, | |
13086 | @code{gdbserver} debugs the specified program only once. When the | |
13087 | program exits, or you detach from it, @value{GDBN} closes the connection | |
13088 | and @code{gdbserver} exits. | |
13089 | ||
6e6c6f50 | 13090 | If you connect using @kbd{target extended-remote}, @code{gdbserver} |
2d717e4f DJ |
13091 | enters multi-process mode. When the debugged program exits, or you |
13092 | detach from it, @value{GDBN} stays connected to @code{gdbserver} even | |
13093 | though no program is running. The @code{run} and @code{attach} | |
13094 | commands instruct @code{gdbserver} to run or attach to a new program. | |
13095 | The @code{run} command uses @code{set remote exec-file} (@pxref{set | |
13096 | remote exec-file}) to select the program to run. Command line | |
13097 | arguments are supported, except for wildcard expansion and I/O | |
13098 | redirection (@pxref{Arguments}). | |
13099 | ||
13100 | To start @code{gdbserver} without supplying an initial command to run | |
13101 | or process ID to attach, use the @option{--multi} command line option. | |
6e6c6f50 | 13102 | Then you can connect using @kbd{target extended-remote} and start |
2d717e4f DJ |
13103 | the program you want to debug. |
13104 | ||
13105 | @code{gdbserver} does not automatically exit in multi-process mode. | |
13106 | You can terminate it by using @code{monitor exit} | |
13107 | (@pxref{Monitor Commands for gdbserver}). | |
13108 | ||
13109 | @subsubsection Other Command-Line Arguments for @code{gdbserver} | |
13110 | ||
13111 | You can include @option{--debug} on the @code{gdbserver} command line. | |
13112 | @code{gdbserver} will display extra status information about the debugging | |
13113 | process. This option is intended for @code{gdbserver} development and | |
13114 | for bug reports to the developers. | |
13115 | ||
ccd213ac DJ |
13116 | The @option{--wrapper} option specifies a wrapper to launch programs |
13117 | for debugging. The option should be followed by the name of the | |
13118 | wrapper, then any command-line arguments to pass to the wrapper, then | |
13119 | @kbd{--} indicating the end of the wrapper arguments. | |
13120 | ||
13121 | @code{gdbserver} runs the specified wrapper program with a combined | |
13122 | command line including the wrapper arguments, then the name of the | |
13123 | program to debug, then any arguments to the program. The wrapper | |
13124 | runs until it executes your program, and then @value{GDBN} gains control. | |
13125 | ||
13126 | You can use any program that eventually calls @code{execve} with | |
13127 | its arguments as a wrapper. Several standard Unix utilities do | |
13128 | this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending | |
13129 | with @code{exec "$@@"} will also work. | |
13130 | ||
13131 | For example, you can use @code{env} to pass an environment variable to | |
13132 | the debugged program, without setting the variable in @code{gdbserver}'s | |
13133 | environment: | |
13134 | ||
13135 | @smallexample | |
13136 | $ gdbserver --wrapper env LD_PRELOAD=libtest.so -- :2222 ./testprog | |
13137 | @end smallexample | |
13138 | ||
2d717e4f DJ |
13139 | @subsection Connecting to @code{gdbserver} |
13140 | ||
13141 | Run @value{GDBN} on the host system. | |
13142 | ||
13143 | First make sure you have the necessary symbol files. Load symbols for | |
f822c95b DJ |
13144 | your application using the @code{file} command before you connect. Use |
13145 | @code{set sysroot} to locate target libraries (unless your @value{GDBN} | |
2d717e4f | 13146 | was compiled with the correct sysroot using @code{--with-sysroot}). |
f822c95b DJ |
13147 | |
13148 | The symbol file and target libraries must exactly match the executable | |
13149 | and libraries on the target, with one exception: the files on the host | |
13150 | system should not be stripped, even if the files on the target system | |
13151 | are. Mismatched or missing files will lead to confusing results | |
13152 | during debugging. On @sc{gnu}/Linux targets, mismatched or missing | |
13153 | files may also prevent @code{gdbserver} from debugging multi-threaded | |
13154 | programs. | |
13155 | ||
79a6e687 | 13156 | Connect to your target (@pxref{Connecting,,Connecting to a Remote Target}). |
6f05cf9f AC |
13157 | For TCP connections, you must start up @code{gdbserver} prior to using |
13158 | the @code{target remote} command. Otherwise you may get an error whose | |
13159 | text depends on the host system, but which usually looks something like | |
2d717e4f | 13160 | @samp{Connection refused}. Don't use the @code{load} |
397ca115 | 13161 | command in @value{GDBN} when using @code{gdbserver}, since the program is |
f822c95b | 13162 | already on the target. |
07f31aa6 | 13163 | |
79a6e687 | 13164 | @subsection Monitor Commands for @code{gdbserver} |
c74d0ad8 | 13165 | @cindex monitor commands, for @code{gdbserver} |
2d717e4f | 13166 | @anchor{Monitor Commands for gdbserver} |
c74d0ad8 DJ |
13167 | |
13168 | During a @value{GDBN} session using @code{gdbserver}, you can use the | |
13169 | @code{monitor} command to send special requests to @code{gdbserver}. | |
2d717e4f | 13170 | Here are the available commands. |
c74d0ad8 DJ |
13171 | |
13172 | @table @code | |
13173 | @item monitor help | |
13174 | List the available monitor commands. | |
13175 | ||
13176 | @item monitor set debug 0 | |
13177 | @itemx monitor set debug 1 | |
13178 | Disable or enable general debugging messages. | |
13179 | ||
13180 | @item monitor set remote-debug 0 | |
13181 | @itemx monitor set remote-debug 1 | |
13182 | Disable or enable specific debugging messages associated with the remote | |
13183 | protocol (@pxref{Remote Protocol}). | |
13184 | ||
2d717e4f DJ |
13185 | @item monitor exit |
13186 | Tell gdbserver to exit immediately. This command should be followed by | |
13187 | @code{disconnect} to close the debugging session. @code{gdbserver} will | |
13188 | detach from any attached processes and kill any processes it created. | |
13189 | Use @code{monitor exit} to terminate @code{gdbserver} at the end | |
13190 | of a multi-process mode debug session. | |
13191 | ||
c74d0ad8 DJ |
13192 | @end table |
13193 | ||
79a6e687 BW |
13194 | @node Remote Configuration |
13195 | @section Remote Configuration | |
501eef12 | 13196 | |
9c16f35a EZ |
13197 | @kindex set remote |
13198 | @kindex show remote | |
13199 | This section documents the configuration options available when | |
13200 | debugging remote programs. For the options related to the File I/O | |
fc320d37 | 13201 | extensions of the remote protocol, see @ref{system, |
9c16f35a | 13202 | system-call-allowed}. |
501eef12 AC |
13203 | |
13204 | @table @code | |
9c16f35a | 13205 | @item set remoteaddresssize @var{bits} |
d3e8051b | 13206 | @cindex address size for remote targets |
9c16f35a EZ |
13207 | @cindex bits in remote address |
13208 | Set the maximum size of address in a memory packet to the specified | |
13209 | number of bits. @value{GDBN} will mask off the address bits above | |
13210 | that number, when it passes addresses to the remote target. The | |
13211 | default value is the number of bits in the target's address. | |
13212 | ||
13213 | @item show remoteaddresssize | |
13214 | Show the current value of remote address size in bits. | |
13215 | ||
13216 | @item set remotebaud @var{n} | |
13217 | @cindex baud rate for remote targets | |
13218 | Set the baud rate for the remote serial I/O to @var{n} baud. The | |
13219 | value is used to set the speed of the serial port used for debugging | |
13220 | remote targets. | |
13221 | ||
13222 | @item show remotebaud | |
13223 | Show the current speed of the remote connection. | |
13224 | ||
13225 | @item set remotebreak | |
13226 | @cindex interrupt remote programs | |
13227 | @cindex BREAK signal instead of Ctrl-C | |
9a6253be | 13228 | @anchor{set remotebreak} |
9c16f35a | 13229 | If set to on, @value{GDBN} sends a @code{BREAK} signal to the remote |
c8aa23ab | 13230 | when you type @kbd{Ctrl-c} to interrupt the program running |
9a7a1b36 | 13231 | on the remote. If set to off, @value{GDBN} sends the @samp{Ctrl-C} |
9c16f35a EZ |
13232 | character instead. The default is off, since most remote systems |
13233 | expect to see @samp{Ctrl-C} as the interrupt signal. | |
13234 | ||
13235 | @item show remotebreak | |
13236 | Show whether @value{GDBN} sends @code{BREAK} or @samp{Ctrl-C} to | |
13237 | interrupt the remote program. | |
13238 | ||
23776285 MR |
13239 | @item set remoteflow on |
13240 | @itemx set remoteflow off | |
13241 | @kindex set remoteflow | |
13242 | Enable or disable hardware flow control (@code{RTS}/@code{CTS}) | |
13243 | on the serial port used to communicate to the remote target. | |
13244 | ||
13245 | @item show remoteflow | |
13246 | @kindex show remoteflow | |
13247 | Show the current setting of hardware flow control. | |
13248 | ||
9c16f35a EZ |
13249 | @item set remotelogbase @var{base} |
13250 | Set the base (a.k.a.@: radix) of logging serial protocol | |
13251 | communications to @var{base}. Supported values of @var{base} are: | |
13252 | @code{ascii}, @code{octal}, and @code{hex}. The default is | |
13253 | @code{ascii}. | |
13254 | ||
13255 | @item show remotelogbase | |
13256 | Show the current setting of the radix for logging remote serial | |
13257 | protocol. | |
13258 | ||
13259 | @item set remotelogfile @var{file} | |
13260 | @cindex record serial communications on file | |
13261 | Record remote serial communications on the named @var{file}. The | |
13262 | default is not to record at all. | |
13263 | ||
13264 | @item show remotelogfile. | |
13265 | Show the current setting of the file name on which to record the | |
13266 | serial communications. | |
13267 | ||
13268 | @item set remotetimeout @var{num} | |
13269 | @cindex timeout for serial communications | |
13270 | @cindex remote timeout | |
13271 | Set the timeout limit to wait for the remote target to respond to | |
13272 | @var{num} seconds. The default is 2 seconds. | |
13273 | ||
13274 | @item show remotetimeout | |
13275 | Show the current number of seconds to wait for the remote target | |
13276 | responses. | |
13277 | ||
13278 | @cindex limit hardware breakpoints and watchpoints | |
13279 | @cindex remote target, limit break- and watchpoints | |
501eef12 AC |
13280 | @anchor{set remote hardware-watchpoint-limit} |
13281 | @anchor{set remote hardware-breakpoint-limit} | |
13282 | @item set remote hardware-watchpoint-limit @var{limit} | |
13283 | @itemx set remote hardware-breakpoint-limit @var{limit} | |
13284 | Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or | |
13285 | watchpoints. A limit of -1, the default, is treated as unlimited. | |
2d717e4f DJ |
13286 | |
13287 | @item set remote exec-file @var{filename} | |
13288 | @itemx show remote exec-file | |
13289 | @anchor{set remote exec-file} | |
13290 | @cindex executable file, for remote target | |
13291 | Select the file used for @code{run} with @code{target | |
13292 | extended-remote}. This should be set to a filename valid on the | |
13293 | target system. If it is not set, the target will use a default | |
13294 | filename (e.g.@: the last program run). | |
501eef12 AC |
13295 | @end table |
13296 | ||
427c3a89 DJ |
13297 | @cindex remote packets, enabling and disabling |
13298 | The @value{GDBN} remote protocol autodetects the packets supported by | |
13299 | your debugging stub. If you need to override the autodetection, you | |
13300 | can use these commands to enable or disable individual packets. Each | |
13301 | packet can be set to @samp{on} (the remote target supports this | |
13302 | packet), @samp{off} (the remote target does not support this packet), | |
13303 | or @samp{auto} (detect remote target support for this packet). They | |
13304 | all default to @samp{auto}. For more information about each packet, | |
13305 | see @ref{Remote Protocol}. | |
13306 | ||
13307 | During normal use, you should not have to use any of these commands. | |
13308 | If you do, that may be a bug in your remote debugging stub, or a bug | |
13309 | in @value{GDBN}. You may want to report the problem to the | |
13310 | @value{GDBN} developers. | |
13311 | ||
cfa9d6d9 DJ |
13312 | For each packet @var{name}, the command to enable or disable the |
13313 | packet is @code{set remote @var{name}-packet}. The available settings | |
13314 | are: | |
427c3a89 | 13315 | |
cfa9d6d9 | 13316 | @multitable @columnfractions 0.28 0.32 0.25 |
427c3a89 DJ |
13317 | @item Command Name |
13318 | @tab Remote Packet | |
13319 | @tab Related Features | |
13320 | ||
cfa9d6d9 | 13321 | @item @code{fetch-register} |
427c3a89 DJ |
13322 | @tab @code{p} |
13323 | @tab @code{info registers} | |
13324 | ||
cfa9d6d9 | 13325 | @item @code{set-register} |
427c3a89 DJ |
13326 | @tab @code{P} |
13327 | @tab @code{set} | |
13328 | ||
cfa9d6d9 | 13329 | @item @code{binary-download} |
427c3a89 DJ |
13330 | @tab @code{X} |
13331 | @tab @code{load}, @code{set} | |
13332 | ||
cfa9d6d9 | 13333 | @item @code{read-aux-vector} |
427c3a89 DJ |
13334 | @tab @code{qXfer:auxv:read} |
13335 | @tab @code{info auxv} | |
13336 | ||
cfa9d6d9 | 13337 | @item @code{symbol-lookup} |
427c3a89 DJ |
13338 | @tab @code{qSymbol} |
13339 | @tab Detecting multiple threads | |
13340 | ||
2d717e4f DJ |
13341 | @item @code{attach} |
13342 | @tab @code{vAttach} | |
13343 | @tab @code{attach} | |
13344 | ||
cfa9d6d9 | 13345 | @item @code{verbose-resume} |
427c3a89 DJ |
13346 | @tab @code{vCont} |
13347 | @tab Stepping or resuming multiple threads | |
13348 | ||
2d717e4f DJ |
13349 | @item @code{run} |
13350 | @tab @code{vRun} | |
13351 | @tab @code{run} | |
13352 | ||
cfa9d6d9 | 13353 | @item @code{software-breakpoint} |
427c3a89 DJ |
13354 | @tab @code{Z0} |
13355 | @tab @code{break} | |
13356 | ||
cfa9d6d9 | 13357 | @item @code{hardware-breakpoint} |
427c3a89 DJ |
13358 | @tab @code{Z1} |
13359 | @tab @code{hbreak} | |
13360 | ||
cfa9d6d9 | 13361 | @item @code{write-watchpoint} |
427c3a89 DJ |
13362 | @tab @code{Z2} |
13363 | @tab @code{watch} | |
13364 | ||
cfa9d6d9 | 13365 | @item @code{read-watchpoint} |
427c3a89 DJ |
13366 | @tab @code{Z3} |
13367 | @tab @code{rwatch} | |
13368 | ||
cfa9d6d9 | 13369 | @item @code{access-watchpoint} |
427c3a89 DJ |
13370 | @tab @code{Z4} |
13371 | @tab @code{awatch} | |
13372 | ||
cfa9d6d9 DJ |
13373 | @item @code{target-features} |
13374 | @tab @code{qXfer:features:read} | |
13375 | @tab @code{set architecture} | |
13376 | ||
13377 | @item @code{library-info} | |
13378 | @tab @code{qXfer:libraries:read} | |
13379 | @tab @code{info sharedlibrary} | |
13380 | ||
13381 | @item @code{memory-map} | |
13382 | @tab @code{qXfer:memory-map:read} | |
13383 | @tab @code{info mem} | |
13384 | ||
13385 | @item @code{read-spu-object} | |
13386 | @tab @code{qXfer:spu:read} | |
13387 | @tab @code{info spu} | |
13388 | ||
13389 | @item @code{write-spu-object} | |
13390 | @tab @code{qXfer:spu:write} | |
13391 | @tab @code{info spu} | |
13392 | ||
13393 | @item @code{get-thread-local-@*storage-address} | |
427c3a89 DJ |
13394 | @tab @code{qGetTLSAddr} |
13395 | @tab Displaying @code{__thread} variables | |
13396 | ||
13397 | @item @code{supported-packets} | |
13398 | @tab @code{qSupported} | |
13399 | @tab Remote communications parameters | |
13400 | ||
cfa9d6d9 | 13401 | @item @code{pass-signals} |
89be2091 DJ |
13402 | @tab @code{QPassSignals} |
13403 | @tab @code{handle @var{signal}} | |
13404 | ||
a6b151f1 DJ |
13405 | @item @code{hostio-close-packet} |
13406 | @tab @code{vFile:close} | |
13407 | @tab @code{remote get}, @code{remote put} | |
13408 | ||
13409 | @item @code{hostio-open-packet} | |
13410 | @tab @code{vFile:open} | |
13411 | @tab @code{remote get}, @code{remote put} | |
13412 | ||
13413 | @item @code{hostio-pread-packet} | |
13414 | @tab @code{vFile:pread} | |
13415 | @tab @code{remote get}, @code{remote put} | |
13416 | ||
13417 | @item @code{hostio-pwrite-packet} | |
13418 | @tab @code{vFile:pwrite} | |
13419 | @tab @code{remote get}, @code{remote put} | |
13420 | ||
13421 | @item @code{hostio-unlink-packet} | |
13422 | @tab @code{vFile:unlink} | |
13423 | @tab @code{remote delete} | |
427c3a89 DJ |
13424 | @end multitable |
13425 | ||
79a6e687 BW |
13426 | @node Remote Stub |
13427 | @section Implementing a Remote Stub | |
7a292a7a | 13428 | |
8e04817f AC |
13429 | @cindex debugging stub, example |
13430 | @cindex remote stub, example | |
13431 | @cindex stub example, remote debugging | |
13432 | The stub files provided with @value{GDBN} implement the target side of the | |
13433 | communication protocol, and the @value{GDBN} side is implemented in the | |
13434 | @value{GDBN} source file @file{remote.c}. Normally, you can simply allow | |
13435 | these subroutines to communicate, and ignore the details. (If you're | |
13436 | implementing your own stub file, you can still ignore the details: start | |
13437 | with one of the existing stub files. @file{sparc-stub.c} is the best | |
13438 | organized, and therefore the easiest to read.) | |
13439 | ||
104c1213 JM |
13440 | @cindex remote serial debugging, overview |
13441 | To debug a program running on another machine (the debugging | |
13442 | @dfn{target} machine), you must first arrange for all the usual | |
13443 | prerequisites for the program to run by itself. For example, for a C | |
13444 | program, you need: | |
c906108c | 13445 | |
104c1213 JM |
13446 | @enumerate |
13447 | @item | |
13448 | A startup routine to set up the C runtime environment; these usually | |
13449 | have a name like @file{crt0}. The startup routine may be supplied by | |
13450 | your hardware supplier, or you may have to write your own. | |
96baa820 | 13451 | |
5d161b24 | 13452 | @item |
d4f3574e | 13453 | A C subroutine library to support your program's |
104c1213 | 13454 | subroutine calls, notably managing input and output. |
96baa820 | 13455 | |
104c1213 JM |
13456 | @item |
13457 | A way of getting your program to the other machine---for example, a | |
13458 | download program. These are often supplied by the hardware | |
13459 | manufacturer, but you may have to write your own from hardware | |
13460 | documentation. | |
13461 | @end enumerate | |
96baa820 | 13462 | |
104c1213 JM |
13463 | The next step is to arrange for your program to use a serial port to |
13464 | communicate with the machine where @value{GDBN} is running (the @dfn{host} | |
13465 | machine). In general terms, the scheme looks like this: | |
96baa820 | 13466 | |
104c1213 JM |
13467 | @table @emph |
13468 | @item On the host, | |
13469 | @value{GDBN} already understands how to use this protocol; when everything | |
13470 | else is set up, you can simply use the @samp{target remote} command | |
13471 | (@pxref{Targets,,Specifying a Debugging Target}). | |
13472 | ||
13473 | @item On the target, | |
13474 | you must link with your program a few special-purpose subroutines that | |
13475 | implement the @value{GDBN} remote serial protocol. The file containing these | |
13476 | subroutines is called a @dfn{debugging stub}. | |
13477 | ||
13478 | On certain remote targets, you can use an auxiliary program | |
13479 | @code{gdbserver} instead of linking a stub into your program. | |
79a6e687 | 13480 | @xref{Server,,Using the @code{gdbserver} Program}, for details. |
104c1213 | 13481 | @end table |
96baa820 | 13482 | |
104c1213 JM |
13483 | The debugging stub is specific to the architecture of the remote |
13484 | machine; for example, use @file{sparc-stub.c} to debug programs on | |
13485 | @sc{sparc} boards. | |
96baa820 | 13486 | |
104c1213 JM |
13487 | @cindex remote serial stub list |
13488 | These working remote stubs are distributed with @value{GDBN}: | |
96baa820 | 13489 | |
104c1213 JM |
13490 | @table @code |
13491 | ||
13492 | @item i386-stub.c | |
41afff9a | 13493 | @cindex @file{i386-stub.c} |
104c1213 JM |
13494 | @cindex Intel |
13495 | @cindex i386 | |
13496 | For Intel 386 and compatible architectures. | |
13497 | ||
13498 | @item m68k-stub.c | |
41afff9a | 13499 | @cindex @file{m68k-stub.c} |
104c1213 JM |
13500 | @cindex Motorola 680x0 |
13501 | @cindex m680x0 | |
13502 | For Motorola 680x0 architectures. | |
13503 | ||
13504 | @item sh-stub.c | |
41afff9a | 13505 | @cindex @file{sh-stub.c} |
172c2a43 | 13506 | @cindex Renesas |
104c1213 | 13507 | @cindex SH |
172c2a43 | 13508 | For Renesas SH architectures. |
104c1213 JM |
13509 | |
13510 | @item sparc-stub.c | |
41afff9a | 13511 | @cindex @file{sparc-stub.c} |
104c1213 JM |
13512 | @cindex Sparc |
13513 | For @sc{sparc} architectures. | |
13514 | ||
13515 | @item sparcl-stub.c | |
41afff9a | 13516 | @cindex @file{sparcl-stub.c} |
104c1213 JM |
13517 | @cindex Fujitsu |
13518 | @cindex SparcLite | |
13519 | For Fujitsu @sc{sparclite} architectures. | |
13520 | ||
13521 | @end table | |
13522 | ||
13523 | The @file{README} file in the @value{GDBN} distribution may list other | |
13524 | recently added stubs. | |
13525 | ||
13526 | @menu | |
13527 | * Stub Contents:: What the stub can do for you | |
13528 | * Bootstrapping:: What you must do for the stub | |
13529 | * Debug Session:: Putting it all together | |
104c1213 JM |
13530 | @end menu |
13531 | ||
6d2ebf8b | 13532 | @node Stub Contents |
79a6e687 | 13533 | @subsection What the Stub Can Do for You |
104c1213 JM |
13534 | |
13535 | @cindex remote serial stub | |
13536 | The debugging stub for your architecture supplies these three | |
13537 | subroutines: | |
13538 | ||
13539 | @table @code | |
13540 | @item set_debug_traps | |
4644b6e3 | 13541 | @findex set_debug_traps |
104c1213 JM |
13542 | @cindex remote serial stub, initialization |
13543 | This routine arranges for @code{handle_exception} to run when your | |
13544 | program stops. You must call this subroutine explicitly near the | |
13545 | beginning of your program. | |
13546 | ||
13547 | @item handle_exception | |
4644b6e3 | 13548 | @findex handle_exception |
104c1213 JM |
13549 | @cindex remote serial stub, main routine |
13550 | This is the central workhorse, but your program never calls it | |
13551 | explicitly---the setup code arranges for @code{handle_exception} to | |
13552 | run when a trap is triggered. | |
13553 | ||
13554 | @code{handle_exception} takes control when your program stops during | |
13555 | execution (for example, on a breakpoint), and mediates communications | |
13556 | with @value{GDBN} on the host machine. This is where the communications | |
13557 | protocol is implemented; @code{handle_exception} acts as the @value{GDBN} | |
d4f3574e | 13558 | representative on the target machine. It begins by sending summary |
104c1213 JM |
13559 | information on the state of your program, then continues to execute, |
13560 | retrieving and transmitting any information @value{GDBN} needs, until you | |
13561 | execute a @value{GDBN} command that makes your program resume; at that point, | |
13562 | @code{handle_exception} returns control to your own code on the target | |
5d161b24 | 13563 | machine. |
104c1213 JM |
13564 | |
13565 | @item breakpoint | |
13566 | @cindex @code{breakpoint} subroutine, remote | |
13567 | Use this auxiliary subroutine to make your program contain a | |
13568 | breakpoint. Depending on the particular situation, this may be the only | |
13569 | way for @value{GDBN} to get control. For instance, if your target | |
13570 | machine has some sort of interrupt button, you won't need to call this; | |
13571 | pressing the interrupt button transfers control to | |
13572 | @code{handle_exception}---in effect, to @value{GDBN}. On some machines, | |
13573 | simply receiving characters on the serial port may also trigger a trap; | |
13574 | again, in that situation, you don't need to call @code{breakpoint} from | |
13575 | your own program---simply running @samp{target remote} from the host | |
5d161b24 | 13576 | @value{GDBN} session gets control. |
104c1213 JM |
13577 | |
13578 | Call @code{breakpoint} if none of these is true, or if you simply want | |
13579 | to make certain your program stops at a predetermined point for the | |
13580 | start of your debugging session. | |
13581 | @end table | |
13582 | ||
6d2ebf8b | 13583 | @node Bootstrapping |
79a6e687 | 13584 | @subsection What You Must Do for the Stub |
104c1213 JM |
13585 | |
13586 | @cindex remote stub, support routines | |
13587 | The debugging stubs that come with @value{GDBN} are set up for a particular | |
13588 | chip architecture, but they have no information about the rest of your | |
13589 | debugging target machine. | |
13590 | ||
13591 | First of all you need to tell the stub how to communicate with the | |
13592 | serial port. | |
13593 | ||
13594 | @table @code | |
13595 | @item int getDebugChar() | |
4644b6e3 | 13596 | @findex getDebugChar |
104c1213 JM |
13597 | Write this subroutine to read a single character from the serial port. |
13598 | It may be identical to @code{getchar} for your target system; a | |
13599 | different name is used to allow you to distinguish the two if you wish. | |
13600 | ||
13601 | @item void putDebugChar(int) | |
4644b6e3 | 13602 | @findex putDebugChar |
104c1213 | 13603 | Write this subroutine to write a single character to the serial port. |
5d161b24 | 13604 | It may be identical to @code{putchar} for your target system; a |
104c1213 JM |
13605 | different name is used to allow you to distinguish the two if you wish. |
13606 | @end table | |
13607 | ||
13608 | @cindex control C, and remote debugging | |
13609 | @cindex interrupting remote targets | |
13610 | If you want @value{GDBN} to be able to stop your program while it is | |
13611 | running, you need to use an interrupt-driven serial driver, and arrange | |
13612 | for it to stop when it receives a @code{^C} (@samp{\003}, the control-C | |
13613 | character). That is the character which @value{GDBN} uses to tell the | |
13614 | remote system to stop. | |
13615 | ||
13616 | Getting the debugging target to return the proper status to @value{GDBN} | |
13617 | probably requires changes to the standard stub; one quick and dirty way | |
13618 | is to just execute a breakpoint instruction (the ``dirty'' part is that | |
13619 | @value{GDBN} reports a @code{SIGTRAP} instead of a @code{SIGINT}). | |
13620 | ||
13621 | Other routines you need to supply are: | |
13622 | ||
13623 | @table @code | |
13624 | @item void exceptionHandler (int @var{exception_number}, void *@var{exception_address}) | |
4644b6e3 | 13625 | @findex exceptionHandler |
104c1213 JM |
13626 | Write this function to install @var{exception_address} in the exception |
13627 | handling tables. You need to do this because the stub does not have any | |
13628 | way of knowing what the exception handling tables on your target system | |
13629 | are like (for example, the processor's table might be in @sc{rom}, | |
13630 | containing entries which point to a table in @sc{ram}). | |
13631 | @var{exception_number} is the exception number which should be changed; | |
13632 | its meaning is architecture-dependent (for example, different numbers | |
13633 | might represent divide by zero, misaligned access, etc). When this | |
13634 | exception occurs, control should be transferred directly to | |
13635 | @var{exception_address}, and the processor state (stack, registers, | |
13636 | and so on) should be just as it is when a processor exception occurs. So if | |
13637 | you want to use a jump instruction to reach @var{exception_address}, it | |
13638 | should be a simple jump, not a jump to subroutine. | |
13639 | ||
13640 | For the 386, @var{exception_address} should be installed as an interrupt | |
13641 | gate so that interrupts are masked while the handler runs. The gate | |
13642 | should be at privilege level 0 (the most privileged level). The | |
13643 | @sc{sparc} and 68k stubs are able to mask interrupts themselves without | |
13644 | help from @code{exceptionHandler}. | |
13645 | ||
13646 | @item void flush_i_cache() | |
4644b6e3 | 13647 | @findex flush_i_cache |
d4f3574e | 13648 | On @sc{sparc} and @sc{sparclite} only, write this subroutine to flush the |
104c1213 JM |
13649 | instruction cache, if any, on your target machine. If there is no |
13650 | instruction cache, this subroutine may be a no-op. | |
13651 | ||
13652 | On target machines that have instruction caches, @value{GDBN} requires this | |
13653 | function to make certain that the state of your program is stable. | |
13654 | @end table | |
13655 | ||
13656 | @noindent | |
13657 | You must also make sure this library routine is available: | |
13658 | ||
13659 | @table @code | |
13660 | @item void *memset(void *, int, int) | |
4644b6e3 | 13661 | @findex memset |
104c1213 JM |
13662 | This is the standard library function @code{memset} that sets an area of |
13663 | memory to a known value. If you have one of the free versions of | |
13664 | @code{libc.a}, @code{memset} can be found there; otherwise, you must | |
13665 | either obtain it from your hardware manufacturer, or write your own. | |
13666 | @end table | |
13667 | ||
13668 | If you do not use the GNU C compiler, you may need other standard | |
13669 | library subroutines as well; this varies from one stub to another, | |
13670 | but in general the stubs are likely to use any of the common library | |
e22ea452 | 13671 | subroutines which @code{@value{NGCC}} generates as inline code. |
104c1213 JM |
13672 | |
13673 | ||
6d2ebf8b | 13674 | @node Debug Session |
79a6e687 | 13675 | @subsection Putting it All Together |
104c1213 JM |
13676 | |
13677 | @cindex remote serial debugging summary | |
13678 | In summary, when your program is ready to debug, you must follow these | |
13679 | steps. | |
13680 | ||
13681 | @enumerate | |
13682 | @item | |
6d2ebf8b | 13683 | Make sure you have defined the supporting low-level routines |
79a6e687 | 13684 | (@pxref{Bootstrapping,,What You Must Do for the Stub}): |
104c1213 JM |
13685 | @display |
13686 | @code{getDebugChar}, @code{putDebugChar}, | |
13687 | @code{flush_i_cache}, @code{memset}, @code{exceptionHandler}. | |
13688 | @end display | |
13689 | ||
13690 | @item | |
13691 | Insert these lines near the top of your program: | |
13692 | ||
474c8240 | 13693 | @smallexample |
104c1213 JM |
13694 | set_debug_traps(); |
13695 | breakpoint(); | |
474c8240 | 13696 | @end smallexample |
104c1213 JM |
13697 | |
13698 | @item | |
13699 | For the 680x0 stub only, you need to provide a variable called | |
13700 | @code{exceptionHook}. Normally you just use: | |
13701 | ||
474c8240 | 13702 | @smallexample |
104c1213 | 13703 | void (*exceptionHook)() = 0; |
474c8240 | 13704 | @end smallexample |
104c1213 | 13705 | |
d4f3574e | 13706 | @noindent |
104c1213 | 13707 | but if before calling @code{set_debug_traps}, you set it to point to a |
598ca718 | 13708 | function in your program, that function is called when |
104c1213 JM |
13709 | @code{@value{GDBN}} continues after stopping on a trap (for example, bus |
13710 | error). The function indicated by @code{exceptionHook} is called with | |
13711 | one parameter: an @code{int} which is the exception number. | |
13712 | ||
13713 | @item | |
13714 | Compile and link together: your program, the @value{GDBN} debugging stub for | |
13715 | your target architecture, and the supporting subroutines. | |
13716 | ||
13717 | @item | |
13718 | Make sure you have a serial connection between your target machine and | |
13719 | the @value{GDBN} host, and identify the serial port on the host. | |
13720 | ||
13721 | @item | |
13722 | @c The "remote" target now provides a `load' command, so we should | |
13723 | @c document that. FIXME. | |
13724 | Download your program to your target machine (or get it there by | |
13725 | whatever means the manufacturer provides), and start it. | |
13726 | ||
13727 | @item | |
07f31aa6 | 13728 | Start @value{GDBN} on the host, and connect to the target |
79a6e687 | 13729 | (@pxref{Connecting,,Connecting to a Remote Target}). |
9db8d71f | 13730 | |
104c1213 JM |
13731 | @end enumerate |
13732 | ||
8e04817f AC |
13733 | @node Configurations |
13734 | @chapter Configuration-Specific Information | |
104c1213 | 13735 | |
8e04817f AC |
13736 | While nearly all @value{GDBN} commands are available for all native and |
13737 | cross versions of the debugger, there are some exceptions. This chapter | |
13738 | describes things that are only available in certain configurations. | |
104c1213 | 13739 | |
8e04817f AC |
13740 | There are three major categories of configurations: native |
13741 | configurations, where the host and target are the same, embedded | |
13742 | operating system configurations, which are usually the same for several | |
13743 | different processor architectures, and bare embedded processors, which | |
13744 | are quite different from each other. | |
104c1213 | 13745 | |
8e04817f AC |
13746 | @menu |
13747 | * Native:: | |
13748 | * Embedded OS:: | |
13749 | * Embedded Processors:: | |
13750 | * Architectures:: | |
13751 | @end menu | |
104c1213 | 13752 | |
8e04817f AC |
13753 | @node Native |
13754 | @section Native | |
104c1213 | 13755 | |
8e04817f AC |
13756 | This section describes details specific to particular native |
13757 | configurations. | |
6cf7e474 | 13758 | |
8e04817f AC |
13759 | @menu |
13760 | * HP-UX:: HP-UX | |
7561d450 | 13761 | * BSD libkvm Interface:: Debugging BSD kernel memory images |
8e04817f AC |
13762 | * SVR4 Process Information:: SVR4 process information |
13763 | * DJGPP Native:: Features specific to the DJGPP port | |
78c47bea | 13764 | * Cygwin Native:: Features specific to the Cygwin port |
14d6dd68 | 13765 | * Hurd Native:: Features specific to @sc{gnu} Hurd |
a64548ea | 13766 | * Neutrino:: Features specific to QNX Neutrino |
8e04817f | 13767 | @end menu |
6cf7e474 | 13768 | |
8e04817f AC |
13769 | @node HP-UX |
13770 | @subsection HP-UX | |
104c1213 | 13771 | |
8e04817f AC |
13772 | On HP-UX systems, if you refer to a function or variable name that |
13773 | begins with a dollar sign, @value{GDBN} searches for a user or system | |
13774 | name first, before it searches for a convenience variable. | |
104c1213 | 13775 | |
9c16f35a | 13776 | |
7561d450 MK |
13777 | @node BSD libkvm Interface |
13778 | @subsection BSD libkvm Interface | |
13779 | ||
13780 | @cindex libkvm | |
13781 | @cindex kernel memory image | |
13782 | @cindex kernel crash dump | |
13783 | ||
13784 | BSD-derived systems (FreeBSD/NetBSD/OpenBSD) have a kernel memory | |
13785 | interface that provides a uniform interface for accessing kernel virtual | |
13786 | memory images, including live systems and crash dumps. @value{GDBN} | |
13787 | uses this interface to allow you to debug live kernels and kernel crash | |
13788 | dumps on many native BSD configurations. This is implemented as a | |
13789 | special @code{kvm} debugging target. For debugging a live system, load | |
13790 | the currently running kernel into @value{GDBN} and connect to the | |
13791 | @code{kvm} target: | |
13792 | ||
13793 | @smallexample | |
13794 | (@value{GDBP}) @b{target kvm} | |
13795 | @end smallexample | |
13796 | ||
13797 | For debugging crash dumps, provide the file name of the crash dump as an | |
13798 | argument: | |
13799 | ||
13800 | @smallexample | |
13801 | (@value{GDBP}) @b{target kvm /var/crash/bsd.0} | |
13802 | @end smallexample | |
13803 | ||
13804 | Once connected to the @code{kvm} target, the following commands are | |
13805 | available: | |
13806 | ||
13807 | @table @code | |
13808 | @kindex kvm | |
13809 | @item kvm pcb | |
721c2651 | 13810 | Set current context from the @dfn{Process Control Block} (PCB) address. |
7561d450 MK |
13811 | |
13812 | @item kvm proc | |
13813 | Set current context from proc address. This command isn't available on | |
13814 | modern FreeBSD systems. | |
13815 | @end table | |
13816 | ||
8e04817f | 13817 | @node SVR4 Process Information |
79a6e687 | 13818 | @subsection SVR4 Process Information |
60bf7e09 EZ |
13819 | @cindex /proc |
13820 | @cindex examine process image | |
13821 | @cindex process info via @file{/proc} | |
104c1213 | 13822 | |
60bf7e09 EZ |
13823 | Many versions of SVR4 and compatible systems provide a facility called |
13824 | @samp{/proc} that can be used to examine the image of a running | |
13825 | process using file-system subroutines. If @value{GDBN} is configured | |
13826 | for an operating system with this facility, the command @code{info | |
13827 | proc} is available to report information about the process running | |
13828 | your program, or about any process running on your system. @code{info | |
13829 | proc} works only on SVR4 systems that include the @code{procfs} code. | |
13830 | This includes, as of this writing, @sc{gnu}/Linux, OSF/1 (Digital | |
13831 | Unix), Solaris, Irix, and Unixware, but not HP-UX, for example. | |
104c1213 | 13832 | |
8e04817f AC |
13833 | @table @code |
13834 | @kindex info proc | |
60bf7e09 | 13835 | @cindex process ID |
8e04817f | 13836 | @item info proc |
60bf7e09 EZ |
13837 | @itemx info proc @var{process-id} |
13838 | Summarize available information about any running process. If a | |
13839 | process ID is specified by @var{process-id}, display information about | |
13840 | that process; otherwise display information about the program being | |
13841 | debugged. The summary includes the debugged process ID, the command | |
13842 | line used to invoke it, its current working directory, and its | |
13843 | executable file's absolute file name. | |
13844 | ||
13845 | On some systems, @var{process-id} can be of the form | |
13846 | @samp{[@var{pid}]/@var{tid}} which specifies a certain thread ID | |
13847 | within a process. If the optional @var{pid} part is missing, it means | |
13848 | a thread from the process being debugged (the leading @samp{/} still | |
13849 | needs to be present, or else @value{GDBN} will interpret the number as | |
13850 | a process ID rather than a thread ID). | |
6cf7e474 | 13851 | |
8e04817f | 13852 | @item info proc mappings |
60bf7e09 EZ |
13853 | @cindex memory address space mappings |
13854 | Report the memory address space ranges accessible in the program, with | |
13855 | information on whether the process has read, write, or execute access | |
13856 | rights to each range. On @sc{gnu}/Linux systems, each memory range | |
13857 | includes the object file which is mapped to that range, instead of the | |
13858 | memory access rights to that range. | |
13859 | ||
13860 | @item info proc stat | |
13861 | @itemx info proc status | |
13862 | @cindex process detailed status information | |
13863 | These subcommands are specific to @sc{gnu}/Linux systems. They show | |
13864 | the process-related information, including the user ID and group ID; | |
13865 | how many threads are there in the process; its virtual memory usage; | |
13866 | the signals that are pending, blocked, and ignored; its TTY; its | |
13867 | consumption of system and user time; its stack size; its @samp{nice} | |
2eecc4ab | 13868 | value; etc. For more information, see the @samp{proc} man page |
60bf7e09 EZ |
13869 | (type @kbd{man 5 proc} from your shell prompt). |
13870 | ||
13871 | @item info proc all | |
13872 | Show all the information about the process described under all of the | |
13873 | above @code{info proc} subcommands. | |
13874 | ||
8e04817f AC |
13875 | @ignore |
13876 | @comment These sub-options of 'info proc' were not included when | |
13877 | @comment procfs.c was re-written. Keep their descriptions around | |
13878 | @comment against the day when someone finds the time to put them back in. | |
13879 | @kindex info proc times | |
13880 | @item info proc times | |
13881 | Starting time, user CPU time, and system CPU time for your program and | |
13882 | its children. | |
6cf7e474 | 13883 | |
8e04817f AC |
13884 | @kindex info proc id |
13885 | @item info proc id | |
13886 | Report on the process IDs related to your program: its own process ID, | |
13887 | the ID of its parent, the process group ID, and the session ID. | |
8e04817f | 13888 | @end ignore |
721c2651 EZ |
13889 | |
13890 | @item set procfs-trace | |
13891 | @kindex set procfs-trace | |
13892 | @cindex @code{procfs} API calls | |
13893 | This command enables and disables tracing of @code{procfs} API calls. | |
13894 | ||
13895 | @item show procfs-trace | |
13896 | @kindex show procfs-trace | |
13897 | Show the current state of @code{procfs} API call tracing. | |
13898 | ||
13899 | @item set procfs-file @var{file} | |
13900 | @kindex set procfs-file | |
13901 | Tell @value{GDBN} to write @code{procfs} API trace to the named | |
13902 | @var{file}. @value{GDBN} appends the trace info to the previous | |
13903 | contents of the file. The default is to display the trace on the | |
13904 | standard output. | |
13905 | ||
13906 | @item show procfs-file | |
13907 | @kindex show procfs-file | |
13908 | Show the file to which @code{procfs} API trace is written. | |
13909 | ||
13910 | @item proc-trace-entry | |
13911 | @itemx proc-trace-exit | |
13912 | @itemx proc-untrace-entry | |
13913 | @itemx proc-untrace-exit | |
13914 | @kindex proc-trace-entry | |
13915 | @kindex proc-trace-exit | |
13916 | @kindex proc-untrace-entry | |
13917 | @kindex proc-untrace-exit | |
13918 | These commands enable and disable tracing of entries into and exits | |
13919 | from the @code{syscall} interface. | |
13920 | ||
13921 | @item info pidlist | |
13922 | @kindex info pidlist | |
13923 | @cindex process list, QNX Neutrino | |
13924 | For QNX Neutrino only, this command displays the list of all the | |
13925 | processes and all the threads within each process. | |
13926 | ||
13927 | @item info meminfo | |
13928 | @kindex info meminfo | |
13929 | @cindex mapinfo list, QNX Neutrino | |
13930 | For QNX Neutrino only, this command displays the list of all mapinfos. | |
8e04817f | 13931 | @end table |
104c1213 | 13932 | |
8e04817f AC |
13933 | @node DJGPP Native |
13934 | @subsection Features for Debugging @sc{djgpp} Programs | |
13935 | @cindex @sc{djgpp} debugging | |
13936 | @cindex native @sc{djgpp} debugging | |
13937 | @cindex MS-DOS-specific commands | |
104c1213 | 13938 | |
514c4d71 EZ |
13939 | @cindex DPMI |
13940 | @sc{djgpp} is a port of the @sc{gnu} development tools to MS-DOS and | |
8e04817f AC |
13941 | MS-Windows. @sc{djgpp} programs are 32-bit protected-mode programs |
13942 | that use the @dfn{DPMI} (DOS Protected-Mode Interface) API to run on | |
13943 | top of real-mode DOS systems and their emulations. | |
104c1213 | 13944 | |
8e04817f AC |
13945 | @value{GDBN} supports native debugging of @sc{djgpp} programs, and |
13946 | defines a few commands specific to the @sc{djgpp} port. This | |
13947 | subsection describes those commands. | |
104c1213 | 13948 | |
8e04817f AC |
13949 | @table @code |
13950 | @kindex info dos | |
13951 | @item info dos | |
13952 | This is a prefix of @sc{djgpp}-specific commands which print | |
13953 | information about the target system and important OS structures. | |
f1251bdd | 13954 | |
8e04817f AC |
13955 | @kindex sysinfo |
13956 | @cindex MS-DOS system info | |
13957 | @cindex free memory information (MS-DOS) | |
13958 | @item info dos sysinfo | |
13959 | This command displays assorted information about the underlying | |
13960 | platform: the CPU type and features, the OS version and flavor, the | |
13961 | DPMI version, and the available conventional and DPMI memory. | |
104c1213 | 13962 | |
8e04817f AC |
13963 | @cindex GDT |
13964 | @cindex LDT | |
13965 | @cindex IDT | |
13966 | @cindex segment descriptor tables | |
13967 | @cindex descriptor tables display | |
13968 | @item info dos gdt | |
13969 | @itemx info dos ldt | |
13970 | @itemx info dos idt | |
13971 | These 3 commands display entries from, respectively, Global, Local, | |
13972 | and Interrupt Descriptor Tables (GDT, LDT, and IDT). The descriptor | |
13973 | tables are data structures which store a descriptor for each segment | |
13974 | that is currently in use. The segment's selector is an index into a | |
13975 | descriptor table; the table entry for that index holds the | |
13976 | descriptor's base address and limit, and its attributes and access | |
13977 | rights. | |
104c1213 | 13978 | |
8e04817f AC |
13979 | A typical @sc{djgpp} program uses 3 segments: a code segment, a data |
13980 | segment (used for both data and the stack), and a DOS segment (which | |
13981 | allows access to DOS/BIOS data structures and absolute addresses in | |
13982 | conventional memory). However, the DPMI host will usually define | |
13983 | additional segments in order to support the DPMI environment. | |
d4f3574e | 13984 | |
8e04817f AC |
13985 | @cindex garbled pointers |
13986 | These commands allow to display entries from the descriptor tables. | |
13987 | Without an argument, all entries from the specified table are | |
13988 | displayed. An argument, which should be an integer expression, means | |
13989 | display a single entry whose index is given by the argument. For | |
13990 | example, here's a convenient way to display information about the | |
13991 | debugged program's data segment: | |
104c1213 | 13992 | |
8e04817f AC |
13993 | @smallexample |
13994 | @exdent @code{(@value{GDBP}) info dos ldt $ds} | |
13995 | @exdent @code{0x13f: base=0x11970000 limit=0x0009ffff 32-Bit Data (Read/Write, Exp-up)} | |
13996 | @end smallexample | |
104c1213 | 13997 | |
8e04817f AC |
13998 | @noindent |
13999 | This comes in handy when you want to see whether a pointer is outside | |
14000 | the data segment's limit (i.e.@: @dfn{garbled}). | |
104c1213 | 14001 | |
8e04817f AC |
14002 | @cindex page tables display (MS-DOS) |
14003 | @item info dos pde | |
14004 | @itemx info dos pte | |
14005 | These two commands display entries from, respectively, the Page | |
14006 | Directory and the Page Tables. Page Directories and Page Tables are | |
14007 | data structures which control how virtual memory addresses are mapped | |
14008 | into physical addresses. A Page Table includes an entry for every | |
14009 | page of memory that is mapped into the program's address space; there | |
14010 | may be several Page Tables, each one holding up to 4096 entries. A | |
14011 | Page Directory has up to 4096 entries, one each for every Page Table | |
14012 | that is currently in use. | |
104c1213 | 14013 | |
8e04817f AC |
14014 | Without an argument, @kbd{info dos pde} displays the entire Page |
14015 | Directory, and @kbd{info dos pte} displays all the entries in all of | |
14016 | the Page Tables. An argument, an integer expression, given to the | |
14017 | @kbd{info dos pde} command means display only that entry from the Page | |
14018 | Directory table. An argument given to the @kbd{info dos pte} command | |
14019 | means display entries from a single Page Table, the one pointed to by | |
14020 | the specified entry in the Page Directory. | |
104c1213 | 14021 | |
8e04817f AC |
14022 | @cindex direct memory access (DMA) on MS-DOS |
14023 | These commands are useful when your program uses @dfn{DMA} (Direct | |
14024 | Memory Access), which needs physical addresses to program the DMA | |
14025 | controller. | |
104c1213 | 14026 | |
8e04817f | 14027 | These commands are supported only with some DPMI servers. |
104c1213 | 14028 | |
8e04817f AC |
14029 | @cindex physical address from linear address |
14030 | @item info dos address-pte @var{addr} | |
14031 | This command displays the Page Table entry for a specified linear | |
514c4d71 EZ |
14032 | address. The argument @var{addr} is a linear address which should |
14033 | already have the appropriate segment's base address added to it, | |
14034 | because this command accepts addresses which may belong to @emph{any} | |
14035 | segment. For example, here's how to display the Page Table entry for | |
14036 | the page where a variable @code{i} is stored: | |
104c1213 | 14037 | |
b383017d | 14038 | @smallexample |
8e04817f AC |
14039 | @exdent @code{(@value{GDBP}) info dos address-pte __djgpp_base_address + (char *)&i} |
14040 | @exdent @code{Page Table entry for address 0x11a00d30:} | |
b383017d | 14041 | @exdent @code{Base=0x02698000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0xd30} |
8e04817f | 14042 | @end smallexample |
104c1213 | 14043 | |
8e04817f AC |
14044 | @noindent |
14045 | This says that @code{i} is stored at offset @code{0xd30} from the page | |
514c4d71 | 14046 | whose physical base address is @code{0x02698000}, and shows all the |
8e04817f | 14047 | attributes of that page. |
104c1213 | 14048 | |
8e04817f AC |
14049 | Note that you must cast the addresses of variables to a @code{char *}, |
14050 | since otherwise the value of @code{__djgpp_base_address}, the base | |
14051 | address of all variables and functions in a @sc{djgpp} program, will | |
14052 | be added using the rules of C pointer arithmetics: if @code{i} is | |
14053 | declared an @code{int}, @value{GDBN} will add 4 times the value of | |
14054 | @code{__djgpp_base_address} to the address of @code{i}. | |
104c1213 | 14055 | |
8e04817f AC |
14056 | Here's another example, it displays the Page Table entry for the |
14057 | transfer buffer: | |
104c1213 | 14058 | |
8e04817f AC |
14059 | @smallexample |
14060 | @exdent @code{(@value{GDBP}) info dos address-pte *((unsigned *)&_go32_info_block + 3)} | |
14061 | @exdent @code{Page Table entry for address 0x29110:} | |
14062 | @exdent @code{Base=0x00029000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0x110} | |
14063 | @end smallexample | |
104c1213 | 14064 | |
8e04817f AC |
14065 | @noindent |
14066 | (The @code{+ 3} offset is because the transfer buffer's address is the | |
514c4d71 EZ |
14067 | 3rd member of the @code{_go32_info_block} structure.) The output |
14068 | clearly shows that this DPMI server maps the addresses in conventional | |
14069 | memory 1:1, i.e.@: the physical (@code{0x00029000} + @code{0x110}) and | |
14070 | linear (@code{0x29110}) addresses are identical. | |
104c1213 | 14071 | |
8e04817f AC |
14072 | This command is supported only with some DPMI servers. |
14073 | @end table | |
104c1213 | 14074 | |
c45da7e6 | 14075 | @cindex DOS serial data link, remote debugging |
a8f24a35 EZ |
14076 | In addition to native debugging, the DJGPP port supports remote |
14077 | debugging via a serial data link. The following commands are specific | |
14078 | to remote serial debugging in the DJGPP port of @value{GDBN}. | |
14079 | ||
14080 | @table @code | |
14081 | @kindex set com1base | |
14082 | @kindex set com1irq | |
14083 | @kindex set com2base | |
14084 | @kindex set com2irq | |
14085 | @kindex set com3base | |
14086 | @kindex set com3irq | |
14087 | @kindex set com4base | |
14088 | @kindex set com4irq | |
14089 | @item set com1base @var{addr} | |
14090 | This command sets the base I/O port address of the @file{COM1} serial | |
14091 | port. | |
14092 | ||
14093 | @item set com1irq @var{irq} | |
14094 | This command sets the @dfn{Interrupt Request} (@code{IRQ}) line to use | |
14095 | for the @file{COM1} serial port. | |
14096 | ||
14097 | There are similar commands @samp{set com2base}, @samp{set com3irq}, | |
14098 | etc.@: for setting the port address and the @code{IRQ} lines for the | |
14099 | other 3 COM ports. | |
14100 | ||
14101 | @kindex show com1base | |
14102 | @kindex show com1irq | |
14103 | @kindex show com2base | |
14104 | @kindex show com2irq | |
14105 | @kindex show com3base | |
14106 | @kindex show com3irq | |
14107 | @kindex show com4base | |
14108 | @kindex show com4irq | |
14109 | The related commands @samp{show com1base}, @samp{show com1irq} etc.@: | |
14110 | display the current settings of the base address and the @code{IRQ} | |
14111 | lines used by the COM ports. | |
c45da7e6 EZ |
14112 | |
14113 | @item info serial | |
14114 | @kindex info serial | |
14115 | @cindex DOS serial port status | |
14116 | This command prints the status of the 4 DOS serial ports. For each | |
14117 | port, it prints whether it's active or not, its I/O base address and | |
14118 | IRQ number, whether it uses a 16550-style FIFO, its baudrate, and the | |
14119 | counts of various errors encountered so far. | |
a8f24a35 EZ |
14120 | @end table |
14121 | ||
14122 | ||
78c47bea | 14123 | @node Cygwin Native |
79a6e687 | 14124 | @subsection Features for Debugging MS Windows PE Executables |
78c47bea PM |
14125 | @cindex MS Windows debugging |
14126 | @cindex native Cygwin debugging | |
14127 | @cindex Cygwin-specific commands | |
14128 | ||
be448670 | 14129 | @value{GDBN} supports native debugging of MS Windows programs, including |
db2e3e2e BW |
14130 | DLLs with and without symbolic debugging information. There are various |
14131 | additional Cygwin-specific commands, described in this section. | |
14132 | Working with DLLs that have no debugging symbols is described in | |
14133 | @ref{Non-debug DLL Symbols}. | |
78c47bea PM |
14134 | |
14135 | @table @code | |
14136 | @kindex info w32 | |
14137 | @item info w32 | |
db2e3e2e | 14138 | This is a prefix of MS Windows-specific commands which print |
78c47bea PM |
14139 | information about the target system and important OS structures. |
14140 | ||
14141 | @item info w32 selector | |
14142 | This command displays information returned by | |
14143 | the Win32 API @code{GetThreadSelectorEntry} function. | |
14144 | It takes an optional argument that is evaluated to | |
14145 | a long value to give the information about this given selector. | |
14146 | Without argument, this command displays information | |
d3e8051b | 14147 | about the six segment registers. |
78c47bea PM |
14148 | |
14149 | @kindex info dll | |
14150 | @item info dll | |
db2e3e2e | 14151 | This is a Cygwin-specific alias of @code{info shared}. |
78c47bea PM |
14152 | |
14153 | @kindex dll-symbols | |
14154 | @item dll-symbols | |
14155 | This command loads symbols from a dll similarly to | |
14156 | add-sym command but without the need to specify a base address. | |
14157 | ||
be90c084 | 14158 | @kindex set cygwin-exceptions |
e16b02ee EZ |
14159 | @cindex debugging the Cygwin DLL |
14160 | @cindex Cygwin DLL, debugging | |
be90c084 | 14161 | @item set cygwin-exceptions @var{mode} |
e16b02ee EZ |
14162 | If @var{mode} is @code{on}, @value{GDBN} will break on exceptions that |
14163 | happen inside the Cygwin DLL. If @var{mode} is @code{off}, | |
14164 | @value{GDBN} will delay recognition of exceptions, and may ignore some | |
14165 | exceptions which seem to be caused by internal Cygwin DLL | |
14166 | ``bookkeeping''. This option is meant primarily for debugging the | |
14167 | Cygwin DLL itself; the default value is @code{off} to avoid annoying | |
14168 | @value{GDBN} users with false @code{SIGSEGV} signals. | |
be90c084 CF |
14169 | |
14170 | @kindex show cygwin-exceptions | |
14171 | @item show cygwin-exceptions | |
e16b02ee EZ |
14172 | Displays whether @value{GDBN} will break on exceptions that happen |
14173 | inside the Cygwin DLL itself. | |
be90c084 | 14174 | |
b383017d | 14175 | @kindex set new-console |
78c47bea | 14176 | @item set new-console @var{mode} |
b383017d | 14177 | If @var{mode} is @code{on} the debuggee will |
78c47bea PM |
14178 | be started in a new console on next start. |
14179 | If @var{mode} is @code{off}i, the debuggee will | |
14180 | be started in the same console as the debugger. | |
14181 | ||
14182 | @kindex show new-console | |
14183 | @item show new-console | |
14184 | Displays whether a new console is used | |
14185 | when the debuggee is started. | |
14186 | ||
14187 | @kindex set new-group | |
14188 | @item set new-group @var{mode} | |
14189 | This boolean value controls whether the debuggee should | |
14190 | start a new group or stay in the same group as the debugger. | |
14191 | This affects the way the Windows OS handles | |
c8aa23ab | 14192 | @samp{Ctrl-C}. |
78c47bea PM |
14193 | |
14194 | @kindex show new-group | |
14195 | @item show new-group | |
14196 | Displays current value of new-group boolean. | |
14197 | ||
14198 | @kindex set debugevents | |
14199 | @item set debugevents | |
219eec71 EZ |
14200 | This boolean value adds debug output concerning kernel events related |
14201 | to the debuggee seen by the debugger. This includes events that | |
14202 | signal thread and process creation and exit, DLL loading and | |
14203 | unloading, console interrupts, and debugging messages produced by the | |
14204 | Windows @code{OutputDebugString} API call. | |
78c47bea PM |
14205 | |
14206 | @kindex set debugexec | |
14207 | @item set debugexec | |
b383017d | 14208 | This boolean value adds debug output concerning execute events |
219eec71 | 14209 | (such as resume thread) seen by the debugger. |
78c47bea PM |
14210 | |
14211 | @kindex set debugexceptions | |
14212 | @item set debugexceptions | |
219eec71 EZ |
14213 | This boolean value adds debug output concerning exceptions in the |
14214 | debuggee seen by the debugger. | |
78c47bea PM |
14215 | |
14216 | @kindex set debugmemory | |
14217 | @item set debugmemory | |
219eec71 EZ |
14218 | This boolean value adds debug output concerning debuggee memory reads |
14219 | and writes by the debugger. | |
78c47bea PM |
14220 | |
14221 | @kindex set shell | |
14222 | @item set shell | |
14223 | This boolean values specifies whether the debuggee is called | |
14224 | via a shell or directly (default value is on). | |
14225 | ||
14226 | @kindex show shell | |
14227 | @item show shell | |
14228 | Displays if the debuggee will be started with a shell. | |
14229 | ||
14230 | @end table | |
14231 | ||
be448670 | 14232 | @menu |
79a6e687 | 14233 | * Non-debug DLL Symbols:: Support for DLLs without debugging symbols |
be448670 CF |
14234 | @end menu |
14235 | ||
79a6e687 BW |
14236 | @node Non-debug DLL Symbols |
14237 | @subsubsection Support for DLLs without Debugging Symbols | |
be448670 CF |
14238 | @cindex DLLs with no debugging symbols |
14239 | @cindex Minimal symbols and DLLs | |
14240 | ||
14241 | Very often on windows, some of the DLLs that your program relies on do | |
14242 | not include symbolic debugging information (for example, | |
db2e3e2e | 14243 | @file{kernel32.dll}). When @value{GDBN} doesn't recognize any debugging |
be448670 | 14244 | symbols in a DLL, it relies on the minimal amount of symbolic |
db2e3e2e | 14245 | information contained in the DLL's export table. This section |
be448670 CF |
14246 | describes working with such symbols, known internally to @value{GDBN} as |
14247 | ``minimal symbols''. | |
14248 | ||
14249 | Note that before the debugged program has started execution, no DLLs | |
db2e3e2e | 14250 | will have been loaded. The easiest way around this problem is simply to |
be448670 | 14251 | start the program --- either by setting a breakpoint or letting the |
db2e3e2e | 14252 | program run once to completion. It is also possible to force |
be448670 | 14253 | @value{GDBN} to load a particular DLL before starting the executable --- |
12c27660 | 14254 | see the shared library information in @ref{Files}, or the |
db2e3e2e | 14255 | @code{dll-symbols} command in @ref{Cygwin Native}. Currently, |
be448670 CF |
14256 | explicitly loading symbols from a DLL with no debugging information will |
14257 | cause the symbol names to be duplicated in @value{GDBN}'s lookup table, | |
14258 | which may adversely affect symbol lookup performance. | |
14259 | ||
79a6e687 | 14260 | @subsubsection DLL Name Prefixes |
be448670 CF |
14261 | |
14262 | In keeping with the naming conventions used by the Microsoft debugging | |
14263 | tools, DLL export symbols are made available with a prefix based on the | |
14264 | DLL name, for instance @code{KERNEL32!CreateFileA}. The plain name is | |
14265 | also entered into the symbol table, so @code{CreateFileA} is often | |
14266 | sufficient. In some cases there will be name clashes within a program | |
14267 | (particularly if the executable itself includes full debugging symbols) | |
14268 | necessitating the use of the fully qualified name when referring to the | |
14269 | contents of the DLL. Use single-quotes around the name to avoid the | |
14270 | exclamation mark (``!'') being interpreted as a language operator. | |
14271 | ||
14272 | Note that the internal name of the DLL may be all upper-case, even | |
14273 | though the file name of the DLL is lower-case, or vice-versa. Since | |
14274 | symbols within @value{GDBN} are @emph{case-sensitive} this may cause | |
14275 | some confusion. If in doubt, try the @code{info functions} and | |
0869d01b NR |
14276 | @code{info variables} commands or even @code{maint print msymbols} |
14277 | (@pxref{Symbols}). Here's an example: | |
be448670 CF |
14278 | |
14279 | @smallexample | |
f7dc1244 | 14280 | (@value{GDBP}) info function CreateFileA |
be448670 CF |
14281 | All functions matching regular expression "CreateFileA": |
14282 | ||
14283 | Non-debugging symbols: | |
14284 | 0x77e885f4 CreateFileA | |
14285 | 0x77e885f4 KERNEL32!CreateFileA | |
14286 | @end smallexample | |
14287 | ||
14288 | @smallexample | |
f7dc1244 | 14289 | (@value{GDBP}) info function ! |
be448670 CF |
14290 | All functions matching regular expression "!": |
14291 | ||
14292 | Non-debugging symbols: | |
14293 | 0x6100114c cygwin1!__assert | |
14294 | 0x61004034 cygwin1!_dll_crt0@@0 | |
14295 | 0x61004240 cygwin1!dll_crt0(per_process *) | |
14296 | [etc...] | |
14297 | @end smallexample | |
14298 | ||
79a6e687 | 14299 | @subsubsection Working with Minimal Symbols |
be448670 CF |
14300 | |
14301 | Symbols extracted from a DLL's export table do not contain very much | |
14302 | type information. All that @value{GDBN} can do is guess whether a symbol | |
14303 | refers to a function or variable depending on the linker section that | |
14304 | contains the symbol. Also note that the actual contents of the memory | |
14305 | contained in a DLL are not available unless the program is running. This | |
14306 | means that you cannot examine the contents of a variable or disassemble | |
14307 | a function within a DLL without a running program. | |
14308 | ||
14309 | Variables are generally treated as pointers and dereferenced | |
14310 | automatically. For this reason, it is often necessary to prefix a | |
14311 | variable name with the address-of operator (``&'') and provide explicit | |
14312 | type information in the command. Here's an example of the type of | |
14313 | problem: | |
14314 | ||
14315 | @smallexample | |
f7dc1244 | 14316 | (@value{GDBP}) print 'cygwin1!__argv' |
be448670 CF |
14317 | $1 = 268572168 |
14318 | @end smallexample | |
14319 | ||
14320 | @smallexample | |
f7dc1244 | 14321 | (@value{GDBP}) x 'cygwin1!__argv' |
be448670 CF |
14322 | 0x10021610: "\230y\"" |
14323 | @end smallexample | |
14324 | ||
14325 | And two possible solutions: | |
14326 | ||
14327 | @smallexample | |
f7dc1244 | 14328 | (@value{GDBP}) print ((char **)'cygwin1!__argv')[0] |
be448670 CF |
14329 | $2 = 0x22fd98 "/cygdrive/c/mydirectory/myprogram" |
14330 | @end smallexample | |
14331 | ||
14332 | @smallexample | |
f7dc1244 | 14333 | (@value{GDBP}) x/2x &'cygwin1!__argv' |
be448670 | 14334 | 0x610c0aa8 <cygwin1!__argv>: 0x10021608 0x00000000 |
f7dc1244 | 14335 | (@value{GDBP}) x/x 0x10021608 |
be448670 | 14336 | 0x10021608: 0x0022fd98 |
f7dc1244 | 14337 | (@value{GDBP}) x/s 0x0022fd98 |
be448670 CF |
14338 | 0x22fd98: "/cygdrive/c/mydirectory/myprogram" |
14339 | @end smallexample | |
14340 | ||
14341 | Setting a break point within a DLL is possible even before the program | |
14342 | starts execution. However, under these circumstances, @value{GDBN} can't | |
14343 | examine the initial instructions of the function in order to skip the | |
14344 | function's frame set-up code. You can work around this by using ``*&'' | |
14345 | to set the breakpoint at a raw memory address: | |
14346 | ||
14347 | @smallexample | |
f7dc1244 | 14348 | (@value{GDBP}) break *&'python22!PyOS_Readline' |
be448670 CF |
14349 | Breakpoint 1 at 0x1e04eff0 |
14350 | @end smallexample | |
14351 | ||
14352 | The author of these extensions is not entirely convinced that setting a | |
14353 | break point within a shared DLL like @file{kernel32.dll} is completely | |
14354 | safe. | |
14355 | ||
14d6dd68 | 14356 | @node Hurd Native |
79a6e687 | 14357 | @subsection Commands Specific to @sc{gnu} Hurd Systems |
14d6dd68 EZ |
14358 | @cindex @sc{gnu} Hurd debugging |
14359 | ||
14360 | This subsection describes @value{GDBN} commands specific to the | |
14361 | @sc{gnu} Hurd native debugging. | |
14362 | ||
14363 | @table @code | |
14364 | @item set signals | |
14365 | @itemx set sigs | |
14366 | @kindex set signals@r{, Hurd command} | |
14367 | @kindex set sigs@r{, Hurd command} | |
14368 | This command toggles the state of inferior signal interception by | |
14369 | @value{GDBN}. Mach exceptions, such as breakpoint traps, are not | |
14370 | affected by this command. @code{sigs} is a shorthand alias for | |
14371 | @code{signals}. | |
14372 | ||
14373 | @item show signals | |
14374 | @itemx show sigs | |
14375 | @kindex show signals@r{, Hurd command} | |
14376 | @kindex show sigs@r{, Hurd command} | |
14377 | Show the current state of intercepting inferior's signals. | |
14378 | ||
14379 | @item set signal-thread | |
14380 | @itemx set sigthread | |
14381 | @kindex set signal-thread | |
14382 | @kindex set sigthread | |
14383 | This command tells @value{GDBN} which thread is the @code{libc} signal | |
14384 | thread. That thread is run when a signal is delivered to a running | |
14385 | process. @code{set sigthread} is the shorthand alias of @code{set | |
14386 | signal-thread}. | |
14387 | ||
14388 | @item show signal-thread | |
14389 | @itemx show sigthread | |
14390 | @kindex show signal-thread | |
14391 | @kindex show sigthread | |
14392 | These two commands show which thread will run when the inferior is | |
14393 | delivered a signal. | |
14394 | ||
14395 | @item set stopped | |
14396 | @kindex set stopped@r{, Hurd command} | |
14397 | This commands tells @value{GDBN} that the inferior process is stopped, | |
14398 | as with the @code{SIGSTOP} signal. The stopped process can be | |
14399 | continued by delivering a signal to it. | |
14400 | ||
14401 | @item show stopped | |
14402 | @kindex show stopped@r{, Hurd command} | |
14403 | This command shows whether @value{GDBN} thinks the debuggee is | |
14404 | stopped. | |
14405 | ||
14406 | @item set exceptions | |
14407 | @kindex set exceptions@r{, Hurd command} | |
14408 | Use this command to turn off trapping of exceptions in the inferior. | |
14409 | When exception trapping is off, neither breakpoints nor | |
14410 | single-stepping will work. To restore the default, set exception | |
14411 | trapping on. | |
14412 | ||
14413 | @item show exceptions | |
14414 | @kindex show exceptions@r{, Hurd command} | |
14415 | Show the current state of trapping exceptions in the inferior. | |
14416 | ||
14417 | @item set task pause | |
14418 | @kindex set task@r{, Hurd commands} | |
14419 | @cindex task attributes (@sc{gnu} Hurd) | |
14420 | @cindex pause current task (@sc{gnu} Hurd) | |
14421 | This command toggles task suspension when @value{GDBN} has control. | |
14422 | Setting it to on takes effect immediately, and the task is suspended | |
14423 | whenever @value{GDBN} gets control. Setting it to off will take | |
14424 | effect the next time the inferior is continued. If this option is set | |
14425 | to off, you can use @code{set thread default pause on} or @code{set | |
14426 | thread pause on} (see below) to pause individual threads. | |
14427 | ||
14428 | @item show task pause | |
14429 | @kindex show task@r{, Hurd commands} | |
14430 | Show the current state of task suspension. | |
14431 | ||
14432 | @item set task detach-suspend-count | |
14433 | @cindex task suspend count | |
14434 | @cindex detach from task, @sc{gnu} Hurd | |
14435 | This command sets the suspend count the task will be left with when | |
14436 | @value{GDBN} detaches from it. | |
14437 | ||
14438 | @item show task detach-suspend-count | |
14439 | Show the suspend count the task will be left with when detaching. | |
14440 | ||
14441 | @item set task exception-port | |
14442 | @itemx set task excp | |
14443 | @cindex task exception port, @sc{gnu} Hurd | |
14444 | This command sets the task exception port to which @value{GDBN} will | |
14445 | forward exceptions. The argument should be the value of the @dfn{send | |
14446 | rights} of the task. @code{set task excp} is a shorthand alias. | |
14447 | ||
14448 | @item set noninvasive | |
14449 | @cindex noninvasive task options | |
14450 | This command switches @value{GDBN} to a mode that is the least | |
14451 | invasive as far as interfering with the inferior is concerned. This | |
14452 | is the same as using @code{set task pause}, @code{set exceptions}, and | |
14453 | @code{set signals} to values opposite to the defaults. | |
14454 | ||
14455 | @item info send-rights | |
14456 | @itemx info receive-rights | |
14457 | @itemx info port-rights | |
14458 | @itemx info port-sets | |
14459 | @itemx info dead-names | |
14460 | @itemx info ports | |
14461 | @itemx info psets | |
14462 | @cindex send rights, @sc{gnu} Hurd | |
14463 | @cindex receive rights, @sc{gnu} Hurd | |
14464 | @cindex port rights, @sc{gnu} Hurd | |
14465 | @cindex port sets, @sc{gnu} Hurd | |
14466 | @cindex dead names, @sc{gnu} Hurd | |
14467 | These commands display information about, respectively, send rights, | |
14468 | receive rights, port rights, port sets, and dead names of a task. | |
14469 | There are also shorthand aliases: @code{info ports} for @code{info | |
14470 | port-rights} and @code{info psets} for @code{info port-sets}. | |
14471 | ||
14472 | @item set thread pause | |
14473 | @kindex set thread@r{, Hurd command} | |
14474 | @cindex thread properties, @sc{gnu} Hurd | |
14475 | @cindex pause current thread (@sc{gnu} Hurd) | |
14476 | This command toggles current thread suspension when @value{GDBN} has | |
14477 | control. Setting it to on takes effect immediately, and the current | |
14478 | thread is suspended whenever @value{GDBN} gets control. Setting it to | |
14479 | off will take effect the next time the inferior is continued. | |
14480 | Normally, this command has no effect, since when @value{GDBN} has | |
14481 | control, the whole task is suspended. However, if you used @code{set | |
14482 | task pause off} (see above), this command comes in handy to suspend | |
14483 | only the current thread. | |
14484 | ||
14485 | @item show thread pause | |
14486 | @kindex show thread@r{, Hurd command} | |
14487 | This command shows the state of current thread suspension. | |
14488 | ||
14489 | @item set thread run | |
d3e8051b | 14490 | This command sets whether the current thread is allowed to run. |
14d6dd68 EZ |
14491 | |
14492 | @item show thread run | |
14493 | Show whether the current thread is allowed to run. | |
14494 | ||
14495 | @item set thread detach-suspend-count | |
14496 | @cindex thread suspend count, @sc{gnu} Hurd | |
14497 | @cindex detach from thread, @sc{gnu} Hurd | |
14498 | This command sets the suspend count @value{GDBN} will leave on a | |
14499 | thread when detaching. This number is relative to the suspend count | |
14500 | found by @value{GDBN} when it notices the thread; use @code{set thread | |
14501 | takeover-suspend-count} to force it to an absolute value. | |
14502 | ||
14503 | @item show thread detach-suspend-count | |
14504 | Show the suspend count @value{GDBN} will leave on the thread when | |
14505 | detaching. | |
14506 | ||
14507 | @item set thread exception-port | |
14508 | @itemx set thread excp | |
14509 | Set the thread exception port to which to forward exceptions. This | |
14510 | overrides the port set by @code{set task exception-port} (see above). | |
14511 | @code{set thread excp} is the shorthand alias. | |
14512 | ||
14513 | @item set thread takeover-suspend-count | |
14514 | Normally, @value{GDBN}'s thread suspend counts are relative to the | |
14515 | value @value{GDBN} finds when it notices each thread. This command | |
14516 | changes the suspend counts to be absolute instead. | |
14517 | ||
14518 | @item set thread default | |
14519 | @itemx show thread default | |
14520 | @cindex thread default settings, @sc{gnu} Hurd | |
14521 | Each of the above @code{set thread} commands has a @code{set thread | |
14522 | default} counterpart (e.g., @code{set thread default pause}, @code{set | |
14523 | thread default exception-port}, etc.). The @code{thread default} | |
14524 | variety of commands sets the default thread properties for all | |
14525 | threads; you can then change the properties of individual threads with | |
14526 | the non-default commands. | |
14527 | @end table | |
14528 | ||
14529 | ||
a64548ea EZ |
14530 | @node Neutrino |
14531 | @subsection QNX Neutrino | |
14532 | @cindex QNX Neutrino | |
14533 | ||
14534 | @value{GDBN} provides the following commands specific to the QNX | |
14535 | Neutrino target: | |
14536 | ||
14537 | @table @code | |
14538 | @item set debug nto-debug | |
14539 | @kindex set debug nto-debug | |
14540 | When set to on, enables debugging messages specific to the QNX | |
14541 | Neutrino support. | |
14542 | ||
14543 | @item show debug nto-debug | |
14544 | @kindex show debug nto-debug | |
14545 | Show the current state of QNX Neutrino messages. | |
14546 | @end table | |
14547 | ||
14548 | ||
8e04817f AC |
14549 | @node Embedded OS |
14550 | @section Embedded Operating Systems | |
104c1213 | 14551 | |
8e04817f AC |
14552 | This section describes configurations involving the debugging of |
14553 | embedded operating systems that are available for several different | |
14554 | architectures. | |
d4f3574e | 14555 | |
8e04817f AC |
14556 | @menu |
14557 | * VxWorks:: Using @value{GDBN} with VxWorks | |
14558 | @end menu | |
104c1213 | 14559 | |
8e04817f AC |
14560 | @value{GDBN} includes the ability to debug programs running on |
14561 | various real-time operating systems. | |
104c1213 | 14562 | |
8e04817f AC |
14563 | @node VxWorks |
14564 | @subsection Using @value{GDBN} with VxWorks | |
104c1213 | 14565 | |
8e04817f | 14566 | @cindex VxWorks |
104c1213 | 14567 | |
8e04817f | 14568 | @table @code |
104c1213 | 14569 | |
8e04817f AC |
14570 | @kindex target vxworks |
14571 | @item target vxworks @var{machinename} | |
14572 | A VxWorks system, attached via TCP/IP. The argument @var{machinename} | |
14573 | is the target system's machine name or IP address. | |
104c1213 | 14574 | |
8e04817f | 14575 | @end table |
104c1213 | 14576 | |
8e04817f AC |
14577 | On VxWorks, @code{load} links @var{filename} dynamically on the |
14578 | current target system as well as adding its symbols in @value{GDBN}. | |
104c1213 | 14579 | |
8e04817f AC |
14580 | @value{GDBN} enables developers to spawn and debug tasks running on networked |
14581 | VxWorks targets from a Unix host. Already-running tasks spawned from | |
14582 | the VxWorks shell can also be debugged. @value{GDBN} uses code that runs on | |
14583 | both the Unix host and on the VxWorks target. The program | |
14584 | @code{@value{GDBP}} is installed and executed on the Unix host. (It may be | |
14585 | installed with the name @code{vxgdb}, to distinguish it from a | |
14586 | @value{GDBN} for debugging programs on the host itself.) | |
104c1213 | 14587 | |
8e04817f AC |
14588 | @table @code |
14589 | @item VxWorks-timeout @var{args} | |
14590 | @kindex vxworks-timeout | |
14591 | All VxWorks-based targets now support the option @code{vxworks-timeout}. | |
14592 | This option is set by the user, and @var{args} represents the number of | |
14593 | seconds @value{GDBN} waits for responses to rpc's. You might use this if | |
14594 | your VxWorks target is a slow software simulator or is on the far side | |
14595 | of a thin network line. | |
14596 | @end table | |
104c1213 | 14597 | |
8e04817f AC |
14598 | The following information on connecting to VxWorks was current when |
14599 | this manual was produced; newer releases of VxWorks may use revised | |
14600 | procedures. | |
104c1213 | 14601 | |
4644b6e3 | 14602 | @findex INCLUDE_RDB |
8e04817f AC |
14603 | To use @value{GDBN} with VxWorks, you must rebuild your VxWorks kernel |
14604 | to include the remote debugging interface routines in the VxWorks | |
14605 | library @file{rdb.a}. To do this, define @code{INCLUDE_RDB} in the | |
14606 | VxWorks configuration file @file{configAll.h} and rebuild your VxWorks | |
14607 | kernel. The resulting kernel contains @file{rdb.a}, and spawns the | |
14608 | source debugging task @code{tRdbTask} when VxWorks is booted. For more | |
14609 | information on configuring and remaking VxWorks, see the manufacturer's | |
14610 | manual. | |
14611 | @c VxWorks, see the @cite{VxWorks Programmer's Guide}. | |
104c1213 | 14612 | |
8e04817f AC |
14613 | Once you have included @file{rdb.a} in your VxWorks system image and set |
14614 | your Unix execution search path to find @value{GDBN}, you are ready to | |
14615 | run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} (or | |
14616 | @code{vxgdb}, depending on your installation). | |
104c1213 | 14617 | |
8e04817f | 14618 | @value{GDBN} comes up showing the prompt: |
104c1213 | 14619 | |
474c8240 | 14620 | @smallexample |
8e04817f | 14621 | (vxgdb) |
474c8240 | 14622 | @end smallexample |
104c1213 | 14623 | |
8e04817f AC |
14624 | @menu |
14625 | * VxWorks Connection:: Connecting to VxWorks | |
14626 | * VxWorks Download:: VxWorks download | |
14627 | * VxWorks Attach:: Running tasks | |
14628 | @end menu | |
104c1213 | 14629 | |
8e04817f AC |
14630 | @node VxWorks Connection |
14631 | @subsubsection Connecting to VxWorks | |
104c1213 | 14632 | |
8e04817f AC |
14633 | The @value{GDBN} command @code{target} lets you connect to a VxWorks target on the |
14634 | network. To connect to a target whose host name is ``@code{tt}'', type: | |
104c1213 | 14635 | |
474c8240 | 14636 | @smallexample |
8e04817f | 14637 | (vxgdb) target vxworks tt |
474c8240 | 14638 | @end smallexample |
104c1213 | 14639 | |
8e04817f AC |
14640 | @need 750 |
14641 | @value{GDBN} displays messages like these: | |
104c1213 | 14642 | |
8e04817f AC |
14643 | @smallexample |
14644 | Attaching remote machine across net... | |
14645 | Connected to tt. | |
14646 | @end smallexample | |
104c1213 | 14647 | |
8e04817f AC |
14648 | @need 1000 |
14649 | @value{GDBN} then attempts to read the symbol tables of any object modules | |
14650 | loaded into the VxWorks target since it was last booted. @value{GDBN} locates | |
14651 | these files by searching the directories listed in the command search | |
79a6e687 | 14652 | path (@pxref{Environment, ,Your Program's Environment}); if it fails |
8e04817f | 14653 | to find an object file, it displays a message such as: |
5d161b24 | 14654 | |
474c8240 | 14655 | @smallexample |
8e04817f | 14656 | prog.o: No such file or directory. |
474c8240 | 14657 | @end smallexample |
104c1213 | 14658 | |
8e04817f AC |
14659 | When this happens, add the appropriate directory to the search path with |
14660 | the @value{GDBN} command @code{path}, and execute the @code{target} | |
14661 | command again. | |
104c1213 | 14662 | |
8e04817f | 14663 | @node VxWorks Download |
79a6e687 | 14664 | @subsubsection VxWorks Download |
104c1213 | 14665 | |
8e04817f AC |
14666 | @cindex download to VxWorks |
14667 | If you have connected to the VxWorks target and you want to debug an | |
14668 | object that has not yet been loaded, you can use the @value{GDBN} | |
14669 | @code{load} command to download a file from Unix to VxWorks | |
14670 | incrementally. The object file given as an argument to the @code{load} | |
14671 | command is actually opened twice: first by the VxWorks target in order | |
14672 | to download the code, then by @value{GDBN} in order to read the symbol | |
14673 | table. This can lead to problems if the current working directories on | |
14674 | the two systems differ. If both systems have NFS mounted the same | |
14675 | filesystems, you can avoid these problems by using absolute paths. | |
14676 | Otherwise, it is simplest to set the working directory on both systems | |
14677 | to the directory in which the object file resides, and then to reference | |
14678 | the file by its name, without any path. For instance, a program | |
14679 | @file{prog.o} may reside in @file{@var{vxpath}/vw/demo/rdb} in VxWorks | |
14680 | and in @file{@var{hostpath}/vw/demo/rdb} on the host. To load this | |
14681 | program, type this on VxWorks: | |
104c1213 | 14682 | |
474c8240 | 14683 | @smallexample |
8e04817f | 14684 | -> cd "@var{vxpath}/vw/demo/rdb" |
474c8240 | 14685 | @end smallexample |
104c1213 | 14686 | |
8e04817f AC |
14687 | @noindent |
14688 | Then, in @value{GDBN}, type: | |
104c1213 | 14689 | |
474c8240 | 14690 | @smallexample |
8e04817f AC |
14691 | (vxgdb) cd @var{hostpath}/vw/demo/rdb |
14692 | (vxgdb) load prog.o | |
474c8240 | 14693 | @end smallexample |
104c1213 | 14694 | |
8e04817f | 14695 | @value{GDBN} displays a response similar to this: |
104c1213 | 14696 | |
8e04817f AC |
14697 | @smallexample |
14698 | Reading symbol data from wherever/vw/demo/rdb/prog.o... done. | |
14699 | @end smallexample | |
104c1213 | 14700 | |
8e04817f AC |
14701 | You can also use the @code{load} command to reload an object module |
14702 | after editing and recompiling the corresponding source file. Note that | |
14703 | this makes @value{GDBN} delete all currently-defined breakpoints, | |
14704 | auto-displays, and convenience variables, and to clear the value | |
14705 | history. (This is necessary in order to preserve the integrity of | |
14706 | debugger's data structures that reference the target system's symbol | |
14707 | table.) | |
104c1213 | 14708 | |
8e04817f | 14709 | @node VxWorks Attach |
79a6e687 | 14710 | @subsubsection Running Tasks |
104c1213 JM |
14711 | |
14712 | @cindex running VxWorks tasks | |
14713 | You can also attach to an existing task using the @code{attach} command as | |
14714 | follows: | |
14715 | ||
474c8240 | 14716 | @smallexample |
104c1213 | 14717 | (vxgdb) attach @var{task} |
474c8240 | 14718 | @end smallexample |
104c1213 JM |
14719 | |
14720 | @noindent | |
14721 | where @var{task} is the VxWorks hexadecimal task ID. The task can be running | |
14722 | or suspended when you attach to it. Running tasks are suspended at | |
14723 | the time of attachment. | |
14724 | ||
6d2ebf8b | 14725 | @node Embedded Processors |
104c1213 JM |
14726 | @section Embedded Processors |
14727 | ||
14728 | This section goes into details specific to particular embedded | |
14729 | configurations. | |
14730 | ||
c45da7e6 EZ |
14731 | @cindex send command to simulator |
14732 | Whenever a specific embedded processor has a simulator, @value{GDBN} | |
14733 | allows to send an arbitrary command to the simulator. | |
14734 | ||
14735 | @table @code | |
14736 | @item sim @var{command} | |
14737 | @kindex sim@r{, a command} | |
14738 | Send an arbitrary @var{command} string to the simulator. Consult the | |
14739 | documentation for the specific simulator in use for information about | |
14740 | acceptable commands. | |
14741 | @end table | |
14742 | ||
7d86b5d5 | 14743 | |
104c1213 | 14744 | @menu |
c45da7e6 | 14745 | * ARM:: ARM RDI |
172c2a43 | 14746 | * M32R/D:: Renesas M32R/D |
104c1213 | 14747 | * M68K:: Motorola M68K |
104c1213 | 14748 | * MIPS Embedded:: MIPS Embedded |
a37295f9 | 14749 | * OpenRISC 1000:: OpenRisc 1000 |
104c1213 | 14750 | * PA:: HP PA Embedded |
4acd40f3 | 14751 | * PowerPC Embedded:: PowerPC Embedded |
104c1213 JM |
14752 | * Sparclet:: Tsqware Sparclet |
14753 | * Sparclite:: Fujitsu Sparclite | |
104c1213 | 14754 | * Z8000:: Zilog Z8000 |
a64548ea EZ |
14755 | * AVR:: Atmel AVR |
14756 | * CRIS:: CRIS | |
14757 | * Super-H:: Renesas Super-H | |
104c1213 JM |
14758 | @end menu |
14759 | ||
6d2ebf8b | 14760 | @node ARM |
104c1213 | 14761 | @subsection ARM |
c45da7e6 | 14762 | @cindex ARM RDI |
104c1213 JM |
14763 | |
14764 | @table @code | |
8e04817f AC |
14765 | @kindex target rdi |
14766 | @item target rdi @var{dev} | |
14767 | ARM Angel monitor, via RDI library interface to ADP protocol. You may | |
14768 | use this target to communicate with both boards running the Angel | |
14769 | monitor, or with the EmbeddedICE JTAG debug device. | |
14770 | ||
14771 | @kindex target rdp | |
14772 | @item target rdp @var{dev} | |
14773 | ARM Demon monitor. | |
14774 | ||
14775 | @end table | |
14776 | ||
e2f4edfd EZ |
14777 | @value{GDBN} provides the following ARM-specific commands: |
14778 | ||
14779 | @table @code | |
14780 | @item set arm disassembler | |
14781 | @kindex set arm | |
14782 | This commands selects from a list of disassembly styles. The | |
14783 | @code{"std"} style is the standard style. | |
14784 | ||
14785 | @item show arm disassembler | |
14786 | @kindex show arm | |
14787 | Show the current disassembly style. | |
14788 | ||
14789 | @item set arm apcs32 | |
14790 | @cindex ARM 32-bit mode | |
14791 | This command toggles ARM operation mode between 32-bit and 26-bit. | |
14792 | ||
14793 | @item show arm apcs32 | |
14794 | Display the current usage of the ARM 32-bit mode. | |
14795 | ||
14796 | @item set arm fpu @var{fputype} | |
14797 | This command sets the ARM floating-point unit (FPU) type. The | |
14798 | argument @var{fputype} can be one of these: | |
14799 | ||
14800 | @table @code | |
14801 | @item auto | |
14802 | Determine the FPU type by querying the OS ABI. | |
14803 | @item softfpa | |
14804 | Software FPU, with mixed-endian doubles on little-endian ARM | |
14805 | processors. | |
14806 | @item fpa | |
14807 | GCC-compiled FPA co-processor. | |
14808 | @item softvfp | |
14809 | Software FPU with pure-endian doubles. | |
14810 | @item vfp | |
14811 | VFP co-processor. | |
14812 | @end table | |
14813 | ||
14814 | @item show arm fpu | |
14815 | Show the current type of the FPU. | |
14816 | ||
14817 | @item set arm abi | |
14818 | This command forces @value{GDBN} to use the specified ABI. | |
14819 | ||
14820 | @item show arm abi | |
14821 | Show the currently used ABI. | |
14822 | ||
14823 | @item set debug arm | |
14824 | Toggle whether to display ARM-specific debugging messages from the ARM | |
14825 | target support subsystem. | |
14826 | ||
14827 | @item show debug arm | |
14828 | Show whether ARM-specific debugging messages are enabled. | |
14829 | @end table | |
14830 | ||
c45da7e6 EZ |
14831 | The following commands are available when an ARM target is debugged |
14832 | using the RDI interface: | |
14833 | ||
14834 | @table @code | |
14835 | @item rdilogfile @r{[}@var{file}@r{]} | |
14836 | @kindex rdilogfile | |
14837 | @cindex ADP (Angel Debugger Protocol) logging | |
14838 | Set the filename for the ADP (Angel Debugger Protocol) packet log. | |
14839 | With an argument, sets the log file to the specified @var{file}. With | |
14840 | no argument, show the current log file name. The default log file is | |
14841 | @file{rdi.log}. | |
14842 | ||
14843 | @item rdilogenable @r{[}@var{arg}@r{]} | |
14844 | @kindex rdilogenable | |
14845 | Control logging of ADP packets. With an argument of 1 or @code{"yes"} | |
14846 | enables logging, with an argument 0 or @code{"no"} disables it. With | |
14847 | no arguments displays the current setting. When logging is enabled, | |
14848 | ADP packets exchanged between @value{GDBN} and the RDI target device | |
14849 | are logged to a file. | |
14850 | ||
14851 | @item set rdiromatzero | |
14852 | @kindex set rdiromatzero | |
14853 | @cindex ROM at zero address, RDI | |
14854 | Tell @value{GDBN} whether the target has ROM at address 0. If on, | |
14855 | vector catching is disabled, so that zero address can be used. If off | |
14856 | (the default), vector catching is enabled. For this command to take | |
14857 | effect, it needs to be invoked prior to the @code{target rdi} command. | |
14858 | ||
14859 | @item show rdiromatzero | |
14860 | @kindex show rdiromatzero | |
14861 | Show the current setting of ROM at zero address. | |
14862 | ||
14863 | @item set rdiheartbeat | |
14864 | @kindex set rdiheartbeat | |
14865 | @cindex RDI heartbeat | |
14866 | Enable or disable RDI heartbeat packets. It is not recommended to | |
14867 | turn on this option, since it confuses ARM and EPI JTAG interface, as | |
14868 | well as the Angel monitor. | |
14869 | ||
14870 | @item show rdiheartbeat | |
14871 | @kindex show rdiheartbeat | |
14872 | Show the setting of RDI heartbeat packets. | |
14873 | @end table | |
14874 | ||
e2f4edfd | 14875 | |
8e04817f | 14876 | @node M32R/D |
ba04e063 | 14877 | @subsection Renesas M32R/D and M32R/SDI |
8e04817f AC |
14878 | |
14879 | @table @code | |
8e04817f AC |
14880 | @kindex target m32r |
14881 | @item target m32r @var{dev} | |
172c2a43 | 14882 | Renesas M32R/D ROM monitor. |
8e04817f | 14883 | |
fb3e19c0 KI |
14884 | @kindex target m32rsdi |
14885 | @item target m32rsdi @var{dev} | |
14886 | Renesas M32R SDI server, connected via parallel port to the board. | |
721c2651 EZ |
14887 | @end table |
14888 | ||
14889 | The following @value{GDBN} commands are specific to the M32R monitor: | |
14890 | ||
14891 | @table @code | |
14892 | @item set download-path @var{path} | |
14893 | @kindex set download-path | |
14894 | @cindex find downloadable @sc{srec} files (M32R) | |
d3e8051b | 14895 | Set the default path for finding downloadable @sc{srec} files. |
721c2651 EZ |
14896 | |
14897 | @item show download-path | |
14898 | @kindex show download-path | |
14899 | Show the default path for downloadable @sc{srec} files. | |
fb3e19c0 | 14900 | |
721c2651 EZ |
14901 | @item set board-address @var{addr} |
14902 | @kindex set board-address | |
14903 | @cindex M32-EVA target board address | |
14904 | Set the IP address for the M32R-EVA target board. | |
14905 | ||
14906 | @item show board-address | |
14907 | @kindex show board-address | |
14908 | Show the current IP address of the target board. | |
14909 | ||
14910 | @item set server-address @var{addr} | |
14911 | @kindex set server-address | |
14912 | @cindex download server address (M32R) | |
14913 | Set the IP address for the download server, which is the @value{GDBN}'s | |
14914 | host machine. | |
14915 | ||
14916 | @item show server-address | |
14917 | @kindex show server-address | |
14918 | Display the IP address of the download server. | |
14919 | ||
14920 | @item upload @r{[}@var{file}@r{]} | |
14921 | @kindex upload@r{, M32R} | |
14922 | Upload the specified @sc{srec} @var{file} via the monitor's Ethernet | |
14923 | upload capability. If no @var{file} argument is given, the current | |
14924 | executable file is uploaded. | |
14925 | ||
14926 | @item tload @r{[}@var{file}@r{]} | |
14927 | @kindex tload@r{, M32R} | |
14928 | Test the @code{upload} command. | |
8e04817f AC |
14929 | @end table |
14930 | ||
ba04e063 EZ |
14931 | The following commands are available for M32R/SDI: |
14932 | ||
14933 | @table @code | |
14934 | @item sdireset | |
14935 | @kindex sdireset | |
14936 | @cindex reset SDI connection, M32R | |
14937 | This command resets the SDI connection. | |
14938 | ||
14939 | @item sdistatus | |
14940 | @kindex sdistatus | |
14941 | This command shows the SDI connection status. | |
14942 | ||
14943 | @item debug_chaos | |
14944 | @kindex debug_chaos | |
14945 | @cindex M32R/Chaos debugging | |
14946 | Instructs the remote that M32R/Chaos debugging is to be used. | |
14947 | ||
14948 | @item use_debug_dma | |
14949 | @kindex use_debug_dma | |
14950 | Instructs the remote to use the DEBUG_DMA method of accessing memory. | |
14951 | ||
14952 | @item use_mon_code | |
14953 | @kindex use_mon_code | |
14954 | Instructs the remote to use the MON_CODE method of accessing memory. | |
14955 | ||
14956 | @item use_ib_break | |
14957 | @kindex use_ib_break | |
14958 | Instructs the remote to set breakpoints by IB break. | |
14959 | ||
14960 | @item use_dbt_break | |
14961 | @kindex use_dbt_break | |
14962 | Instructs the remote to set breakpoints by DBT. | |
14963 | @end table | |
14964 | ||
8e04817f AC |
14965 | @node M68K |
14966 | @subsection M68k | |
14967 | ||
7ce59000 DJ |
14968 | The Motorola m68k configuration includes ColdFire support, and a |
14969 | target command for the following ROM monitor. | |
8e04817f AC |
14970 | |
14971 | @table @code | |
14972 | ||
8e04817f AC |
14973 | @kindex target dbug |
14974 | @item target dbug @var{dev} | |
14975 | dBUG ROM monitor for Motorola ColdFire. | |
14976 | ||
8e04817f AC |
14977 | @end table |
14978 | ||
8e04817f AC |
14979 | @node MIPS Embedded |
14980 | @subsection MIPS Embedded | |
14981 | ||
14982 | @cindex MIPS boards | |
14983 | @value{GDBN} can use the MIPS remote debugging protocol to talk to a | |
14984 | MIPS board attached to a serial line. This is available when | |
14985 | you configure @value{GDBN} with @samp{--target=mips-idt-ecoff}. | |
104c1213 | 14986 | |
8e04817f AC |
14987 | @need 1000 |
14988 | Use these @value{GDBN} commands to specify the connection to your target board: | |
104c1213 | 14989 | |
8e04817f AC |
14990 | @table @code |
14991 | @item target mips @var{port} | |
14992 | @kindex target mips @var{port} | |
14993 | To run a program on the board, start up @code{@value{GDBP}} with the | |
14994 | name of your program as the argument. To connect to the board, use the | |
14995 | command @samp{target mips @var{port}}, where @var{port} is the name of | |
14996 | the serial port connected to the board. If the program has not already | |
14997 | been downloaded to the board, you may use the @code{load} command to | |
14998 | download it. You can then use all the usual @value{GDBN} commands. | |
104c1213 | 14999 | |
8e04817f AC |
15000 | For example, this sequence connects to the target board through a serial |
15001 | port, and loads and runs a program called @var{prog} through the | |
15002 | debugger: | |
104c1213 | 15003 | |
474c8240 | 15004 | @smallexample |
8e04817f AC |
15005 | host$ @value{GDBP} @var{prog} |
15006 | @value{GDBN} is free software and @dots{} | |
15007 | (@value{GDBP}) target mips /dev/ttyb | |
15008 | (@value{GDBP}) load @var{prog} | |
15009 | (@value{GDBP}) run | |
474c8240 | 15010 | @end smallexample |
104c1213 | 15011 | |
8e04817f AC |
15012 | @item target mips @var{hostname}:@var{portnumber} |
15013 | On some @value{GDBN} host configurations, you can specify a TCP | |
15014 | connection (for instance, to a serial line managed by a terminal | |
15015 | concentrator) instead of a serial port, using the syntax | |
15016 | @samp{@var{hostname}:@var{portnumber}}. | |
104c1213 | 15017 | |
8e04817f AC |
15018 | @item target pmon @var{port} |
15019 | @kindex target pmon @var{port} | |
15020 | PMON ROM monitor. | |
104c1213 | 15021 | |
8e04817f AC |
15022 | @item target ddb @var{port} |
15023 | @kindex target ddb @var{port} | |
15024 | NEC's DDB variant of PMON for Vr4300. | |
104c1213 | 15025 | |
8e04817f AC |
15026 | @item target lsi @var{port} |
15027 | @kindex target lsi @var{port} | |
15028 | LSI variant of PMON. | |
104c1213 | 15029 | |
8e04817f AC |
15030 | @kindex target r3900 |
15031 | @item target r3900 @var{dev} | |
15032 | Densan DVE-R3900 ROM monitor for Toshiba R3900 Mips. | |
104c1213 | 15033 | |
8e04817f AC |
15034 | @kindex target array |
15035 | @item target array @var{dev} | |
15036 | Array Tech LSI33K RAID controller board. | |
104c1213 | 15037 | |
8e04817f | 15038 | @end table |
104c1213 | 15039 | |
104c1213 | 15040 | |
8e04817f AC |
15041 | @noindent |
15042 | @value{GDBN} also supports these special commands for MIPS targets: | |
104c1213 | 15043 | |
8e04817f | 15044 | @table @code |
8e04817f AC |
15045 | @item set mipsfpu double |
15046 | @itemx set mipsfpu single | |
15047 | @itemx set mipsfpu none | |
a64548ea | 15048 | @itemx set mipsfpu auto |
8e04817f AC |
15049 | @itemx show mipsfpu |
15050 | @kindex set mipsfpu | |
15051 | @kindex show mipsfpu | |
15052 | @cindex MIPS remote floating point | |
15053 | @cindex floating point, MIPS remote | |
15054 | If your target board does not support the MIPS floating point | |
15055 | coprocessor, you should use the command @samp{set mipsfpu none} (if you | |
15056 | need this, you may wish to put the command in your @value{GDBN} init | |
15057 | file). This tells @value{GDBN} how to find the return value of | |
15058 | functions which return floating point values. It also allows | |
15059 | @value{GDBN} to avoid saving the floating point registers when calling | |
15060 | functions on the board. If you are using a floating point coprocessor | |
15061 | with only single precision floating point support, as on the @sc{r4650} | |
15062 | processor, use the command @samp{set mipsfpu single}. The default | |
15063 | double precision floating point coprocessor may be selected using | |
15064 | @samp{set mipsfpu double}. | |
104c1213 | 15065 | |
8e04817f AC |
15066 | In previous versions the only choices were double precision or no |
15067 | floating point, so @samp{set mipsfpu on} will select double precision | |
15068 | and @samp{set mipsfpu off} will select no floating point. | |
104c1213 | 15069 | |
8e04817f AC |
15070 | As usual, you can inquire about the @code{mipsfpu} variable with |
15071 | @samp{show mipsfpu}. | |
104c1213 | 15072 | |
8e04817f AC |
15073 | @item set timeout @var{seconds} |
15074 | @itemx set retransmit-timeout @var{seconds} | |
15075 | @itemx show timeout | |
15076 | @itemx show retransmit-timeout | |
15077 | @cindex @code{timeout}, MIPS protocol | |
15078 | @cindex @code{retransmit-timeout}, MIPS protocol | |
15079 | @kindex set timeout | |
15080 | @kindex show timeout | |
15081 | @kindex set retransmit-timeout | |
15082 | @kindex show retransmit-timeout | |
15083 | You can control the timeout used while waiting for a packet, in the MIPS | |
15084 | remote protocol, with the @code{set timeout @var{seconds}} command. The | |
15085 | default is 5 seconds. Similarly, you can control the timeout used while | |
15086 | waiting for an acknowledgement of a packet with the @code{set | |
15087 | retransmit-timeout @var{seconds}} command. The default is 3 seconds. | |
15088 | You can inspect both values with @code{show timeout} and @code{show | |
15089 | retransmit-timeout}. (These commands are @emph{only} available when | |
15090 | @value{GDBN} is configured for @samp{--target=mips-idt-ecoff}.) | |
104c1213 | 15091 | |
8e04817f AC |
15092 | The timeout set by @code{set timeout} does not apply when @value{GDBN} |
15093 | is waiting for your program to stop. In that case, @value{GDBN} waits | |
15094 | forever because it has no way of knowing how long the program is going | |
15095 | to run before stopping. | |
ba04e063 EZ |
15096 | |
15097 | @item set syn-garbage-limit @var{num} | |
15098 | @kindex set syn-garbage-limit@r{, MIPS remote} | |
15099 | @cindex synchronize with remote MIPS target | |
15100 | Limit the maximum number of characters @value{GDBN} should ignore when | |
15101 | it tries to synchronize with the remote target. The default is 10 | |
15102 | characters. Setting the limit to -1 means there's no limit. | |
15103 | ||
15104 | @item show syn-garbage-limit | |
15105 | @kindex show syn-garbage-limit@r{, MIPS remote} | |
15106 | Show the current limit on the number of characters to ignore when | |
15107 | trying to synchronize with the remote system. | |
15108 | ||
15109 | @item set monitor-prompt @var{prompt} | |
15110 | @kindex set monitor-prompt@r{, MIPS remote} | |
15111 | @cindex remote monitor prompt | |
15112 | Tell @value{GDBN} to expect the specified @var{prompt} string from the | |
15113 | remote monitor. The default depends on the target: | |
15114 | @table @asis | |
15115 | @item pmon target | |
15116 | @samp{PMON} | |
15117 | @item ddb target | |
15118 | @samp{NEC010} | |
15119 | @item lsi target | |
15120 | @samp{PMON>} | |
15121 | @end table | |
15122 | ||
15123 | @item show monitor-prompt | |
15124 | @kindex show monitor-prompt@r{, MIPS remote} | |
15125 | Show the current strings @value{GDBN} expects as the prompt from the | |
15126 | remote monitor. | |
15127 | ||
15128 | @item set monitor-warnings | |
15129 | @kindex set monitor-warnings@r{, MIPS remote} | |
15130 | Enable or disable monitor warnings about hardware breakpoints. This | |
15131 | has effect only for the @code{lsi} target. When on, @value{GDBN} will | |
15132 | display warning messages whose codes are returned by the @code{lsi} | |
15133 | PMON monitor for breakpoint commands. | |
15134 | ||
15135 | @item show monitor-warnings | |
15136 | @kindex show monitor-warnings@r{, MIPS remote} | |
15137 | Show the current setting of printing monitor warnings. | |
15138 | ||
15139 | @item pmon @var{command} | |
15140 | @kindex pmon@r{, MIPS remote} | |
15141 | @cindex send PMON command | |
15142 | This command allows sending an arbitrary @var{command} string to the | |
15143 | monitor. The monitor must be in debug mode for this to work. | |
8e04817f | 15144 | @end table |
104c1213 | 15145 | |
a37295f9 MM |
15146 | @node OpenRISC 1000 |
15147 | @subsection OpenRISC 1000 | |
15148 | @cindex OpenRISC 1000 | |
15149 | ||
15150 | @cindex or1k boards | |
15151 | See OR1k Architecture document (@uref{www.opencores.org}) for more information | |
15152 | about platform and commands. | |
15153 | ||
15154 | @table @code | |
15155 | ||
15156 | @kindex target jtag | |
15157 | @item target jtag jtag://@var{host}:@var{port} | |
15158 | ||
15159 | Connects to remote JTAG server. | |
15160 | JTAG remote server can be either an or1ksim or JTAG server, | |
15161 | connected via parallel port to the board. | |
15162 | ||
15163 | Example: @code{target jtag jtag://localhost:9999} | |
15164 | ||
15165 | @kindex or1ksim | |
15166 | @item or1ksim @var{command} | |
15167 | If connected to @code{or1ksim} OpenRISC 1000 Architectural | |
15168 | Simulator, proprietary commands can be executed. | |
15169 | ||
15170 | @kindex info or1k spr | |
15171 | @item info or1k spr | |
15172 | Displays spr groups. | |
15173 | ||
15174 | @item info or1k spr @var{group} | |
15175 | @itemx info or1k spr @var{groupno} | |
15176 | Displays register names in selected group. | |
15177 | ||
15178 | @item info or1k spr @var{group} @var{register} | |
15179 | @itemx info or1k spr @var{register} | |
15180 | @itemx info or1k spr @var{groupno} @var{registerno} | |
15181 | @itemx info or1k spr @var{registerno} | |
15182 | Shows information about specified spr register. | |
15183 | ||
15184 | @kindex spr | |
15185 | @item spr @var{group} @var{register} @var{value} | |
15186 | @itemx spr @var{register @var{value}} | |
15187 | @itemx spr @var{groupno} @var{registerno @var{value}} | |
15188 | @itemx spr @var{registerno @var{value}} | |
15189 | Writes @var{value} to specified spr register. | |
15190 | @end table | |
15191 | ||
15192 | Some implementations of OpenRISC 1000 Architecture also have hardware trace. | |
15193 | It is very similar to @value{GDBN} trace, except it does not interfere with normal | |
15194 | program execution and is thus much faster. Hardware breakpoints/watchpoint | |
15195 | triggers can be set using: | |
15196 | @table @code | |
15197 | @item $LEA/$LDATA | |
15198 | Load effective address/data | |
15199 | @item $SEA/$SDATA | |
15200 | Store effective address/data | |
15201 | @item $AEA/$ADATA | |
15202 | Access effective address ($SEA or $LEA) or data ($SDATA/$LDATA) | |
15203 | @item $FETCH | |
15204 | Fetch data | |
15205 | @end table | |
15206 | ||
15207 | When triggered, it can capture low level data, like: @code{PC}, @code{LSEA}, | |
15208 | @code{LDATA}, @code{SDATA}, @code{READSPR}, @code{WRITESPR}, @code{INSTR}. | |
15209 | ||
15210 | @code{htrace} commands: | |
15211 | @cindex OpenRISC 1000 htrace | |
15212 | @table @code | |
15213 | @kindex hwatch | |
15214 | @item hwatch @var{conditional} | |
d3e8051b | 15215 | Set hardware watchpoint on combination of Load/Store Effective Address(es) |
a37295f9 MM |
15216 | or Data. For example: |
15217 | ||
15218 | @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)} | |
15219 | ||
15220 | @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)} | |
15221 | ||
4644b6e3 | 15222 | @kindex htrace |
a37295f9 MM |
15223 | @item htrace info |
15224 | Display information about current HW trace configuration. | |
15225 | ||
a37295f9 MM |
15226 | @item htrace trigger @var{conditional} |
15227 | Set starting criteria for HW trace. | |
15228 | ||
a37295f9 MM |
15229 | @item htrace qualifier @var{conditional} |
15230 | Set acquisition qualifier for HW trace. | |
15231 | ||
a37295f9 MM |
15232 | @item htrace stop @var{conditional} |
15233 | Set HW trace stopping criteria. | |
15234 | ||
f153cc92 | 15235 | @item htrace record [@var{data}]* |
a37295f9 MM |
15236 | Selects the data to be recorded, when qualifier is met and HW trace was |
15237 | triggered. | |
15238 | ||
a37295f9 | 15239 | @item htrace enable |
a37295f9 MM |
15240 | @itemx htrace disable |
15241 | Enables/disables the HW trace. | |
15242 | ||
f153cc92 | 15243 | @item htrace rewind [@var{filename}] |
a37295f9 MM |
15244 | Clears currently recorded trace data. |
15245 | ||
15246 | If filename is specified, new trace file is made and any newly collected data | |
15247 | will be written there. | |
15248 | ||
f153cc92 | 15249 | @item htrace print [@var{start} [@var{len}]] |
a37295f9 MM |
15250 | Prints trace buffer, using current record configuration. |
15251 | ||
a37295f9 MM |
15252 | @item htrace mode continuous |
15253 | Set continuous trace mode. | |
15254 | ||
a37295f9 MM |
15255 | @item htrace mode suspend |
15256 | Set suspend trace mode. | |
15257 | ||
15258 | @end table | |
15259 | ||
4acd40f3 TJB |
15260 | @node PowerPC Embedded |
15261 | @subsection PowerPC Embedded | |
104c1213 | 15262 | |
55eddb0f DJ |
15263 | @value{GDBN} provides the following PowerPC-specific commands: |
15264 | ||
104c1213 | 15265 | @table @code |
55eddb0f DJ |
15266 | @kindex set powerpc |
15267 | @item set powerpc soft-float | |
15268 | @itemx show powerpc soft-float | |
15269 | Force @value{GDBN} to use (or not use) a software floating point calling | |
15270 | convention. By default, @value{GDBN} selects the calling convention based | |
15271 | on the selected architecture and the provided executable file. | |
15272 | ||
15273 | @item set powerpc vector-abi | |
15274 | @itemx show powerpc vector-abi | |
15275 | Force @value{GDBN} to use the specified calling convention for vector | |
15276 | arguments and return values. The valid options are @samp{auto}; | |
15277 | @samp{generic}, to avoid vector registers even if they are present; | |
15278 | @samp{altivec}, to use AltiVec registers; and @samp{spe} to use SPE | |
15279 | registers. By default, @value{GDBN} selects the calling convention | |
15280 | based on the selected architecture and the provided executable file. | |
15281 | ||
8e04817f AC |
15282 | @kindex target dink32 |
15283 | @item target dink32 @var{dev} | |
15284 | DINK32 ROM monitor. | |
104c1213 | 15285 | |
8e04817f AC |
15286 | @kindex target ppcbug |
15287 | @item target ppcbug @var{dev} | |
15288 | @kindex target ppcbug1 | |
15289 | @item target ppcbug1 @var{dev} | |
15290 | PPCBUG ROM monitor for PowerPC. | |
104c1213 | 15291 | |
8e04817f AC |
15292 | @kindex target sds |
15293 | @item target sds @var{dev} | |
15294 | SDS monitor, running on a PowerPC board (such as Motorola's ADS). | |
c45da7e6 | 15295 | @end table |
8e04817f | 15296 | |
c45da7e6 | 15297 | @cindex SDS protocol |
d52fb0e9 | 15298 | The following commands specific to the SDS protocol are supported |
55eddb0f | 15299 | by @value{GDBN}: |
c45da7e6 EZ |
15300 | |
15301 | @table @code | |
15302 | @item set sdstimeout @var{nsec} | |
15303 | @kindex set sdstimeout | |
15304 | Set the timeout for SDS protocol reads to be @var{nsec} seconds. The | |
15305 | default is 2 seconds. | |
15306 | ||
15307 | @item show sdstimeout | |
15308 | @kindex show sdstimeout | |
15309 | Show the current value of the SDS timeout. | |
15310 | ||
15311 | @item sds @var{command} | |
15312 | @kindex sds@r{, a command} | |
15313 | Send the specified @var{command} string to the SDS monitor. | |
8e04817f AC |
15314 | @end table |
15315 | ||
c45da7e6 | 15316 | |
8e04817f AC |
15317 | @node PA |
15318 | @subsection HP PA Embedded | |
104c1213 JM |
15319 | |
15320 | @table @code | |
15321 | ||
8e04817f AC |
15322 | @kindex target op50n |
15323 | @item target op50n @var{dev} | |
15324 | OP50N monitor, running on an OKI HPPA board. | |
15325 | ||
15326 | @kindex target w89k | |
15327 | @item target w89k @var{dev} | |
15328 | W89K monitor, running on a Winbond HPPA board. | |
104c1213 JM |
15329 | |
15330 | @end table | |
15331 | ||
8e04817f AC |
15332 | @node Sparclet |
15333 | @subsection Tsqware Sparclet | |
104c1213 | 15334 | |
8e04817f AC |
15335 | @cindex Sparclet |
15336 | ||
15337 | @value{GDBN} enables developers to debug tasks running on | |
15338 | Sparclet targets from a Unix host. | |
15339 | @value{GDBN} uses code that runs on | |
15340 | both the Unix host and on the Sparclet target. The program | |
15341 | @code{@value{GDBP}} is installed and executed on the Unix host. | |
104c1213 | 15342 | |
8e04817f AC |
15343 | @table @code |
15344 | @item remotetimeout @var{args} | |
15345 | @kindex remotetimeout | |
15346 | @value{GDBN} supports the option @code{remotetimeout}. | |
15347 | This option is set by the user, and @var{args} represents the number of | |
15348 | seconds @value{GDBN} waits for responses. | |
104c1213 JM |
15349 | @end table |
15350 | ||
8e04817f AC |
15351 | @cindex compiling, on Sparclet |
15352 | When compiling for debugging, include the options @samp{-g} to get debug | |
15353 | information and @samp{-Ttext} to relocate the program to where you wish to | |
15354 | load it on the target. You may also want to add the options @samp{-n} or | |
15355 | @samp{-N} in order to reduce the size of the sections. Example: | |
104c1213 | 15356 | |
474c8240 | 15357 | @smallexample |
8e04817f | 15358 | sparclet-aout-gcc prog.c -Ttext 0x12010000 -g -o prog -N |
474c8240 | 15359 | @end smallexample |
104c1213 | 15360 | |
8e04817f | 15361 | You can use @code{objdump} to verify that the addresses are what you intended: |
104c1213 | 15362 | |
474c8240 | 15363 | @smallexample |
8e04817f | 15364 | sparclet-aout-objdump --headers --syms prog |
474c8240 | 15365 | @end smallexample |
104c1213 | 15366 | |
8e04817f AC |
15367 | @cindex running, on Sparclet |
15368 | Once you have set | |
15369 | your Unix execution search path to find @value{GDBN}, you are ready to | |
15370 | run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} | |
15371 | (or @code{sparclet-aout-gdb}, depending on your installation). | |
104c1213 | 15372 | |
8e04817f AC |
15373 | @value{GDBN} comes up showing the prompt: |
15374 | ||
474c8240 | 15375 | @smallexample |
8e04817f | 15376 | (gdbslet) |
474c8240 | 15377 | @end smallexample |
104c1213 JM |
15378 | |
15379 | @menu | |
8e04817f AC |
15380 | * Sparclet File:: Setting the file to debug |
15381 | * Sparclet Connection:: Connecting to Sparclet | |
15382 | * Sparclet Download:: Sparclet download | |
15383 | * Sparclet Execution:: Running and debugging | |
104c1213 JM |
15384 | @end menu |
15385 | ||
8e04817f | 15386 | @node Sparclet File |
79a6e687 | 15387 | @subsubsection Setting File to Debug |
104c1213 | 15388 | |
8e04817f | 15389 | The @value{GDBN} command @code{file} lets you choose with program to debug. |
104c1213 | 15390 | |
474c8240 | 15391 | @smallexample |
8e04817f | 15392 | (gdbslet) file prog |
474c8240 | 15393 | @end smallexample |
104c1213 | 15394 | |
8e04817f AC |
15395 | @need 1000 |
15396 | @value{GDBN} then attempts to read the symbol table of @file{prog}. | |
15397 | @value{GDBN} locates | |
15398 | the file by searching the directories listed in the command search | |
15399 | path. | |
12c27660 | 15400 | If the file was compiled with debug information (option @samp{-g}), source |
8e04817f AC |
15401 | files will be searched as well. |
15402 | @value{GDBN} locates | |
15403 | the source files by searching the directories listed in the directory search | |
79a6e687 | 15404 | path (@pxref{Environment, ,Your Program's Environment}). |
8e04817f AC |
15405 | If it fails |
15406 | to find a file, it displays a message such as: | |
104c1213 | 15407 | |
474c8240 | 15408 | @smallexample |
8e04817f | 15409 | prog: No such file or directory. |
474c8240 | 15410 | @end smallexample |
104c1213 | 15411 | |
8e04817f AC |
15412 | When this happens, add the appropriate directories to the search paths with |
15413 | the @value{GDBN} commands @code{path} and @code{dir}, and execute the | |
15414 | @code{target} command again. | |
104c1213 | 15415 | |
8e04817f AC |
15416 | @node Sparclet Connection |
15417 | @subsubsection Connecting to Sparclet | |
104c1213 | 15418 | |
8e04817f AC |
15419 | The @value{GDBN} command @code{target} lets you connect to a Sparclet target. |
15420 | To connect to a target on serial port ``@code{ttya}'', type: | |
104c1213 | 15421 | |
474c8240 | 15422 | @smallexample |
8e04817f AC |
15423 | (gdbslet) target sparclet /dev/ttya |
15424 | Remote target sparclet connected to /dev/ttya | |
15425 | main () at ../prog.c:3 | |
474c8240 | 15426 | @end smallexample |
104c1213 | 15427 | |
8e04817f AC |
15428 | @need 750 |
15429 | @value{GDBN} displays messages like these: | |
104c1213 | 15430 | |
474c8240 | 15431 | @smallexample |
8e04817f | 15432 | Connected to ttya. |
474c8240 | 15433 | @end smallexample |
104c1213 | 15434 | |
8e04817f | 15435 | @node Sparclet Download |
79a6e687 | 15436 | @subsubsection Sparclet Download |
104c1213 | 15437 | |
8e04817f AC |
15438 | @cindex download to Sparclet |
15439 | Once connected to the Sparclet target, | |
15440 | you can use the @value{GDBN} | |
15441 | @code{load} command to download the file from the host to the target. | |
15442 | The file name and load offset should be given as arguments to the @code{load} | |
15443 | command. | |
15444 | Since the file format is aout, the program must be loaded to the starting | |
15445 | address. You can use @code{objdump} to find out what this value is. The load | |
15446 | offset is an offset which is added to the VMA (virtual memory address) | |
15447 | of each of the file's sections. | |
15448 | For instance, if the program | |
15449 | @file{prog} was linked to text address 0x1201000, with data at 0x12010160 | |
15450 | and bss at 0x12010170, in @value{GDBN}, type: | |
104c1213 | 15451 | |
474c8240 | 15452 | @smallexample |
8e04817f AC |
15453 | (gdbslet) load prog 0x12010000 |
15454 | Loading section .text, size 0xdb0 vma 0x12010000 | |
474c8240 | 15455 | @end smallexample |
104c1213 | 15456 | |
8e04817f AC |
15457 | If the code is loaded at a different address then what the program was linked |
15458 | to, you may need to use the @code{section} and @code{add-symbol-file} commands | |
15459 | to tell @value{GDBN} where to map the symbol table. | |
15460 | ||
15461 | @node Sparclet Execution | |
79a6e687 | 15462 | @subsubsection Running and Debugging |
8e04817f AC |
15463 | |
15464 | @cindex running and debugging Sparclet programs | |
15465 | You can now begin debugging the task using @value{GDBN}'s execution control | |
15466 | commands, @code{b}, @code{step}, @code{run}, etc. See the @value{GDBN} | |
15467 | manual for the list of commands. | |
15468 | ||
474c8240 | 15469 | @smallexample |
8e04817f AC |
15470 | (gdbslet) b main |
15471 | Breakpoint 1 at 0x12010000: file prog.c, line 3. | |
15472 | (gdbslet) run | |
15473 | Starting program: prog | |
15474 | Breakpoint 1, main (argc=1, argv=0xeffff21c) at prog.c:3 | |
15475 | 3 char *symarg = 0; | |
15476 | (gdbslet) step | |
15477 | 4 char *execarg = "hello!"; | |
15478 | (gdbslet) | |
474c8240 | 15479 | @end smallexample |
8e04817f AC |
15480 | |
15481 | @node Sparclite | |
15482 | @subsection Fujitsu Sparclite | |
104c1213 JM |
15483 | |
15484 | @table @code | |
15485 | ||
8e04817f AC |
15486 | @kindex target sparclite |
15487 | @item target sparclite @var{dev} | |
15488 | Fujitsu sparclite boards, used only for the purpose of loading. | |
15489 | You must use an additional command to debug the program. | |
15490 | For example: target remote @var{dev} using @value{GDBN} standard | |
15491 | remote protocol. | |
104c1213 JM |
15492 | |
15493 | @end table | |
15494 | ||
8e04817f AC |
15495 | @node Z8000 |
15496 | @subsection Zilog Z8000 | |
104c1213 | 15497 | |
8e04817f AC |
15498 | @cindex Z8000 |
15499 | @cindex simulator, Z8000 | |
15500 | @cindex Zilog Z8000 simulator | |
104c1213 | 15501 | |
8e04817f AC |
15502 | When configured for debugging Zilog Z8000 targets, @value{GDBN} includes |
15503 | a Z8000 simulator. | |
15504 | ||
15505 | For the Z8000 family, @samp{target sim} simulates either the Z8002 (the | |
15506 | unsegmented variant of the Z8000 architecture) or the Z8001 (the | |
15507 | segmented variant). The simulator recognizes which architecture is | |
15508 | appropriate by inspecting the object code. | |
104c1213 | 15509 | |
8e04817f AC |
15510 | @table @code |
15511 | @item target sim @var{args} | |
15512 | @kindex sim | |
15513 | @kindex target sim@r{, with Z8000} | |
15514 | Debug programs on a simulated CPU. If the simulator supports setup | |
15515 | options, specify them via @var{args}. | |
104c1213 JM |
15516 | @end table |
15517 | ||
8e04817f AC |
15518 | @noindent |
15519 | After specifying this target, you can debug programs for the simulated | |
15520 | CPU in the same style as programs for your host computer; use the | |
15521 | @code{file} command to load a new program image, the @code{run} command | |
15522 | to run your program, and so on. | |
15523 | ||
15524 | As well as making available all the usual machine registers | |
15525 | (@pxref{Registers, ,Registers}), the Z8000 simulator provides three | |
15526 | additional items of information as specially named registers: | |
104c1213 JM |
15527 | |
15528 | @table @code | |
15529 | ||
8e04817f AC |
15530 | @item cycles |
15531 | Counts clock-ticks in the simulator. | |
104c1213 | 15532 | |
8e04817f AC |
15533 | @item insts |
15534 | Counts instructions run in the simulator. | |
104c1213 | 15535 | |
8e04817f AC |
15536 | @item time |
15537 | Execution time in 60ths of a second. | |
104c1213 | 15538 | |
8e04817f | 15539 | @end table |
104c1213 | 15540 | |
8e04817f AC |
15541 | You can refer to these values in @value{GDBN} expressions with the usual |
15542 | conventions; for example, @w{@samp{b fputc if $cycles>5000}} sets a | |
15543 | conditional breakpoint that suspends only after at least 5000 | |
15544 | simulated clock ticks. | |
104c1213 | 15545 | |
a64548ea EZ |
15546 | @node AVR |
15547 | @subsection Atmel AVR | |
15548 | @cindex AVR | |
15549 | ||
15550 | When configured for debugging the Atmel AVR, @value{GDBN} supports the | |
15551 | following AVR-specific commands: | |
15552 | ||
15553 | @table @code | |
15554 | @item info io_registers | |
15555 | @kindex info io_registers@r{, AVR} | |
15556 | @cindex I/O registers (Atmel AVR) | |
15557 | This command displays information about the AVR I/O registers. For | |
15558 | each register, @value{GDBN} prints its number and value. | |
15559 | @end table | |
15560 | ||
15561 | @node CRIS | |
15562 | @subsection CRIS | |
15563 | @cindex CRIS | |
15564 | ||
15565 | When configured for debugging CRIS, @value{GDBN} provides the | |
15566 | following CRIS-specific commands: | |
15567 | ||
15568 | @table @code | |
15569 | @item set cris-version @var{ver} | |
15570 | @cindex CRIS version | |
e22e55c9 OF |
15571 | Set the current CRIS version to @var{ver}, either @samp{10} or @samp{32}. |
15572 | The CRIS version affects register names and sizes. This command is useful in | |
15573 | case autodetection of the CRIS version fails. | |
a64548ea EZ |
15574 | |
15575 | @item show cris-version | |
15576 | Show the current CRIS version. | |
15577 | ||
15578 | @item set cris-dwarf2-cfi | |
15579 | @cindex DWARF-2 CFI and CRIS | |
e22e55c9 OF |
15580 | Set the usage of DWARF-2 CFI for CRIS debugging. The default is @samp{on}. |
15581 | Change to @samp{off} when using @code{gcc-cris} whose version is below | |
15582 | @code{R59}. | |
a64548ea EZ |
15583 | |
15584 | @item show cris-dwarf2-cfi | |
15585 | Show the current state of using DWARF-2 CFI. | |
e22e55c9 OF |
15586 | |
15587 | @item set cris-mode @var{mode} | |
15588 | @cindex CRIS mode | |
15589 | Set the current CRIS mode to @var{mode}. It should only be changed when | |
15590 | debugging in guru mode, in which case it should be set to | |
15591 | @samp{guru} (the default is @samp{normal}). | |
15592 | ||
15593 | @item show cris-mode | |
15594 | Show the current CRIS mode. | |
a64548ea EZ |
15595 | @end table |
15596 | ||
15597 | @node Super-H | |
15598 | @subsection Renesas Super-H | |
15599 | @cindex Super-H | |
15600 | ||
15601 | For the Renesas Super-H processor, @value{GDBN} provides these | |
15602 | commands: | |
15603 | ||
15604 | @table @code | |
15605 | @item regs | |
15606 | @kindex regs@r{, Super-H} | |
15607 | Show the values of all Super-H registers. | |
15608 | @end table | |
15609 | ||
15610 | ||
8e04817f AC |
15611 | @node Architectures |
15612 | @section Architectures | |
104c1213 | 15613 | |
8e04817f AC |
15614 | This section describes characteristics of architectures that affect |
15615 | all uses of @value{GDBN} with the architecture, both native and cross. | |
104c1213 | 15616 | |
8e04817f | 15617 | @menu |
9c16f35a | 15618 | * i386:: |
8e04817f AC |
15619 | * A29K:: |
15620 | * Alpha:: | |
15621 | * MIPS:: | |
a64548ea | 15622 | * HPPA:: HP PA architecture |
23d964e7 | 15623 | * SPU:: Cell Broadband Engine SPU architecture |
4acd40f3 | 15624 | * PowerPC:: |
8e04817f | 15625 | @end menu |
104c1213 | 15626 | |
9c16f35a | 15627 | @node i386 |
db2e3e2e | 15628 | @subsection x86 Architecture-specific Issues |
9c16f35a EZ |
15629 | |
15630 | @table @code | |
15631 | @item set struct-convention @var{mode} | |
15632 | @kindex set struct-convention | |
15633 | @cindex struct return convention | |
15634 | @cindex struct/union returned in registers | |
15635 | Set the convention used by the inferior to return @code{struct}s and | |
15636 | @code{union}s from functions to @var{mode}. Possible values of | |
15637 | @var{mode} are @code{"pcc"}, @code{"reg"}, and @code{"default"} (the | |
15638 | default). @code{"default"} or @code{"pcc"} means that @code{struct}s | |
15639 | are returned on the stack, while @code{"reg"} means that a | |
15640 | @code{struct} or a @code{union} whose size is 1, 2, 4, or 8 bytes will | |
15641 | be returned in a register. | |
15642 | ||
15643 | @item show struct-convention | |
15644 | @kindex show struct-convention | |
15645 | Show the current setting of the convention to return @code{struct}s | |
15646 | from functions. | |
15647 | @end table | |
15648 | ||
8e04817f AC |
15649 | @node A29K |
15650 | @subsection A29K | |
104c1213 JM |
15651 | |
15652 | @table @code | |
104c1213 | 15653 | |
8e04817f AC |
15654 | @kindex set rstack_high_address |
15655 | @cindex AMD 29K register stack | |
15656 | @cindex register stack, AMD29K | |
15657 | @item set rstack_high_address @var{address} | |
15658 | On AMD 29000 family processors, registers are saved in a separate | |
15659 | @dfn{register stack}. There is no way for @value{GDBN} to determine the | |
15660 | extent of this stack. Normally, @value{GDBN} just assumes that the | |
15661 | stack is ``large enough''. This may result in @value{GDBN} referencing | |
15662 | memory locations that do not exist. If necessary, you can get around | |
15663 | this problem by specifying the ending address of the register stack with | |
15664 | the @code{set rstack_high_address} command. The argument should be an | |
15665 | address, which you probably want to precede with @samp{0x} to specify in | |
15666 | hexadecimal. | |
104c1213 | 15667 | |
8e04817f AC |
15668 | @kindex show rstack_high_address |
15669 | @item show rstack_high_address | |
15670 | Display the current limit of the register stack, on AMD 29000 family | |
15671 | processors. | |
104c1213 | 15672 | |
8e04817f | 15673 | @end table |
104c1213 | 15674 | |
8e04817f AC |
15675 | @node Alpha |
15676 | @subsection Alpha | |
104c1213 | 15677 | |
8e04817f | 15678 | See the following section. |
104c1213 | 15679 | |
8e04817f AC |
15680 | @node MIPS |
15681 | @subsection MIPS | |
104c1213 | 15682 | |
8e04817f AC |
15683 | @cindex stack on Alpha |
15684 | @cindex stack on MIPS | |
15685 | @cindex Alpha stack | |
15686 | @cindex MIPS stack | |
15687 | Alpha- and MIPS-based computers use an unusual stack frame, which | |
15688 | sometimes requires @value{GDBN} to search backward in the object code to | |
15689 | find the beginning of a function. | |
104c1213 | 15690 | |
8e04817f AC |
15691 | @cindex response time, MIPS debugging |
15692 | To improve response time (especially for embedded applications, where | |
15693 | @value{GDBN} may be restricted to a slow serial line for this search) | |
15694 | you may want to limit the size of this search, using one of these | |
15695 | commands: | |
104c1213 | 15696 | |
8e04817f AC |
15697 | @table @code |
15698 | @cindex @code{heuristic-fence-post} (Alpha, MIPS) | |
15699 | @item set heuristic-fence-post @var{limit} | |
15700 | Restrict @value{GDBN} to examining at most @var{limit} bytes in its | |
15701 | search for the beginning of a function. A value of @var{0} (the | |
15702 | default) means there is no limit. However, except for @var{0}, the | |
15703 | larger the limit the more bytes @code{heuristic-fence-post} must search | |
e2f4edfd EZ |
15704 | and therefore the longer it takes to run. You should only need to use |
15705 | this command when debugging a stripped executable. | |
104c1213 | 15706 | |
8e04817f AC |
15707 | @item show heuristic-fence-post |
15708 | Display the current limit. | |
15709 | @end table | |
104c1213 JM |
15710 | |
15711 | @noindent | |
8e04817f AC |
15712 | These commands are available @emph{only} when @value{GDBN} is configured |
15713 | for debugging programs on Alpha or MIPS processors. | |
104c1213 | 15714 | |
a64548ea EZ |
15715 | Several MIPS-specific commands are available when debugging MIPS |
15716 | programs: | |
15717 | ||
15718 | @table @code | |
a64548ea EZ |
15719 | @item set mips abi @var{arg} |
15720 | @kindex set mips abi | |
15721 | @cindex set ABI for MIPS | |
15722 | Tell @value{GDBN} which MIPS ABI is used by the inferior. Possible | |
15723 | values of @var{arg} are: | |
15724 | ||
15725 | @table @samp | |
15726 | @item auto | |
15727 | The default ABI associated with the current binary (this is the | |
15728 | default). | |
15729 | @item o32 | |
15730 | @item o64 | |
15731 | @item n32 | |
15732 | @item n64 | |
15733 | @item eabi32 | |
15734 | @item eabi64 | |
15735 | @item auto | |
15736 | @end table | |
15737 | ||
15738 | @item show mips abi | |
15739 | @kindex show mips abi | |
15740 | Show the MIPS ABI used by @value{GDBN} to debug the inferior. | |
15741 | ||
15742 | @item set mipsfpu | |
15743 | @itemx show mipsfpu | |
15744 | @xref{MIPS Embedded, set mipsfpu}. | |
15745 | ||
15746 | @item set mips mask-address @var{arg} | |
15747 | @kindex set mips mask-address | |
15748 | @cindex MIPS addresses, masking | |
15749 | This command determines whether the most-significant 32 bits of 64-bit | |
15750 | MIPS addresses are masked off. The argument @var{arg} can be | |
15751 | @samp{on}, @samp{off}, or @samp{auto}. The latter is the default | |
15752 | setting, which lets @value{GDBN} determine the correct value. | |
15753 | ||
15754 | @item show mips mask-address | |
15755 | @kindex show mips mask-address | |
15756 | Show whether the upper 32 bits of MIPS addresses are masked off or | |
15757 | not. | |
15758 | ||
15759 | @item set remote-mips64-transfers-32bit-regs | |
15760 | @kindex set remote-mips64-transfers-32bit-regs | |
15761 | This command controls compatibility with 64-bit MIPS targets that | |
15762 | transfer data in 32-bit quantities. If you have an old MIPS 64 target | |
15763 | that transfers 32 bits for some registers, like @sc{sr} and @sc{fsr}, | |
15764 | and 64 bits for other registers, set this option to @samp{on}. | |
15765 | ||
15766 | @item show remote-mips64-transfers-32bit-regs | |
15767 | @kindex show remote-mips64-transfers-32bit-regs | |
15768 | Show the current setting of compatibility with older MIPS 64 targets. | |
15769 | ||
15770 | @item set debug mips | |
15771 | @kindex set debug mips | |
15772 | This command turns on and off debugging messages for the MIPS-specific | |
15773 | target code in @value{GDBN}. | |
15774 | ||
15775 | @item show debug mips | |
15776 | @kindex show debug mips | |
15777 | Show the current setting of MIPS debugging messages. | |
15778 | @end table | |
15779 | ||
15780 | ||
15781 | @node HPPA | |
15782 | @subsection HPPA | |
15783 | @cindex HPPA support | |
15784 | ||
d3e8051b | 15785 | When @value{GDBN} is debugging the HP PA architecture, it provides the |
a64548ea EZ |
15786 | following special commands: |
15787 | ||
15788 | @table @code | |
15789 | @item set debug hppa | |
15790 | @kindex set debug hppa | |
db2e3e2e | 15791 | This command determines whether HPPA architecture-specific debugging |
a64548ea EZ |
15792 | messages are to be displayed. |
15793 | ||
15794 | @item show debug hppa | |
15795 | Show whether HPPA debugging messages are displayed. | |
15796 | ||
15797 | @item maint print unwind @var{address} | |
15798 | @kindex maint print unwind@r{, HPPA} | |
15799 | This command displays the contents of the unwind table entry at the | |
15800 | given @var{address}. | |
15801 | ||
15802 | @end table | |
15803 | ||
104c1213 | 15804 | |
23d964e7 UW |
15805 | @node SPU |
15806 | @subsection Cell Broadband Engine SPU architecture | |
15807 | @cindex Cell Broadband Engine | |
15808 | @cindex SPU | |
15809 | ||
15810 | When @value{GDBN} is debugging the Cell Broadband Engine SPU architecture, | |
15811 | it provides the following special commands: | |
15812 | ||
15813 | @table @code | |
15814 | @item info spu event | |
15815 | @kindex info spu | |
15816 | Display SPU event facility status. Shows current event mask | |
15817 | and pending event status. | |
15818 | ||
15819 | @item info spu signal | |
15820 | Display SPU signal notification facility status. Shows pending | |
15821 | signal-control word and signal notification mode of both signal | |
15822 | notification channels. | |
15823 | ||
15824 | @item info spu mailbox | |
15825 | Display SPU mailbox facility status. Shows all pending entries, | |
15826 | in order of processing, in each of the SPU Write Outbound, | |
15827 | SPU Write Outbound Interrupt, and SPU Read Inbound mailboxes. | |
15828 | ||
15829 | @item info spu dma | |
15830 | Display MFC DMA status. Shows all pending commands in the MFC | |
15831 | DMA queue. For each entry, opcode, tag, class IDs, effective | |
15832 | and local store addresses and transfer size are shown. | |
15833 | ||
15834 | @item info spu proxydma | |
15835 | Display MFC Proxy-DMA status. Shows all pending commands in the MFC | |
15836 | Proxy-DMA queue. For each entry, opcode, tag, class IDs, effective | |
15837 | and local store addresses and transfer size are shown. | |
15838 | ||
15839 | @end table | |
15840 | ||
4acd40f3 TJB |
15841 | @node PowerPC |
15842 | @subsection PowerPC | |
15843 | @cindex PowerPC architecture | |
15844 | ||
15845 | When @value{GDBN} is debugging the PowerPC architecture, it provides a set of | |
15846 | pseudo-registers to enable inspection of 128-bit wide Decimal Floating Point | |
15847 | numbers stored in the floating point registers. These values must be stored | |
15848 | in two consecutive registers, always starting at an even register like | |
15849 | @code{f0} or @code{f2}. | |
15850 | ||
15851 | The pseudo-registers go from @code{$dl0} through @code{$dl15}, and are formed | |
15852 | by joining the even/odd register pairs @code{f0} and @code{f1} for @code{$dl0}, | |
15853 | @code{f2} and @code{f3} for @code{$dl1} and so on. | |
15854 | ||
23d964e7 | 15855 | |
8e04817f AC |
15856 | @node Controlling GDB |
15857 | @chapter Controlling @value{GDBN} | |
15858 | ||
15859 | You can alter the way @value{GDBN} interacts with you by using the | |
15860 | @code{set} command. For commands controlling how @value{GDBN} displays | |
79a6e687 | 15861 | data, see @ref{Print Settings, ,Print Settings}. Other settings are |
8e04817f AC |
15862 | described here. |
15863 | ||
15864 | @menu | |
15865 | * Prompt:: Prompt | |
15866 | * Editing:: Command editing | |
d620b259 | 15867 | * Command History:: Command history |
8e04817f AC |
15868 | * Screen Size:: Screen size |
15869 | * Numbers:: Numbers | |
1e698235 | 15870 | * ABI:: Configuring the current ABI |
8e04817f AC |
15871 | * Messages/Warnings:: Optional warnings and messages |
15872 | * Debugging Output:: Optional messages about internal happenings | |
15873 | @end menu | |
15874 | ||
15875 | @node Prompt | |
15876 | @section Prompt | |
104c1213 | 15877 | |
8e04817f | 15878 | @cindex prompt |
104c1213 | 15879 | |
8e04817f AC |
15880 | @value{GDBN} indicates its readiness to read a command by printing a string |
15881 | called the @dfn{prompt}. This string is normally @samp{(@value{GDBP})}. You | |
15882 | can change the prompt string with the @code{set prompt} command. For | |
15883 | instance, when debugging @value{GDBN} with @value{GDBN}, it is useful to change | |
15884 | the prompt in one of the @value{GDBN} sessions so that you can always tell | |
15885 | which one you are talking to. | |
104c1213 | 15886 | |
8e04817f AC |
15887 | @emph{Note:} @code{set prompt} does not add a space for you after the |
15888 | prompt you set. This allows you to set a prompt which ends in a space | |
15889 | or a prompt that does not. | |
104c1213 | 15890 | |
8e04817f AC |
15891 | @table @code |
15892 | @kindex set prompt | |
15893 | @item set prompt @var{newprompt} | |
15894 | Directs @value{GDBN} to use @var{newprompt} as its prompt string henceforth. | |
104c1213 | 15895 | |
8e04817f AC |
15896 | @kindex show prompt |
15897 | @item show prompt | |
15898 | Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}} | |
104c1213 JM |
15899 | @end table |
15900 | ||
8e04817f | 15901 | @node Editing |
79a6e687 | 15902 | @section Command Editing |
8e04817f AC |
15903 | @cindex readline |
15904 | @cindex command line editing | |
104c1213 | 15905 | |
703663ab | 15906 | @value{GDBN} reads its input commands via the @dfn{Readline} interface. This |
8e04817f AC |
15907 | @sc{gnu} library provides consistent behavior for programs which provide a |
15908 | command line interface to the user. Advantages are @sc{gnu} Emacs-style | |
15909 | or @dfn{vi}-style inline editing of commands, @code{csh}-like history | |
15910 | substitution, and a storage and recall of command history across | |
15911 | debugging sessions. | |
104c1213 | 15912 | |
8e04817f AC |
15913 | You may control the behavior of command line editing in @value{GDBN} with the |
15914 | command @code{set}. | |
104c1213 | 15915 | |
8e04817f AC |
15916 | @table @code |
15917 | @kindex set editing | |
15918 | @cindex editing | |
15919 | @item set editing | |
15920 | @itemx set editing on | |
15921 | Enable command line editing (enabled by default). | |
104c1213 | 15922 | |
8e04817f AC |
15923 | @item set editing off |
15924 | Disable command line editing. | |
104c1213 | 15925 | |
8e04817f AC |
15926 | @kindex show editing |
15927 | @item show editing | |
15928 | Show whether command line editing is enabled. | |
104c1213 JM |
15929 | @end table |
15930 | ||
703663ab EZ |
15931 | @xref{Command Line Editing}, for more details about the Readline |
15932 | interface. Users unfamiliar with @sc{gnu} Emacs or @code{vi} are | |
15933 | encouraged to read that chapter. | |
15934 | ||
d620b259 | 15935 | @node Command History |
79a6e687 | 15936 | @section Command History |
703663ab | 15937 | @cindex command history |
8e04817f AC |
15938 | |
15939 | @value{GDBN} can keep track of the commands you type during your | |
15940 | debugging sessions, so that you can be certain of precisely what | |
15941 | happened. Use these commands to manage the @value{GDBN} command | |
15942 | history facility. | |
104c1213 | 15943 | |
703663ab EZ |
15944 | @value{GDBN} uses the @sc{gnu} History library, a part of the Readline |
15945 | package, to provide the history facility. @xref{Using History | |
15946 | Interactively}, for the detailed description of the History library. | |
15947 | ||
d620b259 | 15948 | To issue a command to @value{GDBN} without affecting certain aspects of |
9e6c4bd5 NR |
15949 | the state which is seen by users, prefix it with @samp{server } |
15950 | (@pxref{Server Prefix}). This | |
d620b259 NR |
15951 | means that this command will not affect the command history, nor will it |
15952 | affect @value{GDBN}'s notion of which command to repeat if @key{RET} is | |
15953 | pressed on a line by itself. | |
15954 | ||
15955 | @cindex @code{server}, command prefix | |
15956 | The server prefix does not affect the recording of values into the value | |
15957 | history; to print a value without recording it into the value history, | |
15958 | use the @code{output} command instead of the @code{print} command. | |
15959 | ||
703663ab EZ |
15960 | Here is the description of @value{GDBN} commands related to command |
15961 | history. | |
15962 | ||
104c1213 | 15963 | @table @code |
8e04817f AC |
15964 | @cindex history substitution |
15965 | @cindex history file | |
15966 | @kindex set history filename | |
4644b6e3 | 15967 | @cindex @env{GDBHISTFILE}, environment variable |
8e04817f AC |
15968 | @item set history filename @var{fname} |
15969 | Set the name of the @value{GDBN} command history file to @var{fname}. | |
15970 | This is the file where @value{GDBN} reads an initial command history | |
15971 | list, and where it writes the command history from this session when it | |
15972 | exits. You can access this list through history expansion or through | |
15973 | the history command editing characters listed below. This file defaults | |
15974 | to the value of the environment variable @code{GDBHISTFILE}, or to | |
15975 | @file{./.gdb_history} (@file{./_gdb_history} on MS-DOS) if this variable | |
15976 | is not set. | |
104c1213 | 15977 | |
9c16f35a EZ |
15978 | @cindex save command history |
15979 | @kindex set history save | |
8e04817f AC |
15980 | @item set history save |
15981 | @itemx set history save on | |
15982 | Record command history in a file, whose name may be specified with the | |
15983 | @code{set history filename} command. By default, this option is disabled. | |
104c1213 | 15984 | |
8e04817f AC |
15985 | @item set history save off |
15986 | Stop recording command history in a file. | |
104c1213 | 15987 | |
8e04817f | 15988 | @cindex history size |
9c16f35a | 15989 | @kindex set history size |
6fc08d32 | 15990 | @cindex @env{HISTSIZE}, environment variable |
8e04817f AC |
15991 | @item set history size @var{size} |
15992 | Set the number of commands which @value{GDBN} keeps in its history list. | |
15993 | This defaults to the value of the environment variable | |
15994 | @code{HISTSIZE}, or to 256 if this variable is not set. | |
104c1213 JM |
15995 | @end table |
15996 | ||
8e04817f | 15997 | History expansion assigns special meaning to the character @kbd{!}. |
703663ab | 15998 | @xref{Event Designators}, for more details. |
8e04817f | 15999 | |
703663ab | 16000 | @cindex history expansion, turn on/off |
8e04817f AC |
16001 | Since @kbd{!} is also the logical not operator in C, history expansion |
16002 | is off by default. If you decide to enable history expansion with the | |
16003 | @code{set history expansion on} command, you may sometimes need to | |
16004 | follow @kbd{!} (when it is used as logical not, in an expression) with | |
16005 | a space or a tab to prevent it from being expanded. The readline | |
16006 | history facilities do not attempt substitution on the strings | |
16007 | @kbd{!=} and @kbd{!(}, even when history expansion is enabled. | |
16008 | ||
16009 | The commands to control history expansion are: | |
104c1213 JM |
16010 | |
16011 | @table @code | |
8e04817f AC |
16012 | @item set history expansion on |
16013 | @itemx set history expansion | |
703663ab | 16014 | @kindex set history expansion |
8e04817f | 16015 | Enable history expansion. History expansion is off by default. |
104c1213 | 16016 | |
8e04817f AC |
16017 | @item set history expansion off |
16018 | Disable history expansion. | |
104c1213 | 16019 | |
8e04817f AC |
16020 | @c @group |
16021 | @kindex show history | |
16022 | @item show history | |
16023 | @itemx show history filename | |
16024 | @itemx show history save | |
16025 | @itemx show history size | |
16026 | @itemx show history expansion | |
16027 | These commands display the state of the @value{GDBN} history parameters. | |
16028 | @code{show history} by itself displays all four states. | |
16029 | @c @end group | |
16030 | @end table | |
16031 | ||
16032 | @table @code | |
9c16f35a EZ |
16033 | @kindex show commands |
16034 | @cindex show last commands | |
16035 | @cindex display command history | |
8e04817f AC |
16036 | @item show commands |
16037 | Display the last ten commands in the command history. | |
104c1213 | 16038 | |
8e04817f AC |
16039 | @item show commands @var{n} |
16040 | Print ten commands centered on command number @var{n}. | |
16041 | ||
16042 | @item show commands + | |
16043 | Print ten commands just after the commands last printed. | |
104c1213 JM |
16044 | @end table |
16045 | ||
8e04817f | 16046 | @node Screen Size |
79a6e687 | 16047 | @section Screen Size |
8e04817f AC |
16048 | @cindex size of screen |
16049 | @cindex pauses in output | |
104c1213 | 16050 | |
8e04817f AC |
16051 | Certain commands to @value{GDBN} may produce large amounts of |
16052 | information output to the screen. To help you read all of it, | |
16053 | @value{GDBN} pauses and asks you for input at the end of each page of | |
16054 | output. Type @key{RET} when you want to continue the output, or @kbd{q} | |
16055 | to discard the remaining output. Also, the screen width setting | |
16056 | determines when to wrap lines of output. Depending on what is being | |
16057 | printed, @value{GDBN} tries to break the line at a readable place, | |
16058 | rather than simply letting it overflow onto the following line. | |
16059 | ||
16060 | Normally @value{GDBN} knows the size of the screen from the terminal | |
16061 | driver software. For example, on Unix @value{GDBN} uses the termcap data base | |
16062 | together with the value of the @code{TERM} environment variable and the | |
16063 | @code{stty rows} and @code{stty cols} settings. If this is not correct, | |
16064 | you can override it with the @code{set height} and @code{set | |
16065 | width} commands: | |
16066 | ||
16067 | @table @code | |
16068 | @kindex set height | |
16069 | @kindex set width | |
16070 | @kindex show width | |
16071 | @kindex show height | |
16072 | @item set height @var{lpp} | |
16073 | @itemx show height | |
16074 | @itemx set width @var{cpl} | |
16075 | @itemx show width | |
16076 | These @code{set} commands specify a screen height of @var{lpp} lines and | |
16077 | a screen width of @var{cpl} characters. The associated @code{show} | |
16078 | commands display the current settings. | |
104c1213 | 16079 | |
8e04817f AC |
16080 | If you specify a height of zero lines, @value{GDBN} does not pause during |
16081 | output no matter how long the output is. This is useful if output is to a | |
16082 | file or to an editor buffer. | |
104c1213 | 16083 | |
8e04817f AC |
16084 | Likewise, you can specify @samp{set width 0} to prevent @value{GDBN} |
16085 | from wrapping its output. | |
9c16f35a EZ |
16086 | |
16087 | @item set pagination on | |
16088 | @itemx set pagination off | |
16089 | @kindex set pagination | |
16090 | Turn the output pagination on or off; the default is on. Turning | |
16091 | pagination off is the alternative to @code{set height 0}. | |
16092 | ||
16093 | @item show pagination | |
16094 | @kindex show pagination | |
16095 | Show the current pagination mode. | |
104c1213 JM |
16096 | @end table |
16097 | ||
8e04817f AC |
16098 | @node Numbers |
16099 | @section Numbers | |
16100 | @cindex number representation | |
16101 | @cindex entering numbers | |
104c1213 | 16102 | |
8e04817f AC |
16103 | You can always enter numbers in octal, decimal, or hexadecimal in |
16104 | @value{GDBN} by the usual conventions: octal numbers begin with | |
16105 | @samp{0}, decimal numbers end with @samp{.}, and hexadecimal numbers | |
eb2dae08 EZ |
16106 | begin with @samp{0x}. Numbers that neither begin with @samp{0} or |
16107 | @samp{0x}, nor end with a @samp{.} are, by default, entered in base | |
16108 | 10; likewise, the default display for numbers---when no particular | |
16109 | format is specified---is base 10. You can change the default base for | |
16110 | both input and output with the commands described below. | |
104c1213 | 16111 | |
8e04817f AC |
16112 | @table @code |
16113 | @kindex set input-radix | |
16114 | @item set input-radix @var{base} | |
16115 | Set the default base for numeric input. Supported choices | |
16116 | for @var{base} are decimal 8, 10, or 16. @var{base} must itself be | |
eb2dae08 | 16117 | specified either unambiguously or using the current input radix; for |
8e04817f | 16118 | example, any of |
104c1213 | 16119 | |
8e04817f | 16120 | @smallexample |
9c16f35a EZ |
16121 | set input-radix 012 |
16122 | set input-radix 10. | |
16123 | set input-radix 0xa | |
8e04817f | 16124 | @end smallexample |
104c1213 | 16125 | |
8e04817f | 16126 | @noindent |
9c16f35a | 16127 | sets the input base to decimal. On the other hand, @samp{set input-radix 10} |
eb2dae08 EZ |
16128 | leaves the input radix unchanged, no matter what it was, since |
16129 | @samp{10}, being without any leading or trailing signs of its base, is | |
16130 | interpreted in the current radix. Thus, if the current radix is 16, | |
16131 | @samp{10} is interpreted in hex, i.e.@: as 16 decimal, which doesn't | |
16132 | change the radix. | |
104c1213 | 16133 | |
8e04817f AC |
16134 | @kindex set output-radix |
16135 | @item set output-radix @var{base} | |
16136 | Set the default base for numeric display. Supported choices | |
16137 | for @var{base} are decimal 8, 10, or 16. @var{base} must itself be | |
eb2dae08 | 16138 | specified either unambiguously or using the current input radix. |
104c1213 | 16139 | |
8e04817f AC |
16140 | @kindex show input-radix |
16141 | @item show input-radix | |
16142 | Display the current default base for numeric input. | |
104c1213 | 16143 | |
8e04817f AC |
16144 | @kindex show output-radix |
16145 | @item show output-radix | |
16146 | Display the current default base for numeric display. | |
9c16f35a EZ |
16147 | |
16148 | @item set radix @r{[}@var{base}@r{]} | |
16149 | @itemx show radix | |
16150 | @kindex set radix | |
16151 | @kindex show radix | |
16152 | These commands set and show the default base for both input and output | |
16153 | of numbers. @code{set radix} sets the radix of input and output to | |
16154 | the same base; without an argument, it resets the radix back to its | |
16155 | default value of 10. | |
16156 | ||
8e04817f | 16157 | @end table |
104c1213 | 16158 | |
1e698235 | 16159 | @node ABI |
79a6e687 | 16160 | @section Configuring the Current ABI |
1e698235 DJ |
16161 | |
16162 | @value{GDBN} can determine the @dfn{ABI} (Application Binary Interface) of your | |
16163 | application automatically. However, sometimes you need to override its | |
16164 | conclusions. Use these commands to manage @value{GDBN}'s view of the | |
16165 | current ABI. | |
16166 | ||
98b45e30 DJ |
16167 | @cindex OS ABI |
16168 | @kindex set osabi | |
b4e9345d | 16169 | @kindex show osabi |
98b45e30 DJ |
16170 | |
16171 | One @value{GDBN} configuration can debug binaries for multiple operating | |
b383017d | 16172 | system targets, either via remote debugging or native emulation. |
98b45e30 DJ |
16173 | @value{GDBN} will autodetect the @dfn{OS ABI} (Operating System ABI) in use, |
16174 | but you can override its conclusion using the @code{set osabi} command. | |
16175 | One example where this is useful is in debugging of binaries which use | |
16176 | an alternate C library (e.g.@: @sc{uClibc} for @sc{gnu}/Linux) which does | |
16177 | not have the same identifying marks that the standard C library for your | |
16178 | platform provides. | |
16179 | ||
16180 | @table @code | |
16181 | @item show osabi | |
16182 | Show the OS ABI currently in use. | |
16183 | ||
16184 | @item set osabi | |
16185 | With no argument, show the list of registered available OS ABI's. | |
16186 | ||
16187 | @item set osabi @var{abi} | |
16188 | Set the current OS ABI to @var{abi}. | |
16189 | @end table | |
16190 | ||
1e698235 | 16191 | @cindex float promotion |
1e698235 DJ |
16192 | |
16193 | Generally, the way that an argument of type @code{float} is passed to a | |
16194 | function depends on whether the function is prototyped. For a prototyped | |
16195 | (i.e.@: ANSI/ISO style) function, @code{float} arguments are passed unchanged, | |
16196 | according to the architecture's convention for @code{float}. For unprototyped | |
16197 | (i.e.@: K&R style) functions, @code{float} arguments are first promoted to type | |
16198 | @code{double} and then passed. | |
16199 | ||
16200 | Unfortunately, some forms of debug information do not reliably indicate whether | |
16201 | a function is prototyped. If @value{GDBN} calls a function that is not marked | |
16202 | as prototyped, it consults @kbd{set coerce-float-to-double}. | |
16203 | ||
16204 | @table @code | |
a8f24a35 | 16205 | @kindex set coerce-float-to-double |
1e698235 DJ |
16206 | @item set coerce-float-to-double |
16207 | @itemx set coerce-float-to-double on | |
16208 | Arguments of type @code{float} will be promoted to @code{double} when passed | |
16209 | to an unprototyped function. This is the default setting. | |
16210 | ||
16211 | @item set coerce-float-to-double off | |
16212 | Arguments of type @code{float} will be passed directly to unprototyped | |
16213 | functions. | |
9c16f35a EZ |
16214 | |
16215 | @kindex show coerce-float-to-double | |
16216 | @item show coerce-float-to-double | |
16217 | Show the current setting of promoting @code{float} to @code{double}. | |
1e698235 DJ |
16218 | @end table |
16219 | ||
f1212245 DJ |
16220 | @kindex set cp-abi |
16221 | @kindex show cp-abi | |
16222 | @value{GDBN} needs to know the ABI used for your program's C@t{++} | |
16223 | objects. The correct C@t{++} ABI depends on which C@t{++} compiler was | |
16224 | used to build your application. @value{GDBN} only fully supports | |
16225 | programs with a single C@t{++} ABI; if your program contains code using | |
16226 | multiple C@t{++} ABI's or if @value{GDBN} can not identify your | |
16227 | program's ABI correctly, you can tell @value{GDBN} which ABI to use. | |
16228 | Currently supported ABI's include ``gnu-v2'', for @code{g++} versions | |
16229 | before 3.0, ``gnu-v3'', for @code{g++} versions 3.0 and later, and | |
16230 | ``hpaCC'' for the HP ANSI C@t{++} compiler. Other C@t{++} compilers may | |
16231 | use the ``gnu-v2'' or ``gnu-v3'' ABI's as well. The default setting is | |
16232 | ``auto''. | |
16233 | ||
16234 | @table @code | |
16235 | @item show cp-abi | |
16236 | Show the C@t{++} ABI currently in use. | |
16237 | ||
16238 | @item set cp-abi | |
16239 | With no argument, show the list of supported C@t{++} ABI's. | |
16240 | ||
16241 | @item set cp-abi @var{abi} | |
16242 | @itemx set cp-abi auto | |
16243 | Set the current C@t{++} ABI to @var{abi}, or return to automatic detection. | |
16244 | @end table | |
16245 | ||
8e04817f | 16246 | @node Messages/Warnings |
79a6e687 | 16247 | @section Optional Warnings and Messages |
104c1213 | 16248 | |
9c16f35a EZ |
16249 | @cindex verbose operation |
16250 | @cindex optional warnings | |
8e04817f AC |
16251 | By default, @value{GDBN} is silent about its inner workings. If you are |
16252 | running on a slow machine, you may want to use the @code{set verbose} | |
16253 | command. This makes @value{GDBN} tell you when it does a lengthy | |
16254 | internal operation, so you will not think it has crashed. | |
104c1213 | 16255 | |
8e04817f AC |
16256 | Currently, the messages controlled by @code{set verbose} are those |
16257 | which announce that the symbol table for a source file is being read; | |
79a6e687 | 16258 | see @code{symbol-file} in @ref{Files, ,Commands to Specify Files}. |
104c1213 | 16259 | |
8e04817f AC |
16260 | @table @code |
16261 | @kindex set verbose | |
16262 | @item set verbose on | |
16263 | Enables @value{GDBN} output of certain informational messages. | |
104c1213 | 16264 | |
8e04817f AC |
16265 | @item set verbose off |
16266 | Disables @value{GDBN} output of certain informational messages. | |
104c1213 | 16267 | |
8e04817f AC |
16268 | @kindex show verbose |
16269 | @item show verbose | |
16270 | Displays whether @code{set verbose} is on or off. | |
16271 | @end table | |
104c1213 | 16272 | |
8e04817f AC |
16273 | By default, if @value{GDBN} encounters bugs in the symbol table of an |
16274 | object file, it is silent; but if you are debugging a compiler, you may | |
79a6e687 BW |
16275 | find this information useful (@pxref{Symbol Errors, ,Errors Reading |
16276 | Symbol Files}). | |
104c1213 | 16277 | |
8e04817f | 16278 | @table @code |
104c1213 | 16279 | |
8e04817f AC |
16280 | @kindex set complaints |
16281 | @item set complaints @var{limit} | |
16282 | Permits @value{GDBN} to output @var{limit} complaints about each type of | |
16283 | unusual symbols before becoming silent about the problem. Set | |
16284 | @var{limit} to zero to suppress all complaints; set it to a large number | |
16285 | to prevent complaints from being suppressed. | |
104c1213 | 16286 | |
8e04817f AC |
16287 | @kindex show complaints |
16288 | @item show complaints | |
16289 | Displays how many symbol complaints @value{GDBN} is permitted to produce. | |
104c1213 | 16290 | |
8e04817f | 16291 | @end table |
104c1213 | 16292 | |
8e04817f AC |
16293 | By default, @value{GDBN} is cautious, and asks what sometimes seems to be a |
16294 | lot of stupid questions to confirm certain commands. For example, if | |
16295 | you try to run a program which is already running: | |
104c1213 | 16296 | |
474c8240 | 16297 | @smallexample |
8e04817f AC |
16298 | (@value{GDBP}) run |
16299 | The program being debugged has been started already. | |
16300 | Start it from the beginning? (y or n) | |
474c8240 | 16301 | @end smallexample |
104c1213 | 16302 | |
8e04817f AC |
16303 | If you are willing to unflinchingly face the consequences of your own |
16304 | commands, you can disable this ``feature'': | |
104c1213 | 16305 | |
8e04817f | 16306 | @table @code |
104c1213 | 16307 | |
8e04817f AC |
16308 | @kindex set confirm |
16309 | @cindex flinching | |
16310 | @cindex confirmation | |
16311 | @cindex stupid questions | |
16312 | @item set confirm off | |
16313 | Disables confirmation requests. | |
104c1213 | 16314 | |
8e04817f AC |
16315 | @item set confirm on |
16316 | Enables confirmation requests (the default). | |
104c1213 | 16317 | |
8e04817f AC |
16318 | @kindex show confirm |
16319 | @item show confirm | |
16320 | Displays state of confirmation requests. | |
16321 | ||
16322 | @end table | |
104c1213 | 16323 | |
16026cd7 AS |
16324 | @cindex command tracing |
16325 | If you need to debug user-defined commands or sourced files you may find it | |
16326 | useful to enable @dfn{command tracing}. In this mode each command will be | |
16327 | printed as it is executed, prefixed with one or more @samp{+} symbols, the | |
16328 | quantity denoting the call depth of each command. | |
16329 | ||
16330 | @table @code | |
16331 | @kindex set trace-commands | |
16332 | @cindex command scripts, debugging | |
16333 | @item set trace-commands on | |
16334 | Enable command tracing. | |
16335 | @item set trace-commands off | |
16336 | Disable command tracing. | |
16337 | @item show trace-commands | |
16338 | Display the current state of command tracing. | |
16339 | @end table | |
16340 | ||
8e04817f | 16341 | @node Debugging Output |
79a6e687 | 16342 | @section Optional Messages about Internal Happenings |
4644b6e3 EZ |
16343 | @cindex optional debugging messages |
16344 | ||
da316a69 EZ |
16345 | @value{GDBN} has commands that enable optional debugging messages from |
16346 | various @value{GDBN} subsystems; normally these commands are of | |
16347 | interest to @value{GDBN} maintainers, or when reporting a bug. This | |
16348 | section documents those commands. | |
16349 | ||
104c1213 | 16350 | @table @code |
a8f24a35 EZ |
16351 | @kindex set exec-done-display |
16352 | @item set exec-done-display | |
16353 | Turns on or off the notification of asynchronous commands' | |
16354 | completion. When on, @value{GDBN} will print a message when an | |
16355 | asynchronous command finishes its execution. The default is off. | |
16356 | @kindex show exec-done-display | |
16357 | @item show exec-done-display | |
16358 | Displays the current setting of asynchronous command completion | |
16359 | notification. | |
4644b6e3 EZ |
16360 | @kindex set debug |
16361 | @cindex gdbarch debugging info | |
a8f24a35 | 16362 | @cindex architecture debugging info |
8e04817f | 16363 | @item set debug arch |
a8f24a35 | 16364 | Turns on or off display of gdbarch debugging info. The default is off |
4644b6e3 | 16365 | @kindex show debug |
8e04817f AC |
16366 | @item show debug arch |
16367 | Displays the current state of displaying gdbarch debugging info. | |
721c2651 EZ |
16368 | @item set debug aix-thread |
16369 | @cindex AIX threads | |
16370 | Display debugging messages about inner workings of the AIX thread | |
16371 | module. | |
16372 | @item show debug aix-thread | |
16373 | Show the current state of AIX thread debugging info display. | |
8e04817f | 16374 | @item set debug event |
4644b6e3 | 16375 | @cindex event debugging info |
a8f24a35 | 16376 | Turns on or off display of @value{GDBN} event debugging info. The |
8e04817f | 16377 | default is off. |
8e04817f AC |
16378 | @item show debug event |
16379 | Displays the current state of displaying @value{GDBN} event debugging | |
16380 | info. | |
8e04817f | 16381 | @item set debug expression |
4644b6e3 | 16382 | @cindex expression debugging info |
721c2651 EZ |
16383 | Turns on or off display of debugging info about @value{GDBN} |
16384 | expression parsing. The default is off. | |
8e04817f | 16385 | @item show debug expression |
721c2651 EZ |
16386 | Displays the current state of displaying debugging info about |
16387 | @value{GDBN} expression parsing. | |
7453dc06 | 16388 | @item set debug frame |
4644b6e3 | 16389 | @cindex frame debugging info |
7453dc06 AC |
16390 | Turns on or off display of @value{GDBN} frame debugging info. The |
16391 | default is off. | |
7453dc06 AC |
16392 | @item show debug frame |
16393 | Displays the current state of displaying @value{GDBN} frame debugging | |
16394 | info. | |
30e91e0b RC |
16395 | @item set debug infrun |
16396 | @cindex inferior debugging info | |
16397 | Turns on or off display of @value{GDBN} debugging info for running the inferior. | |
16398 | The default is off. @file{infrun.c} contains GDB's runtime state machine used | |
16399 | for implementing operations such as single-stepping the inferior. | |
16400 | @item show debug infrun | |
16401 | Displays the current state of @value{GDBN} inferior debugging. | |
da316a69 EZ |
16402 | @item set debug lin-lwp |
16403 | @cindex @sc{gnu}/Linux LWP debug messages | |
16404 | @cindex Linux lightweight processes | |
721c2651 | 16405 | Turns on or off debugging messages from the Linux LWP debug support. |
da316a69 EZ |
16406 | @item show debug lin-lwp |
16407 | Show the current state of Linux LWP debugging messages. | |
2b4855ab | 16408 | @item set debug observer |
4644b6e3 | 16409 | @cindex observer debugging info |
2b4855ab AC |
16410 | Turns on or off display of @value{GDBN} observer debugging. This |
16411 | includes info such as the notification of observable events. | |
2b4855ab AC |
16412 | @item show debug observer |
16413 | Displays the current state of observer debugging. | |
8e04817f | 16414 | @item set debug overload |
4644b6e3 | 16415 | @cindex C@t{++} overload debugging info |
8e04817f | 16416 | Turns on or off display of @value{GDBN} C@t{++} overload debugging |
359df76b | 16417 | info. This includes info such as ranking of functions, etc. The default |
8e04817f | 16418 | is off. |
8e04817f AC |
16419 | @item show debug overload |
16420 | Displays the current state of displaying @value{GDBN} C@t{++} overload | |
16421 | debugging info. | |
8e04817f AC |
16422 | @cindex packets, reporting on stdout |
16423 | @cindex serial connections, debugging | |
605a56cb DJ |
16424 | @cindex debug remote protocol |
16425 | @cindex remote protocol debugging | |
16426 | @cindex display remote packets | |
8e04817f AC |
16427 | @item set debug remote |
16428 | Turns on or off display of reports on all packets sent back and forth across | |
16429 | the serial line to the remote machine. The info is printed on the | |
16430 | @value{GDBN} standard output stream. The default is off. | |
8e04817f AC |
16431 | @item show debug remote |
16432 | Displays the state of display of remote packets. | |
8e04817f AC |
16433 | @item set debug serial |
16434 | Turns on or off display of @value{GDBN} serial debugging info. The | |
16435 | default is off. | |
8e04817f AC |
16436 | @item show debug serial |
16437 | Displays the current state of displaying @value{GDBN} serial debugging | |
16438 | info. | |
c45da7e6 EZ |
16439 | @item set debug solib-frv |
16440 | @cindex FR-V shared-library debugging | |
16441 | Turns on or off debugging messages for FR-V shared-library code. | |
16442 | @item show debug solib-frv | |
16443 | Display the current state of FR-V shared-library code debugging | |
16444 | messages. | |
8e04817f | 16445 | @item set debug target |
4644b6e3 | 16446 | @cindex target debugging info |
8e04817f AC |
16447 | Turns on or off display of @value{GDBN} target debugging info. This info |
16448 | includes what is going on at the target level of GDB, as it happens. The | |
701b08bb DJ |
16449 | default is 0. Set it to 1 to track events, and to 2 to also track the |
16450 | value of large memory transfers. Changes to this flag do not take effect | |
16451 | until the next time you connect to a target or use the @code{run} command. | |
8e04817f AC |
16452 | @item show debug target |
16453 | Displays the current state of displaying @value{GDBN} target debugging | |
16454 | info. | |
75feb17d DJ |
16455 | @item set debug timestamp |
16456 | @cindex timestampping debugging info | |
16457 | Turns on or off display of timestamps with @value{GDBN} debugging info. | |
16458 | When enabled, seconds and microseconds are displayed before each debugging | |
16459 | message. | |
16460 | @item show debug timestamp | |
16461 | Displays the current state of displaying timestamps with @value{GDBN} | |
16462 | debugging info. | |
c45da7e6 | 16463 | @item set debugvarobj |
4644b6e3 | 16464 | @cindex variable object debugging info |
8e04817f AC |
16465 | Turns on or off display of @value{GDBN} variable object debugging |
16466 | info. The default is off. | |
c45da7e6 | 16467 | @item show debugvarobj |
8e04817f AC |
16468 | Displays the current state of displaying @value{GDBN} variable object |
16469 | debugging info. | |
e776119f DJ |
16470 | @item set debug xml |
16471 | @cindex XML parser debugging | |
16472 | Turns on or off debugging messages for built-in XML parsers. | |
16473 | @item show debug xml | |
16474 | Displays the current state of XML debugging messages. | |
8e04817f | 16475 | @end table |
104c1213 | 16476 | |
8e04817f AC |
16477 | @node Sequences |
16478 | @chapter Canned Sequences of Commands | |
104c1213 | 16479 | |
8e04817f | 16480 | Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint |
79a6e687 | 16481 | Command Lists}), @value{GDBN} provides two ways to store sequences of |
8e04817f AC |
16482 | commands for execution as a unit: user-defined commands and command |
16483 | files. | |
104c1213 | 16484 | |
8e04817f | 16485 | @menu |
fcc73fe3 EZ |
16486 | * Define:: How to define your own commands |
16487 | * Hooks:: Hooks for user-defined commands | |
16488 | * Command Files:: How to write scripts of commands to be stored in a file | |
16489 | * Output:: Commands for controlled output | |
8e04817f | 16490 | @end menu |
104c1213 | 16491 | |
8e04817f | 16492 | @node Define |
79a6e687 | 16493 | @section User-defined Commands |
104c1213 | 16494 | |
8e04817f | 16495 | @cindex user-defined command |
fcc73fe3 | 16496 | @cindex arguments, to user-defined commands |
8e04817f AC |
16497 | A @dfn{user-defined command} is a sequence of @value{GDBN} commands to |
16498 | which you assign a new name as a command. This is done with the | |
16499 | @code{define} command. User commands may accept up to 10 arguments | |
16500 | separated by whitespace. Arguments are accessed within the user command | |
c03c782f | 16501 | via @code{$arg0@dots{}$arg9}. A trivial example: |
104c1213 | 16502 | |
8e04817f AC |
16503 | @smallexample |
16504 | define adder | |
16505 | print $arg0 + $arg1 + $arg2 | |
c03c782f | 16506 | end |
8e04817f | 16507 | @end smallexample |
104c1213 JM |
16508 | |
16509 | @noindent | |
8e04817f | 16510 | To execute the command use: |
104c1213 | 16511 | |
8e04817f AC |
16512 | @smallexample |
16513 | adder 1 2 3 | |
16514 | @end smallexample | |
104c1213 | 16515 | |
8e04817f AC |
16516 | @noindent |
16517 | This defines the command @code{adder}, which prints the sum of | |
16518 | its three arguments. Note the arguments are text substitutions, so they may | |
16519 | reference variables, use complex expressions, or even perform inferior | |
16520 | functions calls. | |
104c1213 | 16521 | |
fcc73fe3 EZ |
16522 | @cindex argument count in user-defined commands |
16523 | @cindex how many arguments (user-defined commands) | |
c03c782f AS |
16524 | In addition, @code{$argc} may be used to find out how many arguments have |
16525 | been passed. This expands to a number in the range 0@dots{}10. | |
16526 | ||
16527 | @smallexample | |
16528 | define adder | |
16529 | if $argc == 2 | |
16530 | print $arg0 + $arg1 | |
16531 | end | |
16532 | if $argc == 3 | |
16533 | print $arg0 + $arg1 + $arg2 | |
16534 | end | |
16535 | end | |
16536 | @end smallexample | |
16537 | ||
104c1213 | 16538 | @table @code |
104c1213 | 16539 | |
8e04817f AC |
16540 | @kindex define |
16541 | @item define @var{commandname} | |
16542 | Define a command named @var{commandname}. If there is already a command | |
16543 | by that name, you are asked to confirm that you want to redefine it. | |
104c1213 | 16544 | |
8e04817f AC |
16545 | The definition of the command is made up of other @value{GDBN} command lines, |
16546 | which are given following the @code{define} command. The end of these | |
16547 | commands is marked by a line containing @code{end}. | |
104c1213 | 16548 | |
8e04817f | 16549 | @kindex document |
ca91424e | 16550 | @kindex end@r{ (user-defined commands)} |
8e04817f AC |
16551 | @item document @var{commandname} |
16552 | Document the user-defined command @var{commandname}, so that it can be | |
16553 | accessed by @code{help}. The command @var{commandname} must already be | |
16554 | defined. This command reads lines of documentation just as @code{define} | |
16555 | reads the lines of the command definition, ending with @code{end}. | |
16556 | After the @code{document} command is finished, @code{help} on command | |
16557 | @var{commandname} displays the documentation you have written. | |
104c1213 | 16558 | |
8e04817f AC |
16559 | You may use the @code{document} command again to change the |
16560 | documentation of a command. Redefining the command with @code{define} | |
16561 | does not change the documentation. | |
104c1213 | 16562 | |
c45da7e6 EZ |
16563 | @kindex dont-repeat |
16564 | @cindex don't repeat command | |
16565 | @item dont-repeat | |
16566 | Used inside a user-defined command, this tells @value{GDBN} that this | |
16567 | command should not be repeated when the user hits @key{RET} | |
16568 | (@pxref{Command Syntax, repeat last command}). | |
16569 | ||
8e04817f AC |
16570 | @kindex help user-defined |
16571 | @item help user-defined | |
16572 | List all user-defined commands, with the first line of the documentation | |
16573 | (if any) for each. | |
104c1213 | 16574 | |
8e04817f AC |
16575 | @kindex show user |
16576 | @item show user | |
16577 | @itemx show user @var{commandname} | |
16578 | Display the @value{GDBN} commands used to define @var{commandname} (but | |
16579 | not its documentation). If no @var{commandname} is given, display the | |
16580 | definitions for all user-defined commands. | |
104c1213 | 16581 | |
fcc73fe3 | 16582 | @cindex infinite recursion in user-defined commands |
20f01a46 DH |
16583 | @kindex show max-user-call-depth |
16584 | @kindex set max-user-call-depth | |
16585 | @item show max-user-call-depth | |
5ca0cb28 DH |
16586 | @itemx set max-user-call-depth |
16587 | The value of @code{max-user-call-depth} controls how many recursion | |
3f94c067 | 16588 | levels are allowed in user-defined commands before @value{GDBN} suspects an |
5ca0cb28 | 16589 | infinite recursion and aborts the command. |
104c1213 JM |
16590 | @end table |
16591 | ||
fcc73fe3 EZ |
16592 | In addition to the above commands, user-defined commands frequently |
16593 | use control flow commands, described in @ref{Command Files}. | |
16594 | ||
8e04817f AC |
16595 | When user-defined commands are executed, the |
16596 | commands of the definition are not printed. An error in any command | |
16597 | stops execution of the user-defined command. | |
104c1213 | 16598 | |
8e04817f AC |
16599 | If used interactively, commands that would ask for confirmation proceed |
16600 | without asking when used inside a user-defined command. Many @value{GDBN} | |
16601 | commands that normally print messages to say what they are doing omit the | |
16602 | messages when used in a user-defined command. | |
104c1213 | 16603 | |
8e04817f | 16604 | @node Hooks |
79a6e687 | 16605 | @section User-defined Command Hooks |
8e04817f AC |
16606 | @cindex command hooks |
16607 | @cindex hooks, for commands | |
16608 | @cindex hooks, pre-command | |
104c1213 | 16609 | |
8e04817f | 16610 | @kindex hook |
8e04817f AC |
16611 | You may define @dfn{hooks}, which are a special kind of user-defined |
16612 | command. Whenever you run the command @samp{foo}, if the user-defined | |
16613 | command @samp{hook-foo} exists, it is executed (with no arguments) | |
16614 | before that command. | |
104c1213 | 16615 | |
8e04817f AC |
16616 | @cindex hooks, post-command |
16617 | @kindex hookpost | |
8e04817f AC |
16618 | A hook may also be defined which is run after the command you executed. |
16619 | Whenever you run the command @samp{foo}, if the user-defined command | |
16620 | @samp{hookpost-foo} exists, it is executed (with no arguments) after | |
16621 | that command. Post-execution hooks may exist simultaneously with | |
16622 | pre-execution hooks, for the same command. | |
104c1213 | 16623 | |
8e04817f | 16624 | It is valid for a hook to call the command which it hooks. If this |
9f1c6395 | 16625 | occurs, the hook is not re-executed, thereby avoiding infinite recursion. |
104c1213 | 16626 | |
8e04817f AC |
16627 | @c It would be nice if hookpost could be passed a parameter indicating |
16628 | @c if the command it hooks executed properly or not. FIXME! | |
104c1213 | 16629 | |
8e04817f AC |
16630 | @kindex stop@r{, a pseudo-command} |
16631 | In addition, a pseudo-command, @samp{stop} exists. Defining | |
16632 | (@samp{hook-stop}) makes the associated commands execute every time | |
16633 | execution stops in your program: before breakpoint commands are run, | |
16634 | displays are printed, or the stack frame is printed. | |
104c1213 | 16635 | |
8e04817f AC |
16636 | For example, to ignore @code{SIGALRM} signals while |
16637 | single-stepping, but treat them normally during normal execution, | |
16638 | you could define: | |
104c1213 | 16639 | |
474c8240 | 16640 | @smallexample |
8e04817f AC |
16641 | define hook-stop |
16642 | handle SIGALRM nopass | |
16643 | end | |
104c1213 | 16644 | |
8e04817f AC |
16645 | define hook-run |
16646 | handle SIGALRM pass | |
16647 | end | |
104c1213 | 16648 | |
8e04817f | 16649 | define hook-continue |
d3e8051b | 16650 | handle SIGALRM pass |
8e04817f | 16651 | end |
474c8240 | 16652 | @end smallexample |
104c1213 | 16653 | |
d3e8051b | 16654 | As a further example, to hook at the beginning and end of the @code{echo} |
b383017d | 16655 | command, and to add extra text to the beginning and end of the message, |
8e04817f | 16656 | you could define: |
104c1213 | 16657 | |
474c8240 | 16658 | @smallexample |
8e04817f AC |
16659 | define hook-echo |
16660 | echo <<<--- | |
16661 | end | |
104c1213 | 16662 | |
8e04817f AC |
16663 | define hookpost-echo |
16664 | echo --->>>\n | |
16665 | end | |
104c1213 | 16666 | |
8e04817f AC |
16667 | (@value{GDBP}) echo Hello World |
16668 | <<<---Hello World--->>> | |
16669 | (@value{GDBP}) | |
104c1213 | 16670 | |
474c8240 | 16671 | @end smallexample |
104c1213 | 16672 | |
8e04817f AC |
16673 | You can define a hook for any single-word command in @value{GDBN}, but |
16674 | not for command aliases; you should define a hook for the basic command | |
c1468174 | 16675 | name, e.g.@: @code{backtrace} rather than @code{bt}. |
8e04817f AC |
16676 | @c FIXME! So how does Joe User discover whether a command is an alias |
16677 | @c or not? | |
16678 | If an error occurs during the execution of your hook, execution of | |
16679 | @value{GDBN} commands stops and @value{GDBN} issues a prompt | |
16680 | (before the command that you actually typed had a chance to run). | |
104c1213 | 16681 | |
8e04817f AC |
16682 | If you try to define a hook which does not match any known command, you |
16683 | get a warning from the @code{define} command. | |
c906108c | 16684 | |
8e04817f | 16685 | @node Command Files |
79a6e687 | 16686 | @section Command Files |
c906108c | 16687 | |
8e04817f | 16688 | @cindex command files |
fcc73fe3 | 16689 | @cindex scripting commands |
6fc08d32 EZ |
16690 | A command file for @value{GDBN} is a text file made of lines that are |
16691 | @value{GDBN} commands. Comments (lines starting with @kbd{#}) may | |
16692 | also be included. An empty line in a command file does nothing; it | |
16693 | does not mean to repeat the last command, as it would from the | |
16694 | terminal. | |
c906108c | 16695 | |
6fc08d32 EZ |
16696 | You can request the execution of a command file with the @code{source} |
16697 | command: | |
c906108c | 16698 | |
8e04817f AC |
16699 | @table @code |
16700 | @kindex source | |
ca91424e | 16701 | @cindex execute commands from a file |
16026cd7 | 16702 | @item source [@code{-v}] @var{filename} |
8e04817f | 16703 | Execute the command file @var{filename}. |
c906108c SS |
16704 | @end table |
16705 | ||
fcc73fe3 EZ |
16706 | The lines in a command file are generally executed sequentially, |
16707 | unless the order of execution is changed by one of the | |
16708 | @emph{flow-control commands} described below. The commands are not | |
a71ec265 DH |
16709 | printed as they are executed. An error in any command terminates |
16710 | execution of the command file and control is returned to the console. | |
c906108c | 16711 | |
4b505b12 AS |
16712 | @value{GDBN} searches for @var{filename} in the current directory and then |
16713 | on the search path (specified with the @samp{directory} command). | |
16714 | ||
16026cd7 AS |
16715 | If @code{-v}, for verbose mode, is given then @value{GDBN} displays |
16716 | each command as it is executed. The option must be given before | |
16717 | @var{filename}, and is interpreted as part of the filename anywhere else. | |
16718 | ||
8e04817f AC |
16719 | Commands that would ask for confirmation if used interactively proceed |
16720 | without asking when used in a command file. Many @value{GDBN} commands that | |
16721 | normally print messages to say what they are doing omit the messages | |
16722 | when called from command files. | |
c906108c | 16723 | |
8e04817f AC |
16724 | @value{GDBN} also accepts command input from standard input. In this |
16725 | mode, normal output goes to standard output and error output goes to | |
16726 | standard error. Errors in a command file supplied on standard input do | |
6fc08d32 | 16727 | not terminate execution of the command file---execution continues with |
8e04817f | 16728 | the next command. |
c906108c | 16729 | |
474c8240 | 16730 | @smallexample |
8e04817f | 16731 | gdb < cmds > log 2>&1 |
474c8240 | 16732 | @end smallexample |
c906108c | 16733 | |
8e04817f AC |
16734 | (The syntax above will vary depending on the shell used.) This example |
16735 | will execute commands from the file @file{cmds}. All output and errors | |
16736 | would be directed to @file{log}. | |
c906108c | 16737 | |
fcc73fe3 EZ |
16738 | Since commands stored on command files tend to be more general than |
16739 | commands typed interactively, they frequently need to deal with | |
16740 | complicated situations, such as different or unexpected values of | |
16741 | variables and symbols, changes in how the program being debugged is | |
16742 | built, etc. @value{GDBN} provides a set of flow-control commands to | |
16743 | deal with these complexities. Using these commands, you can write | |
16744 | complex scripts that loop over data structures, execute commands | |
16745 | conditionally, etc. | |
16746 | ||
16747 | @table @code | |
16748 | @kindex if | |
16749 | @kindex else | |
16750 | @item if | |
16751 | @itemx else | |
16752 | This command allows to include in your script conditionally executed | |
16753 | commands. The @code{if} command takes a single argument, which is an | |
16754 | expression to evaluate. It is followed by a series of commands that | |
16755 | are executed only if the expression is true (its value is nonzero). | |
16756 | There can then optionally be an @code{else} line, followed by a series | |
16757 | of commands that are only executed if the expression was false. The | |
16758 | end of the list is marked by a line containing @code{end}. | |
16759 | ||
16760 | @kindex while | |
16761 | @item while | |
16762 | This command allows to write loops. Its syntax is similar to | |
16763 | @code{if}: the command takes a single argument, which is an expression | |
16764 | to evaluate, and must be followed by the commands to execute, one per | |
16765 | line, terminated by an @code{end}. These commands are called the | |
16766 | @dfn{body} of the loop. The commands in the body of @code{while} are | |
16767 | executed repeatedly as long as the expression evaluates to true. | |
16768 | ||
16769 | @kindex loop_break | |
16770 | @item loop_break | |
16771 | This command exits the @code{while} loop in whose body it is included. | |
16772 | Execution of the script continues after that @code{while}s @code{end} | |
16773 | line. | |
16774 | ||
16775 | @kindex loop_continue | |
16776 | @item loop_continue | |
16777 | This command skips the execution of the rest of the body of commands | |
16778 | in the @code{while} loop in whose body it is included. Execution | |
16779 | branches to the beginning of the @code{while} loop, where it evaluates | |
16780 | the controlling expression. | |
ca91424e EZ |
16781 | |
16782 | @kindex end@r{ (if/else/while commands)} | |
16783 | @item end | |
16784 | Terminate the block of commands that are the body of @code{if}, | |
16785 | @code{else}, or @code{while} flow-control commands. | |
fcc73fe3 EZ |
16786 | @end table |
16787 | ||
16788 | ||
8e04817f | 16789 | @node Output |
79a6e687 | 16790 | @section Commands for Controlled Output |
c906108c | 16791 | |
8e04817f AC |
16792 | During the execution of a command file or a user-defined command, normal |
16793 | @value{GDBN} output is suppressed; the only output that appears is what is | |
16794 | explicitly printed by the commands in the definition. This section | |
16795 | describes three commands useful for generating exactly the output you | |
16796 | want. | |
c906108c SS |
16797 | |
16798 | @table @code | |
8e04817f AC |
16799 | @kindex echo |
16800 | @item echo @var{text} | |
16801 | @c I do not consider backslash-space a standard C escape sequence | |
16802 | @c because it is not in ANSI. | |
16803 | Print @var{text}. Nonprinting characters can be included in | |
16804 | @var{text} using C escape sequences, such as @samp{\n} to print a | |
16805 | newline. @strong{No newline is printed unless you specify one.} | |
16806 | In addition to the standard C escape sequences, a backslash followed | |
16807 | by a space stands for a space. This is useful for displaying a | |
16808 | string with spaces at the beginning or the end, since leading and | |
16809 | trailing spaces are otherwise trimmed from all arguments. | |
16810 | To print @samp{@w{ }and foo =@w{ }}, use the command | |
16811 | @samp{echo \@w{ }and foo = \@w{ }}. | |
c906108c | 16812 | |
8e04817f AC |
16813 | A backslash at the end of @var{text} can be used, as in C, to continue |
16814 | the command onto subsequent lines. For example, | |
c906108c | 16815 | |
474c8240 | 16816 | @smallexample |
8e04817f AC |
16817 | echo This is some text\n\ |
16818 | which is continued\n\ | |
16819 | onto several lines.\n | |
474c8240 | 16820 | @end smallexample |
c906108c | 16821 | |
8e04817f | 16822 | produces the same output as |
c906108c | 16823 | |
474c8240 | 16824 | @smallexample |
8e04817f AC |
16825 | echo This is some text\n |
16826 | echo which is continued\n | |
16827 | echo onto several lines.\n | |
474c8240 | 16828 | @end smallexample |
c906108c | 16829 | |
8e04817f AC |
16830 | @kindex output |
16831 | @item output @var{expression} | |
16832 | Print the value of @var{expression} and nothing but that value: no | |
16833 | newlines, no @samp{$@var{nn} = }. The value is not entered in the | |
16834 | value history either. @xref{Expressions, ,Expressions}, for more information | |
16835 | on expressions. | |
c906108c | 16836 | |
8e04817f AC |
16837 | @item output/@var{fmt} @var{expression} |
16838 | Print the value of @var{expression} in format @var{fmt}. You can use | |
16839 | the same formats as for @code{print}. @xref{Output Formats,,Output | |
79a6e687 | 16840 | Formats}, for more information. |
c906108c | 16841 | |
8e04817f | 16842 | @kindex printf |
82160952 EZ |
16843 | @item printf @var{template}, @var{expressions}@dots{} |
16844 | Print the values of one or more @var{expressions} under the control of | |
16845 | the string @var{template}. To print several values, make | |
16846 | @var{expressions} be a comma-separated list of individual expressions, | |
16847 | which may be either numbers or pointers. Their values are printed as | |
16848 | specified by @var{template}, exactly as a C program would do by | |
16849 | executing the code below: | |
c906108c | 16850 | |
474c8240 | 16851 | @smallexample |
82160952 | 16852 | printf (@var{template}, @var{expressions}@dots{}); |
474c8240 | 16853 | @end smallexample |
c906108c | 16854 | |
82160952 EZ |
16855 | As in @code{C} @code{printf}, ordinary characters in @var{template} |
16856 | are printed verbatim, while @dfn{conversion specification} introduced | |
16857 | by the @samp{%} character cause subsequent @var{expressions} to be | |
16858 | evaluated, their values converted and formatted according to type and | |
16859 | style information encoded in the conversion specifications, and then | |
16860 | printed. | |
16861 | ||
8e04817f | 16862 | For example, you can print two values in hex like this: |
c906108c | 16863 | |
8e04817f AC |
16864 | @smallexample |
16865 | printf "foo, bar-foo = 0x%x, 0x%x\n", foo, bar-foo | |
16866 | @end smallexample | |
c906108c | 16867 | |
82160952 EZ |
16868 | @code{printf} supports all the standard @code{C} conversion |
16869 | specifications, including the flags and modifiers between the @samp{%} | |
16870 | character and the conversion letter, with the following exceptions: | |
16871 | ||
16872 | @itemize @bullet | |
16873 | @item | |
16874 | The argument-ordering modifiers, such as @samp{2$}, are not supported. | |
16875 | ||
16876 | @item | |
16877 | The modifier @samp{*} is not supported for specifying precision or | |
16878 | width. | |
16879 | ||
16880 | @item | |
16881 | The @samp{'} flag (for separation of digits into groups according to | |
16882 | @code{LC_NUMERIC'}) is not supported. | |
16883 | ||
16884 | @item | |
16885 | The type modifiers @samp{hh}, @samp{j}, @samp{t}, and @samp{z} are not | |
16886 | supported. | |
16887 | ||
16888 | @item | |
16889 | The conversion letter @samp{n} (as in @samp{%n}) is not supported. | |
16890 | ||
16891 | @item | |
16892 | The conversion letters @samp{a} and @samp{A} are not supported. | |
16893 | @end itemize | |
16894 | ||
16895 | @noindent | |
16896 | Note that the @samp{ll} type modifier is supported only if the | |
16897 | underlying @code{C} implementation used to build @value{GDBN} supports | |
16898 | the @code{long long int} type, and the @samp{L} type modifier is | |
16899 | supported only if @code{long double} type is available. | |
16900 | ||
16901 | As in @code{C}, @code{printf} supports simple backslash-escape | |
16902 | sequences, such as @code{\n}, @samp{\t}, @samp{\\}, @samp{\"}, | |
16903 | @samp{\a}, and @samp{\f}, that consist of backslash followed by a | |
16904 | single character. Octal and hexadecimal escape sequences are not | |
16905 | supported. | |
1a619819 LM |
16906 | |
16907 | Additionally, @code{printf} supports conversion specifications for DFP | |
0aea4bf3 LM |
16908 | (@dfn{Decimal Floating Point}) types using the following length modifiers |
16909 | together with a floating point specifier. | |
1a619819 LM |
16910 | letters: |
16911 | ||
16912 | @itemize @bullet | |
16913 | @item | |
16914 | @samp{H} for printing @code{Decimal32} types. | |
16915 | ||
16916 | @item | |
16917 | @samp{D} for printing @code{Decimal64} types. | |
16918 | ||
16919 | @item | |
16920 | @samp{DD} for printing @code{Decimal128} types. | |
16921 | @end itemize | |
16922 | ||
16923 | If the underlying @code{C} implementation used to build @value{GDBN} has | |
0aea4bf3 | 16924 | support for the three length modifiers for DFP types, other modifiers |
3b784c4f | 16925 | such as width and precision will also be available for @value{GDBN} to use. |
1a619819 LM |
16926 | |
16927 | In case there is no such @code{C} support, no additional modifiers will be | |
16928 | available and the value will be printed in the standard way. | |
16929 | ||
16930 | Here's an example of printing DFP types using the above conversion letters: | |
16931 | @smallexample | |
0aea4bf3 | 16932 | printf "D32: %Hf - D64: %Df - D128: %DDf\n",1.2345df,1.2E10dd,1.2E1dl |
1a619819 LM |
16933 | @end smallexample |
16934 | ||
c906108c SS |
16935 | @end table |
16936 | ||
21c294e6 AC |
16937 | @node Interpreters |
16938 | @chapter Command Interpreters | |
16939 | @cindex command interpreters | |
16940 | ||
16941 | @value{GDBN} supports multiple command interpreters, and some command | |
16942 | infrastructure to allow users or user interface writers to switch | |
16943 | between interpreters or run commands in other interpreters. | |
16944 | ||
16945 | @value{GDBN} currently supports two command interpreters, the console | |
16946 | interpreter (sometimes called the command-line interpreter or @sc{cli}) | |
16947 | and the machine interface interpreter (or @sc{gdb/mi}). This manual | |
16948 | describes both of these interfaces in great detail. | |
16949 | ||
16950 | By default, @value{GDBN} will start with the console interpreter. | |
16951 | However, the user may choose to start @value{GDBN} with another | |
16952 | interpreter by specifying the @option{-i} or @option{--interpreter} | |
16953 | startup options. Defined interpreters include: | |
16954 | ||
16955 | @table @code | |
16956 | @item console | |
16957 | @cindex console interpreter | |
16958 | The traditional console or command-line interpreter. This is the most often | |
16959 | used interpreter with @value{GDBN}. With no interpreter specified at runtime, | |
16960 | @value{GDBN} will use this interpreter. | |
16961 | ||
16962 | @item mi | |
16963 | @cindex mi interpreter | |
16964 | The newest @sc{gdb/mi} interface (currently @code{mi2}). Used primarily | |
16965 | by programs wishing to use @value{GDBN} as a backend for a debugger GUI | |
16966 | or an IDE. For more information, see @ref{GDB/MI, ,The @sc{gdb/mi} | |
16967 | Interface}. | |
16968 | ||
16969 | @item mi2 | |
16970 | @cindex mi2 interpreter | |
16971 | The current @sc{gdb/mi} interface. | |
16972 | ||
16973 | @item mi1 | |
16974 | @cindex mi1 interpreter | |
16975 | The @sc{gdb/mi} interface included in @value{GDBN} 5.1, 5.2, and 5.3. | |
16976 | ||
16977 | @end table | |
16978 | ||
16979 | @cindex invoke another interpreter | |
16980 | The interpreter being used by @value{GDBN} may not be dynamically | |
16981 | switched at runtime. Although possible, this could lead to a very | |
16982 | precarious situation. Consider an IDE using @sc{gdb/mi}. If a user | |
16983 | enters the command "interpreter-set console" in a console view, | |
16984 | @value{GDBN} would switch to using the console interpreter, rendering | |
16985 | the IDE inoperable! | |
16986 | ||
16987 | @kindex interpreter-exec | |
16988 | Although you may only choose a single interpreter at startup, you may execute | |
16989 | commands in any interpreter from the current interpreter using the appropriate | |
16990 | command. If you are running the console interpreter, simply use the | |
16991 | @code{interpreter-exec} command: | |
16992 | ||
16993 | @smallexample | |
16994 | interpreter-exec mi "-data-list-register-names" | |
16995 | @end smallexample | |
16996 | ||
16997 | @sc{gdb/mi} has a similar command, although it is only available in versions of | |
16998 | @value{GDBN} which support @sc{gdb/mi} version 2 (or greater). | |
16999 | ||
8e04817f AC |
17000 | @node TUI |
17001 | @chapter @value{GDBN} Text User Interface | |
17002 | @cindex TUI | |
d0d5df6f | 17003 | @cindex Text User Interface |
c906108c | 17004 | |
8e04817f AC |
17005 | @menu |
17006 | * TUI Overview:: TUI overview | |
17007 | * TUI Keys:: TUI key bindings | |
7cf36c78 | 17008 | * TUI Single Key Mode:: TUI single key mode |
db2e3e2e | 17009 | * TUI Commands:: TUI-specific commands |
8e04817f AC |
17010 | * TUI Configuration:: TUI configuration variables |
17011 | @end menu | |
c906108c | 17012 | |
46ba6afa | 17013 | The @value{GDBN} Text User Interface (TUI) is a terminal |
d0d5df6f AC |
17014 | interface which uses the @code{curses} library to show the source |
17015 | file, the assembly output, the program registers and @value{GDBN} | |
46ba6afa BW |
17016 | commands in separate text windows. The TUI mode is supported only |
17017 | on platforms where a suitable version of the @code{curses} library | |
17018 | is available. | |
d0d5df6f | 17019 | |
46ba6afa BW |
17020 | @pindex @value{GDBTUI} |
17021 | The TUI mode is enabled by default when you invoke @value{GDBN} as | |
17022 | either @samp{@value{GDBTUI}} or @samp{@value{GDBP} -tui}. | |
17023 | You can also switch in and out of TUI mode while @value{GDBN} runs by | |
17024 | using various TUI commands and key bindings, such as @kbd{C-x C-a}. | |
17025 | @xref{TUI Keys, ,TUI Key Bindings}. | |
c906108c | 17026 | |
8e04817f | 17027 | @node TUI Overview |
79a6e687 | 17028 | @section TUI Overview |
c906108c | 17029 | |
46ba6afa | 17030 | In TUI mode, @value{GDBN} can display several text windows: |
c906108c | 17031 | |
8e04817f AC |
17032 | @table @emph |
17033 | @item command | |
17034 | This window is the @value{GDBN} command window with the @value{GDBN} | |
46ba6afa BW |
17035 | prompt and the @value{GDBN} output. The @value{GDBN} input is still |
17036 | managed using readline. | |
c906108c | 17037 | |
8e04817f AC |
17038 | @item source |
17039 | The source window shows the source file of the program. The current | |
46ba6afa | 17040 | line and active breakpoints are displayed in this window. |
c906108c | 17041 | |
8e04817f AC |
17042 | @item assembly |
17043 | The assembly window shows the disassembly output of the program. | |
c906108c | 17044 | |
8e04817f | 17045 | @item register |
46ba6afa BW |
17046 | This window shows the processor registers. Registers are highlighted |
17047 | when their values change. | |
c906108c SS |
17048 | @end table |
17049 | ||
269c21fe | 17050 | The source and assembly windows show the current program position |
46ba6afa BW |
17051 | by highlighting the current line and marking it with a @samp{>} marker. |
17052 | Breakpoints are indicated with two markers. The first marker | |
269c21fe SC |
17053 | indicates the breakpoint type: |
17054 | ||
17055 | @table @code | |
17056 | @item B | |
17057 | Breakpoint which was hit at least once. | |
17058 | ||
17059 | @item b | |
17060 | Breakpoint which was never hit. | |
17061 | ||
17062 | @item H | |
17063 | Hardware breakpoint which was hit at least once. | |
17064 | ||
17065 | @item h | |
17066 | Hardware breakpoint which was never hit. | |
269c21fe SC |
17067 | @end table |
17068 | ||
17069 | The second marker indicates whether the breakpoint is enabled or not: | |
17070 | ||
17071 | @table @code | |
17072 | @item + | |
17073 | Breakpoint is enabled. | |
17074 | ||
17075 | @item - | |
17076 | Breakpoint is disabled. | |
269c21fe SC |
17077 | @end table |
17078 | ||
46ba6afa BW |
17079 | The source, assembly and register windows are updated when the current |
17080 | thread changes, when the frame changes, or when the program counter | |
17081 | changes. | |
17082 | ||
17083 | These windows are not all visible at the same time. The command | |
17084 | window is always visible. The others can be arranged in several | |
17085 | layouts: | |
c906108c | 17086 | |
8e04817f AC |
17087 | @itemize @bullet |
17088 | @item | |
46ba6afa | 17089 | source only, |
2df3850c | 17090 | |
8e04817f | 17091 | @item |
46ba6afa | 17092 | assembly only, |
8e04817f AC |
17093 | |
17094 | @item | |
46ba6afa | 17095 | source and assembly, |
8e04817f AC |
17096 | |
17097 | @item | |
46ba6afa | 17098 | source and registers, or |
c906108c | 17099 | |
8e04817f | 17100 | @item |
46ba6afa | 17101 | assembly and registers. |
8e04817f | 17102 | @end itemize |
c906108c | 17103 | |
46ba6afa | 17104 | A status line above the command window shows the following information: |
b7bb15bc SC |
17105 | |
17106 | @table @emph | |
17107 | @item target | |
46ba6afa | 17108 | Indicates the current @value{GDBN} target. |
b7bb15bc SC |
17109 | (@pxref{Targets, ,Specifying a Debugging Target}). |
17110 | ||
17111 | @item process | |
46ba6afa | 17112 | Gives the current process or thread number. |
b7bb15bc SC |
17113 | When no process is being debugged, this field is set to @code{No process}. |
17114 | ||
17115 | @item function | |
17116 | Gives the current function name for the selected frame. | |
17117 | The name is demangled if demangling is turned on (@pxref{Print Settings}). | |
46ba6afa | 17118 | When there is no symbol corresponding to the current program counter, |
b7bb15bc SC |
17119 | the string @code{??} is displayed. |
17120 | ||
17121 | @item line | |
17122 | Indicates the current line number for the selected frame. | |
46ba6afa | 17123 | When the current line number is not known, the string @code{??} is displayed. |
b7bb15bc SC |
17124 | |
17125 | @item pc | |
17126 | Indicates the current program counter address. | |
b7bb15bc SC |
17127 | @end table |
17128 | ||
8e04817f AC |
17129 | @node TUI Keys |
17130 | @section TUI Key Bindings | |
17131 | @cindex TUI key bindings | |
c906108c | 17132 | |
8e04817f | 17133 | The TUI installs several key bindings in the readline keymaps |
46ba6afa | 17134 | (@pxref{Command Line Editing}). The following key bindings |
8e04817f | 17135 | are installed for both TUI mode and the @value{GDBN} standard mode. |
c906108c | 17136 | |
8e04817f AC |
17137 | @table @kbd |
17138 | @kindex C-x C-a | |
17139 | @item C-x C-a | |
17140 | @kindex C-x a | |
17141 | @itemx C-x a | |
17142 | @kindex C-x A | |
17143 | @itemx C-x A | |
46ba6afa BW |
17144 | Enter or leave the TUI mode. When leaving the TUI mode, |
17145 | the curses window management stops and @value{GDBN} operates using | |
17146 | its standard mode, writing on the terminal directly. When reentering | |
17147 | the TUI mode, control is given back to the curses windows. | |
8e04817f | 17148 | The screen is then refreshed. |
c906108c | 17149 | |
8e04817f AC |
17150 | @kindex C-x 1 |
17151 | @item C-x 1 | |
17152 | Use a TUI layout with only one window. The layout will | |
17153 | either be @samp{source} or @samp{assembly}. When the TUI mode | |
17154 | is not active, it will switch to the TUI mode. | |
2df3850c | 17155 | |
8e04817f | 17156 | Think of this key binding as the Emacs @kbd{C-x 1} binding. |
c906108c | 17157 | |
8e04817f AC |
17158 | @kindex C-x 2 |
17159 | @item C-x 2 | |
17160 | Use a TUI layout with at least two windows. When the current | |
46ba6afa | 17161 | layout already has two windows, the next layout with two windows is used. |
8e04817f AC |
17162 | When a new layout is chosen, one window will always be common to the |
17163 | previous layout and the new one. | |
c906108c | 17164 | |
8e04817f | 17165 | Think of it as the Emacs @kbd{C-x 2} binding. |
2df3850c | 17166 | |
72ffddc9 SC |
17167 | @kindex C-x o |
17168 | @item C-x o | |
17169 | Change the active window. The TUI associates several key bindings | |
46ba6afa | 17170 | (like scrolling and arrow keys) with the active window. This command |
72ffddc9 SC |
17171 | gives the focus to the next TUI window. |
17172 | ||
17173 | Think of it as the Emacs @kbd{C-x o} binding. | |
17174 | ||
7cf36c78 SC |
17175 | @kindex C-x s |
17176 | @item C-x s | |
46ba6afa BW |
17177 | Switch in and out of the TUI SingleKey mode that binds single |
17178 | keys to @value{GDBN} commands (@pxref{TUI Single Key Mode}). | |
c906108c SS |
17179 | @end table |
17180 | ||
46ba6afa | 17181 | The following key bindings only work in the TUI mode: |
5d161b24 | 17182 | |
46ba6afa | 17183 | @table @asis |
8e04817f | 17184 | @kindex PgUp |
46ba6afa | 17185 | @item @key{PgUp} |
8e04817f | 17186 | Scroll the active window one page up. |
c906108c | 17187 | |
8e04817f | 17188 | @kindex PgDn |
46ba6afa | 17189 | @item @key{PgDn} |
8e04817f | 17190 | Scroll the active window one page down. |
c906108c | 17191 | |
8e04817f | 17192 | @kindex Up |
46ba6afa | 17193 | @item @key{Up} |
8e04817f | 17194 | Scroll the active window one line up. |
c906108c | 17195 | |
8e04817f | 17196 | @kindex Down |
46ba6afa | 17197 | @item @key{Down} |
8e04817f | 17198 | Scroll the active window one line down. |
c906108c | 17199 | |
8e04817f | 17200 | @kindex Left |
46ba6afa | 17201 | @item @key{Left} |
8e04817f | 17202 | Scroll the active window one column left. |
c906108c | 17203 | |
8e04817f | 17204 | @kindex Right |
46ba6afa | 17205 | @item @key{Right} |
8e04817f | 17206 | Scroll the active window one column right. |
c906108c | 17207 | |
8e04817f | 17208 | @kindex C-L |
46ba6afa | 17209 | @item @kbd{C-L} |
8e04817f | 17210 | Refresh the screen. |
8e04817f | 17211 | @end table |
c906108c | 17212 | |
46ba6afa BW |
17213 | Because the arrow keys scroll the active window in the TUI mode, they |
17214 | are not available for their normal use by readline unless the command | |
17215 | window has the focus. When another window is active, you must use | |
17216 | other readline key bindings such as @kbd{C-p}, @kbd{C-n}, @kbd{C-b} | |
17217 | and @kbd{C-f} to control the command window. | |
8e04817f | 17218 | |
7cf36c78 SC |
17219 | @node TUI Single Key Mode |
17220 | @section TUI Single Key Mode | |
17221 | @cindex TUI single key mode | |
17222 | ||
46ba6afa BW |
17223 | The TUI also provides a @dfn{SingleKey} mode, which binds several |
17224 | frequently used @value{GDBN} commands to single keys. Type @kbd{C-x s} to | |
17225 | switch into this mode, where the following key bindings are used: | |
7cf36c78 SC |
17226 | |
17227 | @table @kbd | |
17228 | @kindex c @r{(SingleKey TUI key)} | |
17229 | @item c | |
17230 | continue | |
17231 | ||
17232 | @kindex d @r{(SingleKey TUI key)} | |
17233 | @item d | |
17234 | down | |
17235 | ||
17236 | @kindex f @r{(SingleKey TUI key)} | |
17237 | @item f | |
17238 | finish | |
17239 | ||
17240 | @kindex n @r{(SingleKey TUI key)} | |
17241 | @item n | |
17242 | next | |
17243 | ||
17244 | @kindex q @r{(SingleKey TUI key)} | |
17245 | @item q | |
46ba6afa | 17246 | exit the SingleKey mode. |
7cf36c78 SC |
17247 | |
17248 | @kindex r @r{(SingleKey TUI key)} | |
17249 | @item r | |
17250 | run | |
17251 | ||
17252 | @kindex s @r{(SingleKey TUI key)} | |
17253 | @item s | |
17254 | step | |
17255 | ||
17256 | @kindex u @r{(SingleKey TUI key)} | |
17257 | @item u | |
17258 | up | |
17259 | ||
17260 | @kindex v @r{(SingleKey TUI key)} | |
17261 | @item v | |
17262 | info locals | |
17263 | ||
17264 | @kindex w @r{(SingleKey TUI key)} | |
17265 | @item w | |
17266 | where | |
7cf36c78 SC |
17267 | @end table |
17268 | ||
17269 | Other keys temporarily switch to the @value{GDBN} command prompt. | |
17270 | The key that was pressed is inserted in the editing buffer so that | |
17271 | it is possible to type most @value{GDBN} commands without interaction | |
46ba6afa BW |
17272 | with the TUI SingleKey mode. Once the command is entered the TUI |
17273 | SingleKey mode is restored. The only way to permanently leave | |
7f9087cb | 17274 | this mode is by typing @kbd{q} or @kbd{C-x s}. |
7cf36c78 SC |
17275 | |
17276 | ||
8e04817f | 17277 | @node TUI Commands |
db2e3e2e | 17278 | @section TUI-specific Commands |
8e04817f AC |
17279 | @cindex TUI commands |
17280 | ||
17281 | The TUI has specific commands to control the text windows. | |
46ba6afa BW |
17282 | These commands are always available, even when @value{GDBN} is not in |
17283 | the TUI mode. When @value{GDBN} is in the standard mode, most | |
17284 | of these commands will automatically switch to the TUI mode. | |
c906108c SS |
17285 | |
17286 | @table @code | |
3d757584 SC |
17287 | @item info win |
17288 | @kindex info win | |
17289 | List and give the size of all displayed windows. | |
17290 | ||
8e04817f | 17291 | @item layout next |
4644b6e3 | 17292 | @kindex layout |
8e04817f | 17293 | Display the next layout. |
2df3850c | 17294 | |
8e04817f | 17295 | @item layout prev |
8e04817f | 17296 | Display the previous layout. |
c906108c | 17297 | |
8e04817f | 17298 | @item layout src |
8e04817f | 17299 | Display the source window only. |
c906108c | 17300 | |
8e04817f | 17301 | @item layout asm |
8e04817f | 17302 | Display the assembly window only. |
c906108c | 17303 | |
8e04817f | 17304 | @item layout split |
8e04817f | 17305 | Display the source and assembly window. |
c906108c | 17306 | |
8e04817f | 17307 | @item layout regs |
8e04817f AC |
17308 | Display the register window together with the source or assembly window. |
17309 | ||
46ba6afa | 17310 | @item focus next |
8e04817f | 17311 | @kindex focus |
46ba6afa BW |
17312 | Make the next window active for scrolling. |
17313 | ||
17314 | @item focus prev | |
17315 | Make the previous window active for scrolling. | |
17316 | ||
17317 | @item focus src | |
17318 | Make the source window active for scrolling. | |
17319 | ||
17320 | @item focus asm | |
17321 | Make the assembly window active for scrolling. | |
17322 | ||
17323 | @item focus regs | |
17324 | Make the register window active for scrolling. | |
17325 | ||
17326 | @item focus cmd | |
17327 | Make the command window active for scrolling. | |
c906108c | 17328 | |
8e04817f AC |
17329 | @item refresh |
17330 | @kindex refresh | |
7f9087cb | 17331 | Refresh the screen. This is similar to typing @kbd{C-L}. |
c906108c | 17332 | |
6a1b180d SC |
17333 | @item tui reg float |
17334 | @kindex tui reg | |
17335 | Show the floating point registers in the register window. | |
17336 | ||
17337 | @item tui reg general | |
17338 | Show the general registers in the register window. | |
17339 | ||
17340 | @item tui reg next | |
17341 | Show the next register group. The list of register groups as well as | |
17342 | their order is target specific. The predefined register groups are the | |
17343 | following: @code{general}, @code{float}, @code{system}, @code{vector}, | |
17344 | @code{all}, @code{save}, @code{restore}. | |
17345 | ||
17346 | @item tui reg system | |
17347 | Show the system registers in the register window. | |
17348 | ||
8e04817f AC |
17349 | @item update |
17350 | @kindex update | |
17351 | Update the source window and the current execution point. | |
c906108c | 17352 | |
8e04817f AC |
17353 | @item winheight @var{name} +@var{count} |
17354 | @itemx winheight @var{name} -@var{count} | |
17355 | @kindex winheight | |
17356 | Change the height of the window @var{name} by @var{count} | |
17357 | lines. Positive counts increase the height, while negative counts | |
17358 | decrease it. | |
2df3850c | 17359 | |
46ba6afa BW |
17360 | @item tabset @var{nchars} |
17361 | @kindex tabset | |
c45da7e6 | 17362 | Set the width of tab stops to be @var{nchars} characters. |
c906108c SS |
17363 | @end table |
17364 | ||
8e04817f | 17365 | @node TUI Configuration |
79a6e687 | 17366 | @section TUI Configuration Variables |
8e04817f | 17367 | @cindex TUI configuration variables |
c906108c | 17368 | |
46ba6afa | 17369 | Several configuration variables control the appearance of TUI windows. |
c906108c | 17370 | |
8e04817f AC |
17371 | @table @code |
17372 | @item set tui border-kind @var{kind} | |
17373 | @kindex set tui border-kind | |
17374 | Select the border appearance for the source, assembly and register windows. | |
17375 | The possible values are the following: | |
17376 | @table @code | |
17377 | @item space | |
17378 | Use a space character to draw the border. | |
c906108c | 17379 | |
8e04817f | 17380 | @item ascii |
46ba6afa | 17381 | Use @sc{ascii} characters @samp{+}, @samp{-} and @samp{|} to draw the border. |
c906108c | 17382 | |
8e04817f AC |
17383 | @item acs |
17384 | Use the Alternate Character Set to draw the border. The border is | |
17385 | drawn using character line graphics if the terminal supports them. | |
8e04817f | 17386 | @end table |
c78b4128 | 17387 | |
8e04817f AC |
17388 | @item set tui border-mode @var{mode} |
17389 | @kindex set tui border-mode | |
46ba6afa BW |
17390 | @itemx set tui active-border-mode @var{mode} |
17391 | @kindex set tui active-border-mode | |
17392 | Select the display attributes for the borders of the inactive windows | |
17393 | or the active window. The @var{mode} can be one of the following: | |
8e04817f AC |
17394 | @table @code |
17395 | @item normal | |
17396 | Use normal attributes to display the border. | |
c906108c | 17397 | |
8e04817f AC |
17398 | @item standout |
17399 | Use standout mode. | |
c906108c | 17400 | |
8e04817f AC |
17401 | @item reverse |
17402 | Use reverse video mode. | |
c906108c | 17403 | |
8e04817f AC |
17404 | @item half |
17405 | Use half bright mode. | |
c906108c | 17406 | |
8e04817f AC |
17407 | @item half-standout |
17408 | Use half bright and standout mode. | |
c906108c | 17409 | |
8e04817f AC |
17410 | @item bold |
17411 | Use extra bright or bold mode. | |
c78b4128 | 17412 | |
8e04817f AC |
17413 | @item bold-standout |
17414 | Use extra bright or bold and standout mode. | |
8e04817f | 17415 | @end table |
8e04817f | 17416 | @end table |
c78b4128 | 17417 | |
8e04817f AC |
17418 | @node Emacs |
17419 | @chapter Using @value{GDBN} under @sc{gnu} Emacs | |
c78b4128 | 17420 | |
8e04817f AC |
17421 | @cindex Emacs |
17422 | @cindex @sc{gnu} Emacs | |
17423 | A special interface allows you to use @sc{gnu} Emacs to view (and | |
17424 | edit) the source files for the program you are debugging with | |
17425 | @value{GDBN}. | |
c906108c | 17426 | |
8e04817f AC |
17427 | To use this interface, use the command @kbd{M-x gdb} in Emacs. Give the |
17428 | executable file you want to debug as an argument. This command starts | |
17429 | @value{GDBN} as a subprocess of Emacs, with input and output through a newly | |
17430 | created Emacs buffer. | |
17431 | @c (Do not use the @code{-tui} option to run @value{GDBN} from Emacs.) | |
c906108c | 17432 | |
5e252a2e | 17433 | Running @value{GDBN} under Emacs can be just like running @value{GDBN} normally except for two |
8e04817f | 17434 | things: |
c906108c | 17435 | |
8e04817f AC |
17436 | @itemize @bullet |
17437 | @item | |
5e252a2e NR |
17438 | All ``terminal'' input and output goes through an Emacs buffer, called |
17439 | the GUD buffer. | |
c906108c | 17440 | |
8e04817f AC |
17441 | This applies both to @value{GDBN} commands and their output, and to the input |
17442 | and output done by the program you are debugging. | |
bf0184be | 17443 | |
8e04817f AC |
17444 | This is useful because it means that you can copy the text of previous |
17445 | commands and input them again; you can even use parts of the output | |
17446 | in this way. | |
bf0184be | 17447 | |
8e04817f AC |
17448 | All the facilities of Emacs' Shell mode are available for interacting |
17449 | with your program. In particular, you can send signals the usual | |
17450 | way---for example, @kbd{C-c C-c} for an interrupt, @kbd{C-c C-z} for a | |
17451 | stop. | |
bf0184be ND |
17452 | |
17453 | @item | |
8e04817f | 17454 | @value{GDBN} displays source code through Emacs. |
bf0184be | 17455 | |
8e04817f AC |
17456 | Each time @value{GDBN} displays a stack frame, Emacs automatically finds the |
17457 | source file for that frame and puts an arrow (@samp{=>}) at the | |
17458 | left margin of the current line. Emacs uses a separate buffer for | |
17459 | source display, and splits the screen to show both your @value{GDBN} session | |
17460 | and the source. | |
bf0184be | 17461 | |
8e04817f AC |
17462 | Explicit @value{GDBN} @code{list} or search commands still produce output as |
17463 | usual, but you probably have no reason to use them from Emacs. | |
5e252a2e NR |
17464 | @end itemize |
17465 | ||
17466 | We call this @dfn{text command mode}. Emacs 22.1, and later, also uses | |
17467 | a graphical mode, enabled by default, which provides further buffers | |
17468 | that can control the execution and describe the state of your program. | |
17469 | @xref{GDB Graphical Interface,,, Emacs, The @sc{gnu} Emacs Manual}. | |
c906108c | 17470 | |
64fabec2 AC |
17471 | If you specify an absolute file name when prompted for the @kbd{M-x |
17472 | gdb} argument, then Emacs sets your current working directory to where | |
17473 | your program resides. If you only specify the file name, then Emacs | |
17474 | sets your current working directory to to the directory associated | |
17475 | with the previous buffer. In this case, @value{GDBN} may find your | |
17476 | program by searching your environment's @code{PATH} variable, but on | |
17477 | some operating systems it might not find the source. So, although the | |
17478 | @value{GDBN} input and output session proceeds normally, the auxiliary | |
17479 | buffer does not display the current source and line of execution. | |
17480 | ||
17481 | The initial working directory of @value{GDBN} is printed on the top | |
5e252a2e NR |
17482 | line of the GUD buffer and this serves as a default for the commands |
17483 | that specify files for @value{GDBN} to operate on. @xref{Files, | |
17484 | ,Commands to Specify Files}. | |
64fabec2 AC |
17485 | |
17486 | By default, @kbd{M-x gdb} calls the program called @file{gdb}. If you | |
17487 | need to call @value{GDBN} by a different name (for example, if you | |
17488 | keep several configurations around, with different names) you can | |
17489 | customize the Emacs variable @code{gud-gdb-command-name} to run the | |
17490 | one you want. | |
8e04817f | 17491 | |
5e252a2e | 17492 | In the GUD buffer, you can use these special Emacs commands in |
8e04817f | 17493 | addition to the standard Shell mode commands: |
c906108c | 17494 | |
8e04817f AC |
17495 | @table @kbd |
17496 | @item C-h m | |
5e252a2e | 17497 | Describe the features of Emacs' GUD Mode. |
c906108c | 17498 | |
64fabec2 | 17499 | @item C-c C-s |
8e04817f AC |
17500 | Execute to another source line, like the @value{GDBN} @code{step} command; also |
17501 | update the display window to show the current file and location. | |
c906108c | 17502 | |
64fabec2 | 17503 | @item C-c C-n |
8e04817f AC |
17504 | Execute to next source line in this function, skipping all function |
17505 | calls, like the @value{GDBN} @code{next} command. Then update the display window | |
17506 | to show the current file and location. | |
c906108c | 17507 | |
64fabec2 | 17508 | @item C-c C-i |
8e04817f AC |
17509 | Execute one instruction, like the @value{GDBN} @code{stepi} command; update |
17510 | display window accordingly. | |
c906108c | 17511 | |
8e04817f AC |
17512 | @item C-c C-f |
17513 | Execute until exit from the selected stack frame, like the @value{GDBN} | |
17514 | @code{finish} command. | |
c906108c | 17515 | |
64fabec2 | 17516 | @item C-c C-r |
8e04817f AC |
17517 | Continue execution of your program, like the @value{GDBN} @code{continue} |
17518 | command. | |
b433d00b | 17519 | |
64fabec2 | 17520 | @item C-c < |
8e04817f AC |
17521 | Go up the number of frames indicated by the numeric argument |
17522 | (@pxref{Arguments, , Numeric Arguments, Emacs, The @sc{gnu} Emacs Manual}), | |
17523 | like the @value{GDBN} @code{up} command. | |
b433d00b | 17524 | |
64fabec2 | 17525 | @item C-c > |
8e04817f AC |
17526 | Go down the number of frames indicated by the numeric argument, like the |
17527 | @value{GDBN} @code{down} command. | |
8e04817f | 17528 | @end table |
c906108c | 17529 | |
7f9087cb | 17530 | In any source file, the Emacs command @kbd{C-x @key{SPC}} (@code{gud-break}) |
8e04817f | 17531 | tells @value{GDBN} to set a breakpoint on the source line point is on. |
c906108c | 17532 | |
5e252a2e NR |
17533 | In text command mode, if you type @kbd{M-x speedbar}, Emacs displays a |
17534 | separate frame which shows a backtrace when the GUD buffer is current. | |
17535 | Move point to any frame in the stack and type @key{RET} to make it | |
17536 | become the current frame and display the associated source in the | |
17537 | source buffer. Alternatively, click @kbd{Mouse-2} to make the | |
17538 | selected frame become the current one. In graphical mode, the | |
17539 | speedbar displays watch expressions. | |
64fabec2 | 17540 | |
8e04817f AC |
17541 | If you accidentally delete the source-display buffer, an easy way to get |
17542 | it back is to type the command @code{f} in the @value{GDBN} buffer, to | |
17543 | request a frame display; when you run under Emacs, this recreates | |
17544 | the source buffer if necessary to show you the context of the current | |
17545 | frame. | |
c906108c | 17546 | |
8e04817f AC |
17547 | The source files displayed in Emacs are in ordinary Emacs buffers |
17548 | which are visiting the source files in the usual way. You can edit | |
17549 | the files with these buffers if you wish; but keep in mind that @value{GDBN} | |
17550 | communicates with Emacs in terms of line numbers. If you add or | |
17551 | delete lines from the text, the line numbers that @value{GDBN} knows cease | |
17552 | to correspond properly with the code. | |
b383017d | 17553 | |
5e252a2e NR |
17554 | A more detailed description of Emacs' interaction with @value{GDBN} is |
17555 | given in the Emacs manual (@pxref{Debuggers,,, Emacs, The @sc{gnu} | |
17556 | Emacs Manual}). | |
c906108c | 17557 | |
8e04817f AC |
17558 | @c The following dropped because Epoch is nonstandard. Reactivate |
17559 | @c if/when v19 does something similar. ---doc@cygnus.com 19dec1990 | |
17560 | @ignore | |
17561 | @kindex Emacs Epoch environment | |
17562 | @kindex Epoch | |
17563 | @kindex inspect | |
c906108c | 17564 | |
8e04817f AC |
17565 | Version 18 of @sc{gnu} Emacs has a built-in window system |
17566 | called the @code{epoch} | |
17567 | environment. Users of this environment can use a new command, | |
17568 | @code{inspect} which performs identically to @code{print} except that | |
17569 | each value is printed in its own window. | |
17570 | @end ignore | |
c906108c | 17571 | |
922fbb7b AC |
17572 | |
17573 | @node GDB/MI | |
17574 | @chapter The @sc{gdb/mi} Interface | |
17575 | ||
17576 | @unnumberedsec Function and Purpose | |
17577 | ||
17578 | @cindex @sc{gdb/mi}, its purpose | |
6b5e8c01 NR |
17579 | @sc{gdb/mi} is a line based machine oriented text interface to |
17580 | @value{GDBN} and is activated by specifying using the | |
17581 | @option{--interpreter} command line option (@pxref{Mode Options}). It | |
17582 | is specifically intended to support the development of systems which | |
17583 | use the debugger as just one small component of a larger system. | |
922fbb7b AC |
17584 | |
17585 | This chapter is a specification of the @sc{gdb/mi} interface. It is written | |
17586 | in the form of a reference manual. | |
17587 | ||
17588 | Note that @sc{gdb/mi} is still under construction, so some of the | |
af6eff6f NR |
17589 | features described below are incomplete and subject to change |
17590 | (@pxref{GDB/MI Development and Front Ends, , @sc{gdb/mi} Development and Front Ends}). | |
922fbb7b AC |
17591 | |
17592 | @unnumberedsec Notation and Terminology | |
17593 | ||
17594 | @cindex notational conventions, for @sc{gdb/mi} | |
17595 | This chapter uses the following notation: | |
17596 | ||
17597 | @itemize @bullet | |
17598 | @item | |
17599 | @code{|} separates two alternatives. | |
17600 | ||
17601 | @item | |
17602 | @code{[ @var{something} ]} indicates that @var{something} is optional: | |
17603 | it may or may not be given. | |
17604 | ||
17605 | @item | |
17606 | @code{( @var{group} )*} means that @var{group} inside the parentheses | |
17607 | may repeat zero or more times. | |
17608 | ||
17609 | @item | |
17610 | @code{( @var{group} )+} means that @var{group} inside the parentheses | |
17611 | may repeat one or more times. | |
17612 | ||
17613 | @item | |
17614 | @code{"@var{string}"} means a literal @var{string}. | |
17615 | @end itemize | |
17616 | ||
17617 | @ignore | |
17618 | @heading Dependencies | |
17619 | @end ignore | |
17620 | ||
922fbb7b AC |
17621 | @menu |
17622 | * GDB/MI Command Syntax:: | |
17623 | * GDB/MI Compatibility with CLI:: | |
af6eff6f | 17624 | * GDB/MI Development and Front Ends:: |
922fbb7b | 17625 | * GDB/MI Output Records:: |
ef21caaf | 17626 | * GDB/MI Simple Examples:: |
922fbb7b | 17627 | * GDB/MI Command Description Format:: |
ef21caaf | 17628 | * GDB/MI Breakpoint Commands:: |
a2c02241 NR |
17629 | * GDB/MI Program Context:: |
17630 | * GDB/MI Thread Commands:: | |
17631 | * GDB/MI Program Execution:: | |
17632 | * GDB/MI Stack Manipulation:: | |
17633 | * GDB/MI Variable Objects:: | |
922fbb7b | 17634 | * GDB/MI Data Manipulation:: |
a2c02241 NR |
17635 | * GDB/MI Tracepoint Commands:: |
17636 | * GDB/MI Symbol Query:: | |
351ff01a | 17637 | * GDB/MI File Commands:: |
922fbb7b AC |
17638 | @ignore |
17639 | * GDB/MI Kod Commands:: | |
17640 | * GDB/MI Memory Overlay Commands:: | |
17641 | * GDB/MI Signal Handling Commands:: | |
17642 | @end ignore | |
922fbb7b | 17643 | * GDB/MI Target Manipulation:: |
a6b151f1 | 17644 | * GDB/MI File Transfer Commands:: |
ef21caaf | 17645 | * GDB/MI Miscellaneous Commands:: |
922fbb7b AC |
17646 | @end menu |
17647 | ||
17648 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
17649 | @node GDB/MI Command Syntax | |
17650 | @section @sc{gdb/mi} Command Syntax | |
17651 | ||
17652 | @menu | |
17653 | * GDB/MI Input Syntax:: | |
17654 | * GDB/MI Output Syntax:: | |
922fbb7b AC |
17655 | @end menu |
17656 | ||
17657 | @node GDB/MI Input Syntax | |
17658 | @subsection @sc{gdb/mi} Input Syntax | |
17659 | ||
17660 | @cindex input syntax for @sc{gdb/mi} | |
17661 | @cindex @sc{gdb/mi}, input syntax | |
17662 | @table @code | |
17663 | @item @var{command} @expansion{} | |
17664 | @code{@var{cli-command} | @var{mi-command}} | |
17665 | ||
17666 | @item @var{cli-command} @expansion{} | |
17667 | @code{[ @var{token} ] @var{cli-command} @var{nl}}, where | |
17668 | @var{cli-command} is any existing @value{GDBN} CLI command. | |
17669 | ||
17670 | @item @var{mi-command} @expansion{} | |
17671 | @code{[ @var{token} ] "-" @var{operation} ( " " @var{option} )* | |
17672 | @code{[} " --" @code{]} ( " " @var{parameter} )* @var{nl}} | |
17673 | ||
17674 | @item @var{token} @expansion{} | |
17675 | "any sequence of digits" | |
17676 | ||
17677 | @item @var{option} @expansion{} | |
17678 | @code{"-" @var{parameter} [ " " @var{parameter} ]} | |
17679 | ||
17680 | @item @var{parameter} @expansion{} | |
17681 | @code{@var{non-blank-sequence} | @var{c-string}} | |
17682 | ||
17683 | @item @var{operation} @expansion{} | |
17684 | @emph{any of the operations described in this chapter} | |
17685 | ||
17686 | @item @var{non-blank-sequence} @expansion{} | |
17687 | @emph{anything, provided it doesn't contain special characters such as | |
17688 | "-", @var{nl}, """ and of course " "} | |
17689 | ||
17690 | @item @var{c-string} @expansion{} | |
17691 | @code{""" @var{seven-bit-iso-c-string-content} """} | |
17692 | ||
17693 | @item @var{nl} @expansion{} | |
17694 | @code{CR | CR-LF} | |
17695 | @end table | |
17696 | ||
17697 | @noindent | |
17698 | Notes: | |
17699 | ||
17700 | @itemize @bullet | |
17701 | @item | |
17702 | The CLI commands are still handled by the @sc{mi} interpreter; their | |
17703 | output is described below. | |
17704 | ||
17705 | @item | |
17706 | The @code{@var{token}}, when present, is passed back when the command | |
17707 | finishes. | |
17708 | ||
17709 | @item | |
17710 | Some @sc{mi} commands accept optional arguments as part of the parameter | |
17711 | list. Each option is identified by a leading @samp{-} (dash) and may be | |
17712 | followed by an optional argument parameter. Options occur first in the | |
17713 | parameter list and can be delimited from normal parameters using | |
17714 | @samp{--} (this is useful when some parameters begin with a dash). | |
17715 | @end itemize | |
17716 | ||
17717 | Pragmatics: | |
17718 | ||
17719 | @itemize @bullet | |
17720 | @item | |
17721 | We want easy access to the existing CLI syntax (for debugging). | |
17722 | ||
17723 | @item | |
17724 | We want it to be easy to spot a @sc{mi} operation. | |
17725 | @end itemize | |
17726 | ||
17727 | @node GDB/MI Output Syntax | |
17728 | @subsection @sc{gdb/mi} Output Syntax | |
17729 | ||
17730 | @cindex output syntax of @sc{gdb/mi} | |
17731 | @cindex @sc{gdb/mi}, output syntax | |
17732 | The output from @sc{gdb/mi} consists of zero or more out-of-band records | |
17733 | followed, optionally, by a single result record. This result record | |
17734 | is for the most recent command. The sequence of output records is | |
594fe323 | 17735 | terminated by @samp{(gdb)}. |
922fbb7b AC |
17736 | |
17737 | If an input command was prefixed with a @code{@var{token}} then the | |
17738 | corresponding output for that command will also be prefixed by that same | |
17739 | @var{token}. | |
17740 | ||
17741 | @table @code | |
17742 | @item @var{output} @expansion{} | |
594fe323 | 17743 | @code{( @var{out-of-band-record} )* [ @var{result-record} ] "(gdb)" @var{nl}} |
922fbb7b AC |
17744 | |
17745 | @item @var{result-record} @expansion{} | |
17746 | @code{ [ @var{token} ] "^" @var{result-class} ( "," @var{result} )* @var{nl}} | |
17747 | ||
17748 | @item @var{out-of-band-record} @expansion{} | |
17749 | @code{@var{async-record} | @var{stream-record}} | |
17750 | ||
17751 | @item @var{async-record} @expansion{} | |
17752 | @code{@var{exec-async-output} | @var{status-async-output} | @var{notify-async-output}} | |
17753 | ||
17754 | @item @var{exec-async-output} @expansion{} | |
17755 | @code{[ @var{token} ] "*" @var{async-output}} | |
17756 | ||
17757 | @item @var{status-async-output} @expansion{} | |
17758 | @code{[ @var{token} ] "+" @var{async-output}} | |
17759 | ||
17760 | @item @var{notify-async-output} @expansion{} | |
17761 | @code{[ @var{token} ] "=" @var{async-output}} | |
17762 | ||
17763 | @item @var{async-output} @expansion{} | |
17764 | @code{@var{async-class} ( "," @var{result} )* @var{nl}} | |
17765 | ||
17766 | @item @var{result-class} @expansion{} | |
17767 | @code{"done" | "running" | "connected" | "error" | "exit"} | |
17768 | ||
17769 | @item @var{async-class} @expansion{} | |
17770 | @code{"stopped" | @var{others}} (where @var{others} will be added | |
17771 | depending on the needs---this is still in development). | |
17772 | ||
17773 | @item @var{result} @expansion{} | |
17774 | @code{ @var{variable} "=" @var{value}} | |
17775 | ||
17776 | @item @var{variable} @expansion{} | |
17777 | @code{ @var{string} } | |
17778 | ||
17779 | @item @var{value} @expansion{} | |
17780 | @code{ @var{const} | @var{tuple} | @var{list} } | |
17781 | ||
17782 | @item @var{const} @expansion{} | |
17783 | @code{@var{c-string}} | |
17784 | ||
17785 | @item @var{tuple} @expansion{} | |
17786 | @code{ "@{@}" | "@{" @var{result} ( "," @var{result} )* "@}" } | |
17787 | ||
17788 | @item @var{list} @expansion{} | |
17789 | @code{ "[]" | "[" @var{value} ( "," @var{value} )* "]" | "[" | |
17790 | @var{result} ( "," @var{result} )* "]" } | |
17791 | ||
17792 | @item @var{stream-record} @expansion{} | |
17793 | @code{@var{console-stream-output} | @var{target-stream-output} | @var{log-stream-output}} | |
17794 | ||
17795 | @item @var{console-stream-output} @expansion{} | |
17796 | @code{"~" @var{c-string}} | |
17797 | ||
17798 | @item @var{target-stream-output} @expansion{} | |
17799 | @code{"@@" @var{c-string}} | |
17800 | ||
17801 | @item @var{log-stream-output} @expansion{} | |
17802 | @code{"&" @var{c-string}} | |
17803 | ||
17804 | @item @var{nl} @expansion{} | |
17805 | @code{CR | CR-LF} | |
17806 | ||
17807 | @item @var{token} @expansion{} | |
17808 | @emph{any sequence of digits}. | |
17809 | @end table | |
17810 | ||
17811 | @noindent | |
17812 | Notes: | |
17813 | ||
17814 | @itemize @bullet | |
17815 | @item | |
17816 | All output sequences end in a single line containing a period. | |
17817 | ||
17818 | @item | |
17819 | The @code{@var{token}} is from the corresponding request. If an execution | |
17820 | command is interrupted by the @samp{-exec-interrupt} command, the | |
17821 | @var{token} associated with the @samp{*stopped} message is the one of the | |
17822 | original execution command, not the one of the interrupt command. | |
17823 | ||
17824 | @item | |
17825 | @cindex status output in @sc{gdb/mi} | |
17826 | @var{status-async-output} contains on-going status information about the | |
17827 | progress of a slow operation. It can be discarded. All status output is | |
17828 | prefixed by @samp{+}. | |
17829 | ||
17830 | @item | |
17831 | @cindex async output in @sc{gdb/mi} | |
17832 | @var{exec-async-output} contains asynchronous state change on the target | |
17833 | (stopped, started, disappeared). All async output is prefixed by | |
17834 | @samp{*}. | |
17835 | ||
17836 | @item | |
17837 | @cindex notify output in @sc{gdb/mi} | |
17838 | @var{notify-async-output} contains supplementary information that the | |
17839 | client should handle (e.g., a new breakpoint information). All notify | |
17840 | output is prefixed by @samp{=}. | |
17841 | ||
17842 | @item | |
17843 | @cindex console output in @sc{gdb/mi} | |
17844 | @var{console-stream-output} is output that should be displayed as is in the | |
17845 | console. It is the textual response to a CLI command. All the console | |
17846 | output is prefixed by @samp{~}. | |
17847 | ||
17848 | @item | |
17849 | @cindex target output in @sc{gdb/mi} | |
17850 | @var{target-stream-output} is the output produced by the target program. | |
17851 | All the target output is prefixed by @samp{@@}. | |
17852 | ||
17853 | @item | |
17854 | @cindex log output in @sc{gdb/mi} | |
17855 | @var{log-stream-output} is output text coming from @value{GDBN}'s internals, for | |
17856 | instance messages that should be displayed as part of an error log. All | |
17857 | the log output is prefixed by @samp{&}. | |
17858 | ||
17859 | @item | |
17860 | @cindex list output in @sc{gdb/mi} | |
17861 | New @sc{gdb/mi} commands should only output @var{lists} containing | |
17862 | @var{values}. | |
17863 | ||
17864 | ||
17865 | @end itemize | |
17866 | ||
17867 | @xref{GDB/MI Stream Records, , @sc{gdb/mi} Stream Records}, for more | |
17868 | details about the various output records. | |
17869 | ||
922fbb7b AC |
17870 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
17871 | @node GDB/MI Compatibility with CLI | |
17872 | @section @sc{gdb/mi} Compatibility with CLI | |
17873 | ||
17874 | @cindex compatibility, @sc{gdb/mi} and CLI | |
17875 | @cindex @sc{gdb/mi}, compatibility with CLI | |
922fbb7b | 17876 | |
a2c02241 NR |
17877 | For the developers convenience CLI commands can be entered directly, |
17878 | but there may be some unexpected behaviour. For example, commands | |
17879 | that query the user will behave as if the user replied yes, breakpoint | |
17880 | command lists are not executed and some CLI commands, such as | |
17881 | @code{if}, @code{when} and @code{define}, prompt for further input with | |
17882 | @samp{>}, which is not valid MI output. | |
ef21caaf NR |
17883 | |
17884 | This feature may be removed at some stage in the future and it is | |
a2c02241 NR |
17885 | recommended that front ends use the @code{-interpreter-exec} command |
17886 | (@pxref{-interpreter-exec}). | |
922fbb7b | 17887 | |
af6eff6f NR |
17888 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
17889 | @node GDB/MI Development and Front Ends | |
17890 | @section @sc{gdb/mi} Development and Front Ends | |
17891 | @cindex @sc{gdb/mi} development | |
17892 | ||
17893 | The application which takes the MI output and presents the state of the | |
17894 | program being debugged to the user is called a @dfn{front end}. | |
17895 | ||
17896 | Although @sc{gdb/mi} is still incomplete, it is currently being used | |
17897 | by a variety of front ends to @value{GDBN}. This makes it difficult | |
17898 | to introduce new functionality without breaking existing usage. This | |
17899 | section tries to minimize the problems by describing how the protocol | |
17900 | might change. | |
17901 | ||
17902 | Some changes in MI need not break a carefully designed front end, and | |
17903 | for these the MI version will remain unchanged. The following is a | |
17904 | list of changes that may occur within one level, so front ends should | |
17905 | parse MI output in a way that can handle them: | |
17906 | ||
17907 | @itemize @bullet | |
17908 | @item | |
17909 | New MI commands may be added. | |
17910 | ||
17911 | @item | |
17912 | New fields may be added to the output of any MI command. | |
17913 | ||
36ece8b3 NR |
17914 | @item |
17915 | The range of values for fields with specified values, e.g., | |
9f708cb2 | 17916 | @code{in_scope} (@pxref{-var-update}) may be extended. |
36ece8b3 | 17917 | |
af6eff6f NR |
17918 | @c The format of field's content e.g type prefix, may change so parse it |
17919 | @c at your own risk. Yes, in general? | |
17920 | ||
17921 | @c The order of fields may change? Shouldn't really matter but it might | |
17922 | @c resolve inconsistencies. | |
17923 | @end itemize | |
17924 | ||
17925 | If the changes are likely to break front ends, the MI version level | |
17926 | will be increased by one. This will allow the front end to parse the | |
17927 | output according to the MI version. Apart from mi0, new versions of | |
17928 | @value{GDBN} will not support old versions of MI and it will be the | |
17929 | responsibility of the front end to work with the new one. | |
17930 | ||
17931 | @c Starting with mi3, add a new command -mi-version that prints the MI | |
17932 | @c version? | |
17933 | ||
17934 | The best way to avoid unexpected changes in MI that might break your front | |
17935 | end is to make your project known to @value{GDBN} developers and | |
7a9a6b69 NR |
17936 | follow development on @email{gdb@@sourceware.org} and |
17937 | @email{gdb-patches@@sourceware.org}. There is also the mailing list | |
af6eff6f | 17938 | @email{dmi-discuss@@lists.freestandards.org}, hosted by the Free Standards |
d3e8051b | 17939 | Group, which has the aim of creating a more general MI protocol |
af6eff6f NR |
17940 | called Debugger Machine Interface (DMI) that will become a standard |
17941 | for all debuggers, not just @value{GDBN}. | |
17942 | @cindex mailing lists | |
17943 | ||
922fbb7b AC |
17944 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
17945 | @node GDB/MI Output Records | |
17946 | @section @sc{gdb/mi} Output Records | |
17947 | ||
17948 | @menu | |
17949 | * GDB/MI Result Records:: | |
17950 | * GDB/MI Stream Records:: | |
17951 | * GDB/MI Out-of-band Records:: | |
17952 | @end menu | |
17953 | ||
17954 | @node GDB/MI Result Records | |
17955 | @subsection @sc{gdb/mi} Result Records | |
17956 | ||
17957 | @cindex result records in @sc{gdb/mi} | |
17958 | @cindex @sc{gdb/mi}, result records | |
17959 | In addition to a number of out-of-band notifications, the response to a | |
17960 | @sc{gdb/mi} command includes one of the following result indications: | |
17961 | ||
17962 | @table @code | |
17963 | @findex ^done | |
17964 | @item "^done" [ "," @var{results} ] | |
17965 | The synchronous operation was successful, @code{@var{results}} are the return | |
17966 | values. | |
17967 | ||
17968 | @item "^running" | |
17969 | @findex ^running | |
17970 | @c Is this one correct? Should it be an out-of-band notification? | |
17971 | The asynchronous operation was successfully started. The target is | |
17972 | running. | |
17973 | ||
ef21caaf NR |
17974 | @item "^connected" |
17975 | @findex ^connected | |
3f94c067 | 17976 | @value{GDBN} has connected to a remote target. |
ef21caaf | 17977 | |
922fbb7b AC |
17978 | @item "^error" "," @var{c-string} |
17979 | @findex ^error | |
17980 | The operation failed. The @code{@var{c-string}} contains the corresponding | |
17981 | error message. | |
ef21caaf NR |
17982 | |
17983 | @item "^exit" | |
17984 | @findex ^exit | |
3f94c067 | 17985 | @value{GDBN} has terminated. |
ef21caaf | 17986 | |
922fbb7b AC |
17987 | @end table |
17988 | ||
17989 | @node GDB/MI Stream Records | |
17990 | @subsection @sc{gdb/mi} Stream Records | |
17991 | ||
17992 | @cindex @sc{gdb/mi}, stream records | |
17993 | @cindex stream records in @sc{gdb/mi} | |
17994 | @value{GDBN} internally maintains a number of output streams: the console, the | |
17995 | target, and the log. The output intended for each of these streams is | |
17996 | funneled through the @sc{gdb/mi} interface using @dfn{stream records}. | |
17997 | ||
17998 | Each stream record begins with a unique @dfn{prefix character} which | |
17999 | identifies its stream (@pxref{GDB/MI Output Syntax, , @sc{gdb/mi} Output | |
18000 | Syntax}). In addition to the prefix, each stream record contains a | |
18001 | @code{@var{string-output}}. This is either raw text (with an implicit new | |
18002 | line) or a quoted C string (which does not contain an implicit newline). | |
18003 | ||
18004 | @table @code | |
18005 | @item "~" @var{string-output} | |
18006 | The console output stream contains text that should be displayed in the | |
18007 | CLI console window. It contains the textual responses to CLI commands. | |
18008 | ||
18009 | @item "@@" @var{string-output} | |
18010 | The target output stream contains any textual output from the running | |
ef21caaf NR |
18011 | target. This is only present when GDB's event loop is truly |
18012 | asynchronous, which is currently only the case for remote targets. | |
922fbb7b AC |
18013 | |
18014 | @item "&" @var{string-output} | |
18015 | The log stream contains debugging messages being produced by @value{GDBN}'s | |
18016 | internals. | |
18017 | @end table | |
18018 | ||
18019 | @node GDB/MI Out-of-band Records | |
18020 | @subsection @sc{gdb/mi} Out-of-band Records | |
18021 | ||
18022 | @cindex out-of-band records in @sc{gdb/mi} | |
18023 | @cindex @sc{gdb/mi}, out-of-band records | |
18024 | @dfn{Out-of-band} records are used to notify the @sc{gdb/mi} client of | |
18025 | additional changes that have occurred. Those changes can either be a | |
18026 | consequence of @sc{gdb/mi} (e.g., a breakpoint modified) or a result of | |
18027 | target activity (e.g., target stopped). | |
18028 | ||
18029 | The following is a preliminary list of possible out-of-band records. | |
034dad6f | 18030 | In particular, the @var{exec-async-output} records. |
922fbb7b AC |
18031 | |
18032 | @table @code | |
034dad6f BR |
18033 | @item *stopped,reason="@var{reason}" |
18034 | @end table | |
18035 | ||
18036 | @var{reason} can be one of the following: | |
18037 | ||
18038 | @table @code | |
18039 | @item breakpoint-hit | |
18040 | A breakpoint was reached. | |
18041 | @item watchpoint-trigger | |
18042 | A watchpoint was triggered. | |
18043 | @item read-watchpoint-trigger | |
18044 | A read watchpoint was triggered. | |
18045 | @item access-watchpoint-trigger | |
18046 | An access watchpoint was triggered. | |
18047 | @item function-finished | |
18048 | An -exec-finish or similar CLI command was accomplished. | |
18049 | @item location-reached | |
18050 | An -exec-until or similar CLI command was accomplished. | |
18051 | @item watchpoint-scope | |
18052 | A watchpoint has gone out of scope. | |
18053 | @item end-stepping-range | |
18054 | An -exec-next, -exec-next-instruction, -exec-step, -exec-step-instruction or | |
18055 | similar CLI command was accomplished. | |
18056 | @item exited-signalled | |
18057 | The inferior exited because of a signal. | |
18058 | @item exited | |
18059 | The inferior exited. | |
18060 | @item exited-normally | |
18061 | The inferior exited normally. | |
18062 | @item signal-received | |
18063 | A signal was received by the inferior. | |
922fbb7b AC |
18064 | @end table |
18065 | ||
18066 | ||
ef21caaf NR |
18067 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
18068 | @node GDB/MI Simple Examples | |
18069 | @section Simple Examples of @sc{gdb/mi} Interaction | |
18070 | @cindex @sc{gdb/mi}, simple examples | |
18071 | ||
18072 | This subsection presents several simple examples of interaction using | |
18073 | the @sc{gdb/mi} interface. In these examples, @samp{->} means that the | |
18074 | following line is passed to @sc{gdb/mi} as input, while @samp{<-} means | |
18075 | the output received from @sc{gdb/mi}. | |
18076 | ||
d3e8051b | 18077 | Note the line breaks shown in the examples are here only for |
ef21caaf NR |
18078 | readability, they don't appear in the real output. |
18079 | ||
79a6e687 | 18080 | @subheading Setting a Breakpoint |
ef21caaf NR |
18081 | |
18082 | Setting a breakpoint generates synchronous output which contains detailed | |
18083 | information of the breakpoint. | |
18084 | ||
18085 | @smallexample | |
18086 | -> -break-insert main | |
18087 | <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep", | |
18088 | enabled="y",addr="0x08048564",func="main",file="myprog.c", | |
18089 | fullname="/home/nickrob/myprog.c",line="68",times="0"@} | |
18090 | <- (gdb) | |
18091 | @end smallexample | |
18092 | ||
18093 | @subheading Program Execution | |
18094 | ||
18095 | Program execution generates asynchronous records and MI gives the | |
18096 | reason that execution stopped. | |
18097 | ||
18098 | @smallexample | |
18099 | -> -exec-run | |
18100 | <- ^running | |
18101 | <- (gdb) | |
18102 | <- *stopped,reason="breakpoint-hit",bkptno="1",thread-id="0", | |
18103 | frame=@{addr="0x08048564",func="main", | |
18104 | args=[@{name="argc",value="1"@},@{name="argv",value="0xbfc4d4d4"@}], | |
18105 | file="myprog.c",fullname="/home/nickrob/myprog.c",line="68"@} | |
18106 | <- (gdb) | |
18107 | -> -exec-continue | |
18108 | <- ^running | |
18109 | <- (gdb) | |
18110 | <- *stopped,reason="exited-normally" | |
18111 | <- (gdb) | |
18112 | @end smallexample | |
18113 | ||
3f94c067 | 18114 | @subheading Quitting @value{GDBN} |
ef21caaf | 18115 | |
3f94c067 | 18116 | Quitting @value{GDBN} just prints the result class @samp{^exit}. |
ef21caaf NR |
18117 | |
18118 | @smallexample | |
18119 | -> (gdb) | |
18120 | <- -gdb-exit | |
18121 | <- ^exit | |
18122 | @end smallexample | |
18123 | ||
a2c02241 | 18124 | @subheading A Bad Command |
ef21caaf NR |
18125 | |
18126 | Here's what happens if you pass a non-existent command: | |
18127 | ||
18128 | @smallexample | |
18129 | -> -rubbish | |
18130 | <- ^error,msg="Undefined MI command: rubbish" | |
594fe323 | 18131 | <- (gdb) |
ef21caaf NR |
18132 | @end smallexample |
18133 | ||
18134 | ||
922fbb7b AC |
18135 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
18136 | @node GDB/MI Command Description Format | |
18137 | @section @sc{gdb/mi} Command Description Format | |
18138 | ||
18139 | The remaining sections describe blocks of commands. Each block of | |
18140 | commands is laid out in a fashion similar to this section. | |
18141 | ||
922fbb7b AC |
18142 | @subheading Motivation |
18143 | ||
18144 | The motivation for this collection of commands. | |
18145 | ||
18146 | @subheading Introduction | |
18147 | ||
18148 | A brief introduction to this collection of commands as a whole. | |
18149 | ||
18150 | @subheading Commands | |
18151 | ||
18152 | For each command in the block, the following is described: | |
18153 | ||
18154 | @subsubheading Synopsis | |
18155 | ||
18156 | @smallexample | |
18157 | -command @var{args}@dots{} | |
18158 | @end smallexample | |
18159 | ||
922fbb7b AC |
18160 | @subsubheading Result |
18161 | ||
265eeb58 | 18162 | @subsubheading @value{GDBN} Command |
922fbb7b | 18163 | |
265eeb58 | 18164 | The corresponding @value{GDBN} CLI command(s), if any. |
922fbb7b AC |
18165 | |
18166 | @subsubheading Example | |
18167 | ||
ef21caaf NR |
18168 | Example(s) formatted for readability. Some of the described commands have |
18169 | not been implemented yet and these are labeled N.A.@: (not available). | |
18170 | ||
18171 | ||
922fbb7b | 18172 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
ef21caaf NR |
18173 | @node GDB/MI Breakpoint Commands |
18174 | @section @sc{gdb/mi} Breakpoint Commands | |
922fbb7b AC |
18175 | |
18176 | @cindex breakpoint commands for @sc{gdb/mi} | |
18177 | @cindex @sc{gdb/mi}, breakpoint commands | |
18178 | This section documents @sc{gdb/mi} commands for manipulating | |
18179 | breakpoints. | |
18180 | ||
18181 | @subheading The @code{-break-after} Command | |
18182 | @findex -break-after | |
18183 | ||
18184 | @subsubheading Synopsis | |
18185 | ||
18186 | @smallexample | |
18187 | -break-after @var{number} @var{count} | |
18188 | @end smallexample | |
18189 | ||
18190 | The breakpoint number @var{number} is not in effect until it has been | |
18191 | hit @var{count} times. To see how this is reflected in the output of | |
18192 | the @samp{-break-list} command, see the description of the | |
18193 | @samp{-break-list} command below. | |
18194 | ||
18195 | @subsubheading @value{GDBN} Command | |
18196 | ||
18197 | The corresponding @value{GDBN} command is @samp{ignore}. | |
18198 | ||
18199 | @subsubheading Example | |
18200 | ||
18201 | @smallexample | |
594fe323 | 18202 | (gdb) |
922fbb7b | 18203 | -break-insert main |
948d5102 NR |
18204 | ^done,bkpt=@{number="1",addr="0x000100d0",file="hello.c", |
18205 | fullname="/home/foo/hello.c",line="5",times="0"@} | |
594fe323 | 18206 | (gdb) |
922fbb7b AC |
18207 | -break-after 1 3 |
18208 | ~ | |
18209 | ^done | |
594fe323 | 18210 | (gdb) |
922fbb7b AC |
18211 | -break-list |
18212 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
18213 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18214 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18215 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18216 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18217 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18218 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18219 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
18220 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
18221 | line="5",times="0",ignore="3"@}]@} | |
594fe323 | 18222 | (gdb) |
922fbb7b AC |
18223 | @end smallexample |
18224 | ||
18225 | @ignore | |
18226 | @subheading The @code{-break-catch} Command | |
18227 | @findex -break-catch | |
18228 | ||
18229 | @subheading The @code{-break-commands} Command | |
18230 | @findex -break-commands | |
18231 | @end ignore | |
18232 | ||
18233 | ||
18234 | @subheading The @code{-break-condition} Command | |
18235 | @findex -break-condition | |
18236 | ||
18237 | @subsubheading Synopsis | |
18238 | ||
18239 | @smallexample | |
18240 | -break-condition @var{number} @var{expr} | |
18241 | @end smallexample | |
18242 | ||
18243 | Breakpoint @var{number} will stop the program only if the condition in | |
18244 | @var{expr} is true. The condition becomes part of the | |
18245 | @samp{-break-list} output (see the description of the @samp{-break-list} | |
18246 | command below). | |
18247 | ||
18248 | @subsubheading @value{GDBN} Command | |
18249 | ||
18250 | The corresponding @value{GDBN} command is @samp{condition}. | |
18251 | ||
18252 | @subsubheading Example | |
18253 | ||
18254 | @smallexample | |
594fe323 | 18255 | (gdb) |
922fbb7b AC |
18256 | -break-condition 1 1 |
18257 | ^done | |
594fe323 | 18258 | (gdb) |
922fbb7b AC |
18259 | -break-list |
18260 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
18261 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18262 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18263 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18264 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18265 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18266 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18267 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
18268 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
18269 | line="5",cond="1",times="0",ignore="3"@}]@} | |
594fe323 | 18270 | (gdb) |
922fbb7b AC |
18271 | @end smallexample |
18272 | ||
18273 | @subheading The @code{-break-delete} Command | |
18274 | @findex -break-delete | |
18275 | ||
18276 | @subsubheading Synopsis | |
18277 | ||
18278 | @smallexample | |
18279 | -break-delete ( @var{breakpoint} )+ | |
18280 | @end smallexample | |
18281 | ||
18282 | Delete the breakpoint(s) whose number(s) are specified in the argument | |
18283 | list. This is obviously reflected in the breakpoint list. | |
18284 | ||
79a6e687 | 18285 | @subsubheading @value{GDBN} Command |
922fbb7b AC |
18286 | |
18287 | The corresponding @value{GDBN} command is @samp{delete}. | |
18288 | ||
18289 | @subsubheading Example | |
18290 | ||
18291 | @smallexample | |
594fe323 | 18292 | (gdb) |
922fbb7b AC |
18293 | -break-delete 1 |
18294 | ^done | |
594fe323 | 18295 | (gdb) |
922fbb7b AC |
18296 | -break-list |
18297 | ^done,BreakpointTable=@{nr_rows="0",nr_cols="6", | |
18298 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18299 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18300 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18301 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18302 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18303 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18304 | body=[]@} | |
594fe323 | 18305 | (gdb) |
922fbb7b AC |
18306 | @end smallexample |
18307 | ||
18308 | @subheading The @code{-break-disable} Command | |
18309 | @findex -break-disable | |
18310 | ||
18311 | @subsubheading Synopsis | |
18312 | ||
18313 | @smallexample | |
18314 | -break-disable ( @var{breakpoint} )+ | |
18315 | @end smallexample | |
18316 | ||
18317 | Disable the named @var{breakpoint}(s). The field @samp{enabled} in the | |
18318 | break list is now set to @samp{n} for the named @var{breakpoint}(s). | |
18319 | ||
18320 | @subsubheading @value{GDBN} Command | |
18321 | ||
18322 | The corresponding @value{GDBN} command is @samp{disable}. | |
18323 | ||
18324 | @subsubheading Example | |
18325 | ||
18326 | @smallexample | |
594fe323 | 18327 | (gdb) |
922fbb7b AC |
18328 | -break-disable 2 |
18329 | ^done | |
594fe323 | 18330 | (gdb) |
922fbb7b AC |
18331 | -break-list |
18332 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
18333 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18334 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18335 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18336 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18337 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18338 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18339 | body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="n", | |
948d5102 NR |
18340 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
18341 | line="5",times="0"@}]@} | |
594fe323 | 18342 | (gdb) |
922fbb7b AC |
18343 | @end smallexample |
18344 | ||
18345 | @subheading The @code{-break-enable} Command | |
18346 | @findex -break-enable | |
18347 | ||
18348 | @subsubheading Synopsis | |
18349 | ||
18350 | @smallexample | |
18351 | -break-enable ( @var{breakpoint} )+ | |
18352 | @end smallexample | |
18353 | ||
18354 | Enable (previously disabled) @var{breakpoint}(s). | |
18355 | ||
18356 | @subsubheading @value{GDBN} Command | |
18357 | ||
18358 | The corresponding @value{GDBN} command is @samp{enable}. | |
18359 | ||
18360 | @subsubheading Example | |
18361 | ||
18362 | @smallexample | |
594fe323 | 18363 | (gdb) |
922fbb7b AC |
18364 | -break-enable 2 |
18365 | ^done | |
594fe323 | 18366 | (gdb) |
922fbb7b AC |
18367 | -break-list |
18368 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
18369 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18370 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18371 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18372 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18373 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18374 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18375 | body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
18376 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
18377 | line="5",times="0"@}]@} | |
594fe323 | 18378 | (gdb) |
922fbb7b AC |
18379 | @end smallexample |
18380 | ||
18381 | @subheading The @code{-break-info} Command | |
18382 | @findex -break-info | |
18383 | ||
18384 | @subsubheading Synopsis | |
18385 | ||
18386 | @smallexample | |
18387 | -break-info @var{breakpoint} | |
18388 | @end smallexample | |
18389 | ||
18390 | @c REDUNDANT??? | |
18391 | Get information about a single breakpoint. | |
18392 | ||
79a6e687 | 18393 | @subsubheading @value{GDBN} Command |
922fbb7b AC |
18394 | |
18395 | The corresponding @value{GDBN} command is @samp{info break @var{breakpoint}}. | |
18396 | ||
18397 | @subsubheading Example | |
18398 | N.A. | |
18399 | ||
18400 | @subheading The @code{-break-insert} Command | |
18401 | @findex -break-insert | |
18402 | ||
18403 | @subsubheading Synopsis | |
18404 | ||
18405 | @smallexample | |
afe8ab22 | 18406 | -break-insert [ -t ] [ -h ] [ -f ] |
922fbb7b | 18407 | [ -c @var{condition} ] [ -i @var{ignore-count} ] |
afe8ab22 | 18408 | [ -p @var{thread} ] [ @var{location} ] |
922fbb7b AC |
18409 | @end smallexample |
18410 | ||
18411 | @noindent | |
afe8ab22 | 18412 | If specified, @var{location}, can be one of: |
922fbb7b AC |
18413 | |
18414 | @itemize @bullet | |
18415 | @item function | |
18416 | @c @item +offset | |
18417 | @c @item -offset | |
18418 | @c @item linenum | |
18419 | @item filename:linenum | |
18420 | @item filename:function | |
18421 | @item *address | |
18422 | @end itemize | |
18423 | ||
18424 | The possible optional parameters of this command are: | |
18425 | ||
18426 | @table @samp | |
18427 | @item -t | |
948d5102 | 18428 | Insert a temporary breakpoint. |
922fbb7b AC |
18429 | @item -h |
18430 | Insert a hardware breakpoint. | |
18431 | @item -c @var{condition} | |
18432 | Make the breakpoint conditional on @var{condition}. | |
18433 | @item -i @var{ignore-count} | |
18434 | Initialize the @var{ignore-count}. | |
afe8ab22 VP |
18435 | @item -f |
18436 | If @var{location} cannot be parsed (for example if it | |
18437 | refers to unknown files or functions), create a pending | |
18438 | breakpoint. Without this flag, @value{GDBN} will report | |
18439 | an error, and won't create a breakpoint, if @var{location} | |
18440 | cannot be parsed. | |
922fbb7b AC |
18441 | @end table |
18442 | ||
18443 | @subsubheading Result | |
18444 | ||
18445 | The result is in the form: | |
18446 | ||
18447 | @smallexample | |
948d5102 NR |
18448 | ^done,bkpt=@{number="@var{number}",type="@var{type}",disp="del"|"keep", |
18449 | enabled="y"|"n",addr="@var{hex}",func="@var{funcname}",file="@var{filename}", | |
ef21caaf NR |
18450 | fullname="@var{full_filename}",line="@var{lineno}",[thread="@var{threadno},] |
18451 | times="@var{times}"@} | |
922fbb7b AC |
18452 | @end smallexample |
18453 | ||
18454 | @noindent | |
948d5102 NR |
18455 | where @var{number} is the @value{GDBN} number for this breakpoint, |
18456 | @var{funcname} is the name of the function where the breakpoint was | |
18457 | inserted, @var{filename} is the name of the source file which contains | |
18458 | this function, @var{lineno} is the source line number within that file | |
18459 | and @var{times} the number of times that the breakpoint has been hit | |
18460 | (always 0 for -break-insert but may be greater for -break-info or -break-list | |
18461 | which use the same output). | |
922fbb7b AC |
18462 | |
18463 | Note: this format is open to change. | |
18464 | @c An out-of-band breakpoint instead of part of the result? | |
18465 | ||
18466 | @subsubheading @value{GDBN} Command | |
18467 | ||
18468 | The corresponding @value{GDBN} commands are @samp{break}, @samp{tbreak}, | |
18469 | @samp{hbreak}, @samp{thbreak}, and @samp{rbreak}. | |
18470 | ||
18471 | @subsubheading Example | |
18472 | ||
18473 | @smallexample | |
594fe323 | 18474 | (gdb) |
922fbb7b | 18475 | -break-insert main |
948d5102 NR |
18476 | ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c", |
18477 | fullname="/home/foo/recursive2.c,line="4",times="0"@} | |
594fe323 | 18478 | (gdb) |
922fbb7b | 18479 | -break-insert -t foo |
948d5102 NR |
18480 | ^done,bkpt=@{number="2",addr="0x00010774",file="recursive2.c", |
18481 | fullname="/home/foo/recursive2.c,line="11",times="0"@} | |
594fe323 | 18482 | (gdb) |
922fbb7b AC |
18483 | -break-list |
18484 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
18485 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18486 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18487 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18488 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18489 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18490 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18491 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
18492 | addr="0x0001072c", func="main",file="recursive2.c", |
18493 | fullname="/home/foo/recursive2.c,"line="4",times="0"@}, | |
922fbb7b | 18494 | bkpt=@{number="2",type="breakpoint",disp="del",enabled="y", |
948d5102 NR |
18495 | addr="0x00010774",func="foo",file="recursive2.c", |
18496 | fullname="/home/foo/recursive2.c",line="11",times="0"@}]@} | |
594fe323 | 18497 | (gdb) |
922fbb7b AC |
18498 | -break-insert -r foo.* |
18499 | ~int foo(int, int); | |
948d5102 NR |
18500 | ^done,bkpt=@{number="3",addr="0x00010774",file="recursive2.c, |
18501 | "fullname="/home/foo/recursive2.c",line="11",times="0"@} | |
594fe323 | 18502 | (gdb) |
922fbb7b AC |
18503 | @end smallexample |
18504 | ||
18505 | @subheading The @code{-break-list} Command | |
18506 | @findex -break-list | |
18507 | ||
18508 | @subsubheading Synopsis | |
18509 | ||
18510 | @smallexample | |
18511 | -break-list | |
18512 | @end smallexample | |
18513 | ||
18514 | Displays the list of inserted breakpoints, showing the following fields: | |
18515 | ||
18516 | @table @samp | |
18517 | @item Number | |
18518 | number of the breakpoint | |
18519 | @item Type | |
18520 | type of the breakpoint: @samp{breakpoint} or @samp{watchpoint} | |
18521 | @item Disposition | |
18522 | should the breakpoint be deleted or disabled when it is hit: @samp{keep} | |
18523 | or @samp{nokeep} | |
18524 | @item Enabled | |
18525 | is the breakpoint enabled or no: @samp{y} or @samp{n} | |
18526 | @item Address | |
18527 | memory location at which the breakpoint is set | |
18528 | @item What | |
18529 | logical location of the breakpoint, expressed by function name, file | |
18530 | name, line number | |
18531 | @item Times | |
18532 | number of times the breakpoint has been hit | |
18533 | @end table | |
18534 | ||
18535 | If there are no breakpoints or watchpoints, the @code{BreakpointTable} | |
18536 | @code{body} field is an empty list. | |
18537 | ||
18538 | @subsubheading @value{GDBN} Command | |
18539 | ||
18540 | The corresponding @value{GDBN} command is @samp{info break}. | |
18541 | ||
18542 | @subsubheading Example | |
18543 | ||
18544 | @smallexample | |
594fe323 | 18545 | (gdb) |
922fbb7b AC |
18546 | -break-list |
18547 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
18548 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18549 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18550 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18551 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18552 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18553 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18554 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
18555 | addr="0x000100d0",func="main",file="hello.c",line="5",times="0"@}, | |
18556 | bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
18557 | addr="0x00010114",func="foo",file="hello.c",fullname="/home/foo/hello.c", |
18558 | line="13",times="0"@}]@} | |
594fe323 | 18559 | (gdb) |
922fbb7b AC |
18560 | @end smallexample |
18561 | ||
18562 | Here's an example of the result when there are no breakpoints: | |
18563 | ||
18564 | @smallexample | |
594fe323 | 18565 | (gdb) |
922fbb7b AC |
18566 | -break-list |
18567 | ^done,BreakpointTable=@{nr_rows="0",nr_cols="6", | |
18568 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18569 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18570 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18571 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18572 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18573 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18574 | body=[]@} | |
594fe323 | 18575 | (gdb) |
922fbb7b AC |
18576 | @end smallexample |
18577 | ||
18578 | @subheading The @code{-break-watch} Command | |
18579 | @findex -break-watch | |
18580 | ||
18581 | @subsubheading Synopsis | |
18582 | ||
18583 | @smallexample | |
18584 | -break-watch [ -a | -r ] | |
18585 | @end smallexample | |
18586 | ||
18587 | Create a watchpoint. With the @samp{-a} option it will create an | |
d3e8051b | 18588 | @dfn{access} watchpoint, i.e., a watchpoint that triggers either on a |
922fbb7b | 18589 | read from or on a write to the memory location. With the @samp{-r} |
d3e8051b | 18590 | option, the watchpoint created is a @dfn{read} watchpoint, i.e., it will |
922fbb7b AC |
18591 | trigger only when the memory location is accessed for reading. Without |
18592 | either of the options, the watchpoint created is a regular watchpoint, | |
d3e8051b | 18593 | i.e., it will trigger when the memory location is accessed for writing. |
79a6e687 | 18594 | @xref{Set Watchpoints, , Setting Watchpoints}. |
922fbb7b AC |
18595 | |
18596 | Note that @samp{-break-list} will report a single list of watchpoints and | |
18597 | breakpoints inserted. | |
18598 | ||
18599 | @subsubheading @value{GDBN} Command | |
18600 | ||
18601 | The corresponding @value{GDBN} commands are @samp{watch}, @samp{awatch}, and | |
18602 | @samp{rwatch}. | |
18603 | ||
18604 | @subsubheading Example | |
18605 | ||
18606 | Setting a watchpoint on a variable in the @code{main} function: | |
18607 | ||
18608 | @smallexample | |
594fe323 | 18609 | (gdb) |
922fbb7b AC |
18610 | -break-watch x |
18611 | ^done,wpt=@{number="2",exp="x"@} | |
594fe323 | 18612 | (gdb) |
922fbb7b AC |
18613 | -exec-continue |
18614 | ^running | |
0869d01b NR |
18615 | (gdb) |
18616 | *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="x"@}, | |
922fbb7b | 18617 | value=@{old="-268439212",new="55"@}, |
76ff342d | 18618 | frame=@{func="main",args=[],file="recursive2.c", |
948d5102 | 18619 | fullname="/home/foo/bar/recursive2.c",line="5"@} |
594fe323 | 18620 | (gdb) |
922fbb7b AC |
18621 | @end smallexample |
18622 | ||
18623 | Setting a watchpoint on a variable local to a function. @value{GDBN} will stop | |
18624 | the program execution twice: first for the variable changing value, then | |
18625 | for the watchpoint going out of scope. | |
18626 | ||
18627 | @smallexample | |
594fe323 | 18628 | (gdb) |
922fbb7b AC |
18629 | -break-watch C |
18630 | ^done,wpt=@{number="5",exp="C"@} | |
594fe323 | 18631 | (gdb) |
922fbb7b AC |
18632 | -exec-continue |
18633 | ^running | |
0869d01b NR |
18634 | (gdb) |
18635 | *stopped,reason="watchpoint-trigger", | |
922fbb7b AC |
18636 | wpt=@{number="5",exp="C"@},value=@{old="-276895068",new="3"@}, |
18637 | frame=@{func="callee4",args=[], | |
76ff342d DJ |
18638 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
18639 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@} | |
594fe323 | 18640 | (gdb) |
922fbb7b AC |
18641 | -exec-continue |
18642 | ^running | |
0869d01b NR |
18643 | (gdb) |
18644 | *stopped,reason="watchpoint-scope",wpnum="5", | |
922fbb7b AC |
18645 | frame=@{func="callee3",args=[@{name="strarg", |
18646 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
18647 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
18648 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 18649 | (gdb) |
922fbb7b AC |
18650 | @end smallexample |
18651 | ||
18652 | Listing breakpoints and watchpoints, at different points in the program | |
18653 | execution. Note that once the watchpoint goes out of scope, it is | |
18654 | deleted. | |
18655 | ||
18656 | @smallexample | |
594fe323 | 18657 | (gdb) |
922fbb7b AC |
18658 | -break-watch C |
18659 | ^done,wpt=@{number="2",exp="C"@} | |
594fe323 | 18660 | (gdb) |
922fbb7b AC |
18661 | -break-list |
18662 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
18663 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18664 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18665 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18666 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18667 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18668 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18669 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
18670 | addr="0x00010734",func="callee4", | |
948d5102 NR |
18671 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
18672 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c"line="8",times="1"@}, | |
922fbb7b AC |
18673 | bkpt=@{number="2",type="watchpoint",disp="keep", |
18674 | enabled="y",addr="",what="C",times="0"@}]@} | |
594fe323 | 18675 | (gdb) |
922fbb7b AC |
18676 | -exec-continue |
18677 | ^running | |
0869d01b NR |
18678 | (gdb) |
18679 | *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="C"@}, | |
922fbb7b AC |
18680 | value=@{old="-276895068",new="3"@}, |
18681 | frame=@{func="callee4",args=[], | |
76ff342d DJ |
18682 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
18683 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@} | |
594fe323 | 18684 | (gdb) |
922fbb7b AC |
18685 | -break-list |
18686 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
18687 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18688 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18689 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18690 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18691 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18692 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18693 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
18694 | addr="0x00010734",func="callee4", | |
948d5102 NR |
18695 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
18696 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"@}, | |
922fbb7b AC |
18697 | bkpt=@{number="2",type="watchpoint",disp="keep", |
18698 | enabled="y",addr="",what="C",times="-5"@}]@} | |
594fe323 | 18699 | (gdb) |
922fbb7b AC |
18700 | -exec-continue |
18701 | ^running | |
18702 | ^done,reason="watchpoint-scope",wpnum="2", | |
18703 | frame=@{func="callee3",args=[@{name="strarg", | |
18704 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
18705 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
18706 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 18707 | (gdb) |
922fbb7b AC |
18708 | -break-list |
18709 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
18710 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
18711 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
18712 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
18713 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
18714 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
18715 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
18716 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
18717 | addr="0x00010734",func="callee4", | |
948d5102 NR |
18718 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
18719 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8", | |
18720 | times="1"@}]@} | |
594fe323 | 18721 | (gdb) |
922fbb7b AC |
18722 | @end smallexample |
18723 | ||
18724 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
a2c02241 NR |
18725 | @node GDB/MI Program Context |
18726 | @section @sc{gdb/mi} Program Context | |
922fbb7b | 18727 | |
a2c02241 NR |
18728 | @subheading The @code{-exec-arguments} Command |
18729 | @findex -exec-arguments | |
922fbb7b | 18730 | |
922fbb7b AC |
18731 | |
18732 | @subsubheading Synopsis | |
18733 | ||
18734 | @smallexample | |
a2c02241 | 18735 | -exec-arguments @var{args} |
922fbb7b AC |
18736 | @end smallexample |
18737 | ||
a2c02241 NR |
18738 | Set the inferior program arguments, to be used in the next |
18739 | @samp{-exec-run}. | |
922fbb7b | 18740 | |
a2c02241 | 18741 | @subsubheading @value{GDBN} Command |
922fbb7b | 18742 | |
a2c02241 | 18743 | The corresponding @value{GDBN} command is @samp{set args}. |
922fbb7b | 18744 | |
a2c02241 | 18745 | @subsubheading Example |
922fbb7b | 18746 | |
a2c02241 NR |
18747 | @c FIXME! |
18748 | Don't have one around. | |
922fbb7b | 18749 | |
a2c02241 NR |
18750 | |
18751 | @subheading The @code{-exec-show-arguments} Command | |
18752 | @findex -exec-show-arguments | |
18753 | ||
18754 | @subsubheading Synopsis | |
18755 | ||
18756 | @smallexample | |
18757 | -exec-show-arguments | |
18758 | @end smallexample | |
18759 | ||
18760 | Print the arguments of the program. | |
922fbb7b AC |
18761 | |
18762 | @subsubheading @value{GDBN} Command | |
18763 | ||
a2c02241 | 18764 | The corresponding @value{GDBN} command is @samp{show args}. |
922fbb7b AC |
18765 | |
18766 | @subsubheading Example | |
a2c02241 | 18767 | N.A. |
922fbb7b | 18768 | |
922fbb7b | 18769 | |
a2c02241 NR |
18770 | @subheading The @code{-environment-cd} Command |
18771 | @findex -environment-cd | |
922fbb7b | 18772 | |
a2c02241 | 18773 | @subsubheading Synopsis |
922fbb7b AC |
18774 | |
18775 | @smallexample | |
a2c02241 | 18776 | -environment-cd @var{pathdir} |
922fbb7b AC |
18777 | @end smallexample |
18778 | ||
a2c02241 | 18779 | Set @value{GDBN}'s working directory. |
922fbb7b | 18780 | |
a2c02241 | 18781 | @subsubheading @value{GDBN} Command |
922fbb7b | 18782 | |
a2c02241 NR |
18783 | The corresponding @value{GDBN} command is @samp{cd}. |
18784 | ||
18785 | @subsubheading Example | |
922fbb7b AC |
18786 | |
18787 | @smallexample | |
594fe323 | 18788 | (gdb) |
a2c02241 NR |
18789 | -environment-cd /kwikemart/marge/ezannoni/flathead-dev/devo/gdb |
18790 | ^done | |
594fe323 | 18791 | (gdb) |
922fbb7b AC |
18792 | @end smallexample |
18793 | ||
18794 | ||
a2c02241 NR |
18795 | @subheading The @code{-environment-directory} Command |
18796 | @findex -environment-directory | |
922fbb7b AC |
18797 | |
18798 | @subsubheading Synopsis | |
18799 | ||
18800 | @smallexample | |
a2c02241 | 18801 | -environment-directory [ -r ] [ @var{pathdir} ]+ |
922fbb7b AC |
18802 | @end smallexample |
18803 | ||
a2c02241 NR |
18804 | Add directories @var{pathdir} to beginning of search path for source files. |
18805 | If the @samp{-r} option is used, the search path is reset to the default | |
18806 | search path. If directories @var{pathdir} are supplied in addition to the | |
18807 | @samp{-r} option, the search path is first reset and then addition | |
18808 | occurs as normal. | |
18809 | Multiple directories may be specified, separated by blanks. Specifying | |
18810 | multiple directories in a single command | |
18811 | results in the directories added to the beginning of the | |
18812 | search path in the same order they were presented in the command. | |
18813 | If blanks are needed as | |
18814 | part of a directory name, double-quotes should be used around | |
18815 | the name. In the command output, the path will show up separated | |
d3e8051b | 18816 | by the system directory-separator character. The directory-separator |
a2c02241 NR |
18817 | character must not be used |
18818 | in any directory name. | |
18819 | If no directories are specified, the current search path is displayed. | |
922fbb7b AC |
18820 | |
18821 | @subsubheading @value{GDBN} Command | |
18822 | ||
a2c02241 | 18823 | The corresponding @value{GDBN} command is @samp{dir}. |
922fbb7b AC |
18824 | |
18825 | @subsubheading Example | |
18826 | ||
922fbb7b | 18827 | @smallexample |
594fe323 | 18828 | (gdb) |
a2c02241 NR |
18829 | -environment-directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb |
18830 | ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd" | |
594fe323 | 18831 | (gdb) |
a2c02241 NR |
18832 | -environment-directory "" |
18833 | ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd" | |
594fe323 | 18834 | (gdb) |
a2c02241 NR |
18835 | -environment-directory -r /home/jjohnstn/src/gdb /usr/src |
18836 | ^done,source-path="/home/jjohnstn/src/gdb:/usr/src:$cdir:$cwd" | |
594fe323 | 18837 | (gdb) |
a2c02241 NR |
18838 | -environment-directory -r |
18839 | ^done,source-path="$cdir:$cwd" | |
594fe323 | 18840 | (gdb) |
922fbb7b AC |
18841 | @end smallexample |
18842 | ||
18843 | ||
a2c02241 NR |
18844 | @subheading The @code{-environment-path} Command |
18845 | @findex -environment-path | |
922fbb7b AC |
18846 | |
18847 | @subsubheading Synopsis | |
18848 | ||
18849 | @smallexample | |
a2c02241 | 18850 | -environment-path [ -r ] [ @var{pathdir} ]+ |
922fbb7b AC |
18851 | @end smallexample |
18852 | ||
a2c02241 NR |
18853 | Add directories @var{pathdir} to beginning of search path for object files. |
18854 | If the @samp{-r} option is used, the search path is reset to the original | |
18855 | search path that existed at gdb start-up. If directories @var{pathdir} are | |
18856 | supplied in addition to the | |
18857 | @samp{-r} option, the search path is first reset and then addition | |
18858 | occurs as normal. | |
18859 | Multiple directories may be specified, separated by blanks. Specifying | |
18860 | multiple directories in a single command | |
18861 | results in the directories added to the beginning of the | |
18862 | search path in the same order they were presented in the command. | |
18863 | If blanks are needed as | |
18864 | part of a directory name, double-quotes should be used around | |
18865 | the name. In the command output, the path will show up separated | |
d3e8051b | 18866 | by the system directory-separator character. The directory-separator |
a2c02241 NR |
18867 | character must not be used |
18868 | in any directory name. | |
18869 | If no directories are specified, the current path is displayed. | |
18870 | ||
922fbb7b AC |
18871 | |
18872 | @subsubheading @value{GDBN} Command | |
18873 | ||
a2c02241 | 18874 | The corresponding @value{GDBN} command is @samp{path}. |
922fbb7b AC |
18875 | |
18876 | @subsubheading Example | |
18877 | ||
922fbb7b | 18878 | @smallexample |
594fe323 | 18879 | (gdb) |
a2c02241 NR |
18880 | -environment-path |
18881 | ^done,path="/usr/bin" | |
594fe323 | 18882 | (gdb) |
a2c02241 NR |
18883 | -environment-path /kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb /bin |
18884 | ^done,path="/kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb:/bin:/usr/bin" | |
594fe323 | 18885 | (gdb) |
a2c02241 NR |
18886 | -environment-path -r /usr/local/bin |
18887 | ^done,path="/usr/local/bin:/usr/bin" | |
594fe323 | 18888 | (gdb) |
922fbb7b AC |
18889 | @end smallexample |
18890 | ||
18891 | ||
a2c02241 NR |
18892 | @subheading The @code{-environment-pwd} Command |
18893 | @findex -environment-pwd | |
922fbb7b AC |
18894 | |
18895 | @subsubheading Synopsis | |
18896 | ||
18897 | @smallexample | |
a2c02241 | 18898 | -environment-pwd |
922fbb7b AC |
18899 | @end smallexample |
18900 | ||
a2c02241 | 18901 | Show the current working directory. |
922fbb7b | 18902 | |
79a6e687 | 18903 | @subsubheading @value{GDBN} Command |
922fbb7b | 18904 | |
a2c02241 | 18905 | The corresponding @value{GDBN} command is @samp{pwd}. |
922fbb7b AC |
18906 | |
18907 | @subsubheading Example | |
18908 | ||
922fbb7b | 18909 | @smallexample |
594fe323 | 18910 | (gdb) |
a2c02241 NR |
18911 | -environment-pwd |
18912 | ^done,cwd="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb" | |
594fe323 | 18913 | (gdb) |
922fbb7b AC |
18914 | @end smallexample |
18915 | ||
a2c02241 NR |
18916 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
18917 | @node GDB/MI Thread Commands | |
18918 | @section @sc{gdb/mi} Thread Commands | |
18919 | ||
18920 | ||
18921 | @subheading The @code{-thread-info} Command | |
18922 | @findex -thread-info | |
922fbb7b AC |
18923 | |
18924 | @subsubheading Synopsis | |
18925 | ||
18926 | @smallexample | |
a2c02241 | 18927 | -thread-info |
922fbb7b AC |
18928 | @end smallexample |
18929 | ||
79a6e687 | 18930 | @subsubheading @value{GDBN} Command |
922fbb7b | 18931 | |
a2c02241 | 18932 | No equivalent. |
922fbb7b AC |
18933 | |
18934 | @subsubheading Example | |
a2c02241 | 18935 | N.A. |
922fbb7b AC |
18936 | |
18937 | ||
a2c02241 NR |
18938 | @subheading The @code{-thread-list-all-threads} Command |
18939 | @findex -thread-list-all-threads | |
922fbb7b AC |
18940 | |
18941 | @subsubheading Synopsis | |
18942 | ||
18943 | @smallexample | |
a2c02241 | 18944 | -thread-list-all-threads |
922fbb7b AC |
18945 | @end smallexample |
18946 | ||
a2c02241 | 18947 | @subsubheading @value{GDBN} Command |
922fbb7b | 18948 | |
a2c02241 | 18949 | The equivalent @value{GDBN} command is @samp{info threads}. |
922fbb7b | 18950 | |
a2c02241 NR |
18951 | @subsubheading Example |
18952 | N.A. | |
922fbb7b | 18953 | |
922fbb7b | 18954 | |
a2c02241 NR |
18955 | @subheading The @code{-thread-list-ids} Command |
18956 | @findex -thread-list-ids | |
922fbb7b | 18957 | |
a2c02241 | 18958 | @subsubheading Synopsis |
922fbb7b | 18959 | |
a2c02241 NR |
18960 | @smallexample |
18961 | -thread-list-ids | |
18962 | @end smallexample | |
922fbb7b | 18963 | |
a2c02241 NR |
18964 | Produces a list of the currently known @value{GDBN} thread ids. At the |
18965 | end of the list it also prints the total number of such threads. | |
922fbb7b AC |
18966 | |
18967 | @subsubheading @value{GDBN} Command | |
18968 | ||
a2c02241 | 18969 | Part of @samp{info threads} supplies the same information. |
922fbb7b AC |
18970 | |
18971 | @subsubheading Example | |
18972 | ||
a2c02241 | 18973 | No threads present, besides the main process: |
922fbb7b AC |
18974 | |
18975 | @smallexample | |
594fe323 | 18976 | (gdb) |
a2c02241 NR |
18977 | -thread-list-ids |
18978 | ^done,thread-ids=@{@},number-of-threads="0" | |
594fe323 | 18979 | (gdb) |
922fbb7b AC |
18980 | @end smallexample |
18981 | ||
922fbb7b | 18982 | |
a2c02241 | 18983 | Several threads: |
922fbb7b AC |
18984 | |
18985 | @smallexample | |
594fe323 | 18986 | (gdb) |
a2c02241 NR |
18987 | -thread-list-ids |
18988 | ^done,thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@}, | |
18989 | number-of-threads="3" | |
594fe323 | 18990 | (gdb) |
922fbb7b AC |
18991 | @end smallexample |
18992 | ||
a2c02241 NR |
18993 | |
18994 | @subheading The @code{-thread-select} Command | |
18995 | @findex -thread-select | |
922fbb7b AC |
18996 | |
18997 | @subsubheading Synopsis | |
18998 | ||
18999 | @smallexample | |
a2c02241 | 19000 | -thread-select @var{threadnum} |
922fbb7b AC |
19001 | @end smallexample |
19002 | ||
a2c02241 NR |
19003 | Make @var{threadnum} the current thread. It prints the number of the new |
19004 | current thread, and the topmost frame for that thread. | |
922fbb7b AC |
19005 | |
19006 | @subsubheading @value{GDBN} Command | |
19007 | ||
a2c02241 | 19008 | The corresponding @value{GDBN} command is @samp{thread}. |
922fbb7b AC |
19009 | |
19010 | @subsubheading Example | |
922fbb7b AC |
19011 | |
19012 | @smallexample | |
594fe323 | 19013 | (gdb) |
a2c02241 NR |
19014 | -exec-next |
19015 | ^running | |
594fe323 | 19016 | (gdb) |
a2c02241 NR |
19017 | *stopped,reason="end-stepping-range",thread-id="2",line="187", |
19018 | file="../../../devo/gdb/testsuite/gdb.threads/linux-dp.c" | |
594fe323 | 19019 | (gdb) |
a2c02241 NR |
19020 | -thread-list-ids |
19021 | ^done, | |
19022 | thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@}, | |
19023 | number-of-threads="3" | |
594fe323 | 19024 | (gdb) |
a2c02241 NR |
19025 | -thread-select 3 |
19026 | ^done,new-thread-id="3", | |
19027 | frame=@{level="0",func="vprintf", | |
19028 | args=[@{name="format",value="0x8048e9c \"%*s%c %d %c\\n\""@}, | |
19029 | @{name="arg",value="0x2"@}],file="vprintf.c",line="31"@} | |
594fe323 | 19030 | (gdb) |
922fbb7b AC |
19031 | @end smallexample |
19032 | ||
a2c02241 NR |
19033 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
19034 | @node GDB/MI Program Execution | |
19035 | @section @sc{gdb/mi} Program Execution | |
922fbb7b | 19036 | |
ef21caaf | 19037 | These are the asynchronous commands which generate the out-of-band |
3f94c067 | 19038 | record @samp{*stopped}. Currently @value{GDBN} only really executes |
ef21caaf NR |
19039 | asynchronously with remote targets and this interaction is mimicked in |
19040 | other cases. | |
922fbb7b | 19041 | |
922fbb7b AC |
19042 | @subheading The @code{-exec-continue} Command |
19043 | @findex -exec-continue | |
19044 | ||
19045 | @subsubheading Synopsis | |
19046 | ||
19047 | @smallexample | |
19048 | -exec-continue | |
19049 | @end smallexample | |
19050 | ||
ef21caaf NR |
19051 | Resumes the execution of the inferior program until a breakpoint is |
19052 | encountered, or until the inferior exits. | |
922fbb7b AC |
19053 | |
19054 | @subsubheading @value{GDBN} Command | |
19055 | ||
19056 | The corresponding @value{GDBN} corresponding is @samp{continue}. | |
19057 | ||
19058 | @subsubheading Example | |
19059 | ||
19060 | @smallexample | |
19061 | -exec-continue | |
19062 | ^running | |
594fe323 | 19063 | (gdb) |
922fbb7b AC |
19064 | @@Hello world |
19065 | *stopped,reason="breakpoint-hit",bkptno="2",frame=@{func="foo",args=[], | |
948d5102 | 19066 | file="hello.c",fullname="/home/foo/bar/hello.c",line="13"@} |
594fe323 | 19067 | (gdb) |
922fbb7b AC |
19068 | @end smallexample |
19069 | ||
19070 | ||
19071 | @subheading The @code{-exec-finish} Command | |
19072 | @findex -exec-finish | |
19073 | ||
19074 | @subsubheading Synopsis | |
19075 | ||
19076 | @smallexample | |
19077 | -exec-finish | |
19078 | @end smallexample | |
19079 | ||
ef21caaf NR |
19080 | Resumes the execution of the inferior program until the current |
19081 | function is exited. Displays the results returned by the function. | |
922fbb7b AC |
19082 | |
19083 | @subsubheading @value{GDBN} Command | |
19084 | ||
19085 | The corresponding @value{GDBN} command is @samp{finish}. | |
19086 | ||
19087 | @subsubheading Example | |
19088 | ||
19089 | Function returning @code{void}. | |
19090 | ||
19091 | @smallexample | |
19092 | -exec-finish | |
19093 | ^running | |
594fe323 | 19094 | (gdb) |
922fbb7b AC |
19095 | @@hello from foo |
19096 | *stopped,reason="function-finished",frame=@{func="main",args=[], | |
948d5102 | 19097 | file="hello.c",fullname="/home/foo/bar/hello.c",line="7"@} |
594fe323 | 19098 | (gdb) |
922fbb7b AC |
19099 | @end smallexample |
19100 | ||
19101 | Function returning other than @code{void}. The name of the internal | |
19102 | @value{GDBN} variable storing the result is printed, together with the | |
19103 | value itself. | |
19104 | ||
19105 | @smallexample | |
19106 | -exec-finish | |
19107 | ^running | |
594fe323 | 19108 | (gdb) |
922fbb7b AC |
19109 | *stopped,reason="function-finished",frame=@{addr="0x000107b0",func="foo", |
19110 | args=[@{name="a",value="1"],@{name="b",value="9"@}@}, | |
948d5102 | 19111 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, |
922fbb7b | 19112 | gdb-result-var="$1",return-value="0" |
594fe323 | 19113 | (gdb) |
922fbb7b AC |
19114 | @end smallexample |
19115 | ||
19116 | ||
19117 | @subheading The @code{-exec-interrupt} Command | |
19118 | @findex -exec-interrupt | |
19119 | ||
19120 | @subsubheading Synopsis | |
19121 | ||
19122 | @smallexample | |
19123 | -exec-interrupt | |
19124 | @end smallexample | |
19125 | ||
ef21caaf NR |
19126 | Interrupts the background execution of the target. Note how the token |
19127 | associated with the stop message is the one for the execution command | |
19128 | that has been interrupted. The token for the interrupt itself only | |
19129 | appears in the @samp{^done} output. If the user is trying to | |
922fbb7b AC |
19130 | interrupt a non-running program, an error message will be printed. |
19131 | ||
19132 | @subsubheading @value{GDBN} Command | |
19133 | ||
19134 | The corresponding @value{GDBN} command is @samp{interrupt}. | |
19135 | ||
19136 | @subsubheading Example | |
19137 | ||
19138 | @smallexample | |
594fe323 | 19139 | (gdb) |
922fbb7b AC |
19140 | 111-exec-continue |
19141 | 111^running | |
19142 | ||
594fe323 | 19143 | (gdb) |
922fbb7b AC |
19144 | 222-exec-interrupt |
19145 | 222^done | |
594fe323 | 19146 | (gdb) |
922fbb7b | 19147 | 111*stopped,signal-name="SIGINT",signal-meaning="Interrupt", |
76ff342d | 19148 | frame=@{addr="0x00010140",func="foo",args=[],file="try.c", |
948d5102 | 19149 | fullname="/home/foo/bar/try.c",line="13"@} |
594fe323 | 19150 | (gdb) |
922fbb7b | 19151 | |
594fe323 | 19152 | (gdb) |
922fbb7b AC |
19153 | -exec-interrupt |
19154 | ^error,msg="mi_cmd_exec_interrupt: Inferior not executing." | |
594fe323 | 19155 | (gdb) |
922fbb7b AC |
19156 | @end smallexample |
19157 | ||
19158 | ||
19159 | @subheading The @code{-exec-next} Command | |
19160 | @findex -exec-next | |
19161 | ||
19162 | @subsubheading Synopsis | |
19163 | ||
19164 | @smallexample | |
19165 | -exec-next | |
19166 | @end smallexample | |
19167 | ||
ef21caaf NR |
19168 | Resumes execution of the inferior program, stopping when the beginning |
19169 | of the next source line is reached. | |
922fbb7b AC |
19170 | |
19171 | @subsubheading @value{GDBN} Command | |
19172 | ||
19173 | The corresponding @value{GDBN} command is @samp{next}. | |
19174 | ||
19175 | @subsubheading Example | |
19176 | ||
19177 | @smallexample | |
19178 | -exec-next | |
19179 | ^running | |
594fe323 | 19180 | (gdb) |
922fbb7b | 19181 | *stopped,reason="end-stepping-range",line="8",file="hello.c" |
594fe323 | 19182 | (gdb) |
922fbb7b AC |
19183 | @end smallexample |
19184 | ||
19185 | ||
19186 | @subheading The @code{-exec-next-instruction} Command | |
19187 | @findex -exec-next-instruction | |
19188 | ||
19189 | @subsubheading Synopsis | |
19190 | ||
19191 | @smallexample | |
19192 | -exec-next-instruction | |
19193 | @end smallexample | |
19194 | ||
ef21caaf NR |
19195 | Executes one machine instruction. If the instruction is a function |
19196 | call, continues until the function returns. If the program stops at an | |
19197 | instruction in the middle of a source line, the address will be | |
19198 | printed as well. | |
922fbb7b AC |
19199 | |
19200 | @subsubheading @value{GDBN} Command | |
19201 | ||
19202 | The corresponding @value{GDBN} command is @samp{nexti}. | |
19203 | ||
19204 | @subsubheading Example | |
19205 | ||
19206 | @smallexample | |
594fe323 | 19207 | (gdb) |
922fbb7b AC |
19208 | -exec-next-instruction |
19209 | ^running | |
19210 | ||
594fe323 | 19211 | (gdb) |
922fbb7b AC |
19212 | *stopped,reason="end-stepping-range", |
19213 | addr="0x000100d4",line="5",file="hello.c" | |
594fe323 | 19214 | (gdb) |
922fbb7b AC |
19215 | @end smallexample |
19216 | ||
19217 | ||
19218 | @subheading The @code{-exec-return} Command | |
19219 | @findex -exec-return | |
19220 | ||
19221 | @subsubheading Synopsis | |
19222 | ||
19223 | @smallexample | |
19224 | -exec-return | |
19225 | @end smallexample | |
19226 | ||
19227 | Makes current function return immediately. Doesn't execute the inferior. | |
19228 | Displays the new current frame. | |
19229 | ||
19230 | @subsubheading @value{GDBN} Command | |
19231 | ||
19232 | The corresponding @value{GDBN} command is @samp{return}. | |
19233 | ||
19234 | @subsubheading Example | |
19235 | ||
19236 | @smallexample | |
594fe323 | 19237 | (gdb) |
922fbb7b AC |
19238 | 200-break-insert callee4 |
19239 | 200^done,bkpt=@{number="1",addr="0x00010734", | |
19240 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8"@} | |
594fe323 | 19241 | (gdb) |
922fbb7b AC |
19242 | 000-exec-run |
19243 | 000^running | |
594fe323 | 19244 | (gdb) |
922fbb7b AC |
19245 | 000*stopped,reason="breakpoint-hit",bkptno="1", |
19246 | frame=@{func="callee4",args=[], | |
76ff342d DJ |
19247 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
19248 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@} | |
594fe323 | 19249 | (gdb) |
922fbb7b AC |
19250 | 205-break-delete |
19251 | 205^done | |
594fe323 | 19252 | (gdb) |
922fbb7b AC |
19253 | 111-exec-return |
19254 | 111^done,frame=@{level="0",func="callee3", | |
19255 | args=[@{name="strarg", | |
19256 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
19257 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
19258 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 19259 | (gdb) |
922fbb7b AC |
19260 | @end smallexample |
19261 | ||
19262 | ||
19263 | @subheading The @code{-exec-run} Command | |
19264 | @findex -exec-run | |
19265 | ||
19266 | @subsubheading Synopsis | |
19267 | ||
19268 | @smallexample | |
19269 | -exec-run | |
19270 | @end smallexample | |
19271 | ||
ef21caaf NR |
19272 | Starts execution of the inferior from the beginning. The inferior |
19273 | executes until either a breakpoint is encountered or the program | |
19274 | exits. In the latter case the output will include an exit code, if | |
19275 | the program has exited exceptionally. | |
922fbb7b AC |
19276 | |
19277 | @subsubheading @value{GDBN} Command | |
19278 | ||
19279 | The corresponding @value{GDBN} command is @samp{run}. | |
19280 | ||
ef21caaf | 19281 | @subsubheading Examples |
922fbb7b AC |
19282 | |
19283 | @smallexample | |
594fe323 | 19284 | (gdb) |
922fbb7b AC |
19285 | -break-insert main |
19286 | ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",line="4"@} | |
594fe323 | 19287 | (gdb) |
922fbb7b AC |
19288 | -exec-run |
19289 | ^running | |
594fe323 | 19290 | (gdb) |
922fbb7b | 19291 | *stopped,reason="breakpoint-hit",bkptno="1", |
76ff342d | 19292 | frame=@{func="main",args=[],file="recursive2.c", |
948d5102 | 19293 | fullname="/home/foo/bar/recursive2.c",line="4"@} |
594fe323 | 19294 | (gdb) |
922fbb7b AC |
19295 | @end smallexample |
19296 | ||
ef21caaf NR |
19297 | @noindent |
19298 | Program exited normally: | |
19299 | ||
19300 | @smallexample | |
594fe323 | 19301 | (gdb) |
ef21caaf NR |
19302 | -exec-run |
19303 | ^running | |
594fe323 | 19304 | (gdb) |
ef21caaf NR |
19305 | x = 55 |
19306 | *stopped,reason="exited-normally" | |
594fe323 | 19307 | (gdb) |
ef21caaf NR |
19308 | @end smallexample |
19309 | ||
19310 | @noindent | |
19311 | Program exited exceptionally: | |
19312 | ||
19313 | @smallexample | |
594fe323 | 19314 | (gdb) |
ef21caaf NR |
19315 | -exec-run |
19316 | ^running | |
594fe323 | 19317 | (gdb) |
ef21caaf NR |
19318 | x = 55 |
19319 | *stopped,reason="exited",exit-code="01" | |
594fe323 | 19320 | (gdb) |
ef21caaf NR |
19321 | @end smallexample |
19322 | ||
19323 | Another way the program can terminate is if it receives a signal such as | |
19324 | @code{SIGINT}. In this case, @sc{gdb/mi} displays this: | |
19325 | ||
19326 | @smallexample | |
594fe323 | 19327 | (gdb) |
ef21caaf NR |
19328 | *stopped,reason="exited-signalled",signal-name="SIGINT", |
19329 | signal-meaning="Interrupt" | |
19330 | @end smallexample | |
19331 | ||
922fbb7b | 19332 | |
a2c02241 NR |
19333 | @c @subheading -exec-signal |
19334 | ||
19335 | ||
19336 | @subheading The @code{-exec-step} Command | |
19337 | @findex -exec-step | |
922fbb7b AC |
19338 | |
19339 | @subsubheading Synopsis | |
19340 | ||
19341 | @smallexample | |
a2c02241 | 19342 | -exec-step |
922fbb7b AC |
19343 | @end smallexample |
19344 | ||
a2c02241 NR |
19345 | Resumes execution of the inferior program, stopping when the beginning |
19346 | of the next source line is reached, if the next source line is not a | |
19347 | function call. If it is, stop at the first instruction of the called | |
19348 | function. | |
922fbb7b AC |
19349 | |
19350 | @subsubheading @value{GDBN} Command | |
19351 | ||
a2c02241 | 19352 | The corresponding @value{GDBN} command is @samp{step}. |
922fbb7b AC |
19353 | |
19354 | @subsubheading Example | |
19355 | ||
19356 | Stepping into a function: | |
19357 | ||
19358 | @smallexample | |
19359 | -exec-step | |
19360 | ^running | |
594fe323 | 19361 | (gdb) |
922fbb7b AC |
19362 | *stopped,reason="end-stepping-range", |
19363 | frame=@{func="foo",args=[@{name="a",value="10"@}, | |
76ff342d | 19364 | @{name="b",value="0"@}],file="recursive2.c", |
948d5102 | 19365 | fullname="/home/foo/bar/recursive2.c",line="11"@} |
594fe323 | 19366 | (gdb) |
922fbb7b AC |
19367 | @end smallexample |
19368 | ||
19369 | Regular stepping: | |
19370 | ||
19371 | @smallexample | |
19372 | -exec-step | |
19373 | ^running | |
594fe323 | 19374 | (gdb) |
922fbb7b | 19375 | *stopped,reason="end-stepping-range",line="14",file="recursive2.c" |
594fe323 | 19376 | (gdb) |
922fbb7b AC |
19377 | @end smallexample |
19378 | ||
19379 | ||
19380 | @subheading The @code{-exec-step-instruction} Command | |
19381 | @findex -exec-step-instruction | |
19382 | ||
19383 | @subsubheading Synopsis | |
19384 | ||
19385 | @smallexample | |
19386 | -exec-step-instruction | |
19387 | @end smallexample | |
19388 | ||
ef21caaf NR |
19389 | Resumes the inferior which executes one machine instruction. The |
19390 | output, once @value{GDBN} has stopped, will vary depending on whether | |
19391 | we have stopped in the middle of a source line or not. In the former | |
19392 | case, the address at which the program stopped will be printed as | |
922fbb7b AC |
19393 | well. |
19394 | ||
19395 | @subsubheading @value{GDBN} Command | |
19396 | ||
19397 | The corresponding @value{GDBN} command is @samp{stepi}. | |
19398 | ||
19399 | @subsubheading Example | |
19400 | ||
19401 | @smallexample | |
594fe323 | 19402 | (gdb) |
922fbb7b AC |
19403 | -exec-step-instruction |
19404 | ^running | |
19405 | ||
594fe323 | 19406 | (gdb) |
922fbb7b | 19407 | *stopped,reason="end-stepping-range", |
76ff342d | 19408 | frame=@{func="foo",args=[],file="try.c", |
948d5102 | 19409 | fullname="/home/foo/bar/try.c",line="10"@} |
594fe323 | 19410 | (gdb) |
922fbb7b AC |
19411 | -exec-step-instruction |
19412 | ^running | |
19413 | ||
594fe323 | 19414 | (gdb) |
922fbb7b | 19415 | *stopped,reason="end-stepping-range", |
76ff342d | 19416 | frame=@{addr="0x000100f4",func="foo",args=[],file="try.c", |
948d5102 | 19417 | fullname="/home/foo/bar/try.c",line="10"@} |
594fe323 | 19418 | (gdb) |
922fbb7b AC |
19419 | @end smallexample |
19420 | ||
19421 | ||
19422 | @subheading The @code{-exec-until} Command | |
19423 | @findex -exec-until | |
19424 | ||
19425 | @subsubheading Synopsis | |
19426 | ||
19427 | @smallexample | |
19428 | -exec-until [ @var{location} ] | |
19429 | @end smallexample | |
19430 | ||
ef21caaf NR |
19431 | Executes the inferior until the @var{location} specified in the |
19432 | argument is reached. If there is no argument, the inferior executes | |
19433 | until a source line greater than the current one is reached. The | |
19434 | reason for stopping in this case will be @samp{location-reached}. | |
922fbb7b AC |
19435 | |
19436 | @subsubheading @value{GDBN} Command | |
19437 | ||
19438 | The corresponding @value{GDBN} command is @samp{until}. | |
19439 | ||
19440 | @subsubheading Example | |
19441 | ||
19442 | @smallexample | |
594fe323 | 19443 | (gdb) |
922fbb7b AC |
19444 | -exec-until recursive2.c:6 |
19445 | ^running | |
594fe323 | 19446 | (gdb) |
922fbb7b AC |
19447 | x = 55 |
19448 | *stopped,reason="location-reached",frame=@{func="main",args=[], | |
948d5102 | 19449 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="6"@} |
594fe323 | 19450 | (gdb) |
922fbb7b AC |
19451 | @end smallexample |
19452 | ||
19453 | @ignore | |
19454 | @subheading -file-clear | |
19455 | Is this going away???? | |
19456 | @end ignore | |
19457 | ||
351ff01a | 19458 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
a2c02241 NR |
19459 | @node GDB/MI Stack Manipulation |
19460 | @section @sc{gdb/mi} Stack Manipulation Commands | |
351ff01a | 19461 | |
922fbb7b | 19462 | |
a2c02241 NR |
19463 | @subheading The @code{-stack-info-frame} Command |
19464 | @findex -stack-info-frame | |
922fbb7b AC |
19465 | |
19466 | @subsubheading Synopsis | |
19467 | ||
19468 | @smallexample | |
a2c02241 | 19469 | -stack-info-frame |
922fbb7b AC |
19470 | @end smallexample |
19471 | ||
a2c02241 | 19472 | Get info on the selected frame. |
922fbb7b AC |
19473 | |
19474 | @subsubheading @value{GDBN} Command | |
19475 | ||
a2c02241 NR |
19476 | The corresponding @value{GDBN} command is @samp{info frame} or @samp{frame} |
19477 | (without arguments). | |
922fbb7b AC |
19478 | |
19479 | @subsubheading Example | |
19480 | ||
19481 | @smallexample | |
594fe323 | 19482 | (gdb) |
a2c02241 NR |
19483 | -stack-info-frame |
19484 | ^done,frame=@{level="1",addr="0x0001076c",func="callee3", | |
19485 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
19486 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@} | |
594fe323 | 19487 | (gdb) |
922fbb7b AC |
19488 | @end smallexample |
19489 | ||
a2c02241 NR |
19490 | @subheading The @code{-stack-info-depth} Command |
19491 | @findex -stack-info-depth | |
922fbb7b AC |
19492 | |
19493 | @subsubheading Synopsis | |
19494 | ||
19495 | @smallexample | |
a2c02241 | 19496 | -stack-info-depth [ @var{max-depth} ] |
922fbb7b AC |
19497 | @end smallexample |
19498 | ||
a2c02241 NR |
19499 | Return the depth of the stack. If the integer argument @var{max-depth} |
19500 | is specified, do not count beyond @var{max-depth} frames. | |
922fbb7b AC |
19501 | |
19502 | @subsubheading @value{GDBN} Command | |
19503 | ||
a2c02241 | 19504 | There's no equivalent @value{GDBN} command. |
922fbb7b AC |
19505 | |
19506 | @subsubheading Example | |
19507 | ||
a2c02241 NR |
19508 | For a stack with frame levels 0 through 11: |
19509 | ||
922fbb7b | 19510 | @smallexample |
594fe323 | 19511 | (gdb) |
a2c02241 NR |
19512 | -stack-info-depth |
19513 | ^done,depth="12" | |
594fe323 | 19514 | (gdb) |
a2c02241 NR |
19515 | -stack-info-depth 4 |
19516 | ^done,depth="4" | |
594fe323 | 19517 | (gdb) |
a2c02241 NR |
19518 | -stack-info-depth 12 |
19519 | ^done,depth="12" | |
594fe323 | 19520 | (gdb) |
a2c02241 NR |
19521 | -stack-info-depth 11 |
19522 | ^done,depth="11" | |
594fe323 | 19523 | (gdb) |
a2c02241 NR |
19524 | -stack-info-depth 13 |
19525 | ^done,depth="12" | |
594fe323 | 19526 | (gdb) |
922fbb7b AC |
19527 | @end smallexample |
19528 | ||
a2c02241 NR |
19529 | @subheading The @code{-stack-list-arguments} Command |
19530 | @findex -stack-list-arguments | |
922fbb7b AC |
19531 | |
19532 | @subsubheading Synopsis | |
19533 | ||
19534 | @smallexample | |
a2c02241 NR |
19535 | -stack-list-arguments @var{show-values} |
19536 | [ @var{low-frame} @var{high-frame} ] | |
922fbb7b AC |
19537 | @end smallexample |
19538 | ||
a2c02241 NR |
19539 | Display a list of the arguments for the frames between @var{low-frame} |
19540 | and @var{high-frame} (inclusive). If @var{low-frame} and | |
2f1acb09 VP |
19541 | @var{high-frame} are not provided, list the arguments for the whole |
19542 | call stack. If the two arguments are equal, show the single frame | |
19543 | at the corresponding level. It is an error if @var{low-frame} is | |
19544 | larger than the actual number of frames. On the other hand, | |
19545 | @var{high-frame} may be larger than the actual number of frames, in | |
19546 | which case only existing frames will be returned. | |
a2c02241 NR |
19547 | |
19548 | The @var{show-values} argument must have a value of 0 or 1. A value of | |
19549 | 0 means that only the names of the arguments are listed, a value of 1 | |
19550 | means that both names and values of the arguments are printed. | |
922fbb7b AC |
19551 | |
19552 | @subsubheading @value{GDBN} Command | |
19553 | ||
a2c02241 NR |
19554 | @value{GDBN} does not have an equivalent command. @code{gdbtk} has a |
19555 | @samp{gdb_get_args} command which partially overlaps with the | |
19556 | functionality of @samp{-stack-list-arguments}. | |
922fbb7b AC |
19557 | |
19558 | @subsubheading Example | |
922fbb7b | 19559 | |
a2c02241 | 19560 | @smallexample |
594fe323 | 19561 | (gdb) |
a2c02241 NR |
19562 | -stack-list-frames |
19563 | ^done, | |
19564 | stack=[ | |
19565 | frame=@{level="0",addr="0x00010734",func="callee4", | |
19566 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
19567 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}, | |
19568 | frame=@{level="1",addr="0x0001076c",func="callee3", | |
19569 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
19570 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@}, | |
19571 | frame=@{level="2",addr="0x0001078c",func="callee2", | |
19572 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
19573 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="22"@}, | |
19574 | frame=@{level="3",addr="0x000107b4",func="callee1", | |
19575 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
19576 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="27"@}, | |
19577 | frame=@{level="4",addr="0x000107e0",func="main", | |
19578 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
19579 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="32"@}] | |
594fe323 | 19580 | (gdb) |
a2c02241 NR |
19581 | -stack-list-arguments 0 |
19582 | ^done, | |
19583 | stack-args=[ | |
19584 | frame=@{level="0",args=[]@}, | |
19585 | frame=@{level="1",args=[name="strarg"]@}, | |
19586 | frame=@{level="2",args=[name="intarg",name="strarg"]@}, | |
19587 | frame=@{level="3",args=[name="intarg",name="strarg",name="fltarg"]@}, | |
19588 | frame=@{level="4",args=[]@}] | |
594fe323 | 19589 | (gdb) |
a2c02241 NR |
19590 | -stack-list-arguments 1 |
19591 | ^done, | |
19592 | stack-args=[ | |
19593 | frame=@{level="0",args=[]@}, | |
19594 | frame=@{level="1", | |
19595 | args=[@{name="strarg",value="0x11940 \"A string argument.\""@}]@}, | |
19596 | frame=@{level="2",args=[ | |
19597 | @{name="intarg",value="2"@}, | |
19598 | @{name="strarg",value="0x11940 \"A string argument.\""@}]@}, | |
19599 | @{frame=@{level="3",args=[ | |
19600 | @{name="intarg",value="2"@}, | |
19601 | @{name="strarg",value="0x11940 \"A string argument.\""@}, | |
19602 | @{name="fltarg",value="3.5"@}]@}, | |
19603 | frame=@{level="4",args=[]@}] | |
594fe323 | 19604 | (gdb) |
a2c02241 NR |
19605 | -stack-list-arguments 0 2 2 |
19606 | ^done,stack-args=[frame=@{level="2",args=[name="intarg",name="strarg"]@}] | |
594fe323 | 19607 | (gdb) |
a2c02241 NR |
19608 | -stack-list-arguments 1 2 2 |
19609 | ^done,stack-args=[frame=@{level="2", | |
19610 | args=[@{name="intarg",value="2"@}, | |
19611 | @{name="strarg",value="0x11940 \"A string argument.\""@}]@}] | |
594fe323 | 19612 | (gdb) |
a2c02241 NR |
19613 | @end smallexample |
19614 | ||
19615 | @c @subheading -stack-list-exception-handlers | |
922fbb7b | 19616 | |
a2c02241 NR |
19617 | |
19618 | @subheading The @code{-stack-list-frames} Command | |
19619 | @findex -stack-list-frames | |
1abaf70c BR |
19620 | |
19621 | @subsubheading Synopsis | |
19622 | ||
19623 | @smallexample | |
a2c02241 | 19624 | -stack-list-frames [ @var{low-frame} @var{high-frame} ] |
1abaf70c BR |
19625 | @end smallexample |
19626 | ||
a2c02241 NR |
19627 | List the frames currently on the stack. For each frame it displays the |
19628 | following info: | |
19629 | ||
19630 | @table @samp | |
19631 | @item @var{level} | |
d3e8051b | 19632 | The frame number, 0 being the topmost frame, i.e., the innermost function. |
a2c02241 NR |
19633 | @item @var{addr} |
19634 | The @code{$pc} value for that frame. | |
19635 | @item @var{func} | |
19636 | Function name. | |
19637 | @item @var{file} | |
19638 | File name of the source file where the function lives. | |
19639 | @item @var{line} | |
19640 | Line number corresponding to the @code{$pc}. | |
19641 | @end table | |
19642 | ||
19643 | If invoked without arguments, this command prints a backtrace for the | |
19644 | whole stack. If given two integer arguments, it shows the frames whose | |
19645 | levels are between the two arguments (inclusive). If the two arguments | |
2ab1eb7a VP |
19646 | are equal, it shows the single frame at the corresponding level. It is |
19647 | an error if @var{low-frame} is larger than the actual number of | |
a5451f4e | 19648 | frames. On the other hand, @var{high-frame} may be larger than the |
2ab1eb7a | 19649 | actual number of frames, in which case only existing frames will be returned. |
1abaf70c BR |
19650 | |
19651 | @subsubheading @value{GDBN} Command | |
19652 | ||
a2c02241 | 19653 | The corresponding @value{GDBN} commands are @samp{backtrace} and @samp{where}. |
1abaf70c BR |
19654 | |
19655 | @subsubheading Example | |
19656 | ||
a2c02241 NR |
19657 | Full stack backtrace: |
19658 | ||
1abaf70c | 19659 | @smallexample |
594fe323 | 19660 | (gdb) |
a2c02241 NR |
19661 | -stack-list-frames |
19662 | ^done,stack= | |
19663 | [frame=@{level="0",addr="0x0001076c",func="foo", | |
19664 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="11"@}, | |
19665 | frame=@{level="1",addr="0x000107a4",func="foo", | |
19666 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19667 | frame=@{level="2",addr="0x000107a4",func="foo", | |
19668 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19669 | frame=@{level="3",addr="0x000107a4",func="foo", | |
19670 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19671 | frame=@{level="4",addr="0x000107a4",func="foo", | |
19672 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19673 | frame=@{level="5",addr="0x000107a4",func="foo", | |
19674 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19675 | frame=@{level="6",addr="0x000107a4",func="foo", | |
19676 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19677 | frame=@{level="7",addr="0x000107a4",func="foo", | |
19678 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19679 | frame=@{level="8",addr="0x000107a4",func="foo", | |
19680 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19681 | frame=@{level="9",addr="0x000107a4",func="foo", | |
19682 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19683 | frame=@{level="10",addr="0x000107a4",func="foo", | |
19684 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19685 | frame=@{level="11",addr="0x00010738",func="main", | |
19686 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="4"@}] | |
594fe323 | 19687 | (gdb) |
1abaf70c BR |
19688 | @end smallexample |
19689 | ||
a2c02241 | 19690 | Show frames between @var{low_frame} and @var{high_frame}: |
1abaf70c | 19691 | |
a2c02241 | 19692 | @smallexample |
594fe323 | 19693 | (gdb) |
a2c02241 NR |
19694 | -stack-list-frames 3 5 |
19695 | ^done,stack= | |
19696 | [frame=@{level="3",addr="0x000107a4",func="foo", | |
19697 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19698 | frame=@{level="4",addr="0x000107a4",func="foo", | |
19699 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
19700 | frame=@{level="5",addr="0x000107a4",func="foo", | |
19701 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}] | |
594fe323 | 19702 | (gdb) |
a2c02241 | 19703 | @end smallexample |
922fbb7b | 19704 | |
a2c02241 | 19705 | Show a single frame: |
922fbb7b AC |
19706 | |
19707 | @smallexample | |
594fe323 | 19708 | (gdb) |
a2c02241 NR |
19709 | -stack-list-frames 3 3 |
19710 | ^done,stack= | |
19711 | [frame=@{level="3",addr="0x000107a4",func="foo", | |
19712 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}] | |
594fe323 | 19713 | (gdb) |
922fbb7b AC |
19714 | @end smallexample |
19715 | ||
922fbb7b | 19716 | |
a2c02241 NR |
19717 | @subheading The @code{-stack-list-locals} Command |
19718 | @findex -stack-list-locals | |
57c22c6c | 19719 | |
a2c02241 | 19720 | @subsubheading Synopsis |
922fbb7b AC |
19721 | |
19722 | @smallexample | |
a2c02241 | 19723 | -stack-list-locals @var{print-values} |
922fbb7b AC |
19724 | @end smallexample |
19725 | ||
a2c02241 NR |
19726 | Display the local variable names for the selected frame. If |
19727 | @var{print-values} is 0 or @code{--no-values}, print only the names of | |
19728 | the variables; if it is 1 or @code{--all-values}, print also their | |
19729 | values; and if it is 2 or @code{--simple-values}, print the name, | |
19730 | type and value for simple data types and the name and type for arrays, | |
19731 | structures and unions. In this last case, a frontend can immediately | |
19732 | display the value of simple data types and create variable objects for | |
d3e8051b | 19733 | other data types when the user wishes to explore their values in |
a2c02241 | 19734 | more detail. |
922fbb7b AC |
19735 | |
19736 | @subsubheading @value{GDBN} Command | |
19737 | ||
a2c02241 | 19738 | @samp{info locals} in @value{GDBN}, @samp{gdb_get_locals} in @code{gdbtk}. |
922fbb7b AC |
19739 | |
19740 | @subsubheading Example | |
922fbb7b AC |
19741 | |
19742 | @smallexample | |
594fe323 | 19743 | (gdb) |
a2c02241 NR |
19744 | -stack-list-locals 0 |
19745 | ^done,locals=[name="A",name="B",name="C"] | |
594fe323 | 19746 | (gdb) |
a2c02241 NR |
19747 | -stack-list-locals --all-values |
19748 | ^done,locals=[@{name="A",value="1"@},@{name="B",value="2"@}, | |
19749 | @{name="C",value="@{1, 2, 3@}"@}] | |
19750 | -stack-list-locals --simple-values | |
19751 | ^done,locals=[@{name="A",type="int",value="1"@}, | |
19752 | @{name="B",type="int",value="2"@},@{name="C",type="int [3]"@}] | |
594fe323 | 19753 | (gdb) |
922fbb7b AC |
19754 | @end smallexample |
19755 | ||
922fbb7b | 19756 | |
a2c02241 NR |
19757 | @subheading The @code{-stack-select-frame} Command |
19758 | @findex -stack-select-frame | |
922fbb7b AC |
19759 | |
19760 | @subsubheading Synopsis | |
19761 | ||
19762 | @smallexample | |
a2c02241 | 19763 | -stack-select-frame @var{framenum} |
922fbb7b AC |
19764 | @end smallexample |
19765 | ||
a2c02241 NR |
19766 | Change the selected frame. Select a different frame @var{framenum} on |
19767 | the stack. | |
922fbb7b AC |
19768 | |
19769 | @subsubheading @value{GDBN} Command | |
19770 | ||
a2c02241 NR |
19771 | The corresponding @value{GDBN} commands are @samp{frame}, @samp{up}, |
19772 | @samp{down}, @samp{select-frame}, @samp{up-silent}, and @samp{down-silent}. | |
922fbb7b AC |
19773 | |
19774 | @subsubheading Example | |
19775 | ||
19776 | @smallexample | |
594fe323 | 19777 | (gdb) |
a2c02241 | 19778 | -stack-select-frame 2 |
922fbb7b | 19779 | ^done |
594fe323 | 19780 | (gdb) |
922fbb7b AC |
19781 | @end smallexample |
19782 | ||
19783 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
a2c02241 NR |
19784 | @node GDB/MI Variable Objects |
19785 | @section @sc{gdb/mi} Variable Objects | |
922fbb7b | 19786 | |
a1b5960f | 19787 | @ignore |
922fbb7b | 19788 | |
a2c02241 | 19789 | @subheading Motivation for Variable Objects in @sc{gdb/mi} |
922fbb7b | 19790 | |
a2c02241 NR |
19791 | For the implementation of a variable debugger window (locals, watched |
19792 | expressions, etc.), we are proposing the adaptation of the existing code | |
19793 | used by @code{Insight}. | |
922fbb7b | 19794 | |
a2c02241 | 19795 | The two main reasons for that are: |
922fbb7b | 19796 | |
a2c02241 NR |
19797 | @enumerate 1 |
19798 | @item | |
19799 | It has been proven in practice (it is already on its second generation). | |
922fbb7b | 19800 | |
a2c02241 NR |
19801 | @item |
19802 | It will shorten development time (needless to say how important it is | |
19803 | now). | |
19804 | @end enumerate | |
922fbb7b | 19805 | |
a2c02241 NR |
19806 | The original interface was designed to be used by Tcl code, so it was |
19807 | slightly changed so it could be used through @sc{gdb/mi}. This section | |
19808 | describes the @sc{gdb/mi} operations that will be available and gives some | |
19809 | hints about their use. | |
922fbb7b | 19810 | |
a2c02241 NR |
19811 | @emph{Note}: In addition to the set of operations described here, we |
19812 | expect the @sc{gui} implementation of a variable window to require, at | |
19813 | least, the following operations: | |
922fbb7b | 19814 | |
a2c02241 NR |
19815 | @itemize @bullet |
19816 | @item @code{-gdb-show} @code{output-radix} | |
19817 | @item @code{-stack-list-arguments} | |
19818 | @item @code{-stack-list-locals} | |
19819 | @item @code{-stack-select-frame} | |
19820 | @end itemize | |
922fbb7b | 19821 | |
a1b5960f VP |
19822 | @end ignore |
19823 | ||
c8b2f53c | 19824 | @subheading Introduction to Variable Objects |
922fbb7b | 19825 | |
a2c02241 | 19826 | @cindex variable objects in @sc{gdb/mi} |
c8b2f53c VP |
19827 | |
19828 | Variable objects are "object-oriented" MI interface for examining and | |
19829 | changing values of expressions. Unlike some other MI interfaces that | |
19830 | work with expressions, variable objects are specifically designed for | |
19831 | simple and efficient presentation in the frontend. A variable object | |
19832 | is identified by string name. When a variable object is created, the | |
19833 | frontend specifies the expression for that variable object. The | |
19834 | expression can be a simple variable, or it can be an arbitrary complex | |
19835 | expression, and can even involve CPU registers. After creating a | |
19836 | variable object, the frontend can invoke other variable object | |
19837 | operations---for example to obtain or change the value of a variable | |
19838 | object, or to change display format. | |
19839 | ||
19840 | Variable objects have hierarchical tree structure. Any variable object | |
19841 | that corresponds to a composite type, such as structure in C, has | |
19842 | a number of child variable objects, for example corresponding to each | |
19843 | element of a structure. A child variable object can itself have | |
19844 | children, recursively. Recursion ends when we reach | |
25d5ea92 VP |
19845 | leaf variable objects, which always have built-in types. Child variable |
19846 | objects are created only by explicit request, so if a frontend | |
19847 | is not interested in the children of a particular variable object, no | |
19848 | child will be created. | |
c8b2f53c VP |
19849 | |
19850 | For a leaf variable object it is possible to obtain its value as a | |
19851 | string, or set the value from a string. String value can be also | |
19852 | obtained for a non-leaf variable object, but it's generally a string | |
19853 | that only indicates the type of the object, and does not list its | |
19854 | contents. Assignment to a non-leaf variable object is not allowed. | |
19855 | ||
19856 | A frontend does not need to read the values of all variable objects each time | |
19857 | the program stops. Instead, MI provides an update command that lists all | |
19858 | variable objects whose values has changed since the last update | |
19859 | operation. This considerably reduces the amount of data that must | |
25d5ea92 VP |
19860 | be transferred to the frontend. As noted above, children variable |
19861 | objects are created on demand, and only leaf variable objects have a | |
19862 | real value. As result, gdb will read target memory only for leaf | |
19863 | variables that frontend has created. | |
19864 | ||
19865 | The automatic update is not always desirable. For example, a frontend | |
19866 | might want to keep a value of some expression for future reference, | |
19867 | and never update it. For another example, fetching memory is | |
19868 | relatively slow for embedded targets, so a frontend might want | |
19869 | to disable automatic update for the variables that are either not | |
19870 | visible on the screen, or ``closed''. This is possible using so | |
19871 | called ``frozen variable objects''. Such variable objects are never | |
19872 | implicitly updated. | |
922fbb7b | 19873 | |
a2c02241 NR |
19874 | The following is the complete set of @sc{gdb/mi} operations defined to |
19875 | access this functionality: | |
922fbb7b | 19876 | |
a2c02241 NR |
19877 | @multitable @columnfractions .4 .6 |
19878 | @item @strong{Operation} | |
19879 | @tab @strong{Description} | |
922fbb7b | 19880 | |
a2c02241 NR |
19881 | @item @code{-var-create} |
19882 | @tab create a variable object | |
19883 | @item @code{-var-delete} | |
22d8a470 | 19884 | @tab delete the variable object and/or its children |
a2c02241 NR |
19885 | @item @code{-var-set-format} |
19886 | @tab set the display format of this variable | |
19887 | @item @code{-var-show-format} | |
19888 | @tab show the display format of this variable | |
19889 | @item @code{-var-info-num-children} | |
19890 | @tab tells how many children this object has | |
19891 | @item @code{-var-list-children} | |
19892 | @tab return a list of the object's children | |
19893 | @item @code{-var-info-type} | |
19894 | @tab show the type of this variable object | |
19895 | @item @code{-var-info-expression} | |
02142340 VP |
19896 | @tab print parent-relative expression that this variable object represents |
19897 | @item @code{-var-info-path-expression} | |
19898 | @tab print full expression that this variable object represents | |
a2c02241 NR |
19899 | @item @code{-var-show-attributes} |
19900 | @tab is this variable editable? does it exist here? | |
19901 | @item @code{-var-evaluate-expression} | |
19902 | @tab get the value of this variable | |
19903 | @item @code{-var-assign} | |
19904 | @tab set the value of this variable | |
19905 | @item @code{-var-update} | |
19906 | @tab update the variable and its children | |
25d5ea92 VP |
19907 | @item @code{-var-set-frozen} |
19908 | @tab set frozeness attribute | |
a2c02241 | 19909 | @end multitable |
922fbb7b | 19910 | |
a2c02241 NR |
19911 | In the next subsection we describe each operation in detail and suggest |
19912 | how it can be used. | |
922fbb7b | 19913 | |
a2c02241 | 19914 | @subheading Description And Use of Operations on Variable Objects |
922fbb7b | 19915 | |
a2c02241 NR |
19916 | @subheading The @code{-var-create} Command |
19917 | @findex -var-create | |
ef21caaf | 19918 | |
a2c02241 | 19919 | @subsubheading Synopsis |
ef21caaf | 19920 | |
a2c02241 NR |
19921 | @smallexample |
19922 | -var-create @{@var{name} | "-"@} | |
19923 | @{@var{frame-addr} | "*"@} @var{expression} | |
19924 | @end smallexample | |
19925 | ||
19926 | This operation creates a variable object, which allows the monitoring of | |
19927 | a variable, the result of an expression, a memory cell or a CPU | |
19928 | register. | |
ef21caaf | 19929 | |
a2c02241 NR |
19930 | The @var{name} parameter is the string by which the object can be |
19931 | referenced. It must be unique. If @samp{-} is specified, the varobj | |
19932 | system will generate a string ``varNNNNNN'' automatically. It will be | |
19933 | unique provided that one does not specify @var{name} on that format. | |
19934 | The command fails if a duplicate name is found. | |
ef21caaf | 19935 | |
a2c02241 NR |
19936 | The frame under which the expression should be evaluated can be |
19937 | specified by @var{frame-addr}. A @samp{*} indicates that the current | |
19938 | frame should be used. | |
922fbb7b | 19939 | |
a2c02241 NR |
19940 | @var{expression} is any expression valid on the current language set (must not |
19941 | begin with a @samp{*}), or one of the following: | |
922fbb7b | 19942 | |
a2c02241 NR |
19943 | @itemize @bullet |
19944 | @item | |
19945 | @samp{*@var{addr}}, where @var{addr} is the address of a memory cell | |
922fbb7b | 19946 | |
a2c02241 NR |
19947 | @item |
19948 | @samp{*@var{addr}-@var{addr}} --- a memory address range (TBD) | |
922fbb7b | 19949 | |
a2c02241 NR |
19950 | @item |
19951 | @samp{$@var{regname}} --- a CPU register name | |
19952 | @end itemize | |
922fbb7b | 19953 | |
a2c02241 | 19954 | @subsubheading Result |
922fbb7b | 19955 | |
a2c02241 NR |
19956 | This operation returns the name, number of children and the type of the |
19957 | object created. Type is returned as a string as the ones generated by | |
19958 | the @value{GDBN} CLI: | |
922fbb7b AC |
19959 | |
19960 | @smallexample | |
a2c02241 | 19961 | name="@var{name}",numchild="N",type="@var{type}" |
dcaaae04 NR |
19962 | @end smallexample |
19963 | ||
a2c02241 NR |
19964 | |
19965 | @subheading The @code{-var-delete} Command | |
19966 | @findex -var-delete | |
922fbb7b AC |
19967 | |
19968 | @subsubheading Synopsis | |
19969 | ||
19970 | @smallexample | |
22d8a470 | 19971 | -var-delete [ -c ] @var{name} |
922fbb7b AC |
19972 | @end smallexample |
19973 | ||
a2c02241 | 19974 | Deletes a previously created variable object and all of its children. |
22d8a470 | 19975 | With the @samp{-c} option, just deletes the children. |
922fbb7b | 19976 | |
a2c02241 | 19977 | Returns an error if the object @var{name} is not found. |
922fbb7b | 19978 | |
922fbb7b | 19979 | |
a2c02241 NR |
19980 | @subheading The @code{-var-set-format} Command |
19981 | @findex -var-set-format | |
922fbb7b | 19982 | |
a2c02241 | 19983 | @subsubheading Synopsis |
922fbb7b AC |
19984 | |
19985 | @smallexample | |
a2c02241 | 19986 | -var-set-format @var{name} @var{format-spec} |
922fbb7b AC |
19987 | @end smallexample |
19988 | ||
a2c02241 NR |
19989 | Sets the output format for the value of the object @var{name} to be |
19990 | @var{format-spec}. | |
19991 | ||
19992 | The syntax for the @var{format-spec} is as follows: | |
19993 | ||
19994 | @smallexample | |
19995 | @var{format-spec} @expansion{} | |
19996 | @{binary | decimal | hexadecimal | octal | natural@} | |
19997 | @end smallexample | |
19998 | ||
c8b2f53c VP |
19999 | The natural format is the default format choosen automatically |
20000 | based on the variable type (like decimal for an @code{int}, hex | |
20001 | for pointers, etc.). | |
20002 | ||
20003 | For a variable with children, the format is set only on the | |
20004 | variable itself, and the children are not affected. | |
a2c02241 NR |
20005 | |
20006 | @subheading The @code{-var-show-format} Command | |
20007 | @findex -var-show-format | |
922fbb7b AC |
20008 | |
20009 | @subsubheading Synopsis | |
20010 | ||
20011 | @smallexample | |
a2c02241 | 20012 | -var-show-format @var{name} |
922fbb7b AC |
20013 | @end smallexample |
20014 | ||
a2c02241 | 20015 | Returns the format used to display the value of the object @var{name}. |
922fbb7b | 20016 | |
a2c02241 NR |
20017 | @smallexample |
20018 | @var{format} @expansion{} | |
20019 | @var{format-spec} | |
20020 | @end smallexample | |
922fbb7b | 20021 | |
922fbb7b | 20022 | |
a2c02241 NR |
20023 | @subheading The @code{-var-info-num-children} Command |
20024 | @findex -var-info-num-children | |
20025 | ||
20026 | @subsubheading Synopsis | |
20027 | ||
20028 | @smallexample | |
20029 | -var-info-num-children @var{name} | |
20030 | @end smallexample | |
20031 | ||
20032 | Returns the number of children of a variable object @var{name}: | |
20033 | ||
20034 | @smallexample | |
20035 | numchild=@var{n} | |
20036 | @end smallexample | |
20037 | ||
20038 | ||
20039 | @subheading The @code{-var-list-children} Command | |
20040 | @findex -var-list-children | |
20041 | ||
20042 | @subsubheading Synopsis | |
20043 | ||
20044 | @smallexample | |
20045 | -var-list-children [@var{print-values}] @var{name} | |
20046 | @end smallexample | |
20047 | @anchor{-var-list-children} | |
20048 | ||
20049 | Return a list of the children of the specified variable object and | |
20050 | create variable objects for them, if they do not already exist. With | |
20051 | a single argument or if @var{print-values} has a value for of 0 or | |
20052 | @code{--no-values}, print only the names of the variables; if | |
20053 | @var{print-values} is 1 or @code{--all-values}, also print their | |
20054 | values; and if it is 2 or @code{--simple-values} print the name and | |
20055 | value for simple data types and just the name for arrays, structures | |
20056 | and unions. | |
922fbb7b AC |
20057 | |
20058 | @subsubheading Example | |
20059 | ||
20060 | @smallexample | |
594fe323 | 20061 | (gdb) |
a2c02241 NR |
20062 | -var-list-children n |
20063 | ^done,numchild=@var{n},children=[@{name=@var{name}, | |
20064 | numchild=@var{n},type=@var{type}@},@r{(repeats N times)}] | |
594fe323 | 20065 | (gdb) |
a2c02241 NR |
20066 | -var-list-children --all-values n |
20067 | ^done,numchild=@var{n},children=[@{name=@var{name}, | |
20068 | numchild=@var{n},value=@var{value},type=@var{type}@},@r{(repeats N times)}] | |
922fbb7b AC |
20069 | @end smallexample |
20070 | ||
922fbb7b | 20071 | |
a2c02241 NR |
20072 | @subheading The @code{-var-info-type} Command |
20073 | @findex -var-info-type | |
922fbb7b | 20074 | |
a2c02241 NR |
20075 | @subsubheading Synopsis |
20076 | ||
20077 | @smallexample | |
20078 | -var-info-type @var{name} | |
20079 | @end smallexample | |
20080 | ||
20081 | Returns the type of the specified variable @var{name}. The type is | |
20082 | returned as a string in the same format as it is output by the | |
20083 | @value{GDBN} CLI: | |
20084 | ||
20085 | @smallexample | |
20086 | type=@var{typename} | |
20087 | @end smallexample | |
20088 | ||
20089 | ||
20090 | @subheading The @code{-var-info-expression} Command | |
20091 | @findex -var-info-expression | |
922fbb7b AC |
20092 | |
20093 | @subsubheading Synopsis | |
20094 | ||
20095 | @smallexample | |
a2c02241 | 20096 | -var-info-expression @var{name} |
922fbb7b AC |
20097 | @end smallexample |
20098 | ||
02142340 VP |
20099 | Returns a string that is suitable for presenting this |
20100 | variable object in user interface. The string is generally | |
20101 | not valid expression in the current language, and cannot be evaluated. | |
20102 | ||
20103 | For example, if @code{a} is an array, and variable object | |
20104 | @code{A} was created for @code{a}, then we'll get this output: | |
922fbb7b | 20105 | |
a2c02241 | 20106 | @smallexample |
02142340 VP |
20107 | (gdb) -var-info-expression A.1 |
20108 | ^done,lang="C",exp="1" | |
a2c02241 | 20109 | @end smallexample |
922fbb7b | 20110 | |
a2c02241 | 20111 | @noindent |
02142340 VP |
20112 | Here, the values of @code{lang} can be @code{@{"C" | "C++" | "Java"@}}. |
20113 | ||
20114 | Note that the output of the @code{-var-list-children} command also | |
20115 | includes those expressions, so the @code{-var-info-expression} command | |
20116 | is of limited use. | |
20117 | ||
20118 | @subheading The @code{-var-info-path-expression} Command | |
20119 | @findex -var-info-path-expression | |
20120 | ||
20121 | @subsubheading Synopsis | |
20122 | ||
20123 | @smallexample | |
20124 | -var-info-path-expression @var{name} | |
20125 | @end smallexample | |
20126 | ||
20127 | Returns an expression that can be evaluated in the current | |
20128 | context and will yield the same value that a variable object has. | |
20129 | Compare this with the @code{-var-info-expression} command, which | |
20130 | result can be used only for UI presentation. Typical use of | |
20131 | the @code{-var-info-path-expression} command is creating a | |
20132 | watchpoint from a variable object. | |
20133 | ||
20134 | For example, suppose @code{C} is a C@t{++} class, derived from class | |
20135 | @code{Base}, and that the @code{Base} class has a member called | |
20136 | @code{m_size}. Assume a variable @code{c} is has the type of | |
20137 | @code{C} and a variable object @code{C} was created for variable | |
20138 | @code{c}. Then, we'll get this output: | |
20139 | @smallexample | |
20140 | (gdb) -var-info-path-expression C.Base.public.m_size | |
20141 | ^done,path_expr=((Base)c).m_size) | |
20142 | @end smallexample | |
922fbb7b | 20143 | |
a2c02241 NR |
20144 | @subheading The @code{-var-show-attributes} Command |
20145 | @findex -var-show-attributes | |
922fbb7b | 20146 | |
a2c02241 | 20147 | @subsubheading Synopsis |
922fbb7b | 20148 | |
a2c02241 NR |
20149 | @smallexample |
20150 | -var-show-attributes @var{name} | |
20151 | @end smallexample | |
922fbb7b | 20152 | |
a2c02241 | 20153 | List attributes of the specified variable object @var{name}: |
922fbb7b AC |
20154 | |
20155 | @smallexample | |
a2c02241 | 20156 | status=@var{attr} [ ( ,@var{attr} )* ] |
922fbb7b AC |
20157 | @end smallexample |
20158 | ||
a2c02241 NR |
20159 | @noindent |
20160 | where @var{attr} is @code{@{ @{ editable | noneditable @} | TBD @}}. | |
20161 | ||
20162 | @subheading The @code{-var-evaluate-expression} Command | |
20163 | @findex -var-evaluate-expression | |
20164 | ||
20165 | @subsubheading Synopsis | |
20166 | ||
20167 | @smallexample | |
20168 | -var-evaluate-expression @var{name} | |
20169 | @end smallexample | |
20170 | ||
20171 | Evaluates the expression that is represented by the specified variable | |
c8b2f53c VP |
20172 | object and returns its value as a string. The format of the |
20173 | string can be changed using the @code{-var-set-format} command. | |
a2c02241 NR |
20174 | |
20175 | @smallexample | |
20176 | value=@var{value} | |
20177 | @end smallexample | |
20178 | ||
20179 | Note that one must invoke @code{-var-list-children} for a variable | |
20180 | before the value of a child variable can be evaluated. | |
20181 | ||
20182 | @subheading The @code{-var-assign} Command | |
20183 | @findex -var-assign | |
20184 | ||
20185 | @subsubheading Synopsis | |
20186 | ||
20187 | @smallexample | |
20188 | -var-assign @var{name} @var{expression} | |
20189 | @end smallexample | |
20190 | ||
20191 | Assigns the value of @var{expression} to the variable object specified | |
20192 | by @var{name}. The object must be @samp{editable}. If the variable's | |
20193 | value is altered by the assign, the variable will show up in any | |
20194 | subsequent @code{-var-update} list. | |
20195 | ||
20196 | @subsubheading Example | |
922fbb7b AC |
20197 | |
20198 | @smallexample | |
594fe323 | 20199 | (gdb) |
a2c02241 NR |
20200 | -var-assign var1 3 |
20201 | ^done,value="3" | |
594fe323 | 20202 | (gdb) |
a2c02241 NR |
20203 | -var-update * |
20204 | ^done,changelist=[@{name="var1",in_scope="true",type_changed="false"@}] | |
594fe323 | 20205 | (gdb) |
922fbb7b AC |
20206 | @end smallexample |
20207 | ||
a2c02241 NR |
20208 | @subheading The @code{-var-update} Command |
20209 | @findex -var-update | |
20210 | ||
20211 | @subsubheading Synopsis | |
20212 | ||
20213 | @smallexample | |
20214 | -var-update [@var{print-values}] @{@var{name} | "*"@} | |
20215 | @end smallexample | |
20216 | ||
c8b2f53c VP |
20217 | Reevaluate the expressions corresponding to the variable object |
20218 | @var{name} and all its direct and indirect children, and return the | |
36ece8b3 NR |
20219 | list of variable objects whose values have changed; @var{name} must |
20220 | be a root variable object. Here, ``changed'' means that the result of | |
20221 | @code{-var-evaluate-expression} before and after the | |
20222 | @code{-var-update} is different. If @samp{*} is used as the variable | |
9f708cb2 VP |
20223 | object names, all existing variable objects are updated, except |
20224 | for frozen ones (@pxref{-var-set-frozen}). The option | |
36ece8b3 NR |
20225 | @var{print-values} determines whether both names and values, or just |
20226 | names are printed. The possible values of this options are the same | |
20227 | as for @code{-var-list-children} (@pxref{-var-list-children}). It is | |
20228 | recommended to use the @samp{--all-values} option, to reduce the | |
20229 | number of MI commands needed on each program stop. | |
c8b2f53c | 20230 | |
a2c02241 NR |
20231 | |
20232 | @subsubheading Example | |
922fbb7b AC |
20233 | |
20234 | @smallexample | |
594fe323 | 20235 | (gdb) |
a2c02241 NR |
20236 | -var-assign var1 3 |
20237 | ^done,value="3" | |
594fe323 | 20238 | (gdb) |
a2c02241 NR |
20239 | -var-update --all-values var1 |
20240 | ^done,changelist=[@{name="var1",value="3",in_scope="true", | |
20241 | type_changed="false"@}] | |
594fe323 | 20242 | (gdb) |
922fbb7b AC |
20243 | @end smallexample |
20244 | ||
9f708cb2 | 20245 | @anchor{-var-update} |
36ece8b3 NR |
20246 | The field in_scope may take three values: |
20247 | ||
20248 | @table @code | |
20249 | @item "true" | |
20250 | The variable object's current value is valid. | |
20251 | ||
20252 | @item "false" | |
20253 | The variable object does not currently hold a valid value but it may | |
20254 | hold one in the future if its associated expression comes back into | |
20255 | scope. | |
20256 | ||
20257 | @item "invalid" | |
20258 | The variable object no longer holds a valid value. | |
20259 | This can occur when the executable file being debugged has changed, | |
20260 | either through recompilation or by using the @value{GDBN} @code{file} | |
20261 | command. The front end should normally choose to delete these variable | |
20262 | objects. | |
20263 | @end table | |
20264 | ||
20265 | In the future new values may be added to this list so the front should | |
20266 | be prepared for this possibility. @xref{GDB/MI Development and Front Ends, ,@sc{GDB/MI} Development and Front Ends}. | |
20267 | ||
25d5ea92 VP |
20268 | @subheading The @code{-var-set-frozen} Command |
20269 | @findex -var-set-frozen | |
9f708cb2 | 20270 | @anchor{-var-set-frozen} |
25d5ea92 VP |
20271 | |
20272 | @subsubheading Synopsis | |
20273 | ||
20274 | @smallexample | |
9f708cb2 | 20275 | -var-set-frozen @var{name} @var{flag} |
25d5ea92 VP |
20276 | @end smallexample |
20277 | ||
9f708cb2 | 20278 | Set the frozenness flag on the variable object @var{name}. The |
25d5ea92 | 20279 | @var{flag} parameter should be either @samp{1} to make the variable |
9f708cb2 | 20280 | frozen or @samp{0} to make it unfrozen. If a variable object is |
25d5ea92 | 20281 | frozen, then neither itself, nor any of its children, are |
9f708cb2 | 20282 | implicitly updated by @code{-var-update} of |
25d5ea92 VP |
20283 | a parent variable or by @code{-var-update *}. Only |
20284 | @code{-var-update} of the variable itself will update its value and | |
20285 | values of its children. After a variable object is unfrozen, it is | |
20286 | implicitly updated by all subsequent @code{-var-update} operations. | |
20287 | Unfreezing a variable does not update it, only subsequent | |
20288 | @code{-var-update} does. | |
20289 | ||
20290 | @subsubheading Example | |
20291 | ||
20292 | @smallexample | |
20293 | (gdb) | |
20294 | -var-set-frozen V 1 | |
20295 | ^done | |
20296 | (gdb) | |
20297 | @end smallexample | |
20298 | ||
20299 | ||
a2c02241 NR |
20300 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
20301 | @node GDB/MI Data Manipulation | |
20302 | @section @sc{gdb/mi} Data Manipulation | |
922fbb7b | 20303 | |
a2c02241 NR |
20304 | @cindex data manipulation, in @sc{gdb/mi} |
20305 | @cindex @sc{gdb/mi}, data manipulation | |
20306 | This section describes the @sc{gdb/mi} commands that manipulate data: | |
20307 | examine memory and registers, evaluate expressions, etc. | |
20308 | ||
20309 | @c REMOVED FROM THE INTERFACE. | |
20310 | @c @subheading -data-assign | |
20311 | @c Change the value of a program variable. Plenty of side effects. | |
79a6e687 | 20312 | @c @subsubheading GDB Command |
a2c02241 NR |
20313 | @c set variable |
20314 | @c @subsubheading Example | |
20315 | @c N.A. | |
20316 | ||
20317 | @subheading The @code{-data-disassemble} Command | |
20318 | @findex -data-disassemble | |
922fbb7b AC |
20319 | |
20320 | @subsubheading Synopsis | |
20321 | ||
20322 | @smallexample | |
a2c02241 NR |
20323 | -data-disassemble |
20324 | [ -s @var{start-addr} -e @var{end-addr} ] | |
20325 | | [ -f @var{filename} -l @var{linenum} [ -n @var{lines} ] ] | |
20326 | -- @var{mode} | |
922fbb7b AC |
20327 | @end smallexample |
20328 | ||
a2c02241 NR |
20329 | @noindent |
20330 | Where: | |
20331 | ||
20332 | @table @samp | |
20333 | @item @var{start-addr} | |
20334 | is the beginning address (or @code{$pc}) | |
20335 | @item @var{end-addr} | |
20336 | is the end address | |
20337 | @item @var{filename} | |
20338 | is the name of the file to disassemble | |
20339 | @item @var{linenum} | |
20340 | is the line number to disassemble around | |
20341 | @item @var{lines} | |
d3e8051b | 20342 | is the number of disassembly lines to be produced. If it is -1, |
a2c02241 NR |
20343 | the whole function will be disassembled, in case no @var{end-addr} is |
20344 | specified. If @var{end-addr} is specified as a non-zero value, and | |
20345 | @var{lines} is lower than the number of disassembly lines between | |
20346 | @var{start-addr} and @var{end-addr}, only @var{lines} lines are | |
20347 | displayed; if @var{lines} is higher than the number of lines between | |
20348 | @var{start-addr} and @var{end-addr}, only the lines up to @var{end-addr} | |
20349 | are displayed. | |
20350 | @item @var{mode} | |
20351 | is either 0 (meaning only disassembly) or 1 (meaning mixed source and | |
20352 | disassembly). | |
20353 | @end table | |
20354 | ||
20355 | @subsubheading Result | |
20356 | ||
20357 | The output for each instruction is composed of four fields: | |
20358 | ||
20359 | @itemize @bullet | |
20360 | @item Address | |
20361 | @item Func-name | |
20362 | @item Offset | |
20363 | @item Instruction | |
20364 | @end itemize | |
20365 | ||
20366 | Note that whatever included in the instruction field, is not manipulated | |
d3e8051b | 20367 | directly by @sc{gdb/mi}, i.e., it is not possible to adjust its format. |
922fbb7b AC |
20368 | |
20369 | @subsubheading @value{GDBN} Command | |
20370 | ||
a2c02241 | 20371 | There's no direct mapping from this command to the CLI. |
922fbb7b AC |
20372 | |
20373 | @subsubheading Example | |
20374 | ||
a2c02241 NR |
20375 | Disassemble from the current value of @code{$pc} to @code{$pc + 20}: |
20376 | ||
922fbb7b | 20377 | @smallexample |
594fe323 | 20378 | (gdb) |
a2c02241 NR |
20379 | -data-disassemble -s $pc -e "$pc + 20" -- 0 |
20380 | ^done, | |
20381 | asm_insns=[ | |
20382 | @{address="0x000107c0",func-name="main",offset="4", | |
20383 | inst="mov 2, %o0"@}, | |
20384 | @{address="0x000107c4",func-name="main",offset="8", | |
20385 | inst="sethi %hi(0x11800), %o2"@}, | |
20386 | @{address="0x000107c8",func-name="main",offset="12", | |
20387 | inst="or %o2, 0x140, %o1\t! 0x11940 <_lib_version+8>"@}, | |
20388 | @{address="0x000107cc",func-name="main",offset="16", | |
20389 | inst="sethi %hi(0x11800), %o2"@}, | |
20390 | @{address="0x000107d0",func-name="main",offset="20", | |
20391 | inst="or %o2, 0x168, %o4\t! 0x11968 <_lib_version+48>"@}] | |
594fe323 | 20392 | (gdb) |
a2c02241 NR |
20393 | @end smallexample |
20394 | ||
20395 | Disassemble the whole @code{main} function. Line 32 is part of | |
20396 | @code{main}. | |
20397 | ||
20398 | @smallexample | |
20399 | -data-disassemble -f basics.c -l 32 -- 0 | |
20400 | ^done,asm_insns=[ | |
20401 | @{address="0x000107bc",func-name="main",offset="0", | |
20402 | inst="save %sp, -112, %sp"@}, | |
20403 | @{address="0x000107c0",func-name="main",offset="4", | |
20404 | inst="mov 2, %o0"@}, | |
20405 | @{address="0x000107c4",func-name="main",offset="8", | |
20406 | inst="sethi %hi(0x11800), %o2"@}, | |
20407 | [@dots{}] | |
20408 | @{address="0x0001081c",func-name="main",offset="96",inst="ret "@}, | |
20409 | @{address="0x00010820",func-name="main",offset="100",inst="restore "@}] | |
594fe323 | 20410 | (gdb) |
922fbb7b AC |
20411 | @end smallexample |
20412 | ||
a2c02241 | 20413 | Disassemble 3 instructions from the start of @code{main}: |
922fbb7b | 20414 | |
a2c02241 | 20415 | @smallexample |
594fe323 | 20416 | (gdb) |
a2c02241 NR |
20417 | -data-disassemble -f basics.c -l 32 -n 3 -- 0 |
20418 | ^done,asm_insns=[ | |
20419 | @{address="0x000107bc",func-name="main",offset="0", | |
20420 | inst="save %sp, -112, %sp"@}, | |
20421 | @{address="0x000107c0",func-name="main",offset="4", | |
20422 | inst="mov 2, %o0"@}, | |
20423 | @{address="0x000107c4",func-name="main",offset="8", | |
20424 | inst="sethi %hi(0x11800), %o2"@}] | |
594fe323 | 20425 | (gdb) |
a2c02241 NR |
20426 | @end smallexample |
20427 | ||
20428 | Disassemble 3 instructions from the start of @code{main} in mixed mode: | |
20429 | ||
20430 | @smallexample | |
594fe323 | 20431 | (gdb) |
a2c02241 NR |
20432 | -data-disassemble -f basics.c -l 32 -n 3 -- 1 |
20433 | ^done,asm_insns=[ | |
20434 | src_and_asm_line=@{line="31", | |
20435 | file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \ | |
20436 | testsuite/gdb.mi/basics.c",line_asm_insn=[ | |
20437 | @{address="0x000107bc",func-name="main",offset="0", | |
20438 | inst="save %sp, -112, %sp"@}]@}, | |
20439 | src_and_asm_line=@{line="32", | |
20440 | file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \ | |
20441 | testsuite/gdb.mi/basics.c",line_asm_insn=[ | |
20442 | @{address="0x000107c0",func-name="main",offset="4", | |
20443 | inst="mov 2, %o0"@}, | |
20444 | @{address="0x000107c4",func-name="main",offset="8", | |
20445 | inst="sethi %hi(0x11800), %o2"@}]@}] | |
594fe323 | 20446 | (gdb) |
a2c02241 NR |
20447 | @end smallexample |
20448 | ||
20449 | ||
20450 | @subheading The @code{-data-evaluate-expression} Command | |
20451 | @findex -data-evaluate-expression | |
922fbb7b AC |
20452 | |
20453 | @subsubheading Synopsis | |
20454 | ||
20455 | @smallexample | |
a2c02241 | 20456 | -data-evaluate-expression @var{expr} |
922fbb7b AC |
20457 | @end smallexample |
20458 | ||
a2c02241 NR |
20459 | Evaluate @var{expr} as an expression. The expression could contain an |
20460 | inferior function call. The function call will execute synchronously. | |
20461 | If the expression contains spaces, it must be enclosed in double quotes. | |
922fbb7b AC |
20462 | |
20463 | @subsubheading @value{GDBN} Command | |
20464 | ||
a2c02241 NR |
20465 | The corresponding @value{GDBN} commands are @samp{print}, @samp{output}, and |
20466 | @samp{call}. In @code{gdbtk} only, there's a corresponding | |
20467 | @samp{gdb_eval} command. | |
922fbb7b AC |
20468 | |
20469 | @subsubheading Example | |
20470 | ||
a2c02241 NR |
20471 | In the following example, the numbers that precede the commands are the |
20472 | @dfn{tokens} described in @ref{GDB/MI Command Syntax, ,@sc{gdb/mi} | |
20473 | Command Syntax}. Notice how @sc{gdb/mi} returns the same tokens in its | |
20474 | output. | |
20475 | ||
922fbb7b | 20476 | @smallexample |
a2c02241 NR |
20477 | 211-data-evaluate-expression A |
20478 | 211^done,value="1" | |
594fe323 | 20479 | (gdb) |
a2c02241 NR |
20480 | 311-data-evaluate-expression &A |
20481 | 311^done,value="0xefffeb7c" | |
594fe323 | 20482 | (gdb) |
a2c02241 NR |
20483 | 411-data-evaluate-expression A+3 |
20484 | 411^done,value="4" | |
594fe323 | 20485 | (gdb) |
a2c02241 NR |
20486 | 511-data-evaluate-expression "A + 3" |
20487 | 511^done,value="4" | |
594fe323 | 20488 | (gdb) |
a2c02241 | 20489 | @end smallexample |
922fbb7b AC |
20490 | |
20491 | ||
a2c02241 NR |
20492 | @subheading The @code{-data-list-changed-registers} Command |
20493 | @findex -data-list-changed-registers | |
922fbb7b AC |
20494 | |
20495 | @subsubheading Synopsis | |
20496 | ||
20497 | @smallexample | |
a2c02241 | 20498 | -data-list-changed-registers |
922fbb7b AC |
20499 | @end smallexample |
20500 | ||
a2c02241 | 20501 | Display a list of the registers that have changed. |
922fbb7b AC |
20502 | |
20503 | @subsubheading @value{GDBN} Command | |
20504 | ||
a2c02241 NR |
20505 | @value{GDBN} doesn't have a direct analog for this command; @code{gdbtk} |
20506 | has the corresponding command @samp{gdb_changed_register_list}. | |
922fbb7b AC |
20507 | |
20508 | @subsubheading Example | |
922fbb7b | 20509 | |
a2c02241 | 20510 | On a PPC MBX board: |
922fbb7b AC |
20511 | |
20512 | @smallexample | |
594fe323 | 20513 | (gdb) |
a2c02241 NR |
20514 | -exec-continue |
20515 | ^running | |
922fbb7b | 20516 | |
594fe323 | 20517 | (gdb) |
a2c02241 NR |
20518 | *stopped,reason="breakpoint-hit",bkptno="1",frame=@{func="main", |
20519 | args=[],file="try.c",fullname="/home/foo/bar/try.c",line="5"@} | |
594fe323 | 20520 | (gdb) |
a2c02241 NR |
20521 | -data-list-changed-registers |
20522 | ^done,changed-registers=["0","1","2","4","5","6","7","8","9", | |
20523 | "10","11","13","14","15","16","17","18","19","20","21","22","23", | |
20524 | "24","25","26","27","28","30","31","64","65","66","67","69"] | |
594fe323 | 20525 | (gdb) |
a2c02241 | 20526 | @end smallexample |
922fbb7b AC |
20527 | |
20528 | ||
a2c02241 NR |
20529 | @subheading The @code{-data-list-register-names} Command |
20530 | @findex -data-list-register-names | |
922fbb7b AC |
20531 | |
20532 | @subsubheading Synopsis | |
20533 | ||
20534 | @smallexample | |
a2c02241 | 20535 | -data-list-register-names [ ( @var{regno} )+ ] |
922fbb7b AC |
20536 | @end smallexample |
20537 | ||
a2c02241 NR |
20538 | Show a list of register names for the current target. If no arguments |
20539 | are given, it shows a list of the names of all the registers. If | |
20540 | integer numbers are given as arguments, it will print a list of the | |
20541 | names of the registers corresponding to the arguments. To ensure | |
20542 | consistency between a register name and its number, the output list may | |
20543 | include empty register names. | |
922fbb7b AC |
20544 | |
20545 | @subsubheading @value{GDBN} Command | |
20546 | ||
a2c02241 NR |
20547 | @value{GDBN} does not have a command which corresponds to |
20548 | @samp{-data-list-register-names}. In @code{gdbtk} there is a | |
20549 | corresponding command @samp{gdb_regnames}. | |
922fbb7b AC |
20550 | |
20551 | @subsubheading Example | |
922fbb7b | 20552 | |
a2c02241 NR |
20553 | For the PPC MBX board: |
20554 | @smallexample | |
594fe323 | 20555 | (gdb) |
a2c02241 NR |
20556 | -data-list-register-names |
20557 | ^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7", | |
20558 | "r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18", | |
20559 | "r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29", | |
20560 | "r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9", | |
20561 | "f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20", | |
20562 | "f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31", | |
20563 | "", "pc","ps","cr","lr","ctr","xer"] | |
594fe323 | 20564 | (gdb) |
a2c02241 NR |
20565 | -data-list-register-names 1 2 3 |
20566 | ^done,register-names=["r1","r2","r3"] | |
594fe323 | 20567 | (gdb) |
a2c02241 | 20568 | @end smallexample |
922fbb7b | 20569 | |
a2c02241 NR |
20570 | @subheading The @code{-data-list-register-values} Command |
20571 | @findex -data-list-register-values | |
922fbb7b AC |
20572 | |
20573 | @subsubheading Synopsis | |
20574 | ||
20575 | @smallexample | |
a2c02241 | 20576 | -data-list-register-values @var{fmt} [ ( @var{regno} )*] |
922fbb7b AC |
20577 | @end smallexample |
20578 | ||
a2c02241 NR |
20579 | Display the registers' contents. @var{fmt} is the format according to |
20580 | which the registers' contents are to be returned, followed by an optional | |
20581 | list of numbers specifying the registers to display. A missing list of | |
20582 | numbers indicates that the contents of all the registers must be returned. | |
20583 | ||
20584 | Allowed formats for @var{fmt} are: | |
20585 | ||
20586 | @table @code | |
20587 | @item x | |
20588 | Hexadecimal | |
20589 | @item o | |
20590 | Octal | |
20591 | @item t | |
20592 | Binary | |
20593 | @item d | |
20594 | Decimal | |
20595 | @item r | |
20596 | Raw | |
20597 | @item N | |
20598 | Natural | |
20599 | @end table | |
922fbb7b AC |
20600 | |
20601 | @subsubheading @value{GDBN} Command | |
20602 | ||
a2c02241 NR |
20603 | The corresponding @value{GDBN} commands are @samp{info reg}, @samp{info |
20604 | all-reg}, and (in @code{gdbtk}) @samp{gdb_fetch_registers}. | |
922fbb7b AC |
20605 | |
20606 | @subsubheading Example | |
922fbb7b | 20607 | |
a2c02241 NR |
20608 | For a PPC MBX board (note: line breaks are for readability only, they |
20609 | don't appear in the actual output): | |
20610 | ||
20611 | @smallexample | |
594fe323 | 20612 | (gdb) |
a2c02241 NR |
20613 | -data-list-register-values r 64 65 |
20614 | ^done,register-values=[@{number="64",value="0xfe00a300"@}, | |
20615 | @{number="65",value="0x00029002"@}] | |
594fe323 | 20616 | (gdb) |
a2c02241 NR |
20617 | -data-list-register-values x |
20618 | ^done,register-values=[@{number="0",value="0xfe0043c8"@}, | |
20619 | @{number="1",value="0x3fff88"@},@{number="2",value="0xfffffffe"@}, | |
20620 | @{number="3",value="0x0"@},@{number="4",value="0xa"@}, | |
20621 | @{number="5",value="0x3fff68"@},@{number="6",value="0x3fff58"@}, | |
20622 | @{number="7",value="0xfe011e98"@},@{number="8",value="0x2"@}, | |
20623 | @{number="9",value="0xfa202820"@},@{number="10",value="0xfa202808"@}, | |
20624 | @{number="11",value="0x1"@},@{number="12",value="0x0"@}, | |
20625 | @{number="13",value="0x4544"@},@{number="14",value="0xffdfffff"@}, | |
20626 | @{number="15",value="0xffffffff"@},@{number="16",value="0xfffffeff"@}, | |
20627 | @{number="17",value="0xefffffed"@},@{number="18",value="0xfffffffe"@}, | |
20628 | @{number="19",value="0xffffffff"@},@{number="20",value="0xffffffff"@}, | |
20629 | @{number="21",value="0xffffffff"@},@{number="22",value="0xfffffff7"@}, | |
20630 | @{number="23",value="0xffffffff"@},@{number="24",value="0xffffffff"@}, | |
20631 | @{number="25",value="0xffffffff"@},@{number="26",value="0xfffffffb"@}, | |
20632 | @{number="27",value="0xffffffff"@},@{number="28",value="0xf7bfffff"@}, | |
20633 | @{number="29",value="0x0"@},@{number="30",value="0xfe010000"@}, | |
20634 | @{number="31",value="0x0"@},@{number="32",value="0x0"@}, | |
20635 | @{number="33",value="0x0"@},@{number="34",value="0x0"@}, | |
20636 | @{number="35",value="0x0"@},@{number="36",value="0x0"@}, | |
20637 | @{number="37",value="0x0"@},@{number="38",value="0x0"@}, | |
20638 | @{number="39",value="0x0"@},@{number="40",value="0x0"@}, | |
20639 | @{number="41",value="0x0"@},@{number="42",value="0x0"@}, | |
20640 | @{number="43",value="0x0"@},@{number="44",value="0x0"@}, | |
20641 | @{number="45",value="0x0"@},@{number="46",value="0x0"@}, | |
20642 | @{number="47",value="0x0"@},@{number="48",value="0x0"@}, | |
20643 | @{number="49",value="0x0"@},@{number="50",value="0x0"@}, | |
20644 | @{number="51",value="0x0"@},@{number="52",value="0x0"@}, | |
20645 | @{number="53",value="0x0"@},@{number="54",value="0x0"@}, | |
20646 | @{number="55",value="0x0"@},@{number="56",value="0x0"@}, | |
20647 | @{number="57",value="0x0"@},@{number="58",value="0x0"@}, | |
20648 | @{number="59",value="0x0"@},@{number="60",value="0x0"@}, | |
20649 | @{number="61",value="0x0"@},@{number="62",value="0x0"@}, | |
20650 | @{number="63",value="0x0"@},@{number="64",value="0xfe00a300"@}, | |
20651 | @{number="65",value="0x29002"@},@{number="66",value="0x202f04b5"@}, | |
20652 | @{number="67",value="0xfe0043b0"@},@{number="68",value="0xfe00b3e4"@}, | |
20653 | @{number="69",value="0x20002b03"@}] | |
594fe323 | 20654 | (gdb) |
a2c02241 | 20655 | @end smallexample |
922fbb7b | 20656 | |
a2c02241 NR |
20657 | |
20658 | @subheading The @code{-data-read-memory} Command | |
20659 | @findex -data-read-memory | |
922fbb7b AC |
20660 | |
20661 | @subsubheading Synopsis | |
20662 | ||
20663 | @smallexample | |
a2c02241 NR |
20664 | -data-read-memory [ -o @var{byte-offset} ] |
20665 | @var{address} @var{word-format} @var{word-size} | |
20666 | @var{nr-rows} @var{nr-cols} [ @var{aschar} ] | |
922fbb7b AC |
20667 | @end smallexample |
20668 | ||
a2c02241 NR |
20669 | @noindent |
20670 | where: | |
922fbb7b | 20671 | |
a2c02241 NR |
20672 | @table @samp |
20673 | @item @var{address} | |
20674 | An expression specifying the address of the first memory word to be | |
20675 | read. Complex expressions containing embedded white space should be | |
20676 | quoted using the C convention. | |
922fbb7b | 20677 | |
a2c02241 NR |
20678 | @item @var{word-format} |
20679 | The format to be used to print the memory words. The notation is the | |
20680 | same as for @value{GDBN}'s @code{print} command (@pxref{Output Formats, | |
79a6e687 | 20681 | ,Output Formats}). |
922fbb7b | 20682 | |
a2c02241 NR |
20683 | @item @var{word-size} |
20684 | The size of each memory word in bytes. | |
922fbb7b | 20685 | |
a2c02241 NR |
20686 | @item @var{nr-rows} |
20687 | The number of rows in the output table. | |
922fbb7b | 20688 | |
a2c02241 NR |
20689 | @item @var{nr-cols} |
20690 | The number of columns in the output table. | |
922fbb7b | 20691 | |
a2c02241 NR |
20692 | @item @var{aschar} |
20693 | If present, indicates that each row should include an @sc{ascii} dump. The | |
20694 | value of @var{aschar} is used as a padding character when a byte is not a | |
20695 | member of the printable @sc{ascii} character set (printable @sc{ascii} | |
20696 | characters are those whose code is between 32 and 126, inclusively). | |
922fbb7b | 20697 | |
a2c02241 NR |
20698 | @item @var{byte-offset} |
20699 | An offset to add to the @var{address} before fetching memory. | |
20700 | @end table | |
922fbb7b | 20701 | |
a2c02241 NR |
20702 | This command displays memory contents as a table of @var{nr-rows} by |
20703 | @var{nr-cols} words, each word being @var{word-size} bytes. In total, | |
20704 | @code{@var{nr-rows} * @var{nr-cols} * @var{word-size}} bytes are read | |
20705 | (returned as @samp{total-bytes}). Should less than the requested number | |
20706 | of bytes be returned by the target, the missing words are identified | |
20707 | using @samp{N/A}. The number of bytes read from the target is returned | |
20708 | in @samp{nr-bytes} and the starting address used to read memory in | |
20709 | @samp{addr}. | |
20710 | ||
20711 | The address of the next/previous row or page is available in | |
20712 | @samp{next-row} and @samp{prev-row}, @samp{next-page} and | |
20713 | @samp{prev-page}. | |
922fbb7b AC |
20714 | |
20715 | @subsubheading @value{GDBN} Command | |
20716 | ||
a2c02241 NR |
20717 | The corresponding @value{GDBN} command is @samp{x}. @code{gdbtk} has |
20718 | @samp{gdb_get_mem} memory read command. | |
922fbb7b AC |
20719 | |
20720 | @subsubheading Example | |
32e7087d | 20721 | |
a2c02241 NR |
20722 | Read six bytes of memory starting at @code{bytes+6} but then offset by |
20723 | @code{-6} bytes. Format as three rows of two columns. One byte per | |
20724 | word. Display each word in hex. | |
32e7087d JB |
20725 | |
20726 | @smallexample | |
594fe323 | 20727 | (gdb) |
a2c02241 NR |
20728 | 9-data-read-memory -o -6 -- bytes+6 x 1 3 2 |
20729 | 9^done,addr="0x00001390",nr-bytes="6",total-bytes="6", | |
20730 | next-row="0x00001396",prev-row="0x0000138e",next-page="0x00001396", | |
20731 | prev-page="0x0000138a",memory=[ | |
20732 | @{addr="0x00001390",data=["0x00","0x01"]@}, | |
20733 | @{addr="0x00001392",data=["0x02","0x03"]@}, | |
20734 | @{addr="0x00001394",data=["0x04","0x05"]@}] | |
594fe323 | 20735 | (gdb) |
32e7087d JB |
20736 | @end smallexample |
20737 | ||
a2c02241 NR |
20738 | Read two bytes of memory starting at address @code{shorts + 64} and |
20739 | display as a single word formatted in decimal. | |
32e7087d | 20740 | |
32e7087d | 20741 | @smallexample |
594fe323 | 20742 | (gdb) |
a2c02241 NR |
20743 | 5-data-read-memory shorts+64 d 2 1 1 |
20744 | 5^done,addr="0x00001510",nr-bytes="2",total-bytes="2", | |
20745 | next-row="0x00001512",prev-row="0x0000150e", | |
20746 | next-page="0x00001512",prev-page="0x0000150e",memory=[ | |
20747 | @{addr="0x00001510",data=["128"]@}] | |
594fe323 | 20748 | (gdb) |
32e7087d JB |
20749 | @end smallexample |
20750 | ||
a2c02241 NR |
20751 | Read thirty two bytes of memory starting at @code{bytes+16} and format |
20752 | as eight rows of four columns. Include a string encoding with @samp{x} | |
20753 | used as the non-printable character. | |
922fbb7b AC |
20754 | |
20755 | @smallexample | |
594fe323 | 20756 | (gdb) |
a2c02241 NR |
20757 | 4-data-read-memory bytes+16 x 1 8 4 x |
20758 | 4^done,addr="0x000013a0",nr-bytes="32",total-bytes="32", | |
20759 | next-row="0x000013c0",prev-row="0x0000139c", | |
20760 | next-page="0x000013c0",prev-page="0x00001380",memory=[ | |
20761 | @{addr="0x000013a0",data=["0x10","0x11","0x12","0x13"],ascii="xxxx"@}, | |
20762 | @{addr="0x000013a4",data=["0x14","0x15","0x16","0x17"],ascii="xxxx"@}, | |
20763 | @{addr="0x000013a8",data=["0x18","0x19","0x1a","0x1b"],ascii="xxxx"@}, | |
20764 | @{addr="0x000013ac",data=["0x1c","0x1d","0x1e","0x1f"],ascii="xxxx"@}, | |
20765 | @{addr="0x000013b0",data=["0x20","0x21","0x22","0x23"],ascii=" !\"#"@}, | |
20766 | @{addr="0x000013b4",data=["0x24","0x25","0x26","0x27"],ascii="$%&'"@}, | |
20767 | @{addr="0x000013b8",data=["0x28","0x29","0x2a","0x2b"],ascii="()*+"@}, | |
20768 | @{addr="0x000013bc",data=["0x2c","0x2d","0x2e","0x2f"],ascii=",-./"@}] | |
594fe323 | 20769 | (gdb) |
922fbb7b AC |
20770 | @end smallexample |
20771 | ||
a2c02241 NR |
20772 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
20773 | @node GDB/MI Tracepoint Commands | |
20774 | @section @sc{gdb/mi} Tracepoint Commands | |
922fbb7b | 20775 | |
a2c02241 | 20776 | The tracepoint commands are not yet implemented. |
922fbb7b | 20777 | |
a2c02241 | 20778 | @c @subheading -trace-actions |
922fbb7b | 20779 | |
a2c02241 | 20780 | @c @subheading -trace-delete |
922fbb7b | 20781 | |
a2c02241 | 20782 | @c @subheading -trace-disable |
922fbb7b | 20783 | |
a2c02241 | 20784 | @c @subheading -trace-dump |
922fbb7b | 20785 | |
a2c02241 | 20786 | @c @subheading -trace-enable |
922fbb7b | 20787 | |
a2c02241 | 20788 | @c @subheading -trace-exists |
922fbb7b | 20789 | |
a2c02241 | 20790 | @c @subheading -trace-find |
922fbb7b | 20791 | |
a2c02241 | 20792 | @c @subheading -trace-frame-number |
922fbb7b | 20793 | |
a2c02241 | 20794 | @c @subheading -trace-info |
922fbb7b | 20795 | |
a2c02241 | 20796 | @c @subheading -trace-insert |
922fbb7b | 20797 | |
a2c02241 | 20798 | @c @subheading -trace-list |
922fbb7b | 20799 | |
a2c02241 | 20800 | @c @subheading -trace-pass-count |
922fbb7b | 20801 | |
a2c02241 | 20802 | @c @subheading -trace-save |
922fbb7b | 20803 | |
a2c02241 | 20804 | @c @subheading -trace-start |
922fbb7b | 20805 | |
a2c02241 | 20806 | @c @subheading -trace-stop |
922fbb7b | 20807 | |
922fbb7b | 20808 | |
a2c02241 NR |
20809 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
20810 | @node GDB/MI Symbol Query | |
20811 | @section @sc{gdb/mi} Symbol Query Commands | |
922fbb7b AC |
20812 | |
20813 | ||
a2c02241 NR |
20814 | @subheading The @code{-symbol-info-address} Command |
20815 | @findex -symbol-info-address | |
922fbb7b AC |
20816 | |
20817 | @subsubheading Synopsis | |
20818 | ||
20819 | @smallexample | |
a2c02241 | 20820 | -symbol-info-address @var{symbol} |
922fbb7b AC |
20821 | @end smallexample |
20822 | ||
a2c02241 | 20823 | Describe where @var{symbol} is stored. |
922fbb7b AC |
20824 | |
20825 | @subsubheading @value{GDBN} Command | |
20826 | ||
a2c02241 | 20827 | The corresponding @value{GDBN} command is @samp{info address}. |
922fbb7b AC |
20828 | |
20829 | @subsubheading Example | |
20830 | N.A. | |
20831 | ||
20832 | ||
a2c02241 NR |
20833 | @subheading The @code{-symbol-info-file} Command |
20834 | @findex -symbol-info-file | |
922fbb7b AC |
20835 | |
20836 | @subsubheading Synopsis | |
20837 | ||
20838 | @smallexample | |
a2c02241 | 20839 | -symbol-info-file |
922fbb7b AC |
20840 | @end smallexample |
20841 | ||
a2c02241 | 20842 | Show the file for the symbol. |
922fbb7b | 20843 | |
a2c02241 | 20844 | @subsubheading @value{GDBN} Command |
922fbb7b | 20845 | |
a2c02241 NR |
20846 | There's no equivalent @value{GDBN} command. @code{gdbtk} has |
20847 | @samp{gdb_find_file}. | |
922fbb7b AC |
20848 | |
20849 | @subsubheading Example | |
20850 | N.A. | |
20851 | ||
20852 | ||
a2c02241 NR |
20853 | @subheading The @code{-symbol-info-function} Command |
20854 | @findex -symbol-info-function | |
922fbb7b AC |
20855 | |
20856 | @subsubheading Synopsis | |
20857 | ||
20858 | @smallexample | |
a2c02241 | 20859 | -symbol-info-function |
922fbb7b AC |
20860 | @end smallexample |
20861 | ||
a2c02241 | 20862 | Show which function the symbol lives in. |
922fbb7b AC |
20863 | |
20864 | @subsubheading @value{GDBN} Command | |
20865 | ||
a2c02241 | 20866 | @samp{gdb_get_function} in @code{gdbtk}. |
922fbb7b AC |
20867 | |
20868 | @subsubheading Example | |
20869 | N.A. | |
20870 | ||
20871 | ||
a2c02241 NR |
20872 | @subheading The @code{-symbol-info-line} Command |
20873 | @findex -symbol-info-line | |
922fbb7b AC |
20874 | |
20875 | @subsubheading Synopsis | |
20876 | ||
20877 | @smallexample | |
a2c02241 | 20878 | -symbol-info-line |
922fbb7b AC |
20879 | @end smallexample |
20880 | ||
a2c02241 | 20881 | Show the core addresses of the code for a source line. |
922fbb7b | 20882 | |
a2c02241 | 20883 | @subsubheading @value{GDBN} Command |
922fbb7b | 20884 | |
a2c02241 NR |
20885 | The corresponding @value{GDBN} command is @samp{info line}. |
20886 | @code{gdbtk} has the @samp{gdb_get_line} and @samp{gdb_get_file} commands. | |
922fbb7b AC |
20887 | |
20888 | @subsubheading Example | |
a2c02241 | 20889 | N.A. |
922fbb7b AC |
20890 | |
20891 | ||
a2c02241 NR |
20892 | @subheading The @code{-symbol-info-symbol} Command |
20893 | @findex -symbol-info-symbol | |
07f31aa6 DJ |
20894 | |
20895 | @subsubheading Synopsis | |
20896 | ||
a2c02241 NR |
20897 | @smallexample |
20898 | -symbol-info-symbol @var{addr} | |
20899 | @end smallexample | |
07f31aa6 | 20900 | |
a2c02241 | 20901 | Describe what symbol is at location @var{addr}. |
07f31aa6 | 20902 | |
a2c02241 | 20903 | @subsubheading @value{GDBN} Command |
07f31aa6 | 20904 | |
a2c02241 | 20905 | The corresponding @value{GDBN} command is @samp{info symbol}. |
07f31aa6 DJ |
20906 | |
20907 | @subsubheading Example | |
a2c02241 | 20908 | N.A. |
07f31aa6 DJ |
20909 | |
20910 | ||
a2c02241 NR |
20911 | @subheading The @code{-symbol-list-functions} Command |
20912 | @findex -symbol-list-functions | |
922fbb7b AC |
20913 | |
20914 | @subsubheading Synopsis | |
20915 | ||
20916 | @smallexample | |
a2c02241 | 20917 | -symbol-list-functions |
922fbb7b AC |
20918 | @end smallexample |
20919 | ||
a2c02241 | 20920 | List the functions in the executable. |
922fbb7b AC |
20921 | |
20922 | @subsubheading @value{GDBN} Command | |
20923 | ||
a2c02241 NR |
20924 | @samp{info functions} in @value{GDBN}, @samp{gdb_listfunc} and |
20925 | @samp{gdb_search} in @code{gdbtk}. | |
922fbb7b AC |
20926 | |
20927 | @subsubheading Example | |
a2c02241 | 20928 | N.A. |
922fbb7b AC |
20929 | |
20930 | ||
a2c02241 NR |
20931 | @subheading The @code{-symbol-list-lines} Command |
20932 | @findex -symbol-list-lines | |
922fbb7b AC |
20933 | |
20934 | @subsubheading Synopsis | |
20935 | ||
20936 | @smallexample | |
a2c02241 | 20937 | -symbol-list-lines @var{filename} |
922fbb7b AC |
20938 | @end smallexample |
20939 | ||
a2c02241 NR |
20940 | Print the list of lines that contain code and their associated program |
20941 | addresses for the given source filename. The entries are sorted in | |
20942 | ascending PC order. | |
922fbb7b AC |
20943 | |
20944 | @subsubheading @value{GDBN} Command | |
20945 | ||
a2c02241 | 20946 | There is no corresponding @value{GDBN} command. |
922fbb7b AC |
20947 | |
20948 | @subsubheading Example | |
a2c02241 | 20949 | @smallexample |
594fe323 | 20950 | (gdb) |
a2c02241 NR |
20951 | -symbol-list-lines basics.c |
20952 | ^done,lines=[@{pc="0x08048554",line="7"@},@{pc="0x0804855a",line="8"@}] | |
594fe323 | 20953 | (gdb) |
a2c02241 | 20954 | @end smallexample |
922fbb7b AC |
20955 | |
20956 | ||
a2c02241 NR |
20957 | @subheading The @code{-symbol-list-types} Command |
20958 | @findex -symbol-list-types | |
922fbb7b AC |
20959 | |
20960 | @subsubheading Synopsis | |
20961 | ||
20962 | @smallexample | |
a2c02241 | 20963 | -symbol-list-types |
922fbb7b AC |
20964 | @end smallexample |
20965 | ||
a2c02241 | 20966 | List all the type names. |
922fbb7b AC |
20967 | |
20968 | @subsubheading @value{GDBN} Command | |
20969 | ||
a2c02241 NR |
20970 | The corresponding commands are @samp{info types} in @value{GDBN}, |
20971 | @samp{gdb_search} in @code{gdbtk}. | |
922fbb7b AC |
20972 | |
20973 | @subsubheading Example | |
20974 | N.A. | |
20975 | ||
20976 | ||
a2c02241 NR |
20977 | @subheading The @code{-symbol-list-variables} Command |
20978 | @findex -symbol-list-variables | |
922fbb7b AC |
20979 | |
20980 | @subsubheading Synopsis | |
20981 | ||
20982 | @smallexample | |
a2c02241 | 20983 | -symbol-list-variables |
922fbb7b AC |
20984 | @end smallexample |
20985 | ||
a2c02241 | 20986 | List all the global and static variable names. |
922fbb7b AC |
20987 | |
20988 | @subsubheading @value{GDBN} Command | |
20989 | ||
a2c02241 | 20990 | @samp{info variables} in @value{GDBN}, @samp{gdb_search} in @code{gdbtk}. |
922fbb7b AC |
20991 | |
20992 | @subsubheading Example | |
20993 | N.A. | |
20994 | ||
20995 | ||
a2c02241 NR |
20996 | @subheading The @code{-symbol-locate} Command |
20997 | @findex -symbol-locate | |
922fbb7b AC |
20998 | |
20999 | @subsubheading Synopsis | |
21000 | ||
21001 | @smallexample | |
a2c02241 | 21002 | -symbol-locate |
922fbb7b AC |
21003 | @end smallexample |
21004 | ||
922fbb7b AC |
21005 | @subsubheading @value{GDBN} Command |
21006 | ||
a2c02241 | 21007 | @samp{gdb_loc} in @code{gdbtk}. |
922fbb7b AC |
21008 | |
21009 | @subsubheading Example | |
21010 | N.A. | |
21011 | ||
21012 | ||
a2c02241 NR |
21013 | @subheading The @code{-symbol-type} Command |
21014 | @findex -symbol-type | |
922fbb7b AC |
21015 | |
21016 | @subsubheading Synopsis | |
21017 | ||
21018 | @smallexample | |
a2c02241 | 21019 | -symbol-type @var{variable} |
922fbb7b AC |
21020 | @end smallexample |
21021 | ||
a2c02241 | 21022 | Show type of @var{variable}. |
922fbb7b | 21023 | |
a2c02241 | 21024 | @subsubheading @value{GDBN} Command |
922fbb7b | 21025 | |
a2c02241 NR |
21026 | The corresponding @value{GDBN} command is @samp{ptype}, @code{gdbtk} has |
21027 | @samp{gdb_obj_variable}. | |
21028 | ||
21029 | @subsubheading Example | |
21030 | N.A. | |
21031 | ||
21032 | ||
21033 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
21034 | @node GDB/MI File Commands | |
21035 | @section @sc{gdb/mi} File Commands | |
21036 | ||
21037 | This section describes the GDB/MI commands to specify executable file names | |
21038 | and to read in and obtain symbol table information. | |
21039 | ||
21040 | @subheading The @code{-file-exec-and-symbols} Command | |
21041 | @findex -file-exec-and-symbols | |
21042 | ||
21043 | @subsubheading Synopsis | |
922fbb7b AC |
21044 | |
21045 | @smallexample | |
a2c02241 | 21046 | -file-exec-and-symbols @var{file} |
922fbb7b AC |
21047 | @end smallexample |
21048 | ||
a2c02241 NR |
21049 | Specify the executable file to be debugged. This file is the one from |
21050 | which the symbol table is also read. If no file is specified, the | |
21051 | command clears the executable and symbol information. If breakpoints | |
21052 | are set when using this command with no arguments, @value{GDBN} will produce | |
21053 | error messages. Otherwise, no output is produced, except a completion | |
21054 | notification. | |
21055 | ||
922fbb7b AC |
21056 | @subsubheading @value{GDBN} Command |
21057 | ||
a2c02241 | 21058 | The corresponding @value{GDBN} command is @samp{file}. |
922fbb7b AC |
21059 | |
21060 | @subsubheading Example | |
21061 | ||
21062 | @smallexample | |
594fe323 | 21063 | (gdb) |
a2c02241 NR |
21064 | -file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
21065 | ^done | |
594fe323 | 21066 | (gdb) |
922fbb7b AC |
21067 | @end smallexample |
21068 | ||
922fbb7b | 21069 | |
a2c02241 NR |
21070 | @subheading The @code{-file-exec-file} Command |
21071 | @findex -file-exec-file | |
922fbb7b AC |
21072 | |
21073 | @subsubheading Synopsis | |
21074 | ||
21075 | @smallexample | |
a2c02241 | 21076 | -file-exec-file @var{file} |
922fbb7b AC |
21077 | @end smallexample |
21078 | ||
a2c02241 NR |
21079 | Specify the executable file to be debugged. Unlike |
21080 | @samp{-file-exec-and-symbols}, the symbol table is @emph{not} read | |
21081 | from this file. If used without argument, @value{GDBN} clears the information | |
21082 | about the executable file. No output is produced, except a completion | |
21083 | notification. | |
922fbb7b | 21084 | |
a2c02241 NR |
21085 | @subsubheading @value{GDBN} Command |
21086 | ||
21087 | The corresponding @value{GDBN} command is @samp{exec-file}. | |
922fbb7b AC |
21088 | |
21089 | @subsubheading Example | |
a2c02241 NR |
21090 | |
21091 | @smallexample | |
594fe323 | 21092 | (gdb) |
a2c02241 NR |
21093 | -file-exec-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
21094 | ^done | |
594fe323 | 21095 | (gdb) |
a2c02241 | 21096 | @end smallexample |
922fbb7b AC |
21097 | |
21098 | ||
a2c02241 NR |
21099 | @subheading The @code{-file-list-exec-sections} Command |
21100 | @findex -file-list-exec-sections | |
922fbb7b AC |
21101 | |
21102 | @subsubheading Synopsis | |
21103 | ||
21104 | @smallexample | |
a2c02241 | 21105 | -file-list-exec-sections |
922fbb7b AC |
21106 | @end smallexample |
21107 | ||
a2c02241 NR |
21108 | List the sections of the current executable file. |
21109 | ||
922fbb7b AC |
21110 | @subsubheading @value{GDBN} Command |
21111 | ||
a2c02241 NR |
21112 | The @value{GDBN} command @samp{info file} shows, among the rest, the same |
21113 | information as this command. @code{gdbtk} has a corresponding command | |
21114 | @samp{gdb_load_info}. | |
922fbb7b AC |
21115 | |
21116 | @subsubheading Example | |
21117 | N.A. | |
21118 | ||
21119 | ||
a2c02241 NR |
21120 | @subheading The @code{-file-list-exec-source-file} Command |
21121 | @findex -file-list-exec-source-file | |
922fbb7b AC |
21122 | |
21123 | @subsubheading Synopsis | |
21124 | ||
21125 | @smallexample | |
a2c02241 | 21126 | -file-list-exec-source-file |
922fbb7b AC |
21127 | @end smallexample |
21128 | ||
a2c02241 | 21129 | List the line number, the current source file, and the absolute path |
44288b44 NR |
21130 | to the current source file for the current executable. The macro |
21131 | information field has a value of @samp{1} or @samp{0} depending on | |
21132 | whether or not the file includes preprocessor macro information. | |
922fbb7b AC |
21133 | |
21134 | @subsubheading @value{GDBN} Command | |
21135 | ||
a2c02241 | 21136 | The @value{GDBN} equivalent is @samp{info source} |
922fbb7b AC |
21137 | |
21138 | @subsubheading Example | |
21139 | ||
922fbb7b | 21140 | @smallexample |
594fe323 | 21141 | (gdb) |
a2c02241 | 21142 | 123-file-list-exec-source-file |
44288b44 | 21143 | 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c,macro-info="1" |
594fe323 | 21144 | (gdb) |
922fbb7b AC |
21145 | @end smallexample |
21146 | ||
21147 | ||
a2c02241 NR |
21148 | @subheading The @code{-file-list-exec-source-files} Command |
21149 | @findex -file-list-exec-source-files | |
922fbb7b AC |
21150 | |
21151 | @subsubheading Synopsis | |
21152 | ||
21153 | @smallexample | |
a2c02241 | 21154 | -file-list-exec-source-files |
922fbb7b AC |
21155 | @end smallexample |
21156 | ||
a2c02241 NR |
21157 | List the source files for the current executable. |
21158 | ||
3f94c067 BW |
21159 | It will always output the filename, but only when @value{GDBN} can find |
21160 | the absolute file name of a source file, will it output the fullname. | |
922fbb7b AC |
21161 | |
21162 | @subsubheading @value{GDBN} Command | |
21163 | ||
a2c02241 NR |
21164 | The @value{GDBN} equivalent is @samp{info sources}. |
21165 | @code{gdbtk} has an analogous command @samp{gdb_listfiles}. | |
922fbb7b AC |
21166 | |
21167 | @subsubheading Example | |
922fbb7b | 21168 | @smallexample |
594fe323 | 21169 | (gdb) |
a2c02241 NR |
21170 | -file-list-exec-source-files |
21171 | ^done,files=[ | |
21172 | @{file=foo.c,fullname=/home/foo.c@}, | |
21173 | @{file=/home/bar.c,fullname=/home/bar.c@}, | |
21174 | @{file=gdb_could_not_find_fullpath.c@}] | |
594fe323 | 21175 | (gdb) |
922fbb7b AC |
21176 | @end smallexample |
21177 | ||
a2c02241 NR |
21178 | @subheading The @code{-file-list-shared-libraries} Command |
21179 | @findex -file-list-shared-libraries | |
922fbb7b | 21180 | |
a2c02241 | 21181 | @subsubheading Synopsis |
922fbb7b | 21182 | |
a2c02241 NR |
21183 | @smallexample |
21184 | -file-list-shared-libraries | |
21185 | @end smallexample | |
922fbb7b | 21186 | |
a2c02241 | 21187 | List the shared libraries in the program. |
922fbb7b | 21188 | |
a2c02241 | 21189 | @subsubheading @value{GDBN} Command |
922fbb7b | 21190 | |
a2c02241 | 21191 | The corresponding @value{GDBN} command is @samp{info shared}. |
922fbb7b | 21192 | |
a2c02241 NR |
21193 | @subsubheading Example |
21194 | N.A. | |
922fbb7b AC |
21195 | |
21196 | ||
a2c02241 NR |
21197 | @subheading The @code{-file-list-symbol-files} Command |
21198 | @findex -file-list-symbol-files | |
922fbb7b | 21199 | |
a2c02241 | 21200 | @subsubheading Synopsis |
922fbb7b | 21201 | |
a2c02241 NR |
21202 | @smallexample |
21203 | -file-list-symbol-files | |
21204 | @end smallexample | |
922fbb7b | 21205 | |
a2c02241 | 21206 | List symbol files. |
922fbb7b | 21207 | |
a2c02241 | 21208 | @subsubheading @value{GDBN} Command |
922fbb7b | 21209 | |
a2c02241 | 21210 | The corresponding @value{GDBN} command is @samp{info file} (part of it). |
922fbb7b | 21211 | |
a2c02241 NR |
21212 | @subsubheading Example |
21213 | N.A. | |
922fbb7b | 21214 | |
922fbb7b | 21215 | |
a2c02241 NR |
21216 | @subheading The @code{-file-symbol-file} Command |
21217 | @findex -file-symbol-file | |
922fbb7b | 21218 | |
a2c02241 | 21219 | @subsubheading Synopsis |
922fbb7b | 21220 | |
a2c02241 NR |
21221 | @smallexample |
21222 | -file-symbol-file @var{file} | |
21223 | @end smallexample | |
922fbb7b | 21224 | |
a2c02241 NR |
21225 | Read symbol table info from the specified @var{file} argument. When |
21226 | used without arguments, clears @value{GDBN}'s symbol table info. No output is | |
21227 | produced, except for a completion notification. | |
922fbb7b | 21228 | |
a2c02241 | 21229 | @subsubheading @value{GDBN} Command |
922fbb7b | 21230 | |
a2c02241 | 21231 | The corresponding @value{GDBN} command is @samp{symbol-file}. |
922fbb7b | 21232 | |
a2c02241 | 21233 | @subsubheading Example |
922fbb7b | 21234 | |
a2c02241 | 21235 | @smallexample |
594fe323 | 21236 | (gdb) |
a2c02241 NR |
21237 | -file-symbol-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
21238 | ^done | |
594fe323 | 21239 | (gdb) |
a2c02241 | 21240 | @end smallexample |
922fbb7b | 21241 | |
a2c02241 | 21242 | @ignore |
a2c02241 NR |
21243 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21244 | @node GDB/MI Memory Overlay Commands | |
21245 | @section @sc{gdb/mi} Memory Overlay Commands | |
922fbb7b | 21246 | |
a2c02241 | 21247 | The memory overlay commands are not implemented. |
922fbb7b | 21248 | |
a2c02241 | 21249 | @c @subheading -overlay-auto |
922fbb7b | 21250 | |
a2c02241 | 21251 | @c @subheading -overlay-list-mapping-state |
922fbb7b | 21252 | |
a2c02241 | 21253 | @c @subheading -overlay-list-overlays |
922fbb7b | 21254 | |
a2c02241 | 21255 | @c @subheading -overlay-map |
922fbb7b | 21256 | |
a2c02241 | 21257 | @c @subheading -overlay-off |
922fbb7b | 21258 | |
a2c02241 | 21259 | @c @subheading -overlay-on |
922fbb7b | 21260 | |
a2c02241 | 21261 | @c @subheading -overlay-unmap |
922fbb7b | 21262 | |
a2c02241 NR |
21263 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21264 | @node GDB/MI Signal Handling Commands | |
21265 | @section @sc{gdb/mi} Signal Handling Commands | |
922fbb7b | 21266 | |
a2c02241 | 21267 | Signal handling commands are not implemented. |
922fbb7b | 21268 | |
a2c02241 | 21269 | @c @subheading -signal-handle |
922fbb7b | 21270 | |
a2c02241 | 21271 | @c @subheading -signal-list-handle-actions |
922fbb7b | 21272 | |
a2c02241 NR |
21273 | @c @subheading -signal-list-signal-types |
21274 | @end ignore | |
922fbb7b | 21275 | |
922fbb7b | 21276 | |
a2c02241 NR |
21277 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21278 | @node GDB/MI Target Manipulation | |
21279 | @section @sc{gdb/mi} Target Manipulation Commands | |
922fbb7b AC |
21280 | |
21281 | ||
a2c02241 NR |
21282 | @subheading The @code{-target-attach} Command |
21283 | @findex -target-attach | |
922fbb7b AC |
21284 | |
21285 | @subsubheading Synopsis | |
21286 | ||
21287 | @smallexample | |
a2c02241 | 21288 | -target-attach @var{pid} | @var{file} |
922fbb7b AC |
21289 | @end smallexample |
21290 | ||
a2c02241 | 21291 | Attach to a process @var{pid} or a file @var{file} outside of @value{GDBN}. |
922fbb7b | 21292 | |
79a6e687 | 21293 | @subsubheading @value{GDBN} Command |
922fbb7b | 21294 | |
a2c02241 | 21295 | The corresponding @value{GDBN} command is @samp{attach}. |
922fbb7b | 21296 | |
a2c02241 NR |
21297 | @subsubheading Example |
21298 | N.A. | |
922fbb7b | 21299 | |
a2c02241 NR |
21300 | |
21301 | @subheading The @code{-target-compare-sections} Command | |
21302 | @findex -target-compare-sections | |
922fbb7b AC |
21303 | |
21304 | @subsubheading Synopsis | |
21305 | ||
21306 | @smallexample | |
a2c02241 | 21307 | -target-compare-sections [ @var{section} ] |
922fbb7b AC |
21308 | @end smallexample |
21309 | ||
a2c02241 NR |
21310 | Compare data of section @var{section} on target to the exec file. |
21311 | Without the argument, all sections are compared. | |
922fbb7b | 21312 | |
a2c02241 | 21313 | @subsubheading @value{GDBN} Command |
922fbb7b | 21314 | |
a2c02241 | 21315 | The @value{GDBN} equivalent is @samp{compare-sections}. |
922fbb7b | 21316 | |
a2c02241 NR |
21317 | @subsubheading Example |
21318 | N.A. | |
21319 | ||
21320 | ||
21321 | @subheading The @code{-target-detach} Command | |
21322 | @findex -target-detach | |
922fbb7b AC |
21323 | |
21324 | @subsubheading Synopsis | |
21325 | ||
21326 | @smallexample | |
a2c02241 | 21327 | -target-detach |
922fbb7b AC |
21328 | @end smallexample |
21329 | ||
a2c02241 NR |
21330 | Detach from the remote target which normally resumes its execution. |
21331 | There's no output. | |
21332 | ||
79a6e687 | 21333 | @subsubheading @value{GDBN} Command |
a2c02241 NR |
21334 | |
21335 | The corresponding @value{GDBN} command is @samp{detach}. | |
21336 | ||
21337 | @subsubheading Example | |
922fbb7b AC |
21338 | |
21339 | @smallexample | |
594fe323 | 21340 | (gdb) |
a2c02241 NR |
21341 | -target-detach |
21342 | ^done | |
594fe323 | 21343 | (gdb) |
922fbb7b AC |
21344 | @end smallexample |
21345 | ||
21346 | ||
a2c02241 NR |
21347 | @subheading The @code{-target-disconnect} Command |
21348 | @findex -target-disconnect | |
922fbb7b AC |
21349 | |
21350 | @subsubheading Synopsis | |
21351 | ||
123dc839 | 21352 | @smallexample |
a2c02241 | 21353 | -target-disconnect |
123dc839 | 21354 | @end smallexample |
922fbb7b | 21355 | |
a2c02241 NR |
21356 | Disconnect from the remote target. There's no output and the target is |
21357 | generally not resumed. | |
21358 | ||
79a6e687 | 21359 | @subsubheading @value{GDBN} Command |
a2c02241 NR |
21360 | |
21361 | The corresponding @value{GDBN} command is @samp{disconnect}. | |
bc8ced35 NR |
21362 | |
21363 | @subsubheading Example | |
922fbb7b AC |
21364 | |
21365 | @smallexample | |
594fe323 | 21366 | (gdb) |
a2c02241 NR |
21367 | -target-disconnect |
21368 | ^done | |
594fe323 | 21369 | (gdb) |
922fbb7b AC |
21370 | @end smallexample |
21371 | ||
21372 | ||
a2c02241 NR |
21373 | @subheading The @code{-target-download} Command |
21374 | @findex -target-download | |
922fbb7b AC |
21375 | |
21376 | @subsubheading Synopsis | |
21377 | ||
21378 | @smallexample | |
a2c02241 | 21379 | -target-download |
922fbb7b AC |
21380 | @end smallexample |
21381 | ||
a2c02241 NR |
21382 | Loads the executable onto the remote target. |
21383 | It prints out an update message every half second, which includes the fields: | |
21384 | ||
21385 | @table @samp | |
21386 | @item section | |
21387 | The name of the section. | |
21388 | @item section-sent | |
21389 | The size of what has been sent so far for that section. | |
21390 | @item section-size | |
21391 | The size of the section. | |
21392 | @item total-sent | |
21393 | The total size of what was sent so far (the current and the previous sections). | |
21394 | @item total-size | |
21395 | The size of the overall executable to download. | |
21396 | @end table | |
21397 | ||
21398 | @noindent | |
21399 | Each message is sent as status record (@pxref{GDB/MI Output Syntax, , | |
21400 | @sc{gdb/mi} Output Syntax}). | |
21401 | ||
21402 | In addition, it prints the name and size of the sections, as they are | |
21403 | downloaded. These messages include the following fields: | |
21404 | ||
21405 | @table @samp | |
21406 | @item section | |
21407 | The name of the section. | |
21408 | @item section-size | |
21409 | The size of the section. | |
21410 | @item total-size | |
21411 | The size of the overall executable to download. | |
21412 | @end table | |
21413 | ||
21414 | @noindent | |
21415 | At the end, a summary is printed. | |
21416 | ||
21417 | @subsubheading @value{GDBN} Command | |
21418 | ||
21419 | The corresponding @value{GDBN} command is @samp{load}. | |
21420 | ||
21421 | @subsubheading Example | |
21422 | ||
21423 | Note: each status message appears on a single line. Here the messages | |
21424 | have been broken down so that they can fit onto a page. | |
922fbb7b AC |
21425 | |
21426 | @smallexample | |
594fe323 | 21427 | (gdb) |
a2c02241 NR |
21428 | -target-download |
21429 | +download,@{section=".text",section-size="6668",total-size="9880"@} | |
21430 | +download,@{section=".text",section-sent="512",section-size="6668", | |
21431 | total-sent="512",total-size="9880"@} | |
21432 | +download,@{section=".text",section-sent="1024",section-size="6668", | |
21433 | total-sent="1024",total-size="9880"@} | |
21434 | +download,@{section=".text",section-sent="1536",section-size="6668", | |
21435 | total-sent="1536",total-size="9880"@} | |
21436 | +download,@{section=".text",section-sent="2048",section-size="6668", | |
21437 | total-sent="2048",total-size="9880"@} | |
21438 | +download,@{section=".text",section-sent="2560",section-size="6668", | |
21439 | total-sent="2560",total-size="9880"@} | |
21440 | +download,@{section=".text",section-sent="3072",section-size="6668", | |
21441 | total-sent="3072",total-size="9880"@} | |
21442 | +download,@{section=".text",section-sent="3584",section-size="6668", | |
21443 | total-sent="3584",total-size="9880"@} | |
21444 | +download,@{section=".text",section-sent="4096",section-size="6668", | |
21445 | total-sent="4096",total-size="9880"@} | |
21446 | +download,@{section=".text",section-sent="4608",section-size="6668", | |
21447 | total-sent="4608",total-size="9880"@} | |
21448 | +download,@{section=".text",section-sent="5120",section-size="6668", | |
21449 | total-sent="5120",total-size="9880"@} | |
21450 | +download,@{section=".text",section-sent="5632",section-size="6668", | |
21451 | total-sent="5632",total-size="9880"@} | |
21452 | +download,@{section=".text",section-sent="6144",section-size="6668", | |
21453 | total-sent="6144",total-size="9880"@} | |
21454 | +download,@{section=".text",section-sent="6656",section-size="6668", | |
21455 | total-sent="6656",total-size="9880"@} | |
21456 | +download,@{section=".init",section-size="28",total-size="9880"@} | |
21457 | +download,@{section=".fini",section-size="28",total-size="9880"@} | |
21458 | +download,@{section=".data",section-size="3156",total-size="9880"@} | |
21459 | +download,@{section=".data",section-sent="512",section-size="3156", | |
21460 | total-sent="7236",total-size="9880"@} | |
21461 | +download,@{section=".data",section-sent="1024",section-size="3156", | |
21462 | total-sent="7748",total-size="9880"@} | |
21463 | +download,@{section=".data",section-sent="1536",section-size="3156", | |
21464 | total-sent="8260",total-size="9880"@} | |
21465 | +download,@{section=".data",section-sent="2048",section-size="3156", | |
21466 | total-sent="8772",total-size="9880"@} | |
21467 | +download,@{section=".data",section-sent="2560",section-size="3156", | |
21468 | total-sent="9284",total-size="9880"@} | |
21469 | +download,@{section=".data",section-sent="3072",section-size="3156", | |
21470 | total-sent="9796",total-size="9880"@} | |
21471 | ^done,address="0x10004",load-size="9880",transfer-rate="6586", | |
21472 | write-rate="429" | |
594fe323 | 21473 | (gdb) |
922fbb7b AC |
21474 | @end smallexample |
21475 | ||
21476 | ||
a2c02241 NR |
21477 | @subheading The @code{-target-exec-status} Command |
21478 | @findex -target-exec-status | |
922fbb7b AC |
21479 | |
21480 | @subsubheading Synopsis | |
21481 | ||
21482 | @smallexample | |
a2c02241 | 21483 | -target-exec-status |
922fbb7b AC |
21484 | @end smallexample |
21485 | ||
a2c02241 NR |
21486 | Provide information on the state of the target (whether it is running or |
21487 | not, for instance). | |
922fbb7b | 21488 | |
a2c02241 | 21489 | @subsubheading @value{GDBN} Command |
922fbb7b | 21490 | |
a2c02241 NR |
21491 | There's no equivalent @value{GDBN} command. |
21492 | ||
21493 | @subsubheading Example | |
21494 | N.A. | |
922fbb7b | 21495 | |
a2c02241 NR |
21496 | |
21497 | @subheading The @code{-target-list-available-targets} Command | |
21498 | @findex -target-list-available-targets | |
922fbb7b AC |
21499 | |
21500 | @subsubheading Synopsis | |
21501 | ||
21502 | @smallexample | |
a2c02241 | 21503 | -target-list-available-targets |
922fbb7b AC |
21504 | @end smallexample |
21505 | ||
a2c02241 | 21506 | List the possible targets to connect to. |
922fbb7b | 21507 | |
a2c02241 | 21508 | @subsubheading @value{GDBN} Command |
922fbb7b | 21509 | |
a2c02241 | 21510 | The corresponding @value{GDBN} command is @samp{help target}. |
922fbb7b | 21511 | |
a2c02241 NR |
21512 | @subsubheading Example |
21513 | N.A. | |
21514 | ||
21515 | ||
21516 | @subheading The @code{-target-list-current-targets} Command | |
21517 | @findex -target-list-current-targets | |
922fbb7b AC |
21518 | |
21519 | @subsubheading Synopsis | |
21520 | ||
21521 | @smallexample | |
a2c02241 | 21522 | -target-list-current-targets |
922fbb7b AC |
21523 | @end smallexample |
21524 | ||
a2c02241 | 21525 | Describe the current target. |
922fbb7b | 21526 | |
a2c02241 | 21527 | @subsubheading @value{GDBN} Command |
922fbb7b | 21528 | |
a2c02241 NR |
21529 | The corresponding information is printed by @samp{info file} (among |
21530 | other things). | |
922fbb7b | 21531 | |
a2c02241 NR |
21532 | @subsubheading Example |
21533 | N.A. | |
21534 | ||
21535 | ||
21536 | @subheading The @code{-target-list-parameters} Command | |
21537 | @findex -target-list-parameters | |
922fbb7b AC |
21538 | |
21539 | @subsubheading Synopsis | |
21540 | ||
21541 | @smallexample | |
a2c02241 | 21542 | -target-list-parameters |
922fbb7b AC |
21543 | @end smallexample |
21544 | ||
a2c02241 NR |
21545 | @c ???? |
21546 | ||
21547 | @subsubheading @value{GDBN} Command | |
21548 | ||
21549 | No equivalent. | |
922fbb7b AC |
21550 | |
21551 | @subsubheading Example | |
a2c02241 NR |
21552 | N.A. |
21553 | ||
21554 | ||
21555 | @subheading The @code{-target-select} Command | |
21556 | @findex -target-select | |
21557 | ||
21558 | @subsubheading Synopsis | |
922fbb7b AC |
21559 | |
21560 | @smallexample | |
a2c02241 | 21561 | -target-select @var{type} @var{parameters @dots{}} |
922fbb7b AC |
21562 | @end smallexample |
21563 | ||
a2c02241 | 21564 | Connect @value{GDBN} to the remote target. This command takes two args: |
922fbb7b | 21565 | |
a2c02241 NR |
21566 | @table @samp |
21567 | @item @var{type} | |
21568 | The type of target, for instance @samp{async}, @samp{remote}, etc. | |
21569 | @item @var{parameters} | |
21570 | Device names, host names and the like. @xref{Target Commands, , | |
79a6e687 | 21571 | Commands for Managing Targets}, for more details. |
a2c02241 NR |
21572 | @end table |
21573 | ||
21574 | The output is a connection notification, followed by the address at | |
21575 | which the target program is, in the following form: | |
922fbb7b AC |
21576 | |
21577 | @smallexample | |
a2c02241 NR |
21578 | ^connected,addr="@var{address}",func="@var{function name}", |
21579 | args=[@var{arg list}] | |
922fbb7b AC |
21580 | @end smallexample |
21581 | ||
a2c02241 NR |
21582 | @subsubheading @value{GDBN} Command |
21583 | ||
21584 | The corresponding @value{GDBN} command is @samp{target}. | |
265eeb58 NR |
21585 | |
21586 | @subsubheading Example | |
922fbb7b | 21587 | |
265eeb58 | 21588 | @smallexample |
594fe323 | 21589 | (gdb) |
a2c02241 NR |
21590 | -target-select async /dev/ttya |
21591 | ^connected,addr="0xfe00a300",func="??",args=[] | |
594fe323 | 21592 | (gdb) |
265eeb58 | 21593 | @end smallexample |
ef21caaf | 21594 | |
a6b151f1 DJ |
21595 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21596 | @node GDB/MI File Transfer Commands | |
21597 | @section @sc{gdb/mi} File Transfer Commands | |
21598 | ||
21599 | ||
21600 | @subheading The @code{-target-file-put} Command | |
21601 | @findex -target-file-put | |
21602 | ||
21603 | @subsubheading Synopsis | |
21604 | ||
21605 | @smallexample | |
21606 | -target-file-put @var{hostfile} @var{targetfile} | |
21607 | @end smallexample | |
21608 | ||
21609 | Copy file @var{hostfile} from the host system (the machine running | |
21610 | @value{GDBN}) to @var{targetfile} on the target system. | |
21611 | ||
21612 | @subsubheading @value{GDBN} Command | |
21613 | ||
21614 | The corresponding @value{GDBN} command is @samp{remote put}. | |
21615 | ||
21616 | @subsubheading Example | |
21617 | ||
21618 | @smallexample | |
21619 | (gdb) | |
21620 | -target-file-put localfile remotefile | |
21621 | ^done | |
21622 | (gdb) | |
21623 | @end smallexample | |
21624 | ||
21625 | ||
21626 | @subheading The @code{-target-file-put} Command | |
21627 | @findex -target-file-get | |
21628 | ||
21629 | @subsubheading Synopsis | |
21630 | ||
21631 | @smallexample | |
21632 | -target-file-get @var{targetfile} @var{hostfile} | |
21633 | @end smallexample | |
21634 | ||
21635 | Copy file @var{targetfile} from the target system to @var{hostfile} | |
21636 | on the host system. | |
21637 | ||
21638 | @subsubheading @value{GDBN} Command | |
21639 | ||
21640 | The corresponding @value{GDBN} command is @samp{remote get}. | |
21641 | ||
21642 | @subsubheading Example | |
21643 | ||
21644 | @smallexample | |
21645 | (gdb) | |
21646 | -target-file-get remotefile localfile | |
21647 | ^done | |
21648 | (gdb) | |
21649 | @end smallexample | |
21650 | ||
21651 | ||
21652 | @subheading The @code{-target-file-delete} Command | |
21653 | @findex -target-file-delete | |
21654 | ||
21655 | @subsubheading Synopsis | |
21656 | ||
21657 | @smallexample | |
21658 | -target-file-delete @var{targetfile} | |
21659 | @end smallexample | |
21660 | ||
21661 | Delete @var{targetfile} from the target system. | |
21662 | ||
21663 | @subsubheading @value{GDBN} Command | |
21664 | ||
21665 | The corresponding @value{GDBN} command is @samp{remote delete}. | |
21666 | ||
21667 | @subsubheading Example | |
21668 | ||
21669 | @smallexample | |
21670 | (gdb) | |
21671 | -target-file-delete remotefile | |
21672 | ^done | |
21673 | (gdb) | |
21674 | @end smallexample | |
21675 | ||
21676 | ||
ef21caaf NR |
21677 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21678 | @node GDB/MI Miscellaneous Commands | |
21679 | @section Miscellaneous @sc{gdb/mi} Commands | |
21680 | ||
21681 | @c @subheading -gdb-complete | |
21682 | ||
21683 | @subheading The @code{-gdb-exit} Command | |
21684 | @findex -gdb-exit | |
21685 | ||
21686 | @subsubheading Synopsis | |
21687 | ||
21688 | @smallexample | |
21689 | -gdb-exit | |
21690 | @end smallexample | |
21691 | ||
21692 | Exit @value{GDBN} immediately. | |
21693 | ||
21694 | @subsubheading @value{GDBN} Command | |
21695 | ||
21696 | Approximately corresponds to @samp{quit}. | |
21697 | ||
21698 | @subsubheading Example | |
21699 | ||
21700 | @smallexample | |
594fe323 | 21701 | (gdb) |
ef21caaf NR |
21702 | -gdb-exit |
21703 | ^exit | |
21704 | @end smallexample | |
21705 | ||
a2c02241 NR |
21706 | |
21707 | @subheading The @code{-exec-abort} Command | |
21708 | @findex -exec-abort | |
21709 | ||
21710 | @subsubheading Synopsis | |
21711 | ||
21712 | @smallexample | |
21713 | -exec-abort | |
21714 | @end smallexample | |
21715 | ||
21716 | Kill the inferior running program. | |
21717 | ||
21718 | @subsubheading @value{GDBN} Command | |
21719 | ||
21720 | The corresponding @value{GDBN} command is @samp{kill}. | |
21721 | ||
21722 | @subsubheading Example | |
21723 | N.A. | |
21724 | ||
21725 | ||
ef21caaf NR |
21726 | @subheading The @code{-gdb-set} Command |
21727 | @findex -gdb-set | |
21728 | ||
21729 | @subsubheading Synopsis | |
21730 | ||
21731 | @smallexample | |
21732 | -gdb-set | |
21733 | @end smallexample | |
21734 | ||
21735 | Set an internal @value{GDBN} variable. | |
21736 | @c IS THIS A DOLLAR VARIABLE? OR SOMETHING LIKE ANNOTATE ????? | |
21737 | ||
21738 | @subsubheading @value{GDBN} Command | |
21739 | ||
21740 | The corresponding @value{GDBN} command is @samp{set}. | |
21741 | ||
21742 | @subsubheading Example | |
21743 | ||
21744 | @smallexample | |
594fe323 | 21745 | (gdb) |
ef21caaf NR |
21746 | -gdb-set $foo=3 |
21747 | ^done | |
594fe323 | 21748 | (gdb) |
ef21caaf NR |
21749 | @end smallexample |
21750 | ||
21751 | ||
21752 | @subheading The @code{-gdb-show} Command | |
21753 | @findex -gdb-show | |
21754 | ||
21755 | @subsubheading Synopsis | |
21756 | ||
21757 | @smallexample | |
21758 | -gdb-show | |
21759 | @end smallexample | |
21760 | ||
21761 | Show the current value of a @value{GDBN} variable. | |
21762 | ||
79a6e687 | 21763 | @subsubheading @value{GDBN} Command |
ef21caaf NR |
21764 | |
21765 | The corresponding @value{GDBN} command is @samp{show}. | |
21766 | ||
21767 | @subsubheading Example | |
21768 | ||
21769 | @smallexample | |
594fe323 | 21770 | (gdb) |
ef21caaf NR |
21771 | -gdb-show annotate |
21772 | ^done,value="0" | |
594fe323 | 21773 | (gdb) |
ef21caaf NR |
21774 | @end smallexample |
21775 | ||
21776 | @c @subheading -gdb-source | |
21777 | ||
21778 | ||
21779 | @subheading The @code{-gdb-version} Command | |
21780 | @findex -gdb-version | |
21781 | ||
21782 | @subsubheading Synopsis | |
21783 | ||
21784 | @smallexample | |
21785 | -gdb-version | |
21786 | @end smallexample | |
21787 | ||
21788 | Show version information for @value{GDBN}. Used mostly in testing. | |
21789 | ||
21790 | @subsubheading @value{GDBN} Command | |
21791 | ||
21792 | The @value{GDBN} equivalent is @samp{show version}. @value{GDBN} by | |
21793 | default shows this information when you start an interactive session. | |
21794 | ||
21795 | @subsubheading Example | |
21796 | ||
21797 | @c This example modifies the actual output from GDB to avoid overfull | |
21798 | @c box in TeX. | |
21799 | @smallexample | |
594fe323 | 21800 | (gdb) |
ef21caaf NR |
21801 | -gdb-version |
21802 | ~GNU gdb 5.2.1 | |
21803 | ~Copyright 2000 Free Software Foundation, Inc. | |
21804 | ~GDB is free software, covered by the GNU General Public License, and | |
21805 | ~you are welcome to change it and/or distribute copies of it under | |
21806 | ~ certain conditions. | |
21807 | ~Type "show copying" to see the conditions. | |
21808 | ~There is absolutely no warranty for GDB. Type "show warranty" for | |
21809 | ~ details. | |
21810 | ~This GDB was configured as | |
21811 | "--host=sparc-sun-solaris2.5.1 --target=ppc-eabi". | |
21812 | ^done | |
594fe323 | 21813 | (gdb) |
ef21caaf NR |
21814 | @end smallexample |
21815 | ||
084344da VP |
21816 | @subheading The @code{-list-features} Command |
21817 | @findex -list-features | |
21818 | ||
21819 | Returns a list of particular features of the MI protocol that | |
21820 | this version of gdb implements. A feature can be a command, | |
21821 | or a new field in an output of some command, or even an | |
21822 | important bugfix. While a frontend can sometimes detect presence | |
21823 | of a feature at runtime, it is easier to perform detection at debugger | |
21824 | startup. | |
21825 | ||
21826 | The command returns a list of strings, with each string naming an | |
21827 | available feature. Each returned string is just a name, it does not | |
21828 | have any internal structure. The list of possible feature names | |
21829 | is given below. | |
21830 | ||
21831 | Example output: | |
21832 | ||
21833 | @smallexample | |
21834 | (gdb) -list-features | |
21835 | ^done,result=["feature1","feature2"] | |
21836 | @end smallexample | |
21837 | ||
21838 | The current list of features is: | |
21839 | ||
21840 | @itemize @minus | |
21841 | @item | |
21842 | @samp{frozen-varobjs}---indicates presence of the | |
21843 | @code{-var-set-frozen} command, as well as possible presense of the | |
21844 | @code{frozen} field in the output of @code{-varobj-create}. | |
8b4ed427 VP |
21845 | @item |
21846 | @samp{pending-breakpoints}---indicates presence of the @code{-f} | |
21847 | option to the @code{-break-insert} command. | |
21848 | ||
084344da VP |
21849 | @end itemize |
21850 | ||
ef21caaf NR |
21851 | @subheading The @code{-interpreter-exec} Command |
21852 | @findex -interpreter-exec | |
21853 | ||
21854 | @subheading Synopsis | |
21855 | ||
21856 | @smallexample | |
21857 | -interpreter-exec @var{interpreter} @var{command} | |
21858 | @end smallexample | |
a2c02241 | 21859 | @anchor{-interpreter-exec} |
ef21caaf NR |
21860 | |
21861 | Execute the specified @var{command} in the given @var{interpreter}. | |
21862 | ||
21863 | @subheading @value{GDBN} Command | |
21864 | ||
21865 | The corresponding @value{GDBN} command is @samp{interpreter-exec}. | |
21866 | ||
21867 | @subheading Example | |
21868 | ||
21869 | @smallexample | |
594fe323 | 21870 | (gdb) |
ef21caaf NR |
21871 | -interpreter-exec console "break main" |
21872 | &"During symbol reading, couldn't parse type; debugger out of date?.\n" | |
21873 | &"During symbol reading, bad structure-type format.\n" | |
21874 | ~"Breakpoint 1 at 0x8074fc6: file ../../src/gdb/main.c, line 743.\n" | |
21875 | ^done | |
594fe323 | 21876 | (gdb) |
ef21caaf NR |
21877 | @end smallexample |
21878 | ||
21879 | @subheading The @code{-inferior-tty-set} Command | |
21880 | @findex -inferior-tty-set | |
21881 | ||
21882 | @subheading Synopsis | |
21883 | ||
21884 | @smallexample | |
21885 | -inferior-tty-set /dev/pts/1 | |
21886 | @end smallexample | |
21887 | ||
21888 | Set terminal for future runs of the program being debugged. | |
21889 | ||
21890 | @subheading @value{GDBN} Command | |
21891 | ||
21892 | The corresponding @value{GDBN} command is @samp{set inferior-tty} /dev/pts/1. | |
21893 | ||
21894 | @subheading Example | |
21895 | ||
21896 | @smallexample | |
594fe323 | 21897 | (gdb) |
ef21caaf NR |
21898 | -inferior-tty-set /dev/pts/1 |
21899 | ^done | |
594fe323 | 21900 | (gdb) |
ef21caaf NR |
21901 | @end smallexample |
21902 | ||
21903 | @subheading The @code{-inferior-tty-show} Command | |
21904 | @findex -inferior-tty-show | |
21905 | ||
21906 | @subheading Synopsis | |
21907 | ||
21908 | @smallexample | |
21909 | -inferior-tty-show | |
21910 | @end smallexample | |
21911 | ||
21912 | Show terminal for future runs of program being debugged. | |
21913 | ||
21914 | @subheading @value{GDBN} Command | |
21915 | ||
21916 | The corresponding @value{GDBN} command is @samp{show inferior-tty}. | |
21917 | ||
21918 | @subheading Example | |
21919 | ||
21920 | @smallexample | |
594fe323 | 21921 | (gdb) |
ef21caaf NR |
21922 | -inferior-tty-set /dev/pts/1 |
21923 | ^done | |
594fe323 | 21924 | (gdb) |
ef21caaf NR |
21925 | -inferior-tty-show |
21926 | ^done,inferior_tty_terminal="/dev/pts/1" | |
594fe323 | 21927 | (gdb) |
ef21caaf | 21928 | @end smallexample |
922fbb7b | 21929 | |
a4eefcd8 NR |
21930 | @subheading The @code{-enable-timings} Command |
21931 | @findex -enable-timings | |
21932 | ||
21933 | @subheading Synopsis | |
21934 | ||
21935 | @smallexample | |
21936 | -enable-timings [yes | no] | |
21937 | @end smallexample | |
21938 | ||
21939 | Toggle the printing of the wallclock, user and system times for an MI | |
21940 | command as a field in its output. This command is to help frontend | |
21941 | developers optimize the performance of their code. No argument is | |
21942 | equivalent to @samp{yes}. | |
21943 | ||
21944 | @subheading @value{GDBN} Command | |
21945 | ||
21946 | No equivalent. | |
21947 | ||
21948 | @subheading Example | |
21949 | ||
21950 | @smallexample | |
21951 | (gdb) | |
21952 | -enable-timings | |
21953 | ^done | |
21954 | (gdb) | |
21955 | -break-insert main | |
21956 | ^done,bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
21957 | addr="0x080484ed",func="main",file="myprog.c", | |
21958 | fullname="/home/nickrob/myprog.c",line="73",times="0"@}, | |
21959 | time=@{wallclock="0.05185",user="0.00800",system="0.00000"@} | |
21960 | (gdb) | |
21961 | -enable-timings no | |
21962 | ^done | |
21963 | (gdb) | |
21964 | -exec-run | |
21965 | ^running | |
21966 | (gdb) | |
21967 | *stopped,reason="breakpoint-hit",bkptno="1",thread-id="0", | |
21968 | frame=@{addr="0x080484ed",func="main",args=[@{name="argc",value="1"@}, | |
21969 | @{name="argv",value="0xbfb60364"@}],file="myprog.c", | |
21970 | fullname="/home/nickrob/myprog.c",line="73"@} | |
21971 | (gdb) | |
21972 | @end smallexample | |
21973 | ||
922fbb7b AC |
21974 | @node Annotations |
21975 | @chapter @value{GDBN} Annotations | |
21976 | ||
086432e2 AC |
21977 | This chapter describes annotations in @value{GDBN}. Annotations were |
21978 | designed to interface @value{GDBN} to graphical user interfaces or other | |
21979 | similar programs which want to interact with @value{GDBN} at a | |
922fbb7b AC |
21980 | relatively high level. |
21981 | ||
d3e8051b | 21982 | The annotation mechanism has largely been superseded by @sc{gdb/mi} |
086432e2 AC |
21983 | (@pxref{GDB/MI}). |
21984 | ||
922fbb7b AC |
21985 | @ignore |
21986 | This is Edition @value{EDITION}, @value{DATE}. | |
21987 | @end ignore | |
21988 | ||
21989 | @menu | |
21990 | * Annotations Overview:: What annotations are; the general syntax. | |
9e6c4bd5 | 21991 | * Server Prefix:: Issuing a command without affecting user state. |
922fbb7b AC |
21992 | * Prompting:: Annotations marking @value{GDBN}'s need for input. |
21993 | * Errors:: Annotations for error messages. | |
922fbb7b AC |
21994 | * Invalidation:: Some annotations describe things now invalid. |
21995 | * Annotations for Running:: | |
21996 | Whether the program is running, how it stopped, etc. | |
21997 | * Source Annotations:: Annotations describing source code. | |
922fbb7b AC |
21998 | @end menu |
21999 | ||
22000 | @node Annotations Overview | |
22001 | @section What is an Annotation? | |
22002 | @cindex annotations | |
22003 | ||
922fbb7b AC |
22004 | Annotations start with a newline character, two @samp{control-z} |
22005 | characters, and the name of the annotation. If there is no additional | |
22006 | information associated with this annotation, the name of the annotation | |
22007 | is followed immediately by a newline. If there is additional | |
22008 | information, the name of the annotation is followed by a space, the | |
22009 | additional information, and a newline. The additional information | |
22010 | cannot contain newline characters. | |
22011 | ||
22012 | Any output not beginning with a newline and two @samp{control-z} | |
22013 | characters denotes literal output from @value{GDBN}. Currently there is | |
22014 | no need for @value{GDBN} to output a newline followed by two | |
22015 | @samp{control-z} characters, but if there was such a need, the | |
22016 | annotations could be extended with an @samp{escape} annotation which | |
22017 | means those three characters as output. | |
22018 | ||
086432e2 AC |
22019 | The annotation @var{level}, which is specified using the |
22020 | @option{--annotate} command line option (@pxref{Mode Options}), controls | |
22021 | how much information @value{GDBN} prints together with its prompt, | |
22022 | values of expressions, source lines, and other types of output. Level 0 | |
d3e8051b | 22023 | is for no annotations, level 1 is for use when @value{GDBN} is run as a |
086432e2 AC |
22024 | subprocess of @sc{gnu} Emacs, level 3 is the maximum annotation suitable |
22025 | for programs that control @value{GDBN}, and level 2 annotations have | |
22026 | been made obsolete (@pxref{Limitations, , Limitations of the Annotation | |
09d4efe1 EZ |
22027 | Interface, annotate, GDB's Obsolete Annotations}). |
22028 | ||
22029 | @table @code | |
22030 | @kindex set annotate | |
22031 | @item set annotate @var{level} | |
e09f16f9 | 22032 | The @value{GDBN} command @code{set annotate} sets the level of |
09d4efe1 | 22033 | annotations to the specified @var{level}. |
9c16f35a EZ |
22034 | |
22035 | @item show annotate | |
22036 | @kindex show annotate | |
22037 | Show the current annotation level. | |
09d4efe1 EZ |
22038 | @end table |
22039 | ||
22040 | This chapter describes level 3 annotations. | |
086432e2 | 22041 | |
922fbb7b AC |
22042 | A simple example of starting up @value{GDBN} with annotations is: |
22043 | ||
22044 | @smallexample | |
086432e2 AC |
22045 | $ @kbd{gdb --annotate=3} |
22046 | GNU gdb 6.0 | |
22047 | Copyright 2003 Free Software Foundation, Inc. | |
922fbb7b AC |
22048 | GDB is free software, covered by the GNU General Public License, |
22049 | and you are welcome to change it and/or distribute copies of it | |
22050 | under certain conditions. | |
22051 | Type "show copying" to see the conditions. | |
22052 | There is absolutely no warranty for GDB. Type "show warranty" | |
22053 | for details. | |
086432e2 | 22054 | This GDB was configured as "i386-pc-linux-gnu" |
922fbb7b AC |
22055 | |
22056 | ^Z^Zpre-prompt | |
f7dc1244 | 22057 | (@value{GDBP}) |
922fbb7b | 22058 | ^Z^Zprompt |
086432e2 | 22059 | @kbd{quit} |
922fbb7b AC |
22060 | |
22061 | ^Z^Zpost-prompt | |
b383017d | 22062 | $ |
922fbb7b AC |
22063 | @end smallexample |
22064 | ||
22065 | Here @samp{quit} is input to @value{GDBN}; the rest is output from | |
22066 | @value{GDBN}. The three lines beginning @samp{^Z^Z} (where @samp{^Z} | |
22067 | denotes a @samp{control-z} character) are annotations; the rest is | |
22068 | output from @value{GDBN}. | |
22069 | ||
9e6c4bd5 NR |
22070 | @node Server Prefix |
22071 | @section The Server Prefix | |
22072 | @cindex server prefix | |
22073 | ||
22074 | If you prefix a command with @samp{server } then it will not affect | |
22075 | the command history, nor will it affect @value{GDBN}'s notion of which | |
22076 | command to repeat if @key{RET} is pressed on a line by itself. This | |
22077 | means that commands can be run behind a user's back by a front-end in | |
22078 | a transparent manner. | |
22079 | ||
22080 | The server prefix does not affect the recording of values into the value | |
22081 | history; to print a value without recording it into the value history, | |
22082 | use the @code{output} command instead of the @code{print} command. | |
22083 | ||
922fbb7b AC |
22084 | @node Prompting |
22085 | @section Annotation for @value{GDBN} Input | |
22086 | ||
22087 | @cindex annotations for prompts | |
22088 | When @value{GDBN} prompts for input, it annotates this fact so it is possible | |
22089 | to know when to send output, when the output from a given command is | |
22090 | over, etc. | |
22091 | ||
22092 | Different kinds of input each have a different @dfn{input type}. Each | |
22093 | input type has three annotations: a @code{pre-} annotation, which | |
22094 | denotes the beginning of any prompt which is being output, a plain | |
22095 | annotation, which denotes the end of the prompt, and then a @code{post-} | |
22096 | annotation which denotes the end of any echo which may (or may not) be | |
22097 | associated with the input. For example, the @code{prompt} input type | |
22098 | features the following annotations: | |
22099 | ||
22100 | @smallexample | |
22101 | ^Z^Zpre-prompt | |
22102 | ^Z^Zprompt | |
22103 | ^Z^Zpost-prompt | |
22104 | @end smallexample | |
22105 | ||
22106 | The input types are | |
22107 | ||
22108 | @table @code | |
e5ac9b53 EZ |
22109 | @findex pre-prompt annotation |
22110 | @findex prompt annotation | |
22111 | @findex post-prompt annotation | |
922fbb7b AC |
22112 | @item prompt |
22113 | When @value{GDBN} is prompting for a command (the main @value{GDBN} prompt). | |
22114 | ||
e5ac9b53 EZ |
22115 | @findex pre-commands annotation |
22116 | @findex commands annotation | |
22117 | @findex post-commands annotation | |
922fbb7b AC |
22118 | @item commands |
22119 | When @value{GDBN} prompts for a set of commands, like in the @code{commands} | |
22120 | command. The annotations are repeated for each command which is input. | |
22121 | ||
e5ac9b53 EZ |
22122 | @findex pre-overload-choice annotation |
22123 | @findex overload-choice annotation | |
22124 | @findex post-overload-choice annotation | |
922fbb7b AC |
22125 | @item overload-choice |
22126 | When @value{GDBN} wants the user to select between various overloaded functions. | |
22127 | ||
e5ac9b53 EZ |
22128 | @findex pre-query annotation |
22129 | @findex query annotation | |
22130 | @findex post-query annotation | |
922fbb7b AC |
22131 | @item query |
22132 | When @value{GDBN} wants the user to confirm a potentially dangerous operation. | |
22133 | ||
e5ac9b53 EZ |
22134 | @findex pre-prompt-for-continue annotation |
22135 | @findex prompt-for-continue annotation | |
22136 | @findex post-prompt-for-continue annotation | |
922fbb7b AC |
22137 | @item prompt-for-continue |
22138 | When @value{GDBN} is asking the user to press return to continue. Note: Don't | |
22139 | expect this to work well; instead use @code{set height 0} to disable | |
22140 | prompting. This is because the counting of lines is buggy in the | |
22141 | presence of annotations. | |
22142 | @end table | |
22143 | ||
22144 | @node Errors | |
22145 | @section Errors | |
22146 | @cindex annotations for errors, warnings and interrupts | |
22147 | ||
e5ac9b53 | 22148 | @findex quit annotation |
922fbb7b AC |
22149 | @smallexample |
22150 | ^Z^Zquit | |
22151 | @end smallexample | |
22152 | ||
22153 | This annotation occurs right before @value{GDBN} responds to an interrupt. | |
22154 | ||
e5ac9b53 | 22155 | @findex error annotation |
922fbb7b AC |
22156 | @smallexample |
22157 | ^Z^Zerror | |
22158 | @end smallexample | |
22159 | ||
22160 | This annotation occurs right before @value{GDBN} responds to an error. | |
22161 | ||
22162 | Quit and error annotations indicate that any annotations which @value{GDBN} was | |
22163 | in the middle of may end abruptly. For example, if a | |
22164 | @code{value-history-begin} annotation is followed by a @code{error}, one | |
22165 | cannot expect to receive the matching @code{value-history-end}. One | |
22166 | cannot expect not to receive it either, however; an error annotation | |
22167 | does not necessarily mean that @value{GDBN} is immediately returning all the way | |
22168 | to the top level. | |
22169 | ||
e5ac9b53 | 22170 | @findex error-begin annotation |
922fbb7b AC |
22171 | A quit or error annotation may be preceded by |
22172 | ||
22173 | @smallexample | |
22174 | ^Z^Zerror-begin | |
22175 | @end smallexample | |
22176 | ||
22177 | Any output between that and the quit or error annotation is the error | |
22178 | message. | |
22179 | ||
22180 | Warning messages are not yet annotated. | |
22181 | @c If we want to change that, need to fix warning(), type_error(), | |
22182 | @c range_error(), and possibly other places. | |
22183 | ||
922fbb7b AC |
22184 | @node Invalidation |
22185 | @section Invalidation Notices | |
22186 | ||
22187 | @cindex annotations for invalidation messages | |
22188 | The following annotations say that certain pieces of state may have | |
22189 | changed. | |
22190 | ||
22191 | @table @code | |
e5ac9b53 | 22192 | @findex frames-invalid annotation |
922fbb7b AC |
22193 | @item ^Z^Zframes-invalid |
22194 | ||
22195 | The frames (for example, output from the @code{backtrace} command) may | |
22196 | have changed. | |
22197 | ||
e5ac9b53 | 22198 | @findex breakpoints-invalid annotation |
922fbb7b AC |
22199 | @item ^Z^Zbreakpoints-invalid |
22200 | ||
22201 | The breakpoints may have changed. For example, the user just added or | |
22202 | deleted a breakpoint. | |
22203 | @end table | |
22204 | ||
22205 | @node Annotations for Running | |
22206 | @section Running the Program | |
22207 | @cindex annotations for running programs | |
22208 | ||
e5ac9b53 EZ |
22209 | @findex starting annotation |
22210 | @findex stopping annotation | |
922fbb7b | 22211 | When the program starts executing due to a @value{GDBN} command such as |
b383017d | 22212 | @code{step} or @code{continue}, |
922fbb7b AC |
22213 | |
22214 | @smallexample | |
22215 | ^Z^Zstarting | |
22216 | @end smallexample | |
22217 | ||
b383017d | 22218 | is output. When the program stops, |
922fbb7b AC |
22219 | |
22220 | @smallexample | |
22221 | ^Z^Zstopped | |
22222 | @end smallexample | |
22223 | ||
22224 | is output. Before the @code{stopped} annotation, a variety of | |
22225 | annotations describe how the program stopped. | |
22226 | ||
22227 | @table @code | |
e5ac9b53 | 22228 | @findex exited annotation |
922fbb7b AC |
22229 | @item ^Z^Zexited @var{exit-status} |
22230 | The program exited, and @var{exit-status} is the exit status (zero for | |
22231 | successful exit, otherwise nonzero). | |
22232 | ||
e5ac9b53 EZ |
22233 | @findex signalled annotation |
22234 | @findex signal-name annotation | |
22235 | @findex signal-name-end annotation | |
22236 | @findex signal-string annotation | |
22237 | @findex signal-string-end annotation | |
922fbb7b AC |
22238 | @item ^Z^Zsignalled |
22239 | The program exited with a signal. After the @code{^Z^Zsignalled}, the | |
22240 | annotation continues: | |
22241 | ||
22242 | @smallexample | |
22243 | @var{intro-text} | |
22244 | ^Z^Zsignal-name | |
22245 | @var{name} | |
22246 | ^Z^Zsignal-name-end | |
22247 | @var{middle-text} | |
22248 | ^Z^Zsignal-string | |
22249 | @var{string} | |
22250 | ^Z^Zsignal-string-end | |
22251 | @var{end-text} | |
22252 | @end smallexample | |
22253 | ||
22254 | @noindent | |
22255 | where @var{name} is the name of the signal, such as @code{SIGILL} or | |
22256 | @code{SIGSEGV}, and @var{string} is the explanation of the signal, such | |
22257 | as @code{Illegal Instruction} or @code{Segmentation fault}. | |
22258 | @var{intro-text}, @var{middle-text}, and @var{end-text} are for the | |
22259 | user's benefit and have no particular format. | |
22260 | ||
e5ac9b53 | 22261 | @findex signal annotation |
922fbb7b AC |
22262 | @item ^Z^Zsignal |
22263 | The syntax of this annotation is just like @code{signalled}, but @value{GDBN} is | |
22264 | just saying that the program received the signal, not that it was | |
22265 | terminated with it. | |
22266 | ||
e5ac9b53 | 22267 | @findex breakpoint annotation |
922fbb7b AC |
22268 | @item ^Z^Zbreakpoint @var{number} |
22269 | The program hit breakpoint number @var{number}. | |
22270 | ||
e5ac9b53 | 22271 | @findex watchpoint annotation |
922fbb7b AC |
22272 | @item ^Z^Zwatchpoint @var{number} |
22273 | The program hit watchpoint number @var{number}. | |
22274 | @end table | |
22275 | ||
22276 | @node Source Annotations | |
22277 | @section Displaying Source | |
22278 | @cindex annotations for source display | |
22279 | ||
e5ac9b53 | 22280 | @findex source annotation |
922fbb7b AC |
22281 | The following annotation is used instead of displaying source code: |
22282 | ||
22283 | @smallexample | |
22284 | ^Z^Zsource @var{filename}:@var{line}:@var{character}:@var{middle}:@var{addr} | |
22285 | @end smallexample | |
22286 | ||
22287 | where @var{filename} is an absolute file name indicating which source | |
22288 | file, @var{line} is the line number within that file (where 1 is the | |
22289 | first line in the file), @var{character} is the character position | |
22290 | within the file (where 0 is the first character in the file) (for most | |
22291 | debug formats this will necessarily point to the beginning of a line), | |
22292 | @var{middle} is @samp{middle} if @var{addr} is in the middle of the | |
22293 | line, or @samp{beg} if @var{addr} is at the beginning of the line, and | |
22294 | @var{addr} is the address in the target program associated with the | |
22295 | source which is being displayed. @var{addr} is in the form @samp{0x} | |
22296 | followed by one or more lowercase hex digits (note that this does not | |
22297 | depend on the language). | |
22298 | ||
8e04817f AC |
22299 | @node GDB Bugs |
22300 | @chapter Reporting Bugs in @value{GDBN} | |
22301 | @cindex bugs in @value{GDBN} | |
22302 | @cindex reporting bugs in @value{GDBN} | |
c906108c | 22303 | |
8e04817f | 22304 | Your bug reports play an essential role in making @value{GDBN} reliable. |
c906108c | 22305 | |
8e04817f AC |
22306 | Reporting a bug may help you by bringing a solution to your problem, or it |
22307 | may not. But in any case the principal function of a bug report is to help | |
22308 | the entire community by making the next version of @value{GDBN} work better. Bug | |
22309 | reports are your contribution to the maintenance of @value{GDBN}. | |
c906108c | 22310 | |
8e04817f AC |
22311 | In order for a bug report to serve its purpose, you must include the |
22312 | information that enables us to fix the bug. | |
c4555f82 SC |
22313 | |
22314 | @menu | |
8e04817f AC |
22315 | * Bug Criteria:: Have you found a bug? |
22316 | * Bug Reporting:: How to report bugs | |
c4555f82 SC |
22317 | @end menu |
22318 | ||
8e04817f | 22319 | @node Bug Criteria |
79a6e687 | 22320 | @section Have You Found a Bug? |
8e04817f | 22321 | @cindex bug criteria |
c4555f82 | 22322 | |
8e04817f | 22323 | If you are not sure whether you have found a bug, here are some guidelines: |
c4555f82 SC |
22324 | |
22325 | @itemize @bullet | |
8e04817f AC |
22326 | @cindex fatal signal |
22327 | @cindex debugger crash | |
22328 | @cindex crash of debugger | |
c4555f82 | 22329 | @item |
8e04817f AC |
22330 | If the debugger gets a fatal signal, for any input whatever, that is a |
22331 | @value{GDBN} bug. Reliable debuggers never crash. | |
22332 | ||
22333 | @cindex error on valid input | |
22334 | @item | |
22335 | If @value{GDBN} produces an error message for valid input, that is a | |
22336 | bug. (Note that if you're cross debugging, the problem may also be | |
22337 | somewhere in the connection to the target.) | |
c4555f82 | 22338 | |
8e04817f | 22339 | @cindex invalid input |
c4555f82 | 22340 | @item |
8e04817f AC |
22341 | If @value{GDBN} does not produce an error message for invalid input, |
22342 | that is a bug. However, you should note that your idea of | |
22343 | ``invalid input'' might be our idea of ``an extension'' or ``support | |
22344 | for traditional practice''. | |
22345 | ||
22346 | @item | |
22347 | If you are an experienced user of debugging tools, your suggestions | |
22348 | for improvement of @value{GDBN} are welcome in any case. | |
c4555f82 SC |
22349 | @end itemize |
22350 | ||
8e04817f | 22351 | @node Bug Reporting |
79a6e687 | 22352 | @section How to Report Bugs |
8e04817f AC |
22353 | @cindex bug reports |
22354 | @cindex @value{GDBN} bugs, reporting | |
22355 | ||
22356 | A number of companies and individuals offer support for @sc{gnu} products. | |
22357 | If you obtained @value{GDBN} from a support organization, we recommend you | |
22358 | contact that organization first. | |
22359 | ||
22360 | You can find contact information for many support companies and | |
22361 | individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs | |
22362 | distribution. | |
22363 | @c should add a web page ref... | |
22364 | ||
129188f6 | 22365 | In any event, we also recommend that you submit bug reports for |
d3e8051b | 22366 | @value{GDBN}. The preferred method is to submit them directly using |
129188f6 AC |
22367 | @uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web |
22368 | page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can | |
22369 | be used. | |
8e04817f AC |
22370 | |
22371 | @strong{Do not send bug reports to @samp{info-gdb}, or to | |
22372 | @samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do | |
22373 | not want to receive bug reports. Those that do have arranged to receive | |
22374 | @samp{bug-gdb}. | |
22375 | ||
22376 | The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which | |
22377 | serves as a repeater. The mailing list and the newsgroup carry exactly | |
22378 | the same messages. Often people think of posting bug reports to the | |
22379 | newsgroup instead of mailing them. This appears to work, but it has one | |
22380 | problem which can be crucial: a newsgroup posting often lacks a mail | |
22381 | path back to the sender. Thus, if we need to ask for more information, | |
22382 | we may be unable to reach you. For this reason, it is better to send | |
22383 | bug reports to the mailing list. | |
c4555f82 | 22384 | |
8e04817f AC |
22385 | The fundamental principle of reporting bugs usefully is this: |
22386 | @strong{report all the facts}. If you are not sure whether to state a | |
22387 | fact or leave it out, state it! | |
c4555f82 | 22388 | |
8e04817f AC |
22389 | Often people omit facts because they think they know what causes the |
22390 | problem and assume that some details do not matter. Thus, you might | |
22391 | assume that the name of the variable you use in an example does not matter. | |
22392 | Well, probably it does not, but one cannot be sure. Perhaps the bug is a | |
22393 | stray memory reference which happens to fetch from the location where that | |
22394 | name is stored in memory; perhaps, if the name were different, the contents | |
22395 | of that location would fool the debugger into doing the right thing despite | |
22396 | the bug. Play it safe and give a specific, complete example. That is the | |
22397 | easiest thing for you to do, and the most helpful. | |
c4555f82 | 22398 | |
8e04817f AC |
22399 | Keep in mind that the purpose of a bug report is to enable us to fix the |
22400 | bug. It may be that the bug has been reported previously, but neither | |
22401 | you nor we can know that unless your bug report is complete and | |
22402 | self-contained. | |
c4555f82 | 22403 | |
8e04817f AC |
22404 | Sometimes people give a few sketchy facts and ask, ``Does this ring a |
22405 | bell?'' Those bug reports are useless, and we urge everyone to | |
22406 | @emph{refuse to respond to them} except to chide the sender to report | |
22407 | bugs properly. | |
22408 | ||
22409 | To enable us to fix the bug, you should include all these things: | |
c4555f82 SC |
22410 | |
22411 | @itemize @bullet | |
22412 | @item | |
8e04817f AC |
22413 | The version of @value{GDBN}. @value{GDBN} announces it if you start |
22414 | with no arguments; you can also print it at any time using @code{show | |
22415 | version}. | |
c4555f82 | 22416 | |
8e04817f AC |
22417 | Without this, we will not know whether there is any point in looking for |
22418 | the bug in the current version of @value{GDBN}. | |
c4555f82 SC |
22419 | |
22420 | @item | |
8e04817f AC |
22421 | The type of machine you are using, and the operating system name and |
22422 | version number. | |
c4555f82 SC |
22423 | |
22424 | @item | |
c1468174 | 22425 | What compiler (and its version) was used to compile @value{GDBN}---e.g.@: |
8e04817f | 22426 | ``@value{GCC}--2.8.1''. |
c4555f82 SC |
22427 | |
22428 | @item | |
8e04817f | 22429 | What compiler (and its version) was used to compile the program you are |
c1468174 | 22430 | debugging---e.g.@: ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP |
3f94c067 BW |
22431 | C Compiler''. For @value{NGCC}, you can say @kbd{@value{GCC} --version} |
22432 | to get this information; for other compilers, see the documentation for | |
22433 | those compilers. | |
c4555f82 | 22434 | |
8e04817f AC |
22435 | @item |
22436 | The command arguments you gave the compiler to compile your example and | |
22437 | observe the bug. For example, did you use @samp{-O}? To guarantee | |
22438 | you will not omit something important, list them all. A copy of the | |
22439 | Makefile (or the output from make) is sufficient. | |
c4555f82 | 22440 | |
8e04817f AC |
22441 | If we were to try to guess the arguments, we would probably guess wrong |
22442 | and then we might not encounter the bug. | |
c4555f82 | 22443 | |
8e04817f AC |
22444 | @item |
22445 | A complete input script, and all necessary source files, that will | |
22446 | reproduce the bug. | |
c4555f82 | 22447 | |
8e04817f AC |
22448 | @item |
22449 | A description of what behavior you observe that you believe is | |
22450 | incorrect. For example, ``It gets a fatal signal.'' | |
c4555f82 | 22451 | |
8e04817f AC |
22452 | Of course, if the bug is that @value{GDBN} gets a fatal signal, then we |
22453 | will certainly notice it. But if the bug is incorrect output, we might | |
22454 | not notice unless it is glaringly wrong. You might as well not give us | |
22455 | a chance to make a mistake. | |
c4555f82 | 22456 | |
8e04817f AC |
22457 | Even if the problem you experience is a fatal signal, you should still |
22458 | say so explicitly. Suppose something strange is going on, such as, your | |
22459 | copy of @value{GDBN} is out of synch, or you have encountered a bug in | |
22460 | the C library on your system. (This has happened!) Your copy might | |
22461 | crash and ours would not. If you told us to expect a crash, then when | |
22462 | ours fails to crash, we would know that the bug was not happening for | |
22463 | us. If you had not told us to expect a crash, then we would not be able | |
22464 | to draw any conclusion from our observations. | |
c4555f82 | 22465 | |
e0c07bf0 MC |
22466 | @pindex script |
22467 | @cindex recording a session script | |
22468 | To collect all this information, you can use a session recording program | |
22469 | such as @command{script}, which is available on many Unix systems. | |
22470 | Just run your @value{GDBN} session inside @command{script} and then | |
22471 | include the @file{typescript} file with your bug report. | |
22472 | ||
22473 | Another way to record a @value{GDBN} session is to run @value{GDBN} | |
22474 | inside Emacs and then save the entire buffer to a file. | |
22475 | ||
8e04817f AC |
22476 | @item |
22477 | If you wish to suggest changes to the @value{GDBN} source, send us context | |
22478 | diffs. If you even discuss something in the @value{GDBN} source, refer to | |
22479 | it by context, not by line number. | |
c4555f82 | 22480 | |
8e04817f AC |
22481 | The line numbers in our development sources will not match those in your |
22482 | sources. Your line numbers would convey no useful information to us. | |
c4555f82 | 22483 | |
8e04817f | 22484 | @end itemize |
c4555f82 | 22485 | |
8e04817f | 22486 | Here are some things that are not necessary: |
c4555f82 | 22487 | |
8e04817f AC |
22488 | @itemize @bullet |
22489 | @item | |
22490 | A description of the envelope of the bug. | |
c4555f82 | 22491 | |
8e04817f AC |
22492 | Often people who encounter a bug spend a lot of time investigating |
22493 | which changes to the input file will make the bug go away and which | |
22494 | changes will not affect it. | |
c4555f82 | 22495 | |
8e04817f AC |
22496 | This is often time consuming and not very useful, because the way we |
22497 | will find the bug is by running a single example under the debugger | |
22498 | with breakpoints, not by pure deduction from a series of examples. | |
22499 | We recommend that you save your time for something else. | |
c4555f82 | 22500 | |
8e04817f AC |
22501 | Of course, if you can find a simpler example to report @emph{instead} |
22502 | of the original one, that is a convenience for us. Errors in the | |
22503 | output will be easier to spot, running under the debugger will take | |
22504 | less time, and so on. | |
c4555f82 | 22505 | |
8e04817f AC |
22506 | However, simplification is not vital; if you do not want to do this, |
22507 | report the bug anyway and send us the entire test case you used. | |
c4555f82 | 22508 | |
8e04817f AC |
22509 | @item |
22510 | A patch for the bug. | |
c4555f82 | 22511 | |
8e04817f AC |
22512 | A patch for the bug does help us if it is a good one. But do not omit |
22513 | the necessary information, such as the test case, on the assumption that | |
22514 | a patch is all we need. We might see problems with your patch and decide | |
22515 | to fix the problem another way, or we might not understand it at all. | |
c4555f82 | 22516 | |
8e04817f AC |
22517 | Sometimes with a program as complicated as @value{GDBN} it is very hard to |
22518 | construct an example that will make the program follow a certain path | |
22519 | through the code. If you do not send us the example, we will not be able | |
22520 | to construct one, so we will not be able to verify that the bug is fixed. | |
c4555f82 | 22521 | |
8e04817f AC |
22522 | And if we cannot understand what bug you are trying to fix, or why your |
22523 | patch should be an improvement, we will not install it. A test case will | |
22524 | help us to understand. | |
c4555f82 | 22525 | |
8e04817f AC |
22526 | @item |
22527 | A guess about what the bug is or what it depends on. | |
c4555f82 | 22528 | |
8e04817f AC |
22529 | Such guesses are usually wrong. Even we cannot guess right about such |
22530 | things without first using the debugger to find the facts. | |
22531 | @end itemize | |
c4555f82 | 22532 | |
8e04817f AC |
22533 | @c The readline documentation is distributed with the readline code |
22534 | @c and consists of the two following files: | |
22535 | @c rluser.texinfo | |
22536 | @c inc-hist.texinfo | |
22537 | @c Use -I with makeinfo to point to the appropriate directory, | |
22538 | @c environment var TEXINPUTS with TeX. | |
5bdf8622 | 22539 | @include rluser.texi |
8e04817f | 22540 | @include inc-hist.texinfo |
c4555f82 | 22541 | |
c4555f82 | 22542 | |
8e04817f AC |
22543 | @node Formatting Documentation |
22544 | @appendix Formatting Documentation | |
c4555f82 | 22545 | |
8e04817f AC |
22546 | @cindex @value{GDBN} reference card |
22547 | @cindex reference card | |
22548 | The @value{GDBN} 4 release includes an already-formatted reference card, ready | |
22549 | for printing with PostScript or Ghostscript, in the @file{gdb} | |
22550 | subdirectory of the main source directory@footnote{In | |
22551 | @file{gdb-@value{GDBVN}/gdb/refcard.ps} of the version @value{GDBVN} | |
22552 | release.}. If you can use PostScript or Ghostscript with your printer, | |
22553 | you can print the reference card immediately with @file{refcard.ps}. | |
c4555f82 | 22554 | |
8e04817f AC |
22555 | The release also includes the source for the reference card. You |
22556 | can format it, using @TeX{}, by typing: | |
c4555f82 | 22557 | |
474c8240 | 22558 | @smallexample |
8e04817f | 22559 | make refcard.dvi |
474c8240 | 22560 | @end smallexample |
c4555f82 | 22561 | |
8e04817f AC |
22562 | The @value{GDBN} reference card is designed to print in @dfn{landscape} |
22563 | mode on US ``letter'' size paper; | |
22564 | that is, on a sheet 11 inches wide by 8.5 inches | |
22565 | high. You will need to specify this form of printing as an option to | |
22566 | your @sc{dvi} output program. | |
c4555f82 | 22567 | |
8e04817f | 22568 | @cindex documentation |
c4555f82 | 22569 | |
8e04817f AC |
22570 | All the documentation for @value{GDBN} comes as part of the machine-readable |
22571 | distribution. The documentation is written in Texinfo format, which is | |
22572 | a documentation system that uses a single source file to produce both | |
22573 | on-line information and a printed manual. You can use one of the Info | |
22574 | formatting commands to create the on-line version of the documentation | |
22575 | and @TeX{} (or @code{texi2roff}) to typeset the printed version. | |
c4555f82 | 22576 | |
8e04817f AC |
22577 | @value{GDBN} includes an already formatted copy of the on-line Info |
22578 | version of this manual in the @file{gdb} subdirectory. The main Info | |
22579 | file is @file{gdb-@value{GDBVN}/gdb/gdb.info}, and it refers to | |
22580 | subordinate files matching @samp{gdb.info*} in the same directory. If | |
22581 | necessary, you can print out these files, or read them with any editor; | |
22582 | but they are easier to read using the @code{info} subsystem in @sc{gnu} | |
22583 | Emacs or the standalone @code{info} program, available as part of the | |
22584 | @sc{gnu} Texinfo distribution. | |
c4555f82 | 22585 | |
8e04817f AC |
22586 | If you want to format these Info files yourself, you need one of the |
22587 | Info formatting programs, such as @code{texinfo-format-buffer} or | |
22588 | @code{makeinfo}. | |
c4555f82 | 22589 | |
8e04817f AC |
22590 | If you have @code{makeinfo} installed, and are in the top level |
22591 | @value{GDBN} source directory (@file{gdb-@value{GDBVN}}, in the case of | |
22592 | version @value{GDBVN}), you can make the Info file by typing: | |
c4555f82 | 22593 | |
474c8240 | 22594 | @smallexample |
8e04817f AC |
22595 | cd gdb |
22596 | make gdb.info | |
474c8240 | 22597 | @end smallexample |
c4555f82 | 22598 | |
8e04817f AC |
22599 | If you want to typeset and print copies of this manual, you need @TeX{}, |
22600 | a program to print its @sc{dvi} output files, and @file{texinfo.tex}, the | |
22601 | Texinfo definitions file. | |
c4555f82 | 22602 | |
8e04817f AC |
22603 | @TeX{} is a typesetting program; it does not print files directly, but |
22604 | produces output files called @sc{dvi} files. To print a typeset | |
22605 | document, you need a program to print @sc{dvi} files. If your system | |
22606 | has @TeX{} installed, chances are it has such a program. The precise | |
22607 | command to use depends on your system; @kbd{lpr -d} is common; another | |
22608 | (for PostScript devices) is @kbd{dvips}. The @sc{dvi} print command may | |
22609 | require a file name without any extension or a @samp{.dvi} extension. | |
c4555f82 | 22610 | |
8e04817f AC |
22611 | @TeX{} also requires a macro definitions file called |
22612 | @file{texinfo.tex}. This file tells @TeX{} how to typeset a document | |
22613 | written in Texinfo format. On its own, @TeX{} cannot either read or | |
22614 | typeset a Texinfo file. @file{texinfo.tex} is distributed with GDB | |
22615 | and is located in the @file{gdb-@var{version-number}/texinfo} | |
22616 | directory. | |
c4555f82 | 22617 | |
8e04817f | 22618 | If you have @TeX{} and a @sc{dvi} printer program installed, you can |
d3e8051b | 22619 | typeset and print this manual. First switch to the @file{gdb} |
8e04817f AC |
22620 | subdirectory of the main source directory (for example, to |
22621 | @file{gdb-@value{GDBVN}/gdb}) and type: | |
c4555f82 | 22622 | |
474c8240 | 22623 | @smallexample |
8e04817f | 22624 | make gdb.dvi |
474c8240 | 22625 | @end smallexample |
c4555f82 | 22626 | |
8e04817f | 22627 | Then give @file{gdb.dvi} to your @sc{dvi} printing program. |
c4555f82 | 22628 | |
8e04817f AC |
22629 | @node Installing GDB |
22630 | @appendix Installing @value{GDBN} | |
8e04817f | 22631 | @cindex installation |
c4555f82 | 22632 | |
7fa2210b DJ |
22633 | @menu |
22634 | * Requirements:: Requirements for building @value{GDBN} | |
db2e3e2e | 22635 | * Running Configure:: Invoking the @value{GDBN} @file{configure} script |
7fa2210b DJ |
22636 | * Separate Objdir:: Compiling @value{GDBN} in another directory |
22637 | * Config Names:: Specifying names for hosts and targets | |
22638 | * Configure Options:: Summary of options for configure | |
22639 | @end menu | |
22640 | ||
22641 | @node Requirements | |
79a6e687 | 22642 | @section Requirements for Building @value{GDBN} |
7fa2210b DJ |
22643 | @cindex building @value{GDBN}, requirements for |
22644 | ||
22645 | Building @value{GDBN} requires various tools and packages to be available. | |
22646 | Other packages will be used only if they are found. | |
22647 | ||
79a6e687 | 22648 | @heading Tools/Packages Necessary for Building @value{GDBN} |
7fa2210b DJ |
22649 | @table @asis |
22650 | @item ISO C90 compiler | |
22651 | @value{GDBN} is written in ISO C90. It should be buildable with any | |
22652 | working C90 compiler, e.g.@: GCC. | |
22653 | ||
22654 | @end table | |
22655 | ||
79a6e687 | 22656 | @heading Tools/Packages Optional for Building @value{GDBN} |
7fa2210b DJ |
22657 | @table @asis |
22658 | @item Expat | |
123dc839 | 22659 | @anchor{Expat} |
7fa2210b DJ |
22660 | @value{GDBN} can use the Expat XML parsing library. This library may be |
22661 | included with your operating system distribution; if it is not, you | |
22662 | can get the latest version from @url{http://expat.sourceforge.net}. | |
db2e3e2e | 22663 | The @file{configure} script will search for this library in several |
7fa2210b DJ |
22664 | standard locations; if it is installed in an unusual path, you can |
22665 | use the @option{--with-libexpat-prefix} option to specify its location. | |
22666 | ||
9cceb671 DJ |
22667 | Expat is used for: |
22668 | ||
22669 | @itemize @bullet | |
22670 | @item | |
22671 | Remote protocol memory maps (@pxref{Memory Map Format}) | |
22672 | @item | |
22673 | Target descriptions (@pxref{Target Descriptions}) | |
22674 | @item | |
22675 | Remote shared library lists (@pxref{Library List Format}) | |
22676 | @item | |
22677 | MS-Windows shared libraries (@pxref{Shared Libraries}) | |
22678 | @end itemize | |
7fa2210b DJ |
22679 | |
22680 | @end table | |
22681 | ||
22682 | @node Running Configure | |
db2e3e2e | 22683 | @section Invoking the @value{GDBN} @file{configure} Script |
7fa2210b | 22684 | @cindex configuring @value{GDBN} |
db2e3e2e | 22685 | @value{GDBN} comes with a @file{configure} script that automates the process |
8e04817f AC |
22686 | of preparing @value{GDBN} for installation; you can then use @code{make} to |
22687 | build the @code{gdb} program. | |
22688 | @iftex | |
22689 | @c irrelevant in info file; it's as current as the code it lives with. | |
22690 | @footnote{If you have a more recent version of @value{GDBN} than @value{GDBVN}, | |
22691 | look at the @file{README} file in the sources; we may have improved the | |
22692 | installation procedures since publishing this manual.} | |
22693 | @end iftex | |
c4555f82 | 22694 | |
8e04817f AC |
22695 | The @value{GDBN} distribution includes all the source code you need for |
22696 | @value{GDBN} in a single directory, whose name is usually composed by | |
22697 | appending the version number to @samp{gdb}. | |
c4555f82 | 22698 | |
8e04817f AC |
22699 | For example, the @value{GDBN} version @value{GDBVN} distribution is in the |
22700 | @file{gdb-@value{GDBVN}} directory. That directory contains: | |
c4555f82 | 22701 | |
8e04817f AC |
22702 | @table @code |
22703 | @item gdb-@value{GDBVN}/configure @r{(and supporting files)} | |
22704 | script for configuring @value{GDBN} and all its supporting libraries | |
c4555f82 | 22705 | |
8e04817f AC |
22706 | @item gdb-@value{GDBVN}/gdb |
22707 | the source specific to @value{GDBN} itself | |
c4555f82 | 22708 | |
8e04817f AC |
22709 | @item gdb-@value{GDBVN}/bfd |
22710 | source for the Binary File Descriptor library | |
c906108c | 22711 | |
8e04817f AC |
22712 | @item gdb-@value{GDBVN}/include |
22713 | @sc{gnu} include files | |
c906108c | 22714 | |
8e04817f AC |
22715 | @item gdb-@value{GDBVN}/libiberty |
22716 | source for the @samp{-liberty} free software library | |
c906108c | 22717 | |
8e04817f AC |
22718 | @item gdb-@value{GDBVN}/opcodes |
22719 | source for the library of opcode tables and disassemblers | |
c906108c | 22720 | |
8e04817f AC |
22721 | @item gdb-@value{GDBVN}/readline |
22722 | source for the @sc{gnu} command-line interface | |
c906108c | 22723 | |
8e04817f AC |
22724 | @item gdb-@value{GDBVN}/glob |
22725 | source for the @sc{gnu} filename pattern-matching subroutine | |
c906108c | 22726 | |
8e04817f AC |
22727 | @item gdb-@value{GDBVN}/mmalloc |
22728 | source for the @sc{gnu} memory-mapped malloc package | |
22729 | @end table | |
c906108c | 22730 | |
db2e3e2e | 22731 | The simplest way to configure and build @value{GDBN} is to run @file{configure} |
8e04817f AC |
22732 | from the @file{gdb-@var{version-number}} source directory, which in |
22733 | this example is the @file{gdb-@value{GDBVN}} directory. | |
c906108c | 22734 | |
8e04817f | 22735 | First switch to the @file{gdb-@var{version-number}} source directory |
db2e3e2e | 22736 | if you are not already in it; then run @file{configure}. Pass the |
8e04817f AC |
22737 | identifier for the platform on which @value{GDBN} will run as an |
22738 | argument. | |
c906108c | 22739 | |
8e04817f | 22740 | For example: |
c906108c | 22741 | |
474c8240 | 22742 | @smallexample |
8e04817f AC |
22743 | cd gdb-@value{GDBVN} |
22744 | ./configure @var{host} | |
22745 | make | |
474c8240 | 22746 | @end smallexample |
c906108c | 22747 | |
8e04817f AC |
22748 | @noindent |
22749 | where @var{host} is an identifier such as @samp{sun4} or | |
22750 | @samp{decstation}, that identifies the platform where @value{GDBN} will run. | |
db2e3e2e | 22751 | (You can often leave off @var{host}; @file{configure} tries to guess the |
8e04817f | 22752 | correct value by examining your system.) |
c906108c | 22753 | |
8e04817f AC |
22754 | Running @samp{configure @var{host}} and then running @code{make} builds the |
22755 | @file{bfd}, @file{readline}, @file{mmalloc}, and @file{libiberty} | |
22756 | libraries, then @code{gdb} itself. The configured source files, and the | |
22757 | binaries, are left in the corresponding source directories. | |
c906108c | 22758 | |
8e04817f | 22759 | @need 750 |
db2e3e2e | 22760 | @file{configure} is a Bourne-shell (@code{/bin/sh}) script; if your |
8e04817f AC |
22761 | system does not recognize this automatically when you run a different |
22762 | shell, you may need to run @code{sh} on it explicitly: | |
c906108c | 22763 | |
474c8240 | 22764 | @smallexample |
8e04817f | 22765 | sh configure @var{host} |
474c8240 | 22766 | @end smallexample |
c906108c | 22767 | |
db2e3e2e | 22768 | If you run @file{configure} from a directory that contains source |
8e04817f | 22769 | directories for multiple libraries or programs, such as the |
db2e3e2e BW |
22770 | @file{gdb-@value{GDBVN}} source directory for version @value{GDBVN}, |
22771 | @file{configure} | |
8e04817f AC |
22772 | creates configuration files for every directory level underneath (unless |
22773 | you tell it not to, with the @samp{--norecursion} option). | |
22774 | ||
db2e3e2e | 22775 | You should run the @file{configure} script from the top directory in the |
94e91d6d | 22776 | source tree, the @file{gdb-@var{version-number}} directory. If you run |
db2e3e2e | 22777 | @file{configure} from one of the subdirectories, you will configure only |
94e91d6d | 22778 | that subdirectory. That is usually not what you want. In particular, |
db2e3e2e | 22779 | if you run the first @file{configure} from the @file{gdb} subdirectory |
94e91d6d MC |
22780 | of the @file{gdb-@var{version-number}} directory, you will omit the |
22781 | configuration of @file{bfd}, @file{readline}, and other sibling | |
22782 | directories of the @file{gdb} subdirectory. This leads to build errors | |
22783 | about missing include files such as @file{bfd/bfd.h}. | |
c906108c | 22784 | |
8e04817f AC |
22785 | You can install @code{@value{GDBP}} anywhere; it has no hardwired paths. |
22786 | However, you should make sure that the shell on your path (named by | |
22787 | the @samp{SHELL} environment variable) is publicly readable. Remember | |
22788 | that @value{GDBN} uses the shell to start your program---some systems refuse to | |
22789 | let @value{GDBN} debug child processes whose programs are not readable. | |
c906108c | 22790 | |
8e04817f | 22791 | @node Separate Objdir |
79a6e687 | 22792 | @section Compiling @value{GDBN} in Another Directory |
c906108c | 22793 | |
8e04817f AC |
22794 | If you want to run @value{GDBN} versions for several host or target machines, |
22795 | you need a different @code{gdb} compiled for each combination of | |
db2e3e2e | 22796 | host and target. @file{configure} is designed to make this easy by |
8e04817f AC |
22797 | allowing you to generate each configuration in a separate subdirectory, |
22798 | rather than in the source directory. If your @code{make} program | |
22799 | handles the @samp{VPATH} feature (@sc{gnu} @code{make} does), running | |
22800 | @code{make} in each of these directories builds the @code{gdb} | |
22801 | program specified there. | |
c906108c | 22802 | |
db2e3e2e | 22803 | To build @code{gdb} in a separate directory, run @file{configure} |
8e04817f | 22804 | with the @samp{--srcdir} option to specify where to find the source. |
db2e3e2e BW |
22805 | (You also need to specify a path to find @file{configure} |
22806 | itself from your working directory. If the path to @file{configure} | |
8e04817f AC |
22807 | would be the same as the argument to @samp{--srcdir}, you can leave out |
22808 | the @samp{--srcdir} option; it is assumed.) | |
c906108c | 22809 | |
8e04817f AC |
22810 | For example, with version @value{GDBVN}, you can build @value{GDBN} in a |
22811 | separate directory for a Sun 4 like this: | |
c906108c | 22812 | |
474c8240 | 22813 | @smallexample |
8e04817f AC |
22814 | @group |
22815 | cd gdb-@value{GDBVN} | |
22816 | mkdir ../gdb-sun4 | |
22817 | cd ../gdb-sun4 | |
22818 | ../gdb-@value{GDBVN}/configure sun4 | |
22819 | make | |
22820 | @end group | |
474c8240 | 22821 | @end smallexample |
c906108c | 22822 | |
db2e3e2e | 22823 | When @file{configure} builds a configuration using a remote source |
8e04817f AC |
22824 | directory, it creates a tree for the binaries with the same structure |
22825 | (and using the same names) as the tree under the source directory. In | |
22826 | the example, you'd find the Sun 4 library @file{libiberty.a} in the | |
22827 | directory @file{gdb-sun4/libiberty}, and @value{GDBN} itself in | |
22828 | @file{gdb-sun4/gdb}. | |
c906108c | 22829 | |
94e91d6d MC |
22830 | Make sure that your path to the @file{configure} script has just one |
22831 | instance of @file{gdb} in it. If your path to @file{configure} looks | |
22832 | like @file{../gdb-@value{GDBVN}/gdb/configure}, you are configuring only | |
22833 | one subdirectory of @value{GDBN}, not the whole package. This leads to | |
22834 | build errors about missing include files such as @file{bfd/bfd.h}. | |
22835 | ||
8e04817f AC |
22836 | One popular reason to build several @value{GDBN} configurations in separate |
22837 | directories is to configure @value{GDBN} for cross-compiling (where | |
22838 | @value{GDBN} runs on one machine---the @dfn{host}---while debugging | |
22839 | programs that run on another machine---the @dfn{target}). | |
22840 | You specify a cross-debugging target by | |
db2e3e2e | 22841 | giving the @samp{--target=@var{target}} option to @file{configure}. |
c906108c | 22842 | |
8e04817f AC |
22843 | When you run @code{make} to build a program or library, you must run |
22844 | it in a configured directory---whatever directory you were in when you | |
db2e3e2e | 22845 | called @file{configure} (or one of its subdirectories). |
c906108c | 22846 | |
db2e3e2e | 22847 | The @code{Makefile} that @file{configure} generates in each source |
8e04817f AC |
22848 | directory also runs recursively. If you type @code{make} in a source |
22849 | directory such as @file{gdb-@value{GDBVN}} (or in a separate configured | |
22850 | directory configured with @samp{--srcdir=@var{dirname}/gdb-@value{GDBVN}}), you | |
22851 | will build all the required libraries, and then build GDB. | |
c906108c | 22852 | |
8e04817f AC |
22853 | When you have multiple hosts or targets configured in separate |
22854 | directories, you can run @code{make} on them in parallel (for example, | |
22855 | if they are NFS-mounted on each of the hosts); they will not interfere | |
22856 | with each other. | |
c906108c | 22857 | |
8e04817f | 22858 | @node Config Names |
79a6e687 | 22859 | @section Specifying Names for Hosts and Targets |
c906108c | 22860 | |
db2e3e2e | 22861 | The specifications used for hosts and targets in the @file{configure} |
8e04817f AC |
22862 | script are based on a three-part naming scheme, but some short predefined |
22863 | aliases are also supported. The full naming scheme encodes three pieces | |
22864 | of information in the following pattern: | |
c906108c | 22865 | |
474c8240 | 22866 | @smallexample |
8e04817f | 22867 | @var{architecture}-@var{vendor}-@var{os} |
474c8240 | 22868 | @end smallexample |
c906108c | 22869 | |
8e04817f AC |
22870 | For example, you can use the alias @code{sun4} as a @var{host} argument, |
22871 | or as the value for @var{target} in a @code{--target=@var{target}} | |
22872 | option. The equivalent full name is @samp{sparc-sun-sunos4}. | |
c906108c | 22873 | |
db2e3e2e | 22874 | The @file{configure} script accompanying @value{GDBN} does not provide |
8e04817f | 22875 | any query facility to list all supported host and target names or |
db2e3e2e | 22876 | aliases. @file{configure} calls the Bourne shell script |
8e04817f AC |
22877 | @code{config.sub} to map abbreviations to full names; you can read the |
22878 | script, if you wish, or you can use it to test your guesses on | |
22879 | abbreviations---for example: | |
c906108c | 22880 | |
8e04817f AC |
22881 | @smallexample |
22882 | % sh config.sub i386-linux | |
22883 | i386-pc-linux-gnu | |
22884 | % sh config.sub alpha-linux | |
22885 | alpha-unknown-linux-gnu | |
22886 | % sh config.sub hp9k700 | |
22887 | hppa1.1-hp-hpux | |
22888 | % sh config.sub sun4 | |
22889 | sparc-sun-sunos4.1.1 | |
22890 | % sh config.sub sun3 | |
22891 | m68k-sun-sunos4.1.1 | |
22892 | % sh config.sub i986v | |
22893 | Invalid configuration `i986v': machine `i986v' not recognized | |
22894 | @end smallexample | |
c906108c | 22895 | |
8e04817f AC |
22896 | @noindent |
22897 | @code{config.sub} is also distributed in the @value{GDBN} source | |
22898 | directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}). | |
d700128c | 22899 | |
8e04817f | 22900 | @node Configure Options |
db2e3e2e | 22901 | @section @file{configure} Options |
c906108c | 22902 | |
db2e3e2e BW |
22903 | Here is a summary of the @file{configure} options and arguments that |
22904 | are most often useful for building @value{GDBN}. @file{configure} also has | |
8e04817f | 22905 | several other options not listed here. @inforef{What Configure |
db2e3e2e | 22906 | Does,,configure.info}, for a full explanation of @file{configure}. |
c906108c | 22907 | |
474c8240 | 22908 | @smallexample |
8e04817f AC |
22909 | configure @r{[}--help@r{]} |
22910 | @r{[}--prefix=@var{dir}@r{]} | |
22911 | @r{[}--exec-prefix=@var{dir}@r{]} | |
22912 | @r{[}--srcdir=@var{dirname}@r{]} | |
22913 | @r{[}--norecursion@r{]} @r{[}--rm@r{]} | |
22914 | @r{[}--target=@var{target}@r{]} | |
22915 | @var{host} | |
474c8240 | 22916 | @end smallexample |
c906108c | 22917 | |
8e04817f AC |
22918 | @noindent |
22919 | You may introduce options with a single @samp{-} rather than | |
22920 | @samp{--} if you prefer; but you may abbreviate option names if you use | |
22921 | @samp{--}. | |
c906108c | 22922 | |
8e04817f AC |
22923 | @table @code |
22924 | @item --help | |
db2e3e2e | 22925 | Display a quick summary of how to invoke @file{configure}. |
c906108c | 22926 | |
8e04817f AC |
22927 | @item --prefix=@var{dir} |
22928 | Configure the source to install programs and files under directory | |
22929 | @file{@var{dir}}. | |
c906108c | 22930 | |
8e04817f AC |
22931 | @item --exec-prefix=@var{dir} |
22932 | Configure the source to install programs under directory | |
22933 | @file{@var{dir}}. | |
c906108c | 22934 | |
8e04817f AC |
22935 | @c avoid splitting the warning from the explanation: |
22936 | @need 2000 | |
22937 | @item --srcdir=@var{dirname} | |
22938 | @strong{Warning: using this option requires @sc{gnu} @code{make}, or another | |
22939 | @code{make} that implements the @code{VPATH} feature.}@* | |
22940 | Use this option to make configurations in directories separate from the | |
22941 | @value{GDBN} source directories. Among other things, you can use this to | |
22942 | build (or maintain) several configurations simultaneously, in separate | |
db2e3e2e | 22943 | directories. @file{configure} writes configuration-specific files in |
8e04817f | 22944 | the current directory, but arranges for them to use the source in the |
db2e3e2e | 22945 | directory @var{dirname}. @file{configure} creates directories under |
8e04817f AC |
22946 | the working directory in parallel to the source directories below |
22947 | @var{dirname}. | |
c906108c | 22948 | |
8e04817f | 22949 | @item --norecursion |
db2e3e2e | 22950 | Configure only the directory level where @file{configure} is executed; do not |
8e04817f | 22951 | propagate configuration to subdirectories. |
c906108c | 22952 | |
8e04817f AC |
22953 | @item --target=@var{target} |
22954 | Configure @value{GDBN} for cross-debugging programs running on the specified | |
22955 | @var{target}. Without this option, @value{GDBN} is configured to debug | |
22956 | programs that run on the same machine (@var{host}) as @value{GDBN} itself. | |
c906108c | 22957 | |
8e04817f | 22958 | There is no convenient way to generate a list of all available targets. |
c906108c | 22959 | |
8e04817f AC |
22960 | @item @var{host} @dots{} |
22961 | Configure @value{GDBN} to run on the specified @var{host}. | |
c906108c | 22962 | |
8e04817f AC |
22963 | There is no convenient way to generate a list of all available hosts. |
22964 | @end table | |
c906108c | 22965 | |
8e04817f AC |
22966 | There are many other options available as well, but they are generally |
22967 | needed for special purposes only. | |
c906108c | 22968 | |
8e04817f AC |
22969 | @node Maintenance Commands |
22970 | @appendix Maintenance Commands | |
22971 | @cindex maintenance commands | |
22972 | @cindex internal commands | |
c906108c | 22973 | |
8e04817f | 22974 | In addition to commands intended for @value{GDBN} users, @value{GDBN} |
09d4efe1 EZ |
22975 | includes a number of commands intended for @value{GDBN} developers, |
22976 | that are not documented elsewhere in this manual. These commands are | |
da316a69 EZ |
22977 | provided here for reference. (For commands that turn on debugging |
22978 | messages, see @ref{Debugging Output}.) | |
c906108c | 22979 | |
8e04817f | 22980 | @table @code |
09d4efe1 EZ |
22981 | @kindex maint agent |
22982 | @item maint agent @var{expression} | |
22983 | Translate the given @var{expression} into remote agent bytecodes. | |
22984 | This command is useful for debugging the Agent Expression mechanism | |
22985 | (@pxref{Agent Expressions}). | |
22986 | ||
8e04817f AC |
22987 | @kindex maint info breakpoints |
22988 | @item @anchor{maint info breakpoints}maint info breakpoints | |
22989 | Using the same format as @samp{info breakpoints}, display both the | |
22990 | breakpoints you've set explicitly, and those @value{GDBN} is using for | |
22991 | internal purposes. Internal breakpoints are shown with negative | |
22992 | breakpoint numbers. The type column identifies what kind of breakpoint | |
22993 | is shown: | |
c906108c | 22994 | |
8e04817f AC |
22995 | @table @code |
22996 | @item breakpoint | |
22997 | Normal, explicitly set breakpoint. | |
c906108c | 22998 | |
8e04817f AC |
22999 | @item watchpoint |
23000 | Normal, explicitly set watchpoint. | |
c906108c | 23001 | |
8e04817f AC |
23002 | @item longjmp |
23003 | Internal breakpoint, used to handle correctly stepping through | |
23004 | @code{longjmp} calls. | |
c906108c | 23005 | |
8e04817f AC |
23006 | @item longjmp resume |
23007 | Internal breakpoint at the target of a @code{longjmp}. | |
c906108c | 23008 | |
8e04817f AC |
23009 | @item until |
23010 | Temporary internal breakpoint used by the @value{GDBN} @code{until} command. | |
c906108c | 23011 | |
8e04817f AC |
23012 | @item finish |
23013 | Temporary internal breakpoint used by the @value{GDBN} @code{finish} command. | |
c906108c | 23014 | |
8e04817f AC |
23015 | @item shlib events |
23016 | Shared library events. | |
c906108c | 23017 | |
8e04817f | 23018 | @end table |
c906108c | 23019 | |
09d4efe1 EZ |
23020 | @kindex maint check-symtabs |
23021 | @item maint check-symtabs | |
23022 | Check the consistency of psymtabs and symtabs. | |
23023 | ||
23024 | @kindex maint cplus first_component | |
23025 | @item maint cplus first_component @var{name} | |
23026 | Print the first C@t{++} class/namespace component of @var{name}. | |
23027 | ||
23028 | @kindex maint cplus namespace | |
23029 | @item maint cplus namespace | |
23030 | Print the list of possible C@t{++} namespaces. | |
23031 | ||
23032 | @kindex maint demangle | |
23033 | @item maint demangle @var{name} | |
d3e8051b | 23034 | Demangle a C@t{++} or Objective-C mangled @var{name}. |
09d4efe1 EZ |
23035 | |
23036 | @kindex maint deprecate | |
23037 | @kindex maint undeprecate | |
23038 | @cindex deprecated commands | |
23039 | @item maint deprecate @var{command} @r{[}@var{replacement}@r{]} | |
23040 | @itemx maint undeprecate @var{command} | |
23041 | Deprecate or undeprecate the named @var{command}. Deprecated commands | |
23042 | cause @value{GDBN} to issue a warning when you use them. The optional | |
23043 | argument @var{replacement} says which newer command should be used in | |
23044 | favor of the deprecated one; if it is given, @value{GDBN} will mention | |
23045 | the replacement as part of the warning. | |
23046 | ||
23047 | @kindex maint dump-me | |
23048 | @item maint dump-me | |
721c2651 | 23049 | @cindex @code{SIGQUIT} signal, dump core of @value{GDBN} |
09d4efe1 | 23050 | Cause a fatal signal in the debugger and force it to dump its core. |
721c2651 EZ |
23051 | This is supported only on systems which support aborting a program |
23052 | with the @code{SIGQUIT} signal. | |
09d4efe1 | 23053 | |
8d30a00d AC |
23054 | @kindex maint internal-error |
23055 | @kindex maint internal-warning | |
09d4efe1 EZ |
23056 | @item maint internal-error @r{[}@var{message-text}@r{]} |
23057 | @itemx maint internal-warning @r{[}@var{message-text}@r{]} | |
8d30a00d AC |
23058 | Cause @value{GDBN} to call the internal function @code{internal_error} |
23059 | or @code{internal_warning} and hence behave as though an internal error | |
23060 | or internal warning has been detected. In addition to reporting the | |
23061 | internal problem, these functions give the user the opportunity to | |
23062 | either quit @value{GDBN} or create a core file of the current | |
23063 | @value{GDBN} session. | |
23064 | ||
09d4efe1 EZ |
23065 | These commands take an optional parameter @var{message-text} that is |
23066 | used as the text of the error or warning message. | |
23067 | ||
d3e8051b | 23068 | Here's an example of using @code{internal-error}: |
09d4efe1 | 23069 | |
8d30a00d | 23070 | @smallexample |
f7dc1244 | 23071 | (@value{GDBP}) @kbd{maint internal-error testing, 1, 2} |
8d30a00d AC |
23072 | @dots{}/maint.c:121: internal-error: testing, 1, 2 |
23073 | A problem internal to GDB has been detected. Further | |
23074 | debugging may prove unreliable. | |
23075 | Quit this debugging session? (y or n) @kbd{n} | |
23076 | Create a core file? (y or n) @kbd{n} | |
f7dc1244 | 23077 | (@value{GDBP}) |
8d30a00d AC |
23078 | @end smallexample |
23079 | ||
09d4efe1 EZ |
23080 | @kindex maint packet |
23081 | @item maint packet @var{text} | |
23082 | If @value{GDBN} is talking to an inferior via the serial protocol, | |
23083 | then this command sends the string @var{text} to the inferior, and | |
23084 | displays the response packet. @value{GDBN} supplies the initial | |
23085 | @samp{$} character, the terminating @samp{#} character, and the | |
23086 | checksum. | |
23087 | ||
23088 | @kindex maint print architecture | |
23089 | @item maint print architecture @r{[}@var{file}@r{]} | |
23090 | Print the entire architecture configuration. The optional argument | |
23091 | @var{file} names the file where the output goes. | |
8d30a00d | 23092 | |
81adfced DJ |
23093 | @kindex maint print c-tdesc |
23094 | @item maint print c-tdesc | |
23095 | Print the current target description (@pxref{Target Descriptions}) as | |
23096 | a C source file. The created source file can be used in @value{GDBN} | |
23097 | when an XML parser is not available to parse the description. | |
23098 | ||
00905d52 AC |
23099 | @kindex maint print dummy-frames |
23100 | @item maint print dummy-frames | |
00905d52 AC |
23101 | Prints the contents of @value{GDBN}'s internal dummy-frame stack. |
23102 | ||
23103 | @smallexample | |
f7dc1244 | 23104 | (@value{GDBP}) @kbd{b add} |
00905d52 | 23105 | @dots{} |
f7dc1244 | 23106 | (@value{GDBP}) @kbd{print add(2,3)} |
00905d52 AC |
23107 | Breakpoint 2, add (a=2, b=3) at @dots{} |
23108 | 58 return (a + b); | |
23109 | The program being debugged stopped while in a function called from GDB. | |
23110 | @dots{} | |
f7dc1244 | 23111 | (@value{GDBP}) @kbd{maint print dummy-frames} |
00905d52 AC |
23112 | 0x1a57c80: pc=0x01014068 fp=0x0200bddc sp=0x0200bdd6 |
23113 | top=0x0200bdd4 id=@{stack=0x200bddc,code=0x101405c@} | |
23114 | call_lo=0x01014000 call_hi=0x01014001 | |
f7dc1244 | 23115 | (@value{GDBP}) |
00905d52 AC |
23116 | @end smallexample |
23117 | ||
23118 | Takes an optional file parameter. | |
23119 | ||
0680b120 AC |
23120 | @kindex maint print registers |
23121 | @kindex maint print raw-registers | |
23122 | @kindex maint print cooked-registers | |
617073a9 | 23123 | @kindex maint print register-groups |
09d4efe1 EZ |
23124 | @item maint print registers @r{[}@var{file}@r{]} |
23125 | @itemx maint print raw-registers @r{[}@var{file}@r{]} | |
23126 | @itemx maint print cooked-registers @r{[}@var{file}@r{]} | |
23127 | @itemx maint print register-groups @r{[}@var{file}@r{]} | |
0680b120 AC |
23128 | Print @value{GDBN}'s internal register data structures. |
23129 | ||
617073a9 AC |
23130 | The command @code{maint print raw-registers} includes the contents of |
23131 | the raw register cache; the command @code{maint print cooked-registers} | |
23132 | includes the (cooked) value of all registers; and the command | |
23133 | @code{maint print register-groups} includes the groups that each | |
23134 | register is a member of. @xref{Registers,, Registers, gdbint, | |
23135 | @value{GDBN} Internals}. | |
0680b120 | 23136 | |
09d4efe1 EZ |
23137 | These commands take an optional parameter, a file name to which to |
23138 | write the information. | |
0680b120 | 23139 | |
617073a9 | 23140 | @kindex maint print reggroups |
09d4efe1 EZ |
23141 | @item maint print reggroups @r{[}@var{file}@r{]} |
23142 | Print @value{GDBN}'s internal register group data structures. The | |
23143 | optional argument @var{file} tells to what file to write the | |
23144 | information. | |
617073a9 | 23145 | |
09d4efe1 | 23146 | The register groups info looks like this: |
617073a9 AC |
23147 | |
23148 | @smallexample | |
f7dc1244 | 23149 | (@value{GDBP}) @kbd{maint print reggroups} |
b383017d RM |
23150 | Group Type |
23151 | general user | |
23152 | float user | |
23153 | all user | |
23154 | vector user | |
23155 | system user | |
23156 | save internal | |
23157 | restore internal | |
617073a9 AC |
23158 | @end smallexample |
23159 | ||
09d4efe1 EZ |
23160 | @kindex flushregs |
23161 | @item flushregs | |
23162 | This command forces @value{GDBN} to flush its internal register cache. | |
23163 | ||
23164 | @kindex maint print objfiles | |
23165 | @cindex info for known object files | |
23166 | @item maint print objfiles | |
23167 | Print a dump of all known object files. For each object file, this | |
23168 | command prints its name, address in memory, and all of its psymtabs | |
23169 | and symtabs. | |
23170 | ||
23171 | @kindex maint print statistics | |
23172 | @cindex bcache statistics | |
23173 | @item maint print statistics | |
23174 | This command prints, for each object file in the program, various data | |
23175 | about that object file followed by the byte cache (@dfn{bcache}) | |
23176 | statistics for the object file. The objfile data includes the number | |
d3e8051b | 23177 | of minimal, partial, full, and stabs symbols, the number of types |
09d4efe1 EZ |
23178 | defined by the objfile, the number of as yet unexpanded psym tables, |
23179 | the number of line tables and string tables, and the amount of memory | |
23180 | used by the various tables. The bcache statistics include the counts, | |
23181 | sizes, and counts of duplicates of all and unique objects, max, | |
23182 | average, and median entry size, total memory used and its overhead and | |
23183 | savings, and various measures of the hash table size and chain | |
23184 | lengths. | |
23185 | ||
c7ba131e JB |
23186 | @kindex maint print target-stack |
23187 | @cindex target stack description | |
23188 | @item maint print target-stack | |
23189 | A @dfn{target} is an interface between the debugger and a particular | |
23190 | kind of file or process. Targets can be stacked in @dfn{strata}, | |
23191 | so that more than one target can potentially respond to a request. | |
23192 | In particular, memory accesses will walk down the stack of targets | |
23193 | until they find a target that is interested in handling that particular | |
23194 | address. | |
23195 | ||
23196 | This command prints a short description of each layer that was pushed on | |
23197 | the @dfn{target stack}, starting from the top layer down to the bottom one. | |
23198 | ||
09d4efe1 EZ |
23199 | @kindex maint print type |
23200 | @cindex type chain of a data type | |
23201 | @item maint print type @var{expr} | |
23202 | Print the type chain for a type specified by @var{expr}. The argument | |
23203 | can be either a type name or a symbol. If it is a symbol, the type of | |
23204 | that symbol is described. The type chain produced by this command is | |
23205 | a recursive definition of the data type as stored in @value{GDBN}'s | |
23206 | data structures, including its flags and contained types. | |
23207 | ||
23208 | @kindex maint set dwarf2 max-cache-age | |
23209 | @kindex maint show dwarf2 max-cache-age | |
23210 | @item maint set dwarf2 max-cache-age | |
23211 | @itemx maint show dwarf2 max-cache-age | |
23212 | Control the DWARF 2 compilation unit cache. | |
23213 | ||
23214 | @cindex DWARF 2 compilation units cache | |
23215 | In object files with inter-compilation-unit references, such as those | |
23216 | produced by the GCC option @samp{-feliminate-dwarf2-dups}, the DWARF 2 | |
23217 | reader needs to frequently refer to previously read compilation units. | |
23218 | This setting controls how long a compilation unit will remain in the | |
23219 | cache if it is not referenced. A higher limit means that cached | |
23220 | compilation units will be stored in memory longer, and more total | |
23221 | memory will be used. Setting it to zero disables caching, which will | |
23222 | slow down @value{GDBN} startup, but reduce memory consumption. | |
23223 | ||
e7ba9c65 DJ |
23224 | @kindex maint set profile |
23225 | @kindex maint show profile | |
23226 | @cindex profiling GDB | |
23227 | @item maint set profile | |
23228 | @itemx maint show profile | |
23229 | Control profiling of @value{GDBN}. | |
23230 | ||
23231 | Profiling will be disabled until you use the @samp{maint set profile} | |
23232 | command to enable it. When you enable profiling, the system will begin | |
23233 | collecting timing and execution count data; when you disable profiling or | |
23234 | exit @value{GDBN}, the results will be written to a log file. Remember that | |
23235 | if you use profiling, @value{GDBN} will overwrite the profiling log file | |
23236 | (often called @file{gmon.out}). If you have a record of important profiling | |
23237 | data in a @file{gmon.out} file, be sure to move it to a safe location. | |
23238 | ||
23239 | Configuring with @samp{--enable-profiling} arranges for @value{GDBN} to be | |
b383017d | 23240 | compiled with the @samp{-pg} compiler option. |
e7ba9c65 | 23241 | |
09d4efe1 EZ |
23242 | @kindex maint show-debug-regs |
23243 | @cindex x86 hardware debug registers | |
23244 | @item maint show-debug-regs | |
23245 | Control whether to show variables that mirror the x86 hardware debug | |
23246 | registers. Use @code{ON} to enable, @code{OFF} to disable. If | |
3f94c067 | 23247 | enabled, the debug registers values are shown when @value{GDBN} inserts or |
09d4efe1 EZ |
23248 | removes a hardware breakpoint or watchpoint, and when the inferior |
23249 | triggers a hardware-assisted breakpoint or watchpoint. | |
23250 | ||
23251 | @kindex maint space | |
23252 | @cindex memory used by commands | |
23253 | @item maint space | |
23254 | Control whether to display memory usage for each command. If set to a | |
23255 | nonzero value, @value{GDBN} will display how much memory each command | |
23256 | took, following the command's own output. This can also be requested | |
23257 | by invoking @value{GDBN} with the @option{--statistics} command-line | |
23258 | switch (@pxref{Mode Options}). | |
23259 | ||
23260 | @kindex maint time | |
23261 | @cindex time of command execution | |
23262 | @item maint time | |
23263 | Control whether to display the execution time for each command. If | |
23264 | set to a nonzero value, @value{GDBN} will display how much time it | |
23265 | took to execute each command, following the command's own output. | |
23266 | This can also be requested by invoking @value{GDBN} with the | |
23267 | @option{--statistics} command-line switch (@pxref{Mode Options}). | |
23268 | ||
23269 | @kindex maint translate-address | |
23270 | @item maint translate-address @r{[}@var{section}@r{]} @var{addr} | |
23271 | Find the symbol stored at the location specified by the address | |
23272 | @var{addr} and an optional section name @var{section}. If found, | |
23273 | @value{GDBN} prints the name of the closest symbol and an offset from | |
23274 | the symbol's location to the specified address. This is similar to | |
23275 | the @code{info address} command (@pxref{Symbols}), except that this | |
23276 | command also allows to find symbols in other sections. | |
ae038cb0 | 23277 | |
8e04817f | 23278 | @end table |
c906108c | 23279 | |
9c16f35a EZ |
23280 | The following command is useful for non-interactive invocations of |
23281 | @value{GDBN}, such as in the test suite. | |
23282 | ||
23283 | @table @code | |
23284 | @item set watchdog @var{nsec} | |
23285 | @kindex set watchdog | |
23286 | @cindex watchdog timer | |
23287 | @cindex timeout for commands | |
23288 | Set the maximum number of seconds @value{GDBN} will wait for the | |
23289 | target operation to finish. If this time expires, @value{GDBN} | |
23290 | reports and error and the command is aborted. | |
23291 | ||
23292 | @item show watchdog | |
23293 | Show the current setting of the target wait timeout. | |
23294 | @end table | |
c906108c | 23295 | |
e0ce93ac | 23296 | @node Remote Protocol |
8e04817f | 23297 | @appendix @value{GDBN} Remote Serial Protocol |
c906108c | 23298 | |
ee2d5c50 AC |
23299 | @menu |
23300 | * Overview:: | |
23301 | * Packets:: | |
23302 | * Stop Reply Packets:: | |
23303 | * General Query Packets:: | |
23304 | * Register Packet Format:: | |
9d29849a | 23305 | * Tracepoint Packets:: |
a6b151f1 | 23306 | * Host I/O Packets:: |
9a6253be | 23307 | * Interrupts:: |
ee2d5c50 | 23308 | * Examples:: |
79a6e687 | 23309 | * File-I/O Remote Protocol Extension:: |
cfa9d6d9 | 23310 | * Library List Format:: |
79a6e687 | 23311 | * Memory Map Format:: |
ee2d5c50 AC |
23312 | @end menu |
23313 | ||
23314 | @node Overview | |
23315 | @section Overview | |
23316 | ||
8e04817f AC |
23317 | There may be occasions when you need to know something about the |
23318 | protocol---for example, if there is only one serial port to your target | |
23319 | machine, you might want your program to do something special if it | |
23320 | recognizes a packet meant for @value{GDBN}. | |
c906108c | 23321 | |
d2c6833e | 23322 | In the examples below, @samp{->} and @samp{<-} are used to indicate |
bf06d120 | 23323 | transmitted and received data, respectively. |
c906108c | 23324 | |
8e04817f AC |
23325 | @cindex protocol, @value{GDBN} remote serial |
23326 | @cindex serial protocol, @value{GDBN} remote | |
23327 | @cindex remote serial protocol | |
23328 | All @value{GDBN} commands and responses (other than acknowledgments) are | |
23329 | sent as a @var{packet}. A @var{packet} is introduced with the character | |
23330 | @samp{$}, the actual @var{packet-data}, and the terminating character | |
23331 | @samp{#} followed by a two-digit @var{checksum}: | |
c906108c | 23332 | |
474c8240 | 23333 | @smallexample |
8e04817f | 23334 | @code{$}@var{packet-data}@code{#}@var{checksum} |
474c8240 | 23335 | @end smallexample |
8e04817f | 23336 | @noindent |
c906108c | 23337 | |
8e04817f AC |
23338 | @cindex checksum, for @value{GDBN} remote |
23339 | @noindent | |
23340 | The two-digit @var{checksum} is computed as the modulo 256 sum of all | |
23341 | characters between the leading @samp{$} and the trailing @samp{#} (an | |
23342 | eight bit unsigned checksum). | |
c906108c | 23343 | |
8e04817f AC |
23344 | Implementors should note that prior to @value{GDBN} 5.0 the protocol |
23345 | specification also included an optional two-digit @var{sequence-id}: | |
c906108c | 23346 | |
474c8240 | 23347 | @smallexample |
8e04817f | 23348 | @code{$}@var{sequence-id}@code{:}@var{packet-data}@code{#}@var{checksum} |
474c8240 | 23349 | @end smallexample |
c906108c | 23350 | |
8e04817f AC |
23351 | @cindex sequence-id, for @value{GDBN} remote |
23352 | @noindent | |
23353 | That @var{sequence-id} was appended to the acknowledgment. @value{GDBN} | |
23354 | has never output @var{sequence-id}s. Stubs that handle packets added | |
23355 | since @value{GDBN} 5.0 must not accept @var{sequence-id}. | |
c906108c | 23356 | |
8e04817f AC |
23357 | @cindex acknowledgment, for @value{GDBN} remote |
23358 | When either the host or the target machine receives a packet, the first | |
23359 | response expected is an acknowledgment: either @samp{+} (to indicate | |
23360 | the package was received correctly) or @samp{-} (to request | |
23361 | retransmission): | |
c906108c | 23362 | |
474c8240 | 23363 | @smallexample |
d2c6833e AC |
23364 | -> @code{$}@var{packet-data}@code{#}@var{checksum} |
23365 | <- @code{+} | |
474c8240 | 23366 | @end smallexample |
8e04817f | 23367 | @noindent |
53a5351d | 23368 | |
8e04817f AC |
23369 | The host (@value{GDBN}) sends @var{command}s, and the target (the |
23370 | debugging stub incorporated in your program) sends a @var{response}. In | |
23371 | the case of step and continue @var{command}s, the response is only sent | |
23372 | when the operation has completed (the target has again stopped). | |
c906108c | 23373 | |
8e04817f AC |
23374 | @var{packet-data} consists of a sequence of characters with the |
23375 | exception of @samp{#} and @samp{$} (see @samp{X} packet for additional | |
23376 | exceptions). | |
c906108c | 23377 | |
ee2d5c50 | 23378 | @cindex remote protocol, field separator |
0876f84a | 23379 | Fields within the packet should be separated using @samp{,} @samp{;} or |
8e04817f | 23380 | @samp{:}. Except where otherwise noted all numbers are represented in |
ee2d5c50 | 23381 | @sc{hex} with leading zeros suppressed. |
c906108c | 23382 | |
8e04817f AC |
23383 | Implementors should note that prior to @value{GDBN} 5.0, the character |
23384 | @samp{:} could not appear as the third character in a packet (as it | |
23385 | would potentially conflict with the @var{sequence-id}). | |
c906108c | 23386 | |
0876f84a DJ |
23387 | @cindex remote protocol, binary data |
23388 | @anchor{Binary Data} | |
23389 | Binary data in most packets is encoded either as two hexadecimal | |
23390 | digits per byte of binary data. This allowed the traditional remote | |
23391 | protocol to work over connections which were only seven-bit clean. | |
23392 | Some packets designed more recently assume an eight-bit clean | |
23393 | connection, and use a more efficient encoding to send and receive | |
23394 | binary data. | |
23395 | ||
23396 | The binary data representation uses @code{7d} (@sc{ascii} @samp{@}}) | |
23397 | as an escape character. Any escaped byte is transmitted as the escape | |
23398 | character followed by the original character XORed with @code{0x20}. | |
23399 | For example, the byte @code{0x7d} would be transmitted as the two | |
23400 | bytes @code{0x7d 0x5d}. The bytes @code{0x23} (@sc{ascii} @samp{#}), | |
23401 | @code{0x24} (@sc{ascii} @samp{$}), and @code{0x7d} (@sc{ascii} | |
23402 | @samp{@}}) must always be escaped. Responses sent by the stub | |
23403 | must also escape @code{0x2a} (@sc{ascii} @samp{*}), so that it | |
23404 | is not interpreted as the start of a run-length encoded sequence | |
23405 | (described next). | |
23406 | ||
1d3811f6 DJ |
23407 | Response @var{data} can be run-length encoded to save space. |
23408 | Run-length encoding replaces runs of identical characters with one | |
23409 | instance of the repeated character, followed by a @samp{*} and a | |
23410 | repeat count. The repeat count is itself sent encoded, to avoid | |
23411 | binary characters in @var{data}: a value of @var{n} is sent as | |
23412 | @code{@var{n}+29}. For a repeat count greater or equal to 3, this | |
23413 | produces a printable @sc{ascii} character, e.g.@: a space (@sc{ascii} | |
23414 | code 32) for a repeat count of 3. (This is because run-length | |
23415 | encoding starts to win for counts 3 or more.) Thus, for example, | |
23416 | @samp{0* } is a run-length encoding of ``0000'': the space character | |
23417 | after @samp{*} means repeat the leading @code{0} @w{@code{32 - 29 = | |
23418 | 3}} more times. | |
23419 | ||
23420 | The printable characters @samp{#} and @samp{$} or with a numeric value | |
23421 | greater than 126 must not be used. Runs of six repeats (@samp{#}) or | |
23422 | seven repeats (@samp{$}) can be expanded using a repeat count of only | |
23423 | five (@samp{"}). For example, @samp{00000000} can be encoded as | |
23424 | @samp{0*"00}. | |
c906108c | 23425 | |
8e04817f AC |
23426 | The error response returned for some packets includes a two character |
23427 | error number. That number is not well defined. | |
c906108c | 23428 | |
f8da2bff | 23429 | @cindex empty response, for unsupported packets |
8e04817f AC |
23430 | For any @var{command} not supported by the stub, an empty response |
23431 | (@samp{$#00}) should be returned. That way it is possible to extend the | |
23432 | protocol. A newer @value{GDBN} can tell if a packet is supported based | |
23433 | on that response. | |
c906108c | 23434 | |
b383017d RM |
23435 | A stub is required to support the @samp{g}, @samp{G}, @samp{m}, @samp{M}, |
23436 | @samp{c}, and @samp{s} @var{command}s. All other @var{command}s are | |
8e04817f | 23437 | optional. |
c906108c | 23438 | |
ee2d5c50 AC |
23439 | @node Packets |
23440 | @section Packets | |
23441 | ||
23442 | The following table provides a complete list of all currently defined | |
23443 | @var{command}s and their corresponding response @var{data}. | |
79a6e687 | 23444 | @xref{File-I/O Remote Protocol Extension}, for details about the File |
9c16f35a | 23445 | I/O extension of the remote protocol. |
ee2d5c50 | 23446 | |
b8ff78ce JB |
23447 | Each packet's description has a template showing the packet's overall |
23448 | syntax, followed by an explanation of the packet's meaning. We | |
23449 | include spaces in some of the templates for clarity; these are not | |
23450 | part of the packet's syntax. No @value{GDBN} packet uses spaces to | |
23451 | separate its components. For example, a template like @samp{foo | |
23452 | @var{bar} @var{baz}} describes a packet beginning with the three ASCII | |
23453 | bytes @samp{foo}, followed by a @var{bar}, followed directly by a | |
3f94c067 | 23454 | @var{baz}. @value{GDBN} does not transmit a space character between the |
b8ff78ce JB |
23455 | @samp{foo} and the @var{bar}, or between the @var{bar} and the |
23456 | @var{baz}. | |
23457 | ||
8ffe2530 JB |
23458 | Note that all packet forms beginning with an upper- or lower-case |
23459 | letter, other than those described here, are reserved for future use. | |
23460 | ||
b8ff78ce | 23461 | Here are the packet descriptions. |
ee2d5c50 | 23462 | |
b8ff78ce | 23463 | @table @samp |
ee2d5c50 | 23464 | |
b8ff78ce JB |
23465 | @item ! |
23466 | @cindex @samp{!} packet | |
2d717e4f | 23467 | @anchor{extended mode} |
8e04817f AC |
23468 | Enable extended mode. In extended mode, the remote server is made |
23469 | persistent. The @samp{R} packet is used to restart the program being | |
23470 | debugged. | |
ee2d5c50 AC |
23471 | |
23472 | Reply: | |
23473 | @table @samp | |
23474 | @item OK | |
8e04817f | 23475 | The remote target both supports and has enabled extended mode. |
ee2d5c50 | 23476 | @end table |
c906108c | 23477 | |
b8ff78ce JB |
23478 | @item ? |
23479 | @cindex @samp{?} packet | |
ee2d5c50 AC |
23480 | Indicate the reason the target halted. The reply is the same as for |
23481 | step and continue. | |
c906108c | 23482 | |
ee2d5c50 AC |
23483 | Reply: |
23484 | @xref{Stop Reply Packets}, for the reply specifications. | |
23485 | ||
b8ff78ce JB |
23486 | @item A @var{arglen},@var{argnum},@var{arg},@dots{} |
23487 | @cindex @samp{A} packet | |
23488 | Initialized @code{argv[]} array passed into program. @var{arglen} | |
23489 | specifies the number of bytes in the hex encoded byte stream | |
23490 | @var{arg}. See @code{gdbserver} for more details. | |
ee2d5c50 AC |
23491 | |
23492 | Reply: | |
23493 | @table @samp | |
23494 | @item OK | |
b8ff78ce JB |
23495 | The arguments were set. |
23496 | @item E @var{NN} | |
23497 | An error occurred. | |
ee2d5c50 AC |
23498 | @end table |
23499 | ||
b8ff78ce JB |
23500 | @item b @var{baud} |
23501 | @cindex @samp{b} packet | |
23502 | (Don't use this packet; its behavior is not well-defined.) | |
ee2d5c50 AC |
23503 | Change the serial line speed to @var{baud}. |
23504 | ||
23505 | JTC: @emph{When does the transport layer state change? When it's | |
23506 | received, or after the ACK is transmitted. In either case, there are | |
23507 | problems if the command or the acknowledgment packet is dropped.} | |
23508 | ||
23509 | Stan: @emph{If people really wanted to add something like this, and get | |
23510 | it working for the first time, they ought to modify ser-unix.c to send | |
23511 | some kind of out-of-band message to a specially-setup stub and have the | |
23512 | switch happen "in between" packets, so that from remote protocol's point | |
23513 | of view, nothing actually happened.} | |
23514 | ||
b8ff78ce JB |
23515 | @item B @var{addr},@var{mode} |
23516 | @cindex @samp{B} packet | |
8e04817f | 23517 | Set (@var{mode} is @samp{S}) or clear (@var{mode} is @samp{C}) a |
2f870471 AC |
23518 | breakpoint at @var{addr}. |
23519 | ||
b8ff78ce | 23520 | Don't use this packet. Use the @samp{Z} and @samp{z} packets instead |
2f870471 | 23521 | (@pxref{insert breakpoint or watchpoint packet}). |
c906108c | 23522 | |
4f553f88 | 23523 | @item c @r{[}@var{addr}@r{]} |
b8ff78ce JB |
23524 | @cindex @samp{c} packet |
23525 | Continue. @var{addr} is address to resume. If @var{addr} is omitted, | |
23526 | resume at current address. | |
c906108c | 23527 | |
ee2d5c50 AC |
23528 | Reply: |
23529 | @xref{Stop Reply Packets}, for the reply specifications. | |
23530 | ||
4f553f88 | 23531 | @item C @var{sig}@r{[};@var{addr}@r{]} |
b8ff78ce | 23532 | @cindex @samp{C} packet |
8e04817f | 23533 | Continue with signal @var{sig} (hex signal number). If |
b8ff78ce | 23534 | @samp{;@var{addr}} is omitted, resume at same address. |
c906108c | 23535 | |
ee2d5c50 AC |
23536 | Reply: |
23537 | @xref{Stop Reply Packets}, for the reply specifications. | |
c906108c | 23538 | |
b8ff78ce JB |
23539 | @item d |
23540 | @cindex @samp{d} packet | |
ee2d5c50 AC |
23541 | Toggle debug flag. |
23542 | ||
b8ff78ce JB |
23543 | Don't use this packet; instead, define a general set packet |
23544 | (@pxref{General Query Packets}). | |
ee2d5c50 | 23545 | |
b8ff78ce JB |
23546 | @item D |
23547 | @cindex @samp{D} packet | |
ee2d5c50 | 23548 | Detach @value{GDBN} from the remote system. Sent to the remote target |
07f31aa6 | 23549 | before @value{GDBN} disconnects via the @code{detach} command. |
ee2d5c50 AC |
23550 | |
23551 | Reply: | |
23552 | @table @samp | |
10fac096 NW |
23553 | @item OK |
23554 | for success | |
b8ff78ce | 23555 | @item E @var{NN} |
10fac096 | 23556 | for an error |
ee2d5c50 | 23557 | @end table |
c906108c | 23558 | |
b8ff78ce JB |
23559 | @item F @var{RC},@var{EE},@var{CF};@var{XX} |
23560 | @cindex @samp{F} packet | |
23561 | A reply from @value{GDBN} to an @samp{F} packet sent by the target. | |
23562 | This is part of the File-I/O protocol extension. @xref{File-I/O | |
79a6e687 | 23563 | Remote Protocol Extension}, for the specification. |
ee2d5c50 | 23564 | |
b8ff78ce | 23565 | @item g |
ee2d5c50 | 23566 | @anchor{read registers packet} |
b8ff78ce | 23567 | @cindex @samp{g} packet |
ee2d5c50 AC |
23568 | Read general registers. |
23569 | ||
23570 | Reply: | |
23571 | @table @samp | |
23572 | @item @var{XX@dots{}} | |
8e04817f AC |
23573 | Each byte of register data is described by two hex digits. The bytes |
23574 | with the register are transmitted in target byte order. The size of | |
b8ff78ce | 23575 | each register and their position within the @samp{g} packet are |
4a9bb1df UW |
23576 | determined by the @value{GDBN} internal gdbarch functions |
23577 | @code{DEPRECATED_REGISTER_RAW_SIZE} and @code{gdbarch_register_name}. The | |
b8ff78ce JB |
23578 | specification of several standard @samp{g} packets is specified below. |
23579 | @item E @var{NN} | |
ee2d5c50 AC |
23580 | for an error. |
23581 | @end table | |
c906108c | 23582 | |
b8ff78ce JB |
23583 | @item G @var{XX@dots{}} |
23584 | @cindex @samp{G} packet | |
23585 | Write general registers. @xref{read registers packet}, for a | |
23586 | description of the @var{XX@dots{}} data. | |
ee2d5c50 AC |
23587 | |
23588 | Reply: | |
23589 | @table @samp | |
23590 | @item OK | |
23591 | for success | |
b8ff78ce | 23592 | @item E @var{NN} |
ee2d5c50 AC |
23593 | for an error |
23594 | @end table | |
23595 | ||
b8ff78ce JB |
23596 | @item H @var{c} @var{t} |
23597 | @cindex @samp{H} packet | |
8e04817f | 23598 | Set thread for subsequent operations (@samp{m}, @samp{M}, @samp{g}, |
ee2d5c50 AC |
23599 | @samp{G}, et.al.). @var{c} depends on the operation to be performed: it |
23600 | should be @samp{c} for step and continue operations, @samp{g} for other | |
b8ff78ce JB |
23601 | operations. The thread designator @var{t} may be @samp{-1}, meaning all |
23602 | the threads, a thread number, or @samp{0} which means pick any thread. | |
ee2d5c50 AC |
23603 | |
23604 | Reply: | |
23605 | @table @samp | |
23606 | @item OK | |
23607 | for success | |
b8ff78ce | 23608 | @item E @var{NN} |
ee2d5c50 AC |
23609 | for an error |
23610 | @end table | |
c906108c | 23611 | |
8e04817f AC |
23612 | @c FIXME: JTC: |
23613 | @c 'H': How restrictive (or permissive) is the thread model. If a | |
23614 | @c thread is selected and stopped, are other threads allowed | |
23615 | @c to continue to execute? As I mentioned above, I think the | |
23616 | @c semantics of each command when a thread is selected must be | |
23617 | @c described. For example: | |
23618 | @c | |
23619 | @c 'g': If the stub supports threads and a specific thread is | |
23620 | @c selected, returns the register block from that thread; | |
23621 | @c otherwise returns current registers. | |
23622 | @c | |
23623 | @c 'G' If the stub supports threads and a specific thread is | |
23624 | @c selected, sets the registers of the register block of | |
23625 | @c that thread; otherwise sets current registers. | |
c906108c | 23626 | |
b8ff78ce | 23627 | @item i @r{[}@var{addr}@r{[},@var{nnn}@r{]]} |
ee2d5c50 | 23628 | @anchor{cycle step packet} |
b8ff78ce JB |
23629 | @cindex @samp{i} packet |
23630 | Step the remote target by a single clock cycle. If @samp{,@var{nnn}} is | |
8e04817f AC |
23631 | present, cycle step @var{nnn} cycles. If @var{addr} is present, cycle |
23632 | step starting at that address. | |
c906108c | 23633 | |
b8ff78ce JB |
23634 | @item I |
23635 | @cindex @samp{I} packet | |
23636 | Signal, then cycle step. @xref{step with signal packet}. @xref{cycle | |
23637 | step packet}. | |
ee2d5c50 | 23638 | |
b8ff78ce JB |
23639 | @item k |
23640 | @cindex @samp{k} packet | |
23641 | Kill request. | |
c906108c | 23642 | |
ac282366 | 23643 | FIXME: @emph{There is no description of how to operate when a specific |
ee2d5c50 AC |
23644 | thread context has been selected (i.e.@: does 'k' kill only that |
23645 | thread?)}. | |
c906108c | 23646 | |
b8ff78ce JB |
23647 | @item m @var{addr},@var{length} |
23648 | @cindex @samp{m} packet | |
8e04817f | 23649 | Read @var{length} bytes of memory starting at address @var{addr}. |
fb031cdf JB |
23650 | Note that @var{addr} may not be aligned to any particular boundary. |
23651 | ||
23652 | The stub need not use any particular size or alignment when gathering | |
23653 | data from memory for the response; even if @var{addr} is word-aligned | |
23654 | and @var{length} is a multiple of the word size, the stub is free to | |
23655 | use byte accesses, or not. For this reason, this packet may not be | |
23656 | suitable for accessing memory-mapped I/O devices. | |
c43c5473 JB |
23657 | @cindex alignment of remote memory accesses |
23658 | @cindex size of remote memory accesses | |
23659 | @cindex memory, alignment and size of remote accesses | |
c906108c | 23660 | |
ee2d5c50 AC |
23661 | Reply: |
23662 | @table @samp | |
23663 | @item @var{XX@dots{}} | |
599b237a | 23664 | Memory contents; each byte is transmitted as a two-digit hexadecimal |
b8ff78ce JB |
23665 | number. The reply may contain fewer bytes than requested if the |
23666 | server was able to read only part of the region of memory. | |
23667 | @item E @var{NN} | |
ee2d5c50 AC |
23668 | @var{NN} is errno |
23669 | @end table | |
23670 | ||
b8ff78ce JB |
23671 | @item M @var{addr},@var{length}:@var{XX@dots{}} |
23672 | @cindex @samp{M} packet | |
8e04817f | 23673 | Write @var{length} bytes of memory starting at address @var{addr}. |
b8ff78ce | 23674 | @var{XX@dots{}} is the data; each byte is transmitted as a two-digit |
599b237a | 23675 | hexadecimal number. |
ee2d5c50 AC |
23676 | |
23677 | Reply: | |
23678 | @table @samp | |
23679 | @item OK | |
23680 | for success | |
b8ff78ce | 23681 | @item E @var{NN} |
8e04817f AC |
23682 | for an error (this includes the case where only part of the data was |
23683 | written). | |
ee2d5c50 | 23684 | @end table |
c906108c | 23685 | |
b8ff78ce JB |
23686 | @item p @var{n} |
23687 | @cindex @samp{p} packet | |
23688 | Read the value of register @var{n}; @var{n} is in hex. | |
2e868123 AC |
23689 | @xref{read registers packet}, for a description of how the returned |
23690 | register value is encoded. | |
ee2d5c50 AC |
23691 | |
23692 | Reply: | |
23693 | @table @samp | |
2e868123 AC |
23694 | @item @var{XX@dots{}} |
23695 | the register's value | |
b8ff78ce | 23696 | @item E @var{NN} |
2e868123 AC |
23697 | for an error |
23698 | @item | |
23699 | Indicating an unrecognized @var{query}. | |
ee2d5c50 AC |
23700 | @end table |
23701 | ||
b8ff78ce | 23702 | @item P @var{n@dots{}}=@var{r@dots{}} |
ee2d5c50 | 23703 | @anchor{write register packet} |
b8ff78ce JB |
23704 | @cindex @samp{P} packet |
23705 | Write register @var{n@dots{}} with value @var{r@dots{}}. The register | |
599b237a | 23706 | number @var{n} is in hexadecimal, and @var{r@dots{}} contains two hex |
8e04817f | 23707 | digits for each byte in the register (target byte order). |
c906108c | 23708 | |
ee2d5c50 AC |
23709 | Reply: |
23710 | @table @samp | |
23711 | @item OK | |
23712 | for success | |
b8ff78ce | 23713 | @item E @var{NN} |
ee2d5c50 AC |
23714 | for an error |
23715 | @end table | |
23716 | ||
5f3bebba JB |
23717 | @item q @var{name} @var{params}@dots{} |
23718 | @itemx Q @var{name} @var{params}@dots{} | |
b8ff78ce | 23719 | @cindex @samp{q} packet |
b8ff78ce | 23720 | @cindex @samp{Q} packet |
5f3bebba JB |
23721 | General query (@samp{q}) and set (@samp{Q}). These packets are |
23722 | described fully in @ref{General Query Packets}. | |
c906108c | 23723 | |
b8ff78ce JB |
23724 | @item r |
23725 | @cindex @samp{r} packet | |
8e04817f | 23726 | Reset the entire system. |
c906108c | 23727 | |
b8ff78ce | 23728 | Don't use this packet; use the @samp{R} packet instead. |
ee2d5c50 | 23729 | |
b8ff78ce JB |
23730 | @item R @var{XX} |
23731 | @cindex @samp{R} packet | |
8e04817f | 23732 | Restart the program being debugged. @var{XX}, while needed, is ignored. |
2d717e4f | 23733 | This packet is only available in extended mode (@pxref{extended mode}). |
ee2d5c50 | 23734 | |
8e04817f | 23735 | The @samp{R} packet has no reply. |
ee2d5c50 | 23736 | |
4f553f88 | 23737 | @item s @r{[}@var{addr}@r{]} |
b8ff78ce JB |
23738 | @cindex @samp{s} packet |
23739 | Single step. @var{addr} is the address at which to resume. If | |
23740 | @var{addr} is omitted, resume at same address. | |
c906108c | 23741 | |
ee2d5c50 AC |
23742 | Reply: |
23743 | @xref{Stop Reply Packets}, for the reply specifications. | |
23744 | ||
4f553f88 | 23745 | @item S @var{sig}@r{[};@var{addr}@r{]} |
ee2d5c50 | 23746 | @anchor{step with signal packet} |
b8ff78ce JB |
23747 | @cindex @samp{S} packet |
23748 | Step with signal. This is analogous to the @samp{C} packet, but | |
23749 | requests a single-step, rather than a normal resumption of execution. | |
c906108c | 23750 | |
ee2d5c50 AC |
23751 | Reply: |
23752 | @xref{Stop Reply Packets}, for the reply specifications. | |
23753 | ||
b8ff78ce JB |
23754 | @item t @var{addr}:@var{PP},@var{MM} |
23755 | @cindex @samp{t} packet | |
8e04817f | 23756 | Search backwards starting at address @var{addr} for a match with pattern |
ee2d5c50 AC |
23757 | @var{PP} and mask @var{MM}. @var{PP} and @var{MM} are 4 bytes. |
23758 | @var{addr} must be at least 3 digits. | |
c906108c | 23759 | |
b8ff78ce JB |
23760 | @item T @var{XX} |
23761 | @cindex @samp{T} packet | |
ee2d5c50 | 23762 | Find out if the thread XX is alive. |
c906108c | 23763 | |
ee2d5c50 AC |
23764 | Reply: |
23765 | @table @samp | |
23766 | @item OK | |
23767 | thread is still alive | |
b8ff78ce | 23768 | @item E @var{NN} |
ee2d5c50 AC |
23769 | thread is dead |
23770 | @end table | |
23771 | ||
b8ff78ce JB |
23772 | @item v |
23773 | Packets starting with @samp{v} are identified by a multi-letter name, | |
23774 | up to the first @samp{;} or @samp{?} (or the end of the packet). | |
86d30acc | 23775 | |
2d717e4f DJ |
23776 | @item vAttach;@var{pid} |
23777 | @cindex @samp{vAttach} packet | |
23778 | Attach to a new process with the specified process ID. @var{pid} is a | |
1fddbabb PA |
23779 | hexadecimal integer identifying the process. If the stub is currently |
23780 | controlling a process, it is killed. The attached process is stopped. | |
2d717e4f DJ |
23781 | |
23782 | This packet is only available in extended mode (@pxref{extended mode}). | |
23783 | ||
23784 | Reply: | |
23785 | @table @samp | |
23786 | @item E @var{nn} | |
23787 | for an error | |
23788 | @item @r{Any stop packet} | |
23789 | for success (@pxref{Stop Reply Packets}) | |
23790 | @end table | |
23791 | ||
b8ff78ce JB |
23792 | @item vCont@r{[};@var{action}@r{[}:@var{tid}@r{]]}@dots{} |
23793 | @cindex @samp{vCont} packet | |
23794 | Resume the inferior, specifying different actions for each thread. | |
86d30acc DJ |
23795 | If an action is specified with no @var{tid}, then it is applied to any |
23796 | threads that don't have a specific action specified; if no default action is | |
23797 | specified then other threads should remain stopped. Specifying multiple | |
23798 | default actions is an error; specifying no actions is also an error. | |
23799 | Thread IDs are specified in hexadecimal. Currently supported actions are: | |
23800 | ||
b8ff78ce | 23801 | @table @samp |
86d30acc DJ |
23802 | @item c |
23803 | Continue. | |
b8ff78ce | 23804 | @item C @var{sig} |
86d30acc DJ |
23805 | Continue with signal @var{sig}. @var{sig} should be two hex digits. |
23806 | @item s | |
23807 | Step. | |
b8ff78ce | 23808 | @item S @var{sig} |
86d30acc DJ |
23809 | Step with signal @var{sig}. @var{sig} should be two hex digits. |
23810 | @end table | |
23811 | ||
23812 | The optional @var{addr} argument normally associated with these packets is | |
b8ff78ce | 23813 | not supported in @samp{vCont}. |
86d30acc DJ |
23814 | |
23815 | Reply: | |
23816 | @xref{Stop Reply Packets}, for the reply specifications. | |
23817 | ||
b8ff78ce JB |
23818 | @item vCont? |
23819 | @cindex @samp{vCont?} packet | |
d3e8051b | 23820 | Request a list of actions supported by the @samp{vCont} packet. |
86d30acc DJ |
23821 | |
23822 | Reply: | |
23823 | @table @samp | |
b8ff78ce JB |
23824 | @item vCont@r{[};@var{action}@dots{}@r{]} |
23825 | The @samp{vCont} packet is supported. Each @var{action} is a supported | |
23826 | command in the @samp{vCont} packet. | |
86d30acc | 23827 | @item |
b8ff78ce | 23828 | The @samp{vCont} packet is not supported. |
86d30acc | 23829 | @end table |
ee2d5c50 | 23830 | |
a6b151f1 DJ |
23831 | @item vFile:@var{operation}:@var{parameter}@dots{} |
23832 | @cindex @samp{vFile} packet | |
23833 | Perform a file operation on the target system. For details, | |
23834 | see @ref{Host I/O Packets}. | |
23835 | ||
68437a39 DJ |
23836 | @item vFlashErase:@var{addr},@var{length} |
23837 | @cindex @samp{vFlashErase} packet | |
23838 | Direct the stub to erase @var{length} bytes of flash starting at | |
23839 | @var{addr}. The region may enclose any number of flash blocks, but | |
23840 | its start and end must fall on block boundaries, as indicated by the | |
79a6e687 BW |
23841 | flash block size appearing in the memory map (@pxref{Memory Map |
23842 | Format}). @value{GDBN} groups flash memory programming operations | |
68437a39 DJ |
23843 | together, and sends a @samp{vFlashDone} request after each group; the |
23844 | stub is allowed to delay erase operation until the @samp{vFlashDone} | |
23845 | packet is received. | |
23846 | ||
23847 | Reply: | |
23848 | @table @samp | |
23849 | @item OK | |
23850 | for success | |
23851 | @item E @var{NN} | |
23852 | for an error | |
23853 | @end table | |
23854 | ||
23855 | @item vFlashWrite:@var{addr}:@var{XX@dots{}} | |
23856 | @cindex @samp{vFlashWrite} packet | |
23857 | Direct the stub to write data to flash address @var{addr}. The data | |
23858 | is passed in binary form using the same encoding as for the @samp{X} | |
23859 | packet (@pxref{Binary Data}). The memory ranges specified by | |
23860 | @samp{vFlashWrite} packets preceding a @samp{vFlashDone} packet must | |
23861 | not overlap, and must appear in order of increasing addresses | |
23862 | (although @samp{vFlashErase} packets for higher addresses may already | |
23863 | have been received; the ordering is guaranteed only between | |
23864 | @samp{vFlashWrite} packets). If a packet writes to an address that was | |
23865 | neither erased by a preceding @samp{vFlashErase} packet nor by some other | |
23866 | target-specific method, the results are unpredictable. | |
23867 | ||
23868 | ||
23869 | Reply: | |
23870 | @table @samp | |
23871 | @item OK | |
23872 | for success | |
23873 | @item E.memtype | |
23874 | for vFlashWrite addressing non-flash memory | |
23875 | @item E @var{NN} | |
23876 | for an error | |
23877 | @end table | |
23878 | ||
23879 | @item vFlashDone | |
23880 | @cindex @samp{vFlashDone} packet | |
23881 | Indicate to the stub that flash programming operation is finished. | |
23882 | The stub is permitted to delay or batch the effects of a group of | |
23883 | @samp{vFlashErase} and @samp{vFlashWrite} packets until a | |
23884 | @samp{vFlashDone} packet is received. The contents of the affected | |
23885 | regions of flash memory are unpredictable until the @samp{vFlashDone} | |
23886 | request is completed. | |
23887 | ||
2d717e4f DJ |
23888 | @item vRun;@var{filename}@r{[};@var{argument}@r{]}@dots{} |
23889 | @cindex @samp{vRun} packet | |
23890 | Run the program @var{filename}, passing it each @var{argument} on its | |
23891 | command line. The file and arguments are hex-encoded strings. If | |
23892 | @var{filename} is an empty string, the stub may use a default program | |
23893 | (e.g.@: the last program run). The program is created in the stopped | |
1fddbabb | 23894 | state. If the stub is currently controlling a process, it is killed. |
2d717e4f DJ |
23895 | |
23896 | This packet is only available in extended mode (@pxref{extended mode}). | |
23897 | ||
23898 | Reply: | |
23899 | @table @samp | |
23900 | @item E @var{nn} | |
23901 | for an error | |
23902 | @item @r{Any stop packet} | |
23903 | for success (@pxref{Stop Reply Packets}) | |
23904 | @end table | |
23905 | ||
b8ff78ce | 23906 | @item X @var{addr},@var{length}:@var{XX@dots{}} |
9a6253be | 23907 | @anchor{X packet} |
b8ff78ce JB |
23908 | @cindex @samp{X} packet |
23909 | Write data to memory, where the data is transmitted in binary. | |
23910 | @var{addr} is address, @var{length} is number of bytes, | |
0876f84a | 23911 | @samp{@var{XX}@dots{}} is binary data (@pxref{Binary Data}). |
c906108c | 23912 | |
ee2d5c50 AC |
23913 | Reply: |
23914 | @table @samp | |
23915 | @item OK | |
23916 | for success | |
b8ff78ce | 23917 | @item E @var{NN} |
ee2d5c50 AC |
23918 | for an error |
23919 | @end table | |
23920 | ||
b8ff78ce JB |
23921 | @item z @var{type},@var{addr},@var{length} |
23922 | @itemx Z @var{type},@var{addr},@var{length} | |
2f870471 | 23923 | @anchor{insert breakpoint or watchpoint packet} |
b8ff78ce JB |
23924 | @cindex @samp{z} packet |
23925 | @cindex @samp{Z} packets | |
23926 | Insert (@samp{Z}) or remove (@samp{z}) a @var{type} breakpoint or | |
2f870471 AC |
23927 | watchpoint starting at address @var{address} and covering the next |
23928 | @var{length} bytes. | |
ee2d5c50 | 23929 | |
2f870471 AC |
23930 | Each breakpoint and watchpoint packet @var{type} is documented |
23931 | separately. | |
23932 | ||
512217c7 AC |
23933 | @emph{Implementation notes: A remote target shall return an empty string |
23934 | for an unrecognized breakpoint or watchpoint packet @var{type}. A | |
23935 | remote target shall support either both or neither of a given | |
b8ff78ce | 23936 | @samp{Z@var{type}@dots{}} and @samp{z@var{type}@dots{}} packet pair. To |
2f870471 AC |
23937 | avoid potential problems with duplicate packets, the operations should |
23938 | be implemented in an idempotent way.} | |
23939 | ||
b8ff78ce JB |
23940 | @item z0,@var{addr},@var{length} |
23941 | @itemx Z0,@var{addr},@var{length} | |
23942 | @cindex @samp{z0} packet | |
23943 | @cindex @samp{Z0} packet | |
23944 | Insert (@samp{Z0}) or remove (@samp{z0}) a memory breakpoint at address | |
23945 | @var{addr} of size @var{length}. | |
2f870471 AC |
23946 | |
23947 | A memory breakpoint is implemented by replacing the instruction at | |
23948 | @var{addr} with a software breakpoint or trap instruction. The | |
b8ff78ce | 23949 | @var{length} is used by targets that indicates the size of the |
2f870471 AC |
23950 | breakpoint (in bytes) that should be inserted (e.g., the @sc{arm} and |
23951 | @sc{mips} can insert either a 2 or 4 byte breakpoint). | |
c906108c | 23952 | |
2f870471 AC |
23953 | @emph{Implementation note: It is possible for a target to copy or move |
23954 | code that contains memory breakpoints (e.g., when implementing | |
23955 | overlays). The behavior of this packet, in the presence of such a | |
23956 | target, is not defined.} | |
c906108c | 23957 | |
ee2d5c50 AC |
23958 | Reply: |
23959 | @table @samp | |
2f870471 AC |
23960 | @item OK |
23961 | success | |
23962 | @item | |
23963 | not supported | |
b8ff78ce | 23964 | @item E @var{NN} |
ee2d5c50 | 23965 | for an error |
2f870471 AC |
23966 | @end table |
23967 | ||
b8ff78ce JB |
23968 | @item z1,@var{addr},@var{length} |
23969 | @itemx Z1,@var{addr},@var{length} | |
23970 | @cindex @samp{z1} packet | |
23971 | @cindex @samp{Z1} packet | |
23972 | Insert (@samp{Z1}) or remove (@samp{z1}) a hardware breakpoint at | |
23973 | address @var{addr} of size @var{length}. | |
2f870471 AC |
23974 | |
23975 | A hardware breakpoint is implemented using a mechanism that is not | |
23976 | dependant on being able to modify the target's memory. | |
23977 | ||
23978 | @emph{Implementation note: A hardware breakpoint is not affected by code | |
23979 | movement.} | |
23980 | ||
23981 | Reply: | |
23982 | @table @samp | |
ee2d5c50 | 23983 | @item OK |
2f870471 AC |
23984 | success |
23985 | @item | |
23986 | not supported | |
b8ff78ce | 23987 | @item E @var{NN} |
2f870471 AC |
23988 | for an error |
23989 | @end table | |
23990 | ||
b8ff78ce JB |
23991 | @item z2,@var{addr},@var{length} |
23992 | @itemx Z2,@var{addr},@var{length} | |
23993 | @cindex @samp{z2} packet | |
23994 | @cindex @samp{Z2} packet | |
23995 | Insert (@samp{Z2}) or remove (@samp{z2}) a write watchpoint. | |
2f870471 AC |
23996 | |
23997 | Reply: | |
23998 | @table @samp | |
23999 | @item OK | |
24000 | success | |
24001 | @item | |
24002 | not supported | |
b8ff78ce | 24003 | @item E @var{NN} |
2f870471 AC |
24004 | for an error |
24005 | @end table | |
24006 | ||
b8ff78ce JB |
24007 | @item z3,@var{addr},@var{length} |
24008 | @itemx Z3,@var{addr},@var{length} | |
24009 | @cindex @samp{z3} packet | |
24010 | @cindex @samp{Z3} packet | |
24011 | Insert (@samp{Z3}) or remove (@samp{z3}) a read watchpoint. | |
2f870471 AC |
24012 | |
24013 | Reply: | |
24014 | @table @samp | |
24015 | @item OK | |
24016 | success | |
24017 | @item | |
24018 | not supported | |
b8ff78ce | 24019 | @item E @var{NN} |
2f870471 AC |
24020 | for an error |
24021 | @end table | |
24022 | ||
b8ff78ce JB |
24023 | @item z4,@var{addr},@var{length} |
24024 | @itemx Z4,@var{addr},@var{length} | |
24025 | @cindex @samp{z4} packet | |
24026 | @cindex @samp{Z4} packet | |
24027 | Insert (@samp{Z4}) or remove (@samp{z4}) an access watchpoint. | |
2f870471 AC |
24028 | |
24029 | Reply: | |
24030 | @table @samp | |
24031 | @item OK | |
24032 | success | |
24033 | @item | |
24034 | not supported | |
b8ff78ce | 24035 | @item E @var{NN} |
2f870471 | 24036 | for an error |
ee2d5c50 AC |
24037 | @end table |
24038 | ||
24039 | @end table | |
c906108c | 24040 | |
ee2d5c50 AC |
24041 | @node Stop Reply Packets |
24042 | @section Stop Reply Packets | |
24043 | @cindex stop reply packets | |
c906108c | 24044 | |
8e04817f AC |
24045 | The @samp{C}, @samp{c}, @samp{S}, @samp{s} and @samp{?} packets can |
24046 | receive any of the below as a reply. In the case of the @samp{C}, | |
24047 | @samp{c}, @samp{S} and @samp{s} packets, that reply is only returned | |
b8ff78ce | 24048 | when the target halts. In the below the exact meaning of @dfn{signal |
89be2091 DJ |
24049 | number} is defined by the header @file{include/gdb/signals.h} in the |
24050 | @value{GDBN} source code. | |
c906108c | 24051 | |
b8ff78ce JB |
24052 | As in the description of request packets, we include spaces in the |
24053 | reply templates for clarity; these are not part of the reply packet's | |
24054 | syntax. No @value{GDBN} stop reply packet uses spaces to separate its | |
24055 | components. | |
c906108c | 24056 | |
b8ff78ce | 24057 | @table @samp |
ee2d5c50 | 24058 | |
b8ff78ce | 24059 | @item S @var{AA} |
599b237a | 24060 | The program received signal number @var{AA} (a two-digit hexadecimal |
940178d3 JB |
24061 | number). This is equivalent to a @samp{T} response with no |
24062 | @var{n}:@var{r} pairs. | |
c906108c | 24063 | |
b8ff78ce JB |
24064 | @item T @var{AA} @var{n1}:@var{r1};@var{n2}:@var{r2};@dots{} |
24065 | @cindex @samp{T} packet reply | |
599b237a | 24066 | The program received signal number @var{AA} (a two-digit hexadecimal |
940178d3 JB |
24067 | number). This is equivalent to an @samp{S} response, except that the |
24068 | @samp{@var{n}:@var{r}} pairs can carry values of important registers | |
24069 | and other information directly in the stop reply packet, reducing | |
24070 | round-trip latency. Single-step and breakpoint traps are reported | |
24071 | this way. Each @samp{@var{n}:@var{r}} pair is interpreted as follows: | |
cfa9d6d9 DJ |
24072 | |
24073 | @itemize @bullet | |
b8ff78ce | 24074 | @item |
599b237a | 24075 | If @var{n} is a hexadecimal number, it is a register number, and the |
b8ff78ce JB |
24076 | corresponding @var{r} gives that register's value. @var{r} is a |
24077 | series of bytes in target byte order, with each byte given by a | |
24078 | two-digit hex number. | |
cfa9d6d9 | 24079 | |
b8ff78ce JB |
24080 | @item |
24081 | If @var{n} is @samp{thread}, then @var{r} is the thread process ID, in | |
24082 | hex. | |
cfa9d6d9 | 24083 | |
b8ff78ce | 24084 | @item |
cfa9d6d9 DJ |
24085 | If @var{n} is a recognized @dfn{stop reason}, it describes a more |
24086 | specific event that stopped the target. The currently defined stop | |
24087 | reasons are listed below. @var{aa} should be @samp{05}, the trap | |
24088 | signal. At most one stop reason should be present. | |
24089 | ||
b8ff78ce JB |
24090 | @item |
24091 | Otherwise, @value{GDBN} should ignore this @samp{@var{n}:@var{r}} pair | |
24092 | and go on to the next; this allows us to extend the protocol in the | |
24093 | future. | |
cfa9d6d9 DJ |
24094 | @end itemize |
24095 | ||
24096 | The currently defined stop reasons are: | |
24097 | ||
24098 | @table @samp | |
24099 | @item watch | |
24100 | @itemx rwatch | |
24101 | @itemx awatch | |
24102 | The packet indicates a watchpoint hit, and @var{r} is the data address, in | |
24103 | hex. | |
24104 | ||
24105 | @cindex shared library events, remote reply | |
24106 | @item library | |
24107 | The packet indicates that the loaded libraries have changed. | |
24108 | @value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new | |
24109 | list of loaded libraries. @var{r} is ignored. | |
24110 | @end table | |
ee2d5c50 | 24111 | |
b8ff78ce | 24112 | @item W @var{AA} |
8e04817f | 24113 | The process exited, and @var{AA} is the exit status. This is only |
ee2d5c50 AC |
24114 | applicable to certain targets. |
24115 | ||
b8ff78ce | 24116 | @item X @var{AA} |
8e04817f | 24117 | The process terminated with signal @var{AA}. |
c906108c | 24118 | |
b8ff78ce JB |
24119 | @item O @var{XX}@dots{} |
24120 | @samp{@var{XX}@dots{}} is hex encoding of @sc{ascii} data, to be | |
24121 | written as the program's console output. This can happen at any time | |
24122 | while the program is running and the debugger should continue to wait | |
24123 | for @samp{W}, @samp{T}, etc. | |
0ce1b118 | 24124 | |
b8ff78ce | 24125 | @item F @var{call-id},@var{parameter}@dots{} |
0ce1b118 CV |
24126 | @var{call-id} is the identifier which says which host system call should |
24127 | be called. This is just the name of the function. Translation into the | |
24128 | correct system call is only applicable as it's defined in @value{GDBN}. | |
79a6e687 | 24129 | @xref{File-I/O Remote Protocol Extension}, for a list of implemented |
0ce1b118 CV |
24130 | system calls. |
24131 | ||
b8ff78ce JB |
24132 | @samp{@var{parameter}@dots{}} is a list of parameters as defined for |
24133 | this very system call. | |
0ce1b118 | 24134 | |
b8ff78ce JB |
24135 | The target replies with this packet when it expects @value{GDBN} to |
24136 | call a host system call on behalf of the target. @value{GDBN} replies | |
24137 | with an appropriate @samp{F} packet and keeps up waiting for the next | |
24138 | reply packet from the target. The latest @samp{C}, @samp{c}, @samp{S} | |
79a6e687 BW |
24139 | or @samp{s} action is expected to be continued. @xref{File-I/O Remote |
24140 | Protocol Extension}, for more details. | |
0ce1b118 | 24141 | |
ee2d5c50 AC |
24142 | @end table |
24143 | ||
24144 | @node General Query Packets | |
24145 | @section General Query Packets | |
9c16f35a | 24146 | @cindex remote query requests |
c906108c | 24147 | |
5f3bebba JB |
24148 | Packets starting with @samp{q} are @dfn{general query packets}; |
24149 | packets starting with @samp{Q} are @dfn{general set packets}. General | |
24150 | query and set packets are a semi-unified form for retrieving and | |
24151 | sending information to and from the stub. | |
24152 | ||
24153 | The initial letter of a query or set packet is followed by a name | |
24154 | indicating what sort of thing the packet applies to. For example, | |
24155 | @value{GDBN} may use a @samp{qSymbol} packet to exchange symbol | |
24156 | definitions with the stub. These packet names follow some | |
24157 | conventions: | |
24158 | ||
24159 | @itemize @bullet | |
24160 | @item | |
24161 | The name must not contain commas, colons or semicolons. | |
24162 | @item | |
24163 | Most @value{GDBN} query and set packets have a leading upper case | |
24164 | letter. | |
24165 | @item | |
24166 | The names of custom vendor packets should use a company prefix, in | |
24167 | lower case, followed by a period. For example, packets designed at | |
24168 | the Acme Corporation might begin with @samp{qacme.foo} (for querying | |
24169 | foos) or @samp{Qacme.bar} (for setting bars). | |
24170 | @end itemize | |
24171 | ||
aa56d27a JB |
24172 | The name of a query or set packet should be separated from any |
24173 | parameters by a @samp{:}; the parameters themselves should be | |
24174 | separated by @samp{,} or @samp{;}. Stubs must be careful to match the | |
369af7bd DJ |
24175 | full packet name, and check for a separator or the end of the packet, |
24176 | in case two packet names share a common prefix. New packets should not begin | |
24177 | with @samp{qC}, @samp{qP}, or @samp{qL}@footnote{The @samp{qP} and @samp{qL} | |
24178 | packets predate these conventions, and have arguments without any terminator | |
24179 | for the packet name; we suspect they are in widespread use in places that | |
24180 | are difficult to upgrade. The @samp{qC} packet has no arguments, but some | |
24181 | existing stubs (e.g.@: RedBoot) are known to not check for the end of the | |
24182 | packet.}. | |
c906108c | 24183 | |
b8ff78ce JB |
24184 | Like the descriptions of the other packets, each description here |
24185 | has a template showing the packet's overall syntax, followed by an | |
24186 | explanation of the packet's meaning. We include spaces in some of the | |
24187 | templates for clarity; these are not part of the packet's syntax. No | |
24188 | @value{GDBN} packet uses spaces to separate its components. | |
24189 | ||
5f3bebba JB |
24190 | Here are the currently defined query and set packets: |
24191 | ||
b8ff78ce | 24192 | @table @samp |
c906108c | 24193 | |
b8ff78ce | 24194 | @item qC |
9c16f35a | 24195 | @cindex current thread, remote request |
b8ff78ce | 24196 | @cindex @samp{qC} packet |
ee2d5c50 AC |
24197 | Return the current thread id. |
24198 | ||
24199 | Reply: | |
24200 | @table @samp | |
b8ff78ce | 24201 | @item QC @var{pid} |
599b237a | 24202 | Where @var{pid} is an unsigned hexadecimal process id. |
b8ff78ce | 24203 | @item @r{(anything else)} |
ee2d5c50 AC |
24204 | Any other reply implies the old pid. |
24205 | @end table | |
24206 | ||
b8ff78ce | 24207 | @item qCRC:@var{addr},@var{length} |
ff2587ec | 24208 | @cindex CRC of memory block, remote request |
b8ff78ce JB |
24209 | @cindex @samp{qCRC} packet |
24210 | Compute the CRC checksum of a block of memory. | |
ff2587ec WZ |
24211 | Reply: |
24212 | @table @samp | |
b8ff78ce | 24213 | @item E @var{NN} |
ff2587ec | 24214 | An error (such as memory fault) |
b8ff78ce JB |
24215 | @item C @var{crc32} |
24216 | The specified memory region's checksum is @var{crc32}. | |
ff2587ec WZ |
24217 | @end table |
24218 | ||
b8ff78ce JB |
24219 | @item qfThreadInfo |
24220 | @itemx qsThreadInfo | |
9c16f35a | 24221 | @cindex list active threads, remote request |
b8ff78ce JB |
24222 | @cindex @samp{qfThreadInfo} packet |
24223 | @cindex @samp{qsThreadInfo} packet | |
24224 | Obtain a list of all active thread ids from the target (OS). Since there | |
8e04817f AC |
24225 | may be too many active threads to fit into one reply packet, this query |
24226 | works iteratively: it may require more than one query/reply sequence to | |
24227 | obtain the entire list of threads. The first query of the sequence will | |
b8ff78ce JB |
24228 | be the @samp{qfThreadInfo} query; subsequent queries in the |
24229 | sequence will be the @samp{qsThreadInfo} query. | |
ee2d5c50 | 24230 | |
b8ff78ce | 24231 | NOTE: This packet replaces the @samp{qL} query (see below). |
ee2d5c50 AC |
24232 | |
24233 | Reply: | |
24234 | @table @samp | |
b8ff78ce | 24235 | @item m @var{id} |
ee2d5c50 | 24236 | A single thread id |
b8ff78ce | 24237 | @item m @var{id},@var{id}@dots{} |
ee2d5c50 | 24238 | a comma-separated list of thread ids |
b8ff78ce JB |
24239 | @item l |
24240 | (lower case letter @samp{L}) denotes end of list. | |
ee2d5c50 AC |
24241 | @end table |
24242 | ||
24243 | In response to each query, the target will reply with a list of one or | |
e1aac25b JB |
24244 | more thread ids, in big-endian unsigned hex, separated by commas. |
24245 | @value{GDBN} will respond to each reply with a request for more thread | |
b8ff78ce JB |
24246 | ids (using the @samp{qs} form of the query), until the target responds |
24247 | with @samp{l} (lower-case el, for @dfn{last}). | |
c906108c | 24248 | |
b8ff78ce | 24249 | @item qGetTLSAddr:@var{thread-id},@var{offset},@var{lm} |
ff2587ec | 24250 | @cindex get thread-local storage address, remote request |
b8ff78ce | 24251 | @cindex @samp{qGetTLSAddr} packet |
ff2587ec WZ |
24252 | Fetch the address associated with thread local storage specified |
24253 | by @var{thread-id}, @var{offset}, and @var{lm}. | |
24254 | ||
24255 | @var{thread-id} is the (big endian, hex encoded) thread id associated with the | |
24256 | thread for which to fetch the TLS address. | |
24257 | ||
24258 | @var{offset} is the (big endian, hex encoded) offset associated with the | |
24259 | thread local variable. (This offset is obtained from the debug | |
24260 | information associated with the variable.) | |
24261 | ||
db2e3e2e | 24262 | @var{lm} is the (big endian, hex encoded) OS/ABI-specific encoding of the |
ff2587ec WZ |
24263 | the load module associated with the thread local storage. For example, |
24264 | a @sc{gnu}/Linux system will pass the link map address of the shared | |
24265 | object associated with the thread local storage under consideration. | |
24266 | Other operating environments may choose to represent the load module | |
24267 | differently, so the precise meaning of this parameter will vary. | |
ee2d5c50 AC |
24268 | |
24269 | Reply: | |
b8ff78ce JB |
24270 | @table @samp |
24271 | @item @var{XX}@dots{} | |
ff2587ec WZ |
24272 | Hex encoded (big endian) bytes representing the address of the thread |
24273 | local storage requested. | |
24274 | ||
b8ff78ce JB |
24275 | @item E @var{nn} |
24276 | An error occurred. @var{nn} are hex digits. | |
ff2587ec | 24277 | |
b8ff78ce JB |
24278 | @item |
24279 | An empty reply indicates that @samp{qGetTLSAddr} is not supported by the stub. | |
ee2d5c50 AC |
24280 | @end table |
24281 | ||
b8ff78ce | 24282 | @item qL @var{startflag} @var{threadcount} @var{nextthread} |
8e04817f AC |
24283 | Obtain thread information from RTOS. Where: @var{startflag} (one hex |
24284 | digit) is one to indicate the first query and zero to indicate a | |
24285 | subsequent query; @var{threadcount} (two hex digits) is the maximum | |
24286 | number of threads the response packet can contain; and @var{nextthread} | |
24287 | (eight hex digits), for subsequent queries (@var{startflag} is zero), is | |
24288 | returned in the response as @var{argthread}. | |
ee2d5c50 | 24289 | |
b8ff78ce | 24290 | Don't use this packet; use the @samp{qfThreadInfo} query instead (see above). |
ee2d5c50 AC |
24291 | |
24292 | Reply: | |
24293 | @table @samp | |
b8ff78ce | 24294 | @item qM @var{count} @var{done} @var{argthread} @var{thread}@dots{} |
8e04817f AC |
24295 | Where: @var{count} (two hex digits) is the number of threads being |
24296 | returned; @var{done} (one hex digit) is zero to indicate more threads | |
24297 | and one indicates no further threads; @var{argthreadid} (eight hex | |
b8ff78ce | 24298 | digits) is @var{nextthread} from the request packet; @var{thread}@dots{} |
ee2d5c50 | 24299 | is a sequence of thread IDs from the target. @var{threadid} (eight hex |
8e04817f | 24300 | digits). See @code{remote.c:parse_threadlist_response()}. |
ee2d5c50 | 24301 | @end table |
c906108c | 24302 | |
b8ff78ce | 24303 | @item qOffsets |
9c16f35a | 24304 | @cindex section offsets, remote request |
b8ff78ce | 24305 | @cindex @samp{qOffsets} packet |
31d99776 DJ |
24306 | Get section offsets that the target used when relocating the downloaded |
24307 | image. | |
c906108c | 24308 | |
ee2d5c50 AC |
24309 | Reply: |
24310 | @table @samp | |
31d99776 DJ |
24311 | @item Text=@var{xxx};Data=@var{yyy}@r{[};Bss=@var{zzz}@r{]} |
24312 | Relocate the @code{Text} section by @var{xxx} from its original address. | |
24313 | Relocate the @code{Data} section by @var{yyy} from its original address. | |
24314 | If the object file format provides segment information (e.g.@: @sc{elf} | |
24315 | @samp{PT_LOAD} program headers), @value{GDBN} will relocate entire | |
24316 | segments by the supplied offsets. | |
24317 | ||
24318 | @emph{Note: while a @code{Bss} offset may be included in the response, | |
24319 | @value{GDBN} ignores this and instead applies the @code{Data} offset | |
24320 | to the @code{Bss} section.} | |
24321 | ||
24322 | @item TextSeg=@var{xxx}@r{[};DataSeg=@var{yyy}@r{]} | |
24323 | Relocate the first segment of the object file, which conventionally | |
24324 | contains program code, to a starting address of @var{xxx}. If | |
24325 | @samp{DataSeg} is specified, relocate the second segment, which | |
24326 | conventionally contains modifiable data, to a starting address of | |
24327 | @var{yyy}. @value{GDBN} will report an error if the object file | |
24328 | does not contain segment information, or does not contain at least | |
24329 | as many segments as mentioned in the reply. Extra segments are | |
24330 | kept at fixed offsets relative to the last relocated segment. | |
ee2d5c50 AC |
24331 | @end table |
24332 | ||
b8ff78ce | 24333 | @item qP @var{mode} @var{threadid} |
9c16f35a | 24334 | @cindex thread information, remote request |
b8ff78ce | 24335 | @cindex @samp{qP} packet |
8e04817f AC |
24336 | Returns information on @var{threadid}. Where: @var{mode} is a hex |
24337 | encoded 32 bit mode; @var{threadid} is a hex encoded 64 bit thread ID. | |
ee2d5c50 | 24338 | |
aa56d27a JB |
24339 | Don't use this packet; use the @samp{qThreadExtraInfo} query instead |
24340 | (see below). | |
24341 | ||
b8ff78ce | 24342 | Reply: see @code{remote.c:remote_unpack_thread_info_response()}. |
c906108c | 24343 | |
89be2091 DJ |
24344 | @item QPassSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{} |
24345 | @cindex pass signals to inferior, remote request | |
24346 | @cindex @samp{QPassSignals} packet | |
23181151 | 24347 | @anchor{QPassSignals} |
89be2091 DJ |
24348 | Each listed @var{signal} should be passed directly to the inferior process. |
24349 | Signals are numbered identically to continue packets and stop replies | |
24350 | (@pxref{Stop Reply Packets}). Each @var{signal} list item should be | |
24351 | strictly greater than the previous item. These signals do not need to stop | |
24352 | the inferior, or be reported to @value{GDBN}. All other signals should be | |
24353 | reported to @value{GDBN}. Multiple @samp{QPassSignals} packets do not | |
24354 | combine; any earlier @samp{QPassSignals} list is completely replaced by the | |
24355 | new list. This packet improves performance when using @samp{handle | |
24356 | @var{signal} nostop noprint pass}. | |
24357 | ||
24358 | Reply: | |
24359 | @table @samp | |
24360 | @item OK | |
24361 | The request succeeded. | |
24362 | ||
24363 | @item E @var{nn} | |
24364 | An error occurred. @var{nn} are hex digits. | |
24365 | ||
24366 | @item | |
24367 | An empty reply indicates that @samp{QPassSignals} is not supported by | |
24368 | the stub. | |
24369 | @end table | |
24370 | ||
24371 | Use of this packet is controlled by the @code{set remote pass-signals} | |
79a6e687 | 24372 | command (@pxref{Remote Configuration, set remote pass-signals}). |
89be2091 DJ |
24373 | This packet is not probed by default; the remote stub must request it, |
24374 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
24375 | ||
b8ff78ce | 24376 | @item qRcmd,@var{command} |
ff2587ec | 24377 | @cindex execute remote command, remote request |
b8ff78ce | 24378 | @cindex @samp{qRcmd} packet |
ff2587ec | 24379 | @var{command} (hex encoded) is passed to the local interpreter for |
b8ff78ce JB |
24380 | execution. Invalid commands should be reported using the output |
24381 | string. Before the final result packet, the target may also respond | |
24382 | with a number of intermediate @samp{O@var{output}} console output | |
24383 | packets. @emph{Implementors should note that providing access to a | |
24384 | stubs's interpreter may have security implications}. | |
fa93a9d8 | 24385 | |
ff2587ec WZ |
24386 | Reply: |
24387 | @table @samp | |
24388 | @item OK | |
24389 | A command response with no output. | |
24390 | @item @var{OUTPUT} | |
24391 | A command response with the hex encoded output string @var{OUTPUT}. | |
b8ff78ce | 24392 | @item E @var{NN} |
ff2587ec | 24393 | Indicate a badly formed request. |
b8ff78ce JB |
24394 | @item |
24395 | An empty reply indicates that @samp{qRcmd} is not recognized. | |
ff2587ec | 24396 | @end table |
fa93a9d8 | 24397 | |
aa56d27a JB |
24398 | (Note that the @code{qRcmd} packet's name is separated from the |
24399 | command by a @samp{,}, not a @samp{:}, contrary to the naming | |
24400 | conventions above. Please don't use this packet as a model for new | |
24401 | packets.) | |
24402 | ||
be2a5f71 DJ |
24403 | @item qSupported @r{[}:@var{gdbfeature} @r{[};@var{gdbfeature}@r{]}@dots{} @r{]} |
24404 | @cindex supported packets, remote query | |
24405 | @cindex features of the remote protocol | |
24406 | @cindex @samp{qSupported} packet | |
0876f84a | 24407 | @anchor{qSupported} |
be2a5f71 DJ |
24408 | Tell the remote stub about features supported by @value{GDBN}, and |
24409 | query the stub for features it supports. This packet allows | |
24410 | @value{GDBN} and the remote stub to take advantage of each others' | |
24411 | features. @samp{qSupported} also consolidates multiple feature probes | |
24412 | at startup, to improve @value{GDBN} performance---a single larger | |
24413 | packet performs better than multiple smaller probe packets on | |
24414 | high-latency links. Some features may enable behavior which must not | |
24415 | be on by default, e.g.@: because it would confuse older clients or | |
24416 | stubs. Other features may describe packets which could be | |
24417 | automatically probed for, but are not. These features must be | |
24418 | reported before @value{GDBN} will use them. This ``default | |
24419 | unsupported'' behavior is not appropriate for all packets, but it | |
24420 | helps to keep the initial connection time under control with new | |
24421 | versions of @value{GDBN} which support increasing numbers of packets. | |
24422 | ||
24423 | Reply: | |
24424 | @table @samp | |
24425 | @item @var{stubfeature} @r{[};@var{stubfeature}@r{]}@dots{} | |
24426 | The stub supports or does not support each returned @var{stubfeature}, | |
24427 | depending on the form of each @var{stubfeature} (see below for the | |
24428 | possible forms). | |
24429 | @item | |
24430 | An empty reply indicates that @samp{qSupported} is not recognized, | |
24431 | or that no features needed to be reported to @value{GDBN}. | |
24432 | @end table | |
24433 | ||
24434 | The allowed forms for each feature (either a @var{gdbfeature} in the | |
24435 | @samp{qSupported} packet, or a @var{stubfeature} in the response) | |
24436 | are: | |
24437 | ||
24438 | @table @samp | |
24439 | @item @var{name}=@var{value} | |
24440 | The remote protocol feature @var{name} is supported, and associated | |
24441 | with the specified @var{value}. The format of @var{value} depends | |
24442 | on the feature, but it must not include a semicolon. | |
24443 | @item @var{name}+ | |
24444 | The remote protocol feature @var{name} is supported, and does not | |
24445 | need an associated value. | |
24446 | @item @var{name}- | |
24447 | The remote protocol feature @var{name} is not supported. | |
24448 | @item @var{name}? | |
24449 | The remote protocol feature @var{name} may be supported, and | |
24450 | @value{GDBN} should auto-detect support in some other way when it is | |
24451 | needed. This form will not be used for @var{gdbfeature} notifications, | |
24452 | but may be used for @var{stubfeature} responses. | |
24453 | @end table | |
24454 | ||
24455 | Whenever the stub receives a @samp{qSupported} request, the | |
24456 | supplied set of @value{GDBN} features should override any previous | |
24457 | request. This allows @value{GDBN} to put the stub in a known | |
24458 | state, even if the stub had previously been communicating with | |
24459 | a different version of @value{GDBN}. | |
24460 | ||
24461 | No values of @var{gdbfeature} (for the packet sent by @value{GDBN}) | |
24462 | are defined yet. Stubs should ignore any unknown values for | |
24463 | @var{gdbfeature}. Any @value{GDBN} which sends a @samp{qSupported} | |
24464 | packet supports receiving packets of unlimited length (earlier | |
24465 | versions of @value{GDBN} may reject overly long responses). Values | |
24466 | for @var{gdbfeature} may be defined in the future to let the stub take | |
24467 | advantage of new features in @value{GDBN}, e.g.@: incompatible | |
24468 | improvements in the remote protocol---support for unlimited length | |
24469 | responses would be a @var{gdbfeature} example, if it were not implied by | |
24470 | the @samp{qSupported} query. The stub's reply should be independent | |
24471 | of the @var{gdbfeature} entries sent by @value{GDBN}; first @value{GDBN} | |
24472 | describes all the features it supports, and then the stub replies with | |
24473 | all the features it supports. | |
24474 | ||
24475 | Similarly, @value{GDBN} will silently ignore unrecognized stub feature | |
24476 | responses, as long as each response uses one of the standard forms. | |
24477 | ||
24478 | Some features are flags. A stub which supports a flag feature | |
24479 | should respond with a @samp{+} form response. Other features | |
24480 | require values, and the stub should respond with an @samp{=} | |
24481 | form response. | |
24482 | ||
24483 | Each feature has a default value, which @value{GDBN} will use if | |
24484 | @samp{qSupported} is not available or if the feature is not mentioned | |
24485 | in the @samp{qSupported} response. The default values are fixed; a | |
24486 | stub is free to omit any feature responses that match the defaults. | |
24487 | ||
24488 | Not all features can be probed, but for those which can, the probing | |
24489 | mechanism is useful: in some cases, a stub's internal | |
24490 | architecture may not allow the protocol layer to know some information | |
24491 | about the underlying target in advance. This is especially common in | |
24492 | stubs which may be configured for multiple targets. | |
24493 | ||
24494 | These are the currently defined stub features and their properties: | |
24495 | ||
cfa9d6d9 | 24496 | @multitable @columnfractions 0.35 0.2 0.12 0.2 |
be2a5f71 DJ |
24497 | @c NOTE: The first row should be @headitem, but we do not yet require |
24498 | @c a new enough version of Texinfo (4.7) to use @headitem. | |
0876f84a | 24499 | @item Feature Name |
be2a5f71 DJ |
24500 | @tab Value Required |
24501 | @tab Default | |
24502 | @tab Probe Allowed | |
24503 | ||
24504 | @item @samp{PacketSize} | |
24505 | @tab Yes | |
24506 | @tab @samp{-} | |
24507 | @tab No | |
24508 | ||
0876f84a DJ |
24509 | @item @samp{qXfer:auxv:read} |
24510 | @tab No | |
24511 | @tab @samp{-} | |
24512 | @tab Yes | |
24513 | ||
23181151 DJ |
24514 | @item @samp{qXfer:features:read} |
24515 | @tab No | |
24516 | @tab @samp{-} | |
24517 | @tab Yes | |
24518 | ||
cfa9d6d9 DJ |
24519 | @item @samp{qXfer:libraries:read} |
24520 | @tab No | |
24521 | @tab @samp{-} | |
24522 | @tab Yes | |
24523 | ||
68437a39 DJ |
24524 | @item @samp{qXfer:memory-map:read} |
24525 | @tab No | |
24526 | @tab @samp{-} | |
24527 | @tab Yes | |
24528 | ||
0e7f50da UW |
24529 | @item @samp{qXfer:spu:read} |
24530 | @tab No | |
24531 | @tab @samp{-} | |
24532 | @tab Yes | |
24533 | ||
24534 | @item @samp{qXfer:spu:write} | |
24535 | @tab No | |
24536 | @tab @samp{-} | |
24537 | @tab Yes | |
24538 | ||
89be2091 DJ |
24539 | @item @samp{QPassSignals} |
24540 | @tab No | |
24541 | @tab @samp{-} | |
24542 | @tab Yes | |
24543 | ||
be2a5f71 DJ |
24544 | @end multitable |
24545 | ||
24546 | These are the currently defined stub features, in more detail: | |
24547 | ||
24548 | @table @samp | |
24549 | @cindex packet size, remote protocol | |
24550 | @item PacketSize=@var{bytes} | |
24551 | The remote stub can accept packets up to at least @var{bytes} in | |
24552 | length. @value{GDBN} will send packets up to this size for bulk | |
24553 | transfers, and will never send larger packets. This is a limit on the | |
24554 | data characters in the packet, including the frame and checksum. | |
24555 | There is no trailing NUL byte in a remote protocol packet; if the stub | |
24556 | stores packets in a NUL-terminated format, it should allow an extra | |
24557 | byte in its buffer for the NUL. If this stub feature is not supported, | |
24558 | @value{GDBN} guesses based on the size of the @samp{g} packet response. | |
24559 | ||
0876f84a DJ |
24560 | @item qXfer:auxv:read |
24561 | The remote stub understands the @samp{qXfer:auxv:read} packet | |
24562 | (@pxref{qXfer auxiliary vector read}). | |
24563 | ||
23181151 DJ |
24564 | @item qXfer:features:read |
24565 | The remote stub understands the @samp{qXfer:features:read} packet | |
24566 | (@pxref{qXfer target description read}). | |
24567 | ||
cfa9d6d9 DJ |
24568 | @item qXfer:libraries:read |
24569 | The remote stub understands the @samp{qXfer:libraries:read} packet | |
24570 | (@pxref{qXfer library list read}). | |
24571 | ||
23181151 DJ |
24572 | @item qXfer:memory-map:read |
24573 | The remote stub understands the @samp{qXfer:memory-map:read} packet | |
24574 | (@pxref{qXfer memory map read}). | |
24575 | ||
0e7f50da UW |
24576 | @item qXfer:spu:read |
24577 | The remote stub understands the @samp{qXfer:spu:read} packet | |
24578 | (@pxref{qXfer spu read}). | |
24579 | ||
24580 | @item qXfer:spu:write | |
24581 | The remote stub understands the @samp{qXfer:spu:write} packet | |
24582 | (@pxref{qXfer spu write}). | |
24583 | ||
23181151 DJ |
24584 | @item QPassSignals |
24585 | The remote stub understands the @samp{QPassSignals} packet | |
24586 | (@pxref{QPassSignals}). | |
24587 | ||
be2a5f71 DJ |
24588 | @end table |
24589 | ||
b8ff78ce | 24590 | @item qSymbol:: |
ff2587ec | 24591 | @cindex symbol lookup, remote request |
b8ff78ce | 24592 | @cindex @samp{qSymbol} packet |
ff2587ec WZ |
24593 | Notify the target that @value{GDBN} is prepared to serve symbol lookup |
24594 | requests. Accept requests from the target for the values of symbols. | |
fa93a9d8 JB |
24595 | |
24596 | Reply: | |
ff2587ec | 24597 | @table @samp |
b8ff78ce | 24598 | @item OK |
ff2587ec | 24599 | The target does not need to look up any (more) symbols. |
b8ff78ce | 24600 | @item qSymbol:@var{sym_name} |
ff2587ec WZ |
24601 | The target requests the value of symbol @var{sym_name} (hex encoded). |
24602 | @value{GDBN} may provide the value by using the | |
b8ff78ce JB |
24603 | @samp{qSymbol:@var{sym_value}:@var{sym_name}} message, described |
24604 | below. | |
ff2587ec | 24605 | @end table |
83761cbd | 24606 | |
b8ff78ce | 24607 | @item qSymbol:@var{sym_value}:@var{sym_name} |
ff2587ec WZ |
24608 | Set the value of @var{sym_name} to @var{sym_value}. |
24609 | ||
24610 | @var{sym_name} (hex encoded) is the name of a symbol whose value the | |
24611 | target has previously requested. | |
24612 | ||
24613 | @var{sym_value} (hex) is the value for symbol @var{sym_name}. If | |
24614 | @value{GDBN} cannot supply a value for @var{sym_name}, then this field | |
24615 | will be empty. | |
24616 | ||
24617 | Reply: | |
24618 | @table @samp | |
b8ff78ce | 24619 | @item OK |
ff2587ec | 24620 | The target does not need to look up any (more) symbols. |
b8ff78ce | 24621 | @item qSymbol:@var{sym_name} |
ff2587ec WZ |
24622 | The target requests the value of a new symbol @var{sym_name} (hex |
24623 | encoded). @value{GDBN} will continue to supply the values of symbols | |
24624 | (if available), until the target ceases to request them. | |
fa93a9d8 | 24625 | @end table |
0abb7bc7 | 24626 | |
9d29849a JB |
24627 | @item QTDP |
24628 | @itemx QTFrame | |
24629 | @xref{Tracepoint Packets}. | |
24630 | ||
b8ff78ce | 24631 | @item qThreadExtraInfo,@var{id} |
ff2587ec | 24632 | @cindex thread attributes info, remote request |
b8ff78ce JB |
24633 | @cindex @samp{qThreadExtraInfo} packet |
24634 | Obtain a printable string description of a thread's attributes from | |
24635 | the target OS. @var{id} is a thread-id in big-endian hex. This | |
24636 | string may contain anything that the target OS thinks is interesting | |
24637 | for @value{GDBN} to tell the user about the thread. The string is | |
24638 | displayed in @value{GDBN}'s @code{info threads} display. Some | |
24639 | examples of possible thread extra info strings are @samp{Runnable}, or | |
24640 | @samp{Blocked on Mutex}. | |
ff2587ec WZ |
24641 | |
24642 | Reply: | |
24643 | @table @samp | |
b8ff78ce JB |
24644 | @item @var{XX}@dots{} |
24645 | Where @samp{@var{XX}@dots{}} is a hex encoding of @sc{ascii} data, | |
24646 | comprising the printable string containing the extra information about | |
24647 | the thread's attributes. | |
ff2587ec | 24648 | @end table |
814e32d7 | 24649 | |
aa56d27a JB |
24650 | (Note that the @code{qThreadExtraInfo} packet's name is separated from |
24651 | the command by a @samp{,}, not a @samp{:}, contrary to the naming | |
24652 | conventions above. Please don't use this packet as a model for new | |
24653 | packets.) | |
24654 | ||
9d29849a JB |
24655 | @item QTStart |
24656 | @itemx QTStop | |
24657 | @itemx QTinit | |
24658 | @itemx QTro | |
24659 | @itemx qTStatus | |
24660 | @xref{Tracepoint Packets}. | |
24661 | ||
0876f84a DJ |
24662 | @item qXfer:@var{object}:read:@var{annex}:@var{offset},@var{length} |
24663 | @cindex read special object, remote request | |
24664 | @cindex @samp{qXfer} packet | |
68437a39 | 24665 | @anchor{qXfer read} |
0876f84a DJ |
24666 | Read uninterpreted bytes from the target's special data area |
24667 | identified by the keyword @var{object}. Request @var{length} bytes | |
24668 | starting at @var{offset} bytes into the data. The content and | |
0e7f50da | 24669 | encoding of @var{annex} is specific to @var{object}; it can supply |
0876f84a DJ |
24670 | additional details about what data to access. |
24671 | ||
24672 | Here are the specific requests of this form defined so far. All | |
24673 | @samp{qXfer:@var{object}:read:@dots{}} requests use the same reply | |
24674 | formats, listed below. | |
24675 | ||
24676 | @table @samp | |
24677 | @item qXfer:auxv:read::@var{offset},@var{length} | |
24678 | @anchor{qXfer auxiliary vector read} | |
24679 | Access the target's @dfn{auxiliary vector}. @xref{OS Information, | |
427c3a89 | 24680 | auxiliary vector}. Note @var{annex} must be empty. |
0876f84a DJ |
24681 | |
24682 | This packet is not probed by default; the remote stub must request it, | |
89be2091 | 24683 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). |
0876f84a | 24684 | |
23181151 DJ |
24685 | @item qXfer:features:read:@var{annex}:@var{offset},@var{length} |
24686 | @anchor{qXfer target description read} | |
24687 | Access the @dfn{target description}. @xref{Target Descriptions}. The | |
24688 | annex specifies which XML document to access. The main description is | |
24689 | always loaded from the @samp{target.xml} annex. | |
24690 | ||
24691 | This packet is not probed by default; the remote stub must request it, | |
24692 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
24693 | ||
cfa9d6d9 DJ |
24694 | @item qXfer:libraries:read:@var{annex}:@var{offset},@var{length} |
24695 | @anchor{qXfer library list read} | |
24696 | Access the target's list of loaded libraries. @xref{Library List Format}. | |
24697 | The annex part of the generic @samp{qXfer} packet must be empty | |
24698 | (@pxref{qXfer read}). | |
24699 | ||
24700 | Targets which maintain a list of libraries in the program's memory do | |
24701 | not need to implement this packet; it is designed for platforms where | |
24702 | the operating system manages the list of loaded libraries. | |
24703 | ||
24704 | This packet is not probed by default; the remote stub must request it, | |
24705 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
24706 | ||
68437a39 DJ |
24707 | @item qXfer:memory-map:read::@var{offset},@var{length} |
24708 | @anchor{qXfer memory map read} | |
79a6e687 | 24709 | Access the target's @dfn{memory-map}. @xref{Memory Map Format}. The |
68437a39 DJ |
24710 | annex part of the generic @samp{qXfer} packet must be empty |
24711 | (@pxref{qXfer read}). | |
24712 | ||
0e7f50da UW |
24713 | This packet is not probed by default; the remote stub must request it, |
24714 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
24715 | ||
24716 | @item qXfer:spu:read:@var{annex}:@var{offset},@var{length} | |
24717 | @anchor{qXfer spu read} | |
24718 | Read contents of an @code{spufs} file on the target system. The | |
24719 | annex specifies which file to read; it must be of the form | |
24720 | @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID | |
24721 | in the target process, and @var{name} identifes the @code{spufs} file | |
24722 | in that context to be accessed. | |
24723 | ||
68437a39 DJ |
24724 | This packet is not probed by default; the remote stub must request it, |
24725 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
24726 | @end table | |
24727 | ||
0876f84a DJ |
24728 | Reply: |
24729 | @table @samp | |
24730 | @item m @var{data} | |
24731 | Data @var{data} (@pxref{Binary Data}) has been read from the | |
24732 | target. There may be more data at a higher address (although | |
24733 | it is permitted to return @samp{m} even for the last valid | |
24734 | block of data, as long as at least one byte of data was read). | |
24735 | @var{data} may have fewer bytes than the @var{length} in the | |
24736 | request. | |
24737 | ||
24738 | @item l @var{data} | |
24739 | Data @var{data} (@pxref{Binary Data}) has been read from the target. | |
24740 | There is no more data to be read. @var{data} may have fewer bytes | |
24741 | than the @var{length} in the request. | |
24742 | ||
24743 | @item l | |
24744 | The @var{offset} in the request is at the end of the data. | |
24745 | There is no more data to be read. | |
24746 | ||
24747 | @item E00 | |
24748 | The request was malformed, or @var{annex} was invalid. | |
24749 | ||
24750 | @item E @var{nn} | |
24751 | The offset was invalid, or there was an error encountered reading the data. | |
24752 | @var{nn} is a hex-encoded @code{errno} value. | |
24753 | ||
24754 | @item | |
24755 | An empty reply indicates the @var{object} string was not recognized by | |
24756 | the stub, or that the object does not support reading. | |
24757 | @end table | |
24758 | ||
24759 | @item qXfer:@var{object}:write:@var{annex}:@var{offset}:@var{data}@dots{} | |
24760 | @cindex write data into object, remote request | |
24761 | Write uninterpreted bytes into the target's special data area | |
24762 | identified by the keyword @var{object}, starting at @var{offset} bytes | |
0e7f50da | 24763 | into the data. @var{data}@dots{} is the binary-encoded data |
0876f84a | 24764 | (@pxref{Binary Data}) to be written. The content and encoding of @var{annex} |
0e7f50da | 24765 | is specific to @var{object}; it can supply additional details about what data |
0876f84a DJ |
24766 | to access. |
24767 | ||
0e7f50da UW |
24768 | Here are the specific requests of this form defined so far. All |
24769 | @samp{qXfer:@var{object}:write:@dots{}} requests use the same reply | |
24770 | formats, listed below. | |
24771 | ||
24772 | @table @samp | |
24773 | @item qXfer:@var{spu}:write:@var{annex}:@var{offset}:@var{data}@dots{} | |
24774 | @anchor{qXfer spu write} | |
24775 | Write @var{data} to an @code{spufs} file on the target system. The | |
24776 | annex specifies which file to write; it must be of the form | |
24777 | @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID | |
24778 | in the target process, and @var{name} identifes the @code{spufs} file | |
24779 | in that context to be accessed. | |
24780 | ||
24781 | This packet is not probed by default; the remote stub must request it, | |
24782 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
24783 | @end table | |
0876f84a DJ |
24784 | |
24785 | Reply: | |
24786 | @table @samp | |
24787 | @item @var{nn} | |
24788 | @var{nn} (hex encoded) is the number of bytes written. | |
24789 | This may be fewer bytes than supplied in the request. | |
24790 | ||
24791 | @item E00 | |
24792 | The request was malformed, or @var{annex} was invalid. | |
24793 | ||
24794 | @item E @var{nn} | |
24795 | The offset was invalid, or there was an error encountered writing the data. | |
24796 | @var{nn} is a hex-encoded @code{errno} value. | |
24797 | ||
24798 | @item | |
24799 | An empty reply indicates the @var{object} string was not | |
24800 | recognized by the stub, or that the object does not support writing. | |
24801 | @end table | |
24802 | ||
24803 | @item qXfer:@var{object}:@var{operation}:@dots{} | |
24804 | Requests of this form may be added in the future. When a stub does | |
24805 | not recognize the @var{object} keyword, or its support for | |
24806 | @var{object} does not recognize the @var{operation} keyword, the stub | |
24807 | must respond with an empty packet. | |
24808 | ||
ee2d5c50 AC |
24809 | @end table |
24810 | ||
24811 | @node Register Packet Format | |
24812 | @section Register Packet Format | |
eb12ee30 | 24813 | |
b8ff78ce | 24814 | The following @code{g}/@code{G} packets have previously been defined. |
ee2d5c50 AC |
24815 | In the below, some thirty-two bit registers are transferred as |
24816 | sixty-four bits. Those registers should be zero/sign extended (which?) | |
599b237a BW |
24817 | to fill the space allocated. Register bytes are transferred in target |
24818 | byte order. The two nibbles within a register byte are transferred | |
ee2d5c50 | 24819 | most-significant - least-significant. |
eb12ee30 | 24820 | |
ee2d5c50 | 24821 | @table @r |
eb12ee30 | 24822 | |
8e04817f | 24823 | @item MIPS32 |
ee2d5c50 | 24824 | |
599b237a | 24825 | All registers are transferred as thirty-two bit quantities in the order: |
8e04817f AC |
24826 | 32 general-purpose; sr; lo; hi; bad; cause; pc; 32 floating-point |
24827 | registers; fsr; fir; fp. | |
eb12ee30 | 24828 | |
8e04817f | 24829 | @item MIPS64 |
ee2d5c50 | 24830 | |
599b237a | 24831 | All registers are transferred as sixty-four bit quantities (including |
8e04817f AC |
24832 | thirty-two bit registers such as @code{sr}). The ordering is the same |
24833 | as @code{MIPS32}. | |
eb12ee30 | 24834 | |
ee2d5c50 AC |
24835 | @end table |
24836 | ||
9d29849a JB |
24837 | @node Tracepoint Packets |
24838 | @section Tracepoint Packets | |
24839 | @cindex tracepoint packets | |
24840 | @cindex packets, tracepoint | |
24841 | ||
24842 | Here we describe the packets @value{GDBN} uses to implement | |
24843 | tracepoints (@pxref{Tracepoints}). | |
24844 | ||
24845 | @table @samp | |
24846 | ||
24847 | @item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}@r{[}-@r{]} | |
24848 | Create a new tracepoint, number @var{n}, at @var{addr}. If @var{ena} | |
24849 | is @samp{E}, then the tracepoint is enabled; if it is @samp{D}, then | |
24850 | the tracepoint is disabled. @var{step} is the tracepoint's step | |
24851 | count, and @var{pass} is its pass count. If the trailing @samp{-} is | |
24852 | present, further @samp{QTDP} packets will follow to specify this | |
24853 | tracepoint's actions. | |
24854 | ||
24855 | Replies: | |
24856 | @table @samp | |
24857 | @item OK | |
24858 | The packet was understood and carried out. | |
24859 | @item | |
24860 | The packet was not recognized. | |
24861 | @end table | |
24862 | ||
24863 | @item QTDP:-@var{n}:@var{addr}:@r{[}S@r{]}@var{action}@dots{}@r{[}-@r{]} | |
24864 | Define actions to be taken when a tracepoint is hit. @var{n} and | |
24865 | @var{addr} must be the same as in the initial @samp{QTDP} packet for | |
24866 | this tracepoint. This packet may only be sent immediately after | |
24867 | another @samp{QTDP} packet that ended with a @samp{-}. If the | |
24868 | trailing @samp{-} is present, further @samp{QTDP} packets will follow, | |
24869 | specifying more actions for this tracepoint. | |
24870 | ||
24871 | In the series of action packets for a given tracepoint, at most one | |
24872 | can have an @samp{S} before its first @var{action}. If such a packet | |
24873 | is sent, it and the following packets define ``while-stepping'' | |
24874 | actions. Any prior packets define ordinary actions --- that is, those | |
24875 | taken when the tracepoint is first hit. If no action packet has an | |
24876 | @samp{S}, then all the packets in the series specify ordinary | |
24877 | tracepoint actions. | |
24878 | ||
24879 | The @samp{@var{action}@dots{}} portion of the packet is a series of | |
24880 | actions, concatenated without separators. Each action has one of the | |
24881 | following forms: | |
24882 | ||
24883 | @table @samp | |
24884 | ||
24885 | @item R @var{mask} | |
24886 | Collect the registers whose bits are set in @var{mask}. @var{mask} is | |
599b237a | 24887 | a hexadecimal number whose @var{i}'th bit is set if register number |
9d29849a JB |
24888 | @var{i} should be collected. (The least significant bit is numbered |
24889 | zero.) Note that @var{mask} may be any number of digits long; it may | |
24890 | not fit in a 32-bit word. | |
24891 | ||
24892 | @item M @var{basereg},@var{offset},@var{len} | |
24893 | Collect @var{len} bytes of memory starting at the address in register | |
24894 | number @var{basereg}, plus @var{offset}. If @var{basereg} is | |
24895 | @samp{-1}, then the range has a fixed address: @var{offset} is the | |
24896 | address of the lowest byte to collect. The @var{basereg}, | |
599b237a | 24897 | @var{offset}, and @var{len} parameters are all unsigned hexadecimal |
9d29849a JB |
24898 | values (the @samp{-1} value for @var{basereg} is a special case). |
24899 | ||
24900 | @item X @var{len},@var{expr} | |
24901 | Evaluate @var{expr}, whose length is @var{len}, and collect memory as | |
24902 | it directs. @var{expr} is an agent expression, as described in | |
24903 | @ref{Agent Expressions}. Each byte of the expression is encoded as a | |
24904 | two-digit hex number in the packet; @var{len} is the number of bytes | |
24905 | in the expression (and thus one-half the number of hex digits in the | |
24906 | packet). | |
24907 | ||
24908 | @end table | |
24909 | ||
24910 | Any number of actions may be packed together in a single @samp{QTDP} | |
24911 | packet, as long as the packet does not exceed the maximum packet | |
c1947b85 JB |
24912 | length (400 bytes, for many stubs). There may be only one @samp{R} |
24913 | action per tracepoint, and it must precede any @samp{M} or @samp{X} | |
24914 | actions. Any registers referred to by @samp{M} and @samp{X} actions | |
24915 | must be collected by a preceding @samp{R} action. (The | |
24916 | ``while-stepping'' actions are treated as if they were attached to a | |
24917 | separate tracepoint, as far as these restrictions are concerned.) | |
9d29849a JB |
24918 | |
24919 | Replies: | |
24920 | @table @samp | |
24921 | @item OK | |
24922 | The packet was understood and carried out. | |
24923 | @item | |
24924 | The packet was not recognized. | |
24925 | @end table | |
24926 | ||
24927 | @item QTFrame:@var{n} | |
24928 | Select the @var{n}'th tracepoint frame from the buffer, and use the | |
24929 | register and memory contents recorded there to answer subsequent | |
24930 | request packets from @value{GDBN}. | |
24931 | ||
24932 | A successful reply from the stub indicates that the stub has found the | |
24933 | requested frame. The response is a series of parts, concatenated | |
24934 | without separators, describing the frame we selected. Each part has | |
24935 | one of the following forms: | |
24936 | ||
24937 | @table @samp | |
24938 | @item F @var{f} | |
24939 | The selected frame is number @var{n} in the trace frame buffer; | |
599b237a | 24940 | @var{f} is a hexadecimal number. If @var{f} is @samp{-1}, then there |
9d29849a JB |
24941 | was no frame matching the criteria in the request packet. |
24942 | ||
24943 | @item T @var{t} | |
24944 | The selected trace frame records a hit of tracepoint number @var{t}; | |
599b237a | 24945 | @var{t} is a hexadecimal number. |
9d29849a JB |
24946 | |
24947 | @end table | |
24948 | ||
24949 | @item QTFrame:pc:@var{addr} | |
24950 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
24951 | currently selected frame whose PC is @var{addr}; | |
599b237a | 24952 | @var{addr} is a hexadecimal number. |
9d29849a JB |
24953 | |
24954 | @item QTFrame:tdp:@var{t} | |
24955 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
24956 | currently selected frame that is a hit of tracepoint @var{t}; @var{t} | |
599b237a | 24957 | is a hexadecimal number. |
9d29849a JB |
24958 | |
24959 | @item QTFrame:range:@var{start}:@var{end} | |
24960 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
24961 | currently selected frame whose PC is between @var{start} (inclusive) | |
599b237a | 24962 | and @var{end} (exclusive); @var{start} and @var{end} are hexadecimal |
9d29849a JB |
24963 | numbers. |
24964 | ||
24965 | @item QTFrame:outside:@var{start}:@var{end} | |
24966 | Like @samp{QTFrame:range:@var{start}:@var{end}}, but select the first | |
24967 | frame @emph{outside} the given range of addresses. | |
24968 | ||
24969 | @item QTStart | |
24970 | Begin the tracepoint experiment. Begin collecting data from tracepoint | |
24971 | hits in the trace frame buffer. | |
24972 | ||
24973 | @item QTStop | |
24974 | End the tracepoint experiment. Stop collecting trace frames. | |
24975 | ||
24976 | @item QTinit | |
24977 | Clear the table of tracepoints, and empty the trace frame buffer. | |
24978 | ||
24979 | @item QTro:@var{start1},@var{end1}:@var{start2},@var{end2}:@dots{} | |
24980 | Establish the given ranges of memory as ``transparent''. The stub | |
24981 | will answer requests for these ranges from memory's current contents, | |
24982 | if they were not collected as part of the tracepoint hit. | |
24983 | ||
24984 | @value{GDBN} uses this to mark read-only regions of memory, like those | |
24985 | containing program code. Since these areas never change, they should | |
24986 | still have the same contents they did when the tracepoint was hit, so | |
24987 | there's no reason for the stub to refuse to provide their contents. | |
24988 | ||
24989 | @item qTStatus | |
24990 | Ask the stub if there is a trace experiment running right now. | |
24991 | ||
24992 | Replies: | |
24993 | @table @samp | |
24994 | @item T0 | |
24995 | There is no trace experiment running. | |
24996 | @item T1 | |
24997 | There is a trace experiment running. | |
24998 | @end table | |
24999 | ||
25000 | @end table | |
25001 | ||
25002 | ||
a6b151f1 DJ |
25003 | @node Host I/O Packets |
25004 | @section Host I/O Packets | |
25005 | @cindex Host I/O, remote protocol | |
25006 | @cindex file transfer, remote protocol | |
25007 | ||
25008 | The @dfn{Host I/O} packets allow @value{GDBN} to perform I/O | |
25009 | operations on the far side of a remote link. For example, Host I/O is | |
25010 | used to upload and download files to a remote target with its own | |
25011 | filesystem. Host I/O uses the same constant values and data structure | |
25012 | layout as the target-initiated File-I/O protocol. However, the | |
25013 | Host I/O packets are structured differently. The target-initiated | |
25014 | protocol relies on target memory to store parameters and buffers. | |
25015 | Host I/O requests are initiated by @value{GDBN}, and the | |
25016 | target's memory is not involved. @xref{File-I/O Remote Protocol | |
25017 | Extension}, for more details on the target-initiated protocol. | |
25018 | ||
25019 | The Host I/O request packets all encode a single operation along with | |
25020 | its arguments. They have this format: | |
25021 | ||
25022 | @table @samp | |
25023 | ||
25024 | @item vFile:@var{operation}: @var{parameter}@dots{} | |
25025 | @var{operation} is the name of the particular request; the target | |
25026 | should compare the entire packet name up to the second colon when checking | |
25027 | for a supported operation. The format of @var{parameter} depends on | |
25028 | the operation. Numbers are always passed in hexadecimal. Negative | |
25029 | numbers have an explicit minus sign (i.e.@: two's complement is not | |
25030 | used). Strings (e.g.@: filenames) are encoded as a series of | |
25031 | hexadecimal bytes. The last argument to a system call may be a | |
25032 | buffer of escaped binary data (@pxref{Binary Data}). | |
25033 | ||
25034 | @end table | |
25035 | ||
25036 | The valid responses to Host I/O packets are: | |
25037 | ||
25038 | @table @samp | |
25039 | ||
25040 | @item F @var{result} [, @var{errno}] [; @var{attachment}] | |
25041 | @var{result} is the integer value returned by this operation, usually | |
25042 | non-negative for success and -1 for errors. If an error has occured, | |
25043 | @var{errno} will be included in the result. @var{errno} will have a | |
25044 | value defined by the File-I/O protocol (@pxref{Errno Values}). For | |
25045 | operations which return data, @var{attachment} supplies the data as a | |
25046 | binary buffer. Binary buffers in response packets are escaped in the | |
25047 | normal way (@pxref{Binary Data}). See the individual packet | |
25048 | documentation for the interpretation of @var{result} and | |
25049 | @var{attachment}. | |
25050 | ||
25051 | @item | |
25052 | An empty response indicates that this operation is not recognized. | |
25053 | ||
25054 | @end table | |
25055 | ||
25056 | These are the supported Host I/O operations: | |
25057 | ||
25058 | @table @samp | |
25059 | @item vFile:open: @var{pathname}, @var{flags}, @var{mode} | |
25060 | Open a file at @var{pathname} and return a file descriptor for it, or | |
25061 | return -1 if an error occurs. @var{pathname} is a string, | |
25062 | @var{flags} is an integer indicating a mask of open flags | |
25063 | (@pxref{Open Flags}), and @var{mode} is an integer indicating a mask | |
25064 | of mode bits to use if the file is created (@pxref{mode_t Values}). | |
c1c25a1a | 25065 | @xref{open}, for details of the open flags and mode values. |
a6b151f1 DJ |
25066 | |
25067 | @item vFile:close: @var{fd} | |
25068 | Close the open file corresponding to @var{fd} and return 0, or | |
25069 | -1 if an error occurs. | |
25070 | ||
25071 | @item vFile:pread: @var{fd}, @var{count}, @var{offset} | |
25072 | Read data from the open file corresponding to @var{fd}. Up to | |
25073 | @var{count} bytes will be read from the file, starting at @var{offset} | |
25074 | relative to the start of the file. The target may read fewer bytes; | |
25075 | common reasons include packet size limits and an end-of-file | |
25076 | condition. The number of bytes read is returned. Zero should only be | |
25077 | returned for a successful read at the end of the file, or if | |
25078 | @var{count} was zero. | |
25079 | ||
25080 | The data read should be returned as a binary attachment on success. | |
25081 | If zero bytes were read, the response should include an empty binary | |
25082 | attachment (i.e.@: a trailing semicolon). The return value is the | |
25083 | number of target bytes read; the binary attachment may be longer if | |
25084 | some characters were escaped. | |
25085 | ||
25086 | @item vFile:pwrite: @var{fd}, @var{offset}, @var{data} | |
25087 | Write @var{data} (a binary buffer) to the open file corresponding | |
25088 | to @var{fd}. Start the write at @var{offset} from the start of the | |
25089 | file. Unlike many @code{write} system calls, there is no | |
25090 | separate @var{count} argument; the length of @var{data} in the | |
25091 | packet is used. @samp{vFile:write} returns the number of bytes written, | |
25092 | which may be shorter than the length of @var{data}, or -1 if an | |
25093 | error occurred. | |
25094 | ||
25095 | @item vFile:unlink: @var{pathname} | |
25096 | Delete the file at @var{pathname} on the target. Return 0, | |
25097 | or -1 if an error occurs. @var{pathname} is a string. | |
25098 | ||
25099 | @end table | |
25100 | ||
9a6253be KB |
25101 | @node Interrupts |
25102 | @section Interrupts | |
25103 | @cindex interrupts (remote protocol) | |
25104 | ||
25105 | When a program on the remote target is running, @value{GDBN} may | |
25106 | attempt to interrupt it by sending a @samp{Ctrl-C} or a @code{BREAK}, | |
25107 | control of which is specified via @value{GDBN}'s @samp{remotebreak} | |
25108 | setting (@pxref{set remotebreak}). | |
25109 | ||
25110 | The precise meaning of @code{BREAK} is defined by the transport | |
25111 | mechanism and may, in fact, be undefined. @value{GDBN} does | |
25112 | not currently define a @code{BREAK} mechanism for any of the network | |
25113 | interfaces. | |
25114 | ||
25115 | @samp{Ctrl-C}, on the other hand, is defined and implemented for all | |
25116 | transport mechanisms. It is represented by sending the single byte | |
25117 | @code{0x03} without any of the usual packet overhead described in | |
25118 | the Overview section (@pxref{Overview}). When a @code{0x03} byte is | |
25119 | transmitted as part of a packet, it is considered to be packet data | |
25120 | and does @emph{not} represent an interrupt. E.g., an @samp{X} packet | |
0876f84a | 25121 | (@pxref{X packet}), used for binary downloads, may include an unescaped |
9a6253be KB |
25122 | @code{0x03} as part of its packet. |
25123 | ||
25124 | Stubs are not required to recognize these interrupt mechanisms and the | |
25125 | precise meaning associated with receipt of the interrupt is | |
25126 | implementation defined. If the stub is successful at interrupting the | |
25127 | running program, it is expected that it will send one of the Stop | |
25128 | Reply Packets (@pxref{Stop Reply Packets}) to @value{GDBN} as a result | |
25129 | of successfully stopping the program. Interrupts received while the | |
25130 | program is stopped will be discarded. | |
25131 | ||
ee2d5c50 AC |
25132 | @node Examples |
25133 | @section Examples | |
eb12ee30 | 25134 | |
8e04817f AC |
25135 | Example sequence of a target being re-started. Notice how the restart |
25136 | does not get any direct output: | |
eb12ee30 | 25137 | |
474c8240 | 25138 | @smallexample |
d2c6833e AC |
25139 | -> @code{R00} |
25140 | <- @code{+} | |
8e04817f | 25141 | @emph{target restarts} |
d2c6833e | 25142 | -> @code{?} |
8e04817f | 25143 | <- @code{+} |
d2c6833e AC |
25144 | <- @code{T001:1234123412341234} |
25145 | -> @code{+} | |
474c8240 | 25146 | @end smallexample |
eb12ee30 | 25147 | |
8e04817f | 25148 | Example sequence of a target being stepped by a single instruction: |
eb12ee30 | 25149 | |
474c8240 | 25150 | @smallexample |
d2c6833e | 25151 | -> @code{G1445@dots{}} |
8e04817f | 25152 | <- @code{+} |
d2c6833e AC |
25153 | -> @code{s} |
25154 | <- @code{+} | |
25155 | @emph{time passes} | |
25156 | <- @code{T001:1234123412341234} | |
8e04817f | 25157 | -> @code{+} |
d2c6833e | 25158 | -> @code{g} |
8e04817f | 25159 | <- @code{+} |
d2c6833e AC |
25160 | <- @code{1455@dots{}} |
25161 | -> @code{+} | |
474c8240 | 25162 | @end smallexample |
eb12ee30 | 25163 | |
79a6e687 BW |
25164 | @node File-I/O Remote Protocol Extension |
25165 | @section File-I/O Remote Protocol Extension | |
0ce1b118 CV |
25166 | @cindex File-I/O remote protocol extension |
25167 | ||
25168 | @menu | |
25169 | * File-I/O Overview:: | |
79a6e687 BW |
25170 | * Protocol Basics:: |
25171 | * The F Request Packet:: | |
25172 | * The F Reply Packet:: | |
25173 | * The Ctrl-C Message:: | |
0ce1b118 | 25174 | * Console I/O:: |
79a6e687 | 25175 | * List of Supported Calls:: |
db2e3e2e | 25176 | * Protocol-specific Representation of Datatypes:: |
0ce1b118 CV |
25177 | * Constants:: |
25178 | * File-I/O Examples:: | |
25179 | @end menu | |
25180 | ||
25181 | @node File-I/O Overview | |
25182 | @subsection File-I/O Overview | |
25183 | @cindex file-i/o overview | |
25184 | ||
9c16f35a | 25185 | The @dfn{File I/O remote protocol extension} (short: File-I/O) allows the |
fc320d37 | 25186 | target to use the host's file system and console I/O to perform various |
0ce1b118 | 25187 | system calls. System calls on the target system are translated into a |
fc320d37 SL |
25188 | remote protocol packet to the host system, which then performs the needed |
25189 | actions and returns a response packet to the target system. | |
0ce1b118 CV |
25190 | This simulates file system operations even on targets that lack file systems. |
25191 | ||
fc320d37 SL |
25192 | The protocol is defined to be independent of both the host and target systems. |
25193 | It uses its own internal representation of datatypes and values. Both | |
0ce1b118 | 25194 | @value{GDBN} and the target's @value{GDBN} stub are responsible for |
fc320d37 SL |
25195 | translating the system-dependent value representations into the internal |
25196 | protocol representations when data is transmitted. | |
0ce1b118 | 25197 | |
fc320d37 SL |
25198 | The communication is synchronous. A system call is possible only when |
25199 | @value{GDBN} is waiting for a response from the @samp{C}, @samp{c}, @samp{S} | |
25200 | or @samp{s} packets. While @value{GDBN} handles the request for a system call, | |
0ce1b118 | 25201 | the target is stopped to allow deterministic access to the target's |
fc320d37 SL |
25202 | memory. Therefore File-I/O is not interruptible by target signals. On |
25203 | the other hand, it is possible to interrupt File-I/O by a user interrupt | |
c8aa23ab | 25204 | (@samp{Ctrl-C}) within @value{GDBN}. |
0ce1b118 CV |
25205 | |
25206 | The target's request to perform a host system call does not finish | |
25207 | the latest @samp{C}, @samp{c}, @samp{S} or @samp{s} action. That means, | |
25208 | after finishing the system call, the target returns to continuing the | |
25209 | previous activity (continue, step). No additional continue or step | |
25210 | request from @value{GDBN} is required. | |
25211 | ||
25212 | @smallexample | |
f7dc1244 | 25213 | (@value{GDBP}) continue |
0ce1b118 CV |
25214 | <- target requests 'system call X' |
25215 | target is stopped, @value{GDBN} executes system call | |
3f94c067 BW |
25216 | -> @value{GDBN} returns result |
25217 | ... target continues, @value{GDBN} returns to wait for the target | |
0ce1b118 CV |
25218 | <- target hits breakpoint and sends a Txx packet |
25219 | @end smallexample | |
25220 | ||
fc320d37 SL |
25221 | The protocol only supports I/O on the console and to regular files on |
25222 | the host file system. Character or block special devices, pipes, | |
25223 | named pipes, sockets or any other communication method on the host | |
0ce1b118 CV |
25224 | system are not supported by this protocol. |
25225 | ||
79a6e687 BW |
25226 | @node Protocol Basics |
25227 | @subsection Protocol Basics | |
0ce1b118 CV |
25228 | @cindex protocol basics, file-i/o |
25229 | ||
fc320d37 SL |
25230 | The File-I/O protocol uses the @code{F} packet as the request as well |
25231 | as reply packet. Since a File-I/O system call can only occur when | |
25232 | @value{GDBN} is waiting for a response from the continuing or stepping target, | |
25233 | the File-I/O request is a reply that @value{GDBN} has to expect as a result | |
25234 | of a previous @samp{C}, @samp{c}, @samp{S} or @samp{s} packet. | |
0ce1b118 CV |
25235 | This @code{F} packet contains all information needed to allow @value{GDBN} |
25236 | to call the appropriate host system call: | |
25237 | ||
25238 | @itemize @bullet | |
b383017d | 25239 | @item |
0ce1b118 CV |
25240 | A unique identifier for the requested system call. |
25241 | ||
25242 | @item | |
25243 | All parameters to the system call. Pointers are given as addresses | |
25244 | in the target memory address space. Pointers to strings are given as | |
b383017d | 25245 | pointer/length pair. Numerical values are given as they are. |
db2e3e2e | 25246 | Numerical control flags are given in a protocol-specific representation. |
0ce1b118 CV |
25247 | |
25248 | @end itemize | |
25249 | ||
fc320d37 | 25250 | At this point, @value{GDBN} has to perform the following actions. |
0ce1b118 CV |
25251 | |
25252 | @itemize @bullet | |
b383017d | 25253 | @item |
fc320d37 SL |
25254 | If the parameters include pointer values to data needed as input to a |
25255 | system call, @value{GDBN} requests this data from the target with a | |
0ce1b118 CV |
25256 | standard @code{m} packet request. This additional communication has to be |
25257 | expected by the target implementation and is handled as any other @code{m} | |
25258 | packet. | |
25259 | ||
25260 | @item | |
25261 | @value{GDBN} translates all value from protocol representation to host | |
25262 | representation as needed. Datatypes are coerced into the host types. | |
25263 | ||
25264 | @item | |
fc320d37 | 25265 | @value{GDBN} calls the system call. |
0ce1b118 CV |
25266 | |
25267 | @item | |
25268 | It then coerces datatypes back to protocol representation. | |
25269 | ||
25270 | @item | |
fc320d37 SL |
25271 | If the system call is expected to return data in buffer space specified |
25272 | by pointer parameters to the call, the data is transmitted to the | |
0ce1b118 CV |
25273 | target using a @code{M} or @code{X} packet. This packet has to be expected |
25274 | by the target implementation and is handled as any other @code{M} or @code{X} | |
25275 | packet. | |
25276 | ||
25277 | @end itemize | |
25278 | ||
25279 | Eventually @value{GDBN} replies with another @code{F} packet which contains all | |
25280 | necessary information for the target to continue. This at least contains | |
25281 | ||
25282 | @itemize @bullet | |
25283 | @item | |
25284 | Return value. | |
25285 | ||
25286 | @item | |
25287 | @code{errno}, if has been changed by the system call. | |
25288 | ||
25289 | @item | |
25290 | ``Ctrl-C'' flag. | |
25291 | ||
25292 | @end itemize | |
25293 | ||
25294 | After having done the needed type and value coercion, the target continues | |
25295 | the latest continue or step action. | |
25296 | ||
79a6e687 BW |
25297 | @node The F Request Packet |
25298 | @subsection The @code{F} Request Packet | |
0ce1b118 CV |
25299 | @cindex file-i/o request packet |
25300 | @cindex @code{F} request packet | |
25301 | ||
25302 | The @code{F} request packet has the following format: | |
25303 | ||
25304 | @table @samp | |
fc320d37 | 25305 | @item F@var{call-id},@var{parameter@dots{}} |
0ce1b118 CV |
25306 | |
25307 | @var{call-id} is the identifier to indicate the host system call to be called. | |
25308 | This is just the name of the function. | |
25309 | ||
fc320d37 SL |
25310 | @var{parameter@dots{}} are the parameters to the system call. |
25311 | Parameters are hexadecimal integer values, either the actual values in case | |
25312 | of scalar datatypes, pointers to target buffer space in case of compound | |
25313 | datatypes and unspecified memory areas, or pointer/length pairs in case | |
25314 | of string parameters. These are appended to the @var{call-id} as a | |
25315 | comma-delimited list. All values are transmitted in ASCII | |
25316 | string representation, pointer/length pairs separated by a slash. | |
0ce1b118 | 25317 | |
b383017d | 25318 | @end table |
0ce1b118 | 25319 | |
fc320d37 | 25320 | |
0ce1b118 | 25321 | |
79a6e687 BW |
25322 | @node The F Reply Packet |
25323 | @subsection The @code{F} Reply Packet | |
0ce1b118 CV |
25324 | @cindex file-i/o reply packet |
25325 | @cindex @code{F} reply packet | |
25326 | ||
25327 | The @code{F} reply packet has the following format: | |
25328 | ||
25329 | @table @samp | |
25330 | ||
d3bdde98 | 25331 | @item F@var{retcode},@var{errno},@var{Ctrl-C flag};@var{call-specific attachment} |
0ce1b118 CV |
25332 | |
25333 | @var{retcode} is the return code of the system call as hexadecimal value. | |
25334 | ||
db2e3e2e BW |
25335 | @var{errno} is the @code{errno} set by the call, in protocol-specific |
25336 | representation. | |
0ce1b118 CV |
25337 | This parameter can be omitted if the call was successful. |
25338 | ||
fc320d37 SL |
25339 | @var{Ctrl-C flag} is only sent if the user requested a break. In this |
25340 | case, @var{errno} must be sent as well, even if the call was successful. | |
25341 | The @var{Ctrl-C flag} itself consists of the character @samp{C}: | |
0ce1b118 CV |
25342 | |
25343 | @smallexample | |
25344 | F0,0,C | |
25345 | @end smallexample | |
25346 | ||
25347 | @noindent | |
fc320d37 | 25348 | or, if the call was interrupted before the host call has been performed: |
0ce1b118 CV |
25349 | |
25350 | @smallexample | |
25351 | F-1,4,C | |
25352 | @end smallexample | |
25353 | ||
25354 | @noindent | |
db2e3e2e | 25355 | assuming 4 is the protocol-specific representation of @code{EINTR}. |
0ce1b118 CV |
25356 | |
25357 | @end table | |
25358 | ||
0ce1b118 | 25359 | |
79a6e687 BW |
25360 | @node The Ctrl-C Message |
25361 | @subsection The @samp{Ctrl-C} Message | |
0ce1b118 CV |
25362 | @cindex ctrl-c message, in file-i/o protocol |
25363 | ||
c8aa23ab | 25364 | If the @samp{Ctrl-C} flag is set in the @value{GDBN} |
79a6e687 | 25365 | reply packet (@pxref{The F Reply Packet}), |
fc320d37 | 25366 | the target should behave as if it had |
0ce1b118 | 25367 | gotten a break message. The meaning for the target is ``system call |
fc320d37 | 25368 | interrupted by @code{SIGINT}''. Consequentially, the target should actually stop |
0ce1b118 | 25369 | (as with a break message) and return to @value{GDBN} with a @code{T02} |
c8aa23ab | 25370 | packet. |
fc320d37 SL |
25371 | |
25372 | It's important for the target to know in which | |
25373 | state the system call was interrupted. There are two possible cases: | |
0ce1b118 CV |
25374 | |
25375 | @itemize @bullet | |
25376 | @item | |
25377 | The system call hasn't been performed on the host yet. | |
25378 | ||
25379 | @item | |
25380 | The system call on the host has been finished. | |
25381 | ||
25382 | @end itemize | |
25383 | ||
25384 | These two states can be distinguished by the target by the value of the | |
25385 | returned @code{errno}. If it's the protocol representation of @code{EINTR}, the system | |
25386 | call hasn't been performed. This is equivalent to the @code{EINTR} handling | |
25387 | on POSIX systems. In any other case, the target may presume that the | |
fc320d37 | 25388 | system call has been finished --- successfully or not --- and should behave |
0ce1b118 CV |
25389 | as if the break message arrived right after the system call. |
25390 | ||
fc320d37 | 25391 | @value{GDBN} must behave reliably. If the system call has not been called |
0ce1b118 CV |
25392 | yet, @value{GDBN} may send the @code{F} reply immediately, setting @code{EINTR} as |
25393 | @code{errno} in the packet. If the system call on the host has been finished | |
fc320d37 SL |
25394 | before the user requests a break, the full action must be finished by |
25395 | @value{GDBN}. This requires sending @code{M} or @code{X} packets as necessary. | |
25396 | The @code{F} packet may only be sent when either nothing has happened | |
0ce1b118 CV |
25397 | or the full action has been completed. |
25398 | ||
25399 | @node Console I/O | |
25400 | @subsection Console I/O | |
25401 | @cindex console i/o as part of file-i/o | |
25402 | ||
d3e8051b | 25403 | By default and if not explicitly closed by the target system, the file |
0ce1b118 CV |
25404 | descriptors 0, 1 and 2 are connected to the @value{GDBN} console. Output |
25405 | on the @value{GDBN} console is handled as any other file output operation | |
25406 | (@code{write(1, @dots{})} or @code{write(2, @dots{})}). Console input is handled | |
25407 | by @value{GDBN} so that after the target read request from file descriptor | |
25408 | 0 all following typing is buffered until either one of the following | |
25409 | conditions is met: | |
25410 | ||
25411 | @itemize @bullet | |
25412 | @item | |
c8aa23ab | 25413 | The user types @kbd{Ctrl-c}. The behaviour is as explained above, and the |
0ce1b118 CV |
25414 | @code{read} |
25415 | system call is treated as finished. | |
25416 | ||
25417 | @item | |
7f9087cb | 25418 | The user presses @key{RET}. This is treated as end of input with a trailing |
fc320d37 | 25419 | newline. |
0ce1b118 CV |
25420 | |
25421 | @item | |
c8aa23ab EZ |
25422 | The user types @kbd{Ctrl-d}. This is treated as end of input. No trailing |
25423 | character (neither newline nor @samp{Ctrl-D}) is appended to the input. | |
0ce1b118 CV |
25424 | |
25425 | @end itemize | |
25426 | ||
fc320d37 SL |
25427 | If the user has typed more characters than fit in the buffer given to |
25428 | the @code{read} call, the trailing characters are buffered in @value{GDBN} until | |
25429 | either another @code{read(0, @dots{})} is requested by the target, or debugging | |
25430 | is stopped at the user's request. | |
0ce1b118 | 25431 | |
0ce1b118 | 25432 | |
79a6e687 BW |
25433 | @node List of Supported Calls |
25434 | @subsection List of Supported Calls | |
0ce1b118 CV |
25435 | @cindex list of supported file-i/o calls |
25436 | ||
25437 | @menu | |
25438 | * open:: | |
25439 | * close:: | |
25440 | * read:: | |
25441 | * write:: | |
25442 | * lseek:: | |
25443 | * rename:: | |
25444 | * unlink:: | |
25445 | * stat/fstat:: | |
25446 | * gettimeofday:: | |
25447 | * isatty:: | |
25448 | * system:: | |
25449 | @end menu | |
25450 | ||
25451 | @node open | |
25452 | @unnumberedsubsubsec open | |
25453 | @cindex open, file-i/o system call | |
25454 | ||
fc320d37 SL |
25455 | @table @asis |
25456 | @item Synopsis: | |
0ce1b118 | 25457 | @smallexample |
0ce1b118 CV |
25458 | int open(const char *pathname, int flags); |
25459 | int open(const char *pathname, int flags, mode_t mode); | |
0ce1b118 CV |
25460 | @end smallexample |
25461 | ||
fc320d37 SL |
25462 | @item Request: |
25463 | @samp{Fopen,@var{pathptr}/@var{len},@var{flags},@var{mode}} | |
25464 | ||
0ce1b118 | 25465 | @noindent |
fc320d37 | 25466 | @var{flags} is the bitwise @code{OR} of the following values: |
0ce1b118 CV |
25467 | |
25468 | @table @code | |
b383017d | 25469 | @item O_CREAT |
0ce1b118 CV |
25470 | If the file does not exist it will be created. The host |
25471 | rules apply as far as file ownership and time stamps | |
25472 | are concerned. | |
25473 | ||
b383017d | 25474 | @item O_EXCL |
fc320d37 | 25475 | When used with @code{O_CREAT}, if the file already exists it is |
0ce1b118 CV |
25476 | an error and open() fails. |
25477 | ||
b383017d | 25478 | @item O_TRUNC |
0ce1b118 | 25479 | If the file already exists and the open mode allows |
fc320d37 SL |
25480 | writing (@code{O_RDWR} or @code{O_WRONLY} is given) it will be |
25481 | truncated to zero length. | |
0ce1b118 | 25482 | |
b383017d | 25483 | @item O_APPEND |
0ce1b118 CV |
25484 | The file is opened in append mode. |
25485 | ||
b383017d | 25486 | @item O_RDONLY |
0ce1b118 CV |
25487 | The file is opened for reading only. |
25488 | ||
b383017d | 25489 | @item O_WRONLY |
0ce1b118 CV |
25490 | The file is opened for writing only. |
25491 | ||
b383017d | 25492 | @item O_RDWR |
0ce1b118 | 25493 | The file is opened for reading and writing. |
fc320d37 | 25494 | @end table |
0ce1b118 CV |
25495 | |
25496 | @noindent | |
fc320d37 | 25497 | Other bits are silently ignored. |
0ce1b118 | 25498 | |
0ce1b118 CV |
25499 | |
25500 | @noindent | |
fc320d37 | 25501 | @var{mode} is the bitwise @code{OR} of the following values: |
0ce1b118 CV |
25502 | |
25503 | @table @code | |
b383017d | 25504 | @item S_IRUSR |
0ce1b118 CV |
25505 | User has read permission. |
25506 | ||
b383017d | 25507 | @item S_IWUSR |
0ce1b118 CV |
25508 | User has write permission. |
25509 | ||
b383017d | 25510 | @item S_IRGRP |
0ce1b118 CV |
25511 | Group has read permission. |
25512 | ||
b383017d | 25513 | @item S_IWGRP |
0ce1b118 CV |
25514 | Group has write permission. |
25515 | ||
b383017d | 25516 | @item S_IROTH |
0ce1b118 CV |
25517 | Others have read permission. |
25518 | ||
b383017d | 25519 | @item S_IWOTH |
0ce1b118 | 25520 | Others have write permission. |
fc320d37 | 25521 | @end table |
0ce1b118 CV |
25522 | |
25523 | @noindent | |
fc320d37 | 25524 | Other bits are silently ignored. |
0ce1b118 | 25525 | |
0ce1b118 | 25526 | |
fc320d37 SL |
25527 | @item Return value: |
25528 | @code{open} returns the new file descriptor or -1 if an error | |
25529 | occurred. | |
0ce1b118 | 25530 | |
fc320d37 | 25531 | @item Errors: |
0ce1b118 CV |
25532 | |
25533 | @table @code | |
b383017d | 25534 | @item EEXIST |
fc320d37 | 25535 | @var{pathname} already exists and @code{O_CREAT} and @code{O_EXCL} were used. |
0ce1b118 | 25536 | |
b383017d | 25537 | @item EISDIR |
fc320d37 | 25538 | @var{pathname} refers to a directory. |
0ce1b118 | 25539 | |
b383017d | 25540 | @item EACCES |
0ce1b118 CV |
25541 | The requested access is not allowed. |
25542 | ||
25543 | @item ENAMETOOLONG | |
fc320d37 | 25544 | @var{pathname} was too long. |
0ce1b118 | 25545 | |
b383017d | 25546 | @item ENOENT |
fc320d37 | 25547 | A directory component in @var{pathname} does not exist. |
0ce1b118 | 25548 | |
b383017d | 25549 | @item ENODEV |
fc320d37 | 25550 | @var{pathname} refers to a device, pipe, named pipe or socket. |
0ce1b118 | 25551 | |
b383017d | 25552 | @item EROFS |
fc320d37 | 25553 | @var{pathname} refers to a file on a read-only filesystem and |
0ce1b118 CV |
25554 | write access was requested. |
25555 | ||
b383017d | 25556 | @item EFAULT |
fc320d37 | 25557 | @var{pathname} is an invalid pointer value. |
0ce1b118 | 25558 | |
b383017d | 25559 | @item ENOSPC |
0ce1b118 CV |
25560 | No space on device to create the file. |
25561 | ||
b383017d | 25562 | @item EMFILE |
0ce1b118 CV |
25563 | The process already has the maximum number of files open. |
25564 | ||
b383017d | 25565 | @item ENFILE |
0ce1b118 CV |
25566 | The limit on the total number of files open on the system |
25567 | has been reached. | |
25568 | ||
b383017d | 25569 | @item EINTR |
0ce1b118 CV |
25570 | The call was interrupted by the user. |
25571 | @end table | |
25572 | ||
fc320d37 SL |
25573 | @end table |
25574 | ||
0ce1b118 CV |
25575 | @node close |
25576 | @unnumberedsubsubsec close | |
25577 | @cindex close, file-i/o system call | |
25578 | ||
fc320d37 SL |
25579 | @table @asis |
25580 | @item Synopsis: | |
0ce1b118 | 25581 | @smallexample |
0ce1b118 | 25582 | int close(int fd); |
fc320d37 | 25583 | @end smallexample |
0ce1b118 | 25584 | |
fc320d37 SL |
25585 | @item Request: |
25586 | @samp{Fclose,@var{fd}} | |
0ce1b118 | 25587 | |
fc320d37 SL |
25588 | @item Return value: |
25589 | @code{close} returns zero on success, or -1 if an error occurred. | |
0ce1b118 | 25590 | |
fc320d37 | 25591 | @item Errors: |
0ce1b118 CV |
25592 | |
25593 | @table @code | |
b383017d | 25594 | @item EBADF |
fc320d37 | 25595 | @var{fd} isn't a valid open file descriptor. |
0ce1b118 | 25596 | |
b383017d | 25597 | @item EINTR |
0ce1b118 CV |
25598 | The call was interrupted by the user. |
25599 | @end table | |
25600 | ||
fc320d37 SL |
25601 | @end table |
25602 | ||
0ce1b118 CV |
25603 | @node read |
25604 | @unnumberedsubsubsec read | |
25605 | @cindex read, file-i/o system call | |
25606 | ||
fc320d37 SL |
25607 | @table @asis |
25608 | @item Synopsis: | |
0ce1b118 | 25609 | @smallexample |
0ce1b118 | 25610 | int read(int fd, void *buf, unsigned int count); |
fc320d37 | 25611 | @end smallexample |
0ce1b118 | 25612 | |
fc320d37 SL |
25613 | @item Request: |
25614 | @samp{Fread,@var{fd},@var{bufptr},@var{count}} | |
0ce1b118 | 25615 | |
fc320d37 | 25616 | @item Return value: |
0ce1b118 CV |
25617 | On success, the number of bytes read is returned. |
25618 | Zero indicates end of file. If count is zero, read | |
b383017d | 25619 | returns zero as well. On error, -1 is returned. |
0ce1b118 | 25620 | |
fc320d37 | 25621 | @item Errors: |
0ce1b118 CV |
25622 | |
25623 | @table @code | |
b383017d | 25624 | @item EBADF |
fc320d37 | 25625 | @var{fd} is not a valid file descriptor or is not open for |
0ce1b118 CV |
25626 | reading. |
25627 | ||
b383017d | 25628 | @item EFAULT |
fc320d37 | 25629 | @var{bufptr} is an invalid pointer value. |
0ce1b118 | 25630 | |
b383017d | 25631 | @item EINTR |
0ce1b118 CV |
25632 | The call was interrupted by the user. |
25633 | @end table | |
25634 | ||
fc320d37 SL |
25635 | @end table |
25636 | ||
0ce1b118 CV |
25637 | @node write |
25638 | @unnumberedsubsubsec write | |
25639 | @cindex write, file-i/o system call | |
25640 | ||
fc320d37 SL |
25641 | @table @asis |
25642 | @item Synopsis: | |
0ce1b118 | 25643 | @smallexample |
0ce1b118 | 25644 | int write(int fd, const void *buf, unsigned int count); |
fc320d37 | 25645 | @end smallexample |
0ce1b118 | 25646 | |
fc320d37 SL |
25647 | @item Request: |
25648 | @samp{Fwrite,@var{fd},@var{bufptr},@var{count}} | |
0ce1b118 | 25649 | |
fc320d37 | 25650 | @item Return value: |
0ce1b118 CV |
25651 | On success, the number of bytes written are returned. |
25652 | Zero indicates nothing was written. On error, -1 | |
25653 | is returned. | |
25654 | ||
fc320d37 | 25655 | @item Errors: |
0ce1b118 CV |
25656 | |
25657 | @table @code | |
b383017d | 25658 | @item EBADF |
fc320d37 | 25659 | @var{fd} is not a valid file descriptor or is not open for |
0ce1b118 CV |
25660 | writing. |
25661 | ||
b383017d | 25662 | @item EFAULT |
fc320d37 | 25663 | @var{bufptr} is an invalid pointer value. |
0ce1b118 | 25664 | |
b383017d | 25665 | @item EFBIG |
0ce1b118 | 25666 | An attempt was made to write a file that exceeds the |
db2e3e2e | 25667 | host-specific maximum file size allowed. |
0ce1b118 | 25668 | |
b383017d | 25669 | @item ENOSPC |
0ce1b118 CV |
25670 | No space on device to write the data. |
25671 | ||
b383017d | 25672 | @item EINTR |
0ce1b118 CV |
25673 | The call was interrupted by the user. |
25674 | @end table | |
25675 | ||
fc320d37 SL |
25676 | @end table |
25677 | ||
0ce1b118 CV |
25678 | @node lseek |
25679 | @unnumberedsubsubsec lseek | |
25680 | @cindex lseek, file-i/o system call | |
25681 | ||
fc320d37 SL |
25682 | @table @asis |
25683 | @item Synopsis: | |
0ce1b118 | 25684 | @smallexample |
0ce1b118 | 25685 | long lseek (int fd, long offset, int flag); |
0ce1b118 CV |
25686 | @end smallexample |
25687 | ||
fc320d37 SL |
25688 | @item Request: |
25689 | @samp{Flseek,@var{fd},@var{offset},@var{flag}} | |
25690 | ||
25691 | @var{flag} is one of: | |
0ce1b118 CV |
25692 | |
25693 | @table @code | |
b383017d | 25694 | @item SEEK_SET |
fc320d37 | 25695 | The offset is set to @var{offset} bytes. |
0ce1b118 | 25696 | |
b383017d | 25697 | @item SEEK_CUR |
fc320d37 | 25698 | The offset is set to its current location plus @var{offset} |
0ce1b118 CV |
25699 | bytes. |
25700 | ||
b383017d | 25701 | @item SEEK_END |
fc320d37 | 25702 | The offset is set to the size of the file plus @var{offset} |
0ce1b118 CV |
25703 | bytes. |
25704 | @end table | |
25705 | ||
fc320d37 | 25706 | @item Return value: |
0ce1b118 CV |
25707 | On success, the resulting unsigned offset in bytes from |
25708 | the beginning of the file is returned. Otherwise, a | |
25709 | value of -1 is returned. | |
25710 | ||
fc320d37 | 25711 | @item Errors: |
0ce1b118 CV |
25712 | |
25713 | @table @code | |
b383017d | 25714 | @item EBADF |
fc320d37 | 25715 | @var{fd} is not a valid open file descriptor. |
0ce1b118 | 25716 | |
b383017d | 25717 | @item ESPIPE |
fc320d37 | 25718 | @var{fd} is associated with the @value{GDBN} console. |
0ce1b118 | 25719 | |
b383017d | 25720 | @item EINVAL |
fc320d37 | 25721 | @var{flag} is not a proper value. |
0ce1b118 | 25722 | |
b383017d | 25723 | @item EINTR |
0ce1b118 CV |
25724 | The call was interrupted by the user. |
25725 | @end table | |
25726 | ||
fc320d37 SL |
25727 | @end table |
25728 | ||
0ce1b118 CV |
25729 | @node rename |
25730 | @unnumberedsubsubsec rename | |
25731 | @cindex rename, file-i/o system call | |
25732 | ||
fc320d37 SL |
25733 | @table @asis |
25734 | @item Synopsis: | |
0ce1b118 | 25735 | @smallexample |
0ce1b118 | 25736 | int rename(const char *oldpath, const char *newpath); |
fc320d37 | 25737 | @end smallexample |
0ce1b118 | 25738 | |
fc320d37 SL |
25739 | @item Request: |
25740 | @samp{Frename,@var{oldpathptr}/@var{len},@var{newpathptr}/@var{len}} | |
0ce1b118 | 25741 | |
fc320d37 | 25742 | @item Return value: |
0ce1b118 CV |
25743 | On success, zero is returned. On error, -1 is returned. |
25744 | ||
fc320d37 | 25745 | @item Errors: |
0ce1b118 CV |
25746 | |
25747 | @table @code | |
b383017d | 25748 | @item EISDIR |
fc320d37 | 25749 | @var{newpath} is an existing directory, but @var{oldpath} is not a |
0ce1b118 CV |
25750 | directory. |
25751 | ||
b383017d | 25752 | @item EEXIST |
fc320d37 | 25753 | @var{newpath} is a non-empty directory. |
0ce1b118 | 25754 | |
b383017d | 25755 | @item EBUSY |
fc320d37 | 25756 | @var{oldpath} or @var{newpath} is a directory that is in use by some |
0ce1b118 CV |
25757 | process. |
25758 | ||
b383017d | 25759 | @item EINVAL |
0ce1b118 CV |
25760 | An attempt was made to make a directory a subdirectory |
25761 | of itself. | |
25762 | ||
b383017d | 25763 | @item ENOTDIR |
fc320d37 SL |
25764 | A component used as a directory in @var{oldpath} or new |
25765 | path is not a directory. Or @var{oldpath} is a directory | |
25766 | and @var{newpath} exists but is not a directory. | |
0ce1b118 | 25767 | |
b383017d | 25768 | @item EFAULT |
fc320d37 | 25769 | @var{oldpathptr} or @var{newpathptr} are invalid pointer values. |
0ce1b118 | 25770 | |
b383017d | 25771 | @item EACCES |
0ce1b118 CV |
25772 | No access to the file or the path of the file. |
25773 | ||
25774 | @item ENAMETOOLONG | |
b383017d | 25775 | |
fc320d37 | 25776 | @var{oldpath} or @var{newpath} was too long. |
0ce1b118 | 25777 | |
b383017d | 25778 | @item ENOENT |
fc320d37 | 25779 | A directory component in @var{oldpath} or @var{newpath} does not exist. |
0ce1b118 | 25780 | |
b383017d | 25781 | @item EROFS |
0ce1b118 CV |
25782 | The file is on a read-only filesystem. |
25783 | ||
b383017d | 25784 | @item ENOSPC |
0ce1b118 CV |
25785 | The device containing the file has no room for the new |
25786 | directory entry. | |
25787 | ||
b383017d | 25788 | @item EINTR |
0ce1b118 CV |
25789 | The call was interrupted by the user. |
25790 | @end table | |
25791 | ||
fc320d37 SL |
25792 | @end table |
25793 | ||
0ce1b118 CV |
25794 | @node unlink |
25795 | @unnumberedsubsubsec unlink | |
25796 | @cindex unlink, file-i/o system call | |
25797 | ||
fc320d37 SL |
25798 | @table @asis |
25799 | @item Synopsis: | |
0ce1b118 | 25800 | @smallexample |
0ce1b118 | 25801 | int unlink(const char *pathname); |
fc320d37 | 25802 | @end smallexample |
0ce1b118 | 25803 | |
fc320d37 SL |
25804 | @item Request: |
25805 | @samp{Funlink,@var{pathnameptr}/@var{len}} | |
0ce1b118 | 25806 | |
fc320d37 | 25807 | @item Return value: |
0ce1b118 CV |
25808 | On success, zero is returned. On error, -1 is returned. |
25809 | ||
fc320d37 | 25810 | @item Errors: |
0ce1b118 CV |
25811 | |
25812 | @table @code | |
b383017d | 25813 | @item EACCES |
0ce1b118 CV |
25814 | No access to the file or the path of the file. |
25815 | ||
b383017d | 25816 | @item EPERM |
0ce1b118 CV |
25817 | The system does not allow unlinking of directories. |
25818 | ||
b383017d | 25819 | @item EBUSY |
fc320d37 | 25820 | The file @var{pathname} cannot be unlinked because it's |
0ce1b118 CV |
25821 | being used by another process. |
25822 | ||
b383017d | 25823 | @item EFAULT |
fc320d37 | 25824 | @var{pathnameptr} is an invalid pointer value. |
0ce1b118 CV |
25825 | |
25826 | @item ENAMETOOLONG | |
fc320d37 | 25827 | @var{pathname} was too long. |
0ce1b118 | 25828 | |
b383017d | 25829 | @item ENOENT |
fc320d37 | 25830 | A directory component in @var{pathname} does not exist. |
0ce1b118 | 25831 | |
b383017d | 25832 | @item ENOTDIR |
0ce1b118 CV |
25833 | A component of the path is not a directory. |
25834 | ||
b383017d | 25835 | @item EROFS |
0ce1b118 CV |
25836 | The file is on a read-only filesystem. |
25837 | ||
b383017d | 25838 | @item EINTR |
0ce1b118 CV |
25839 | The call was interrupted by the user. |
25840 | @end table | |
25841 | ||
fc320d37 SL |
25842 | @end table |
25843 | ||
0ce1b118 CV |
25844 | @node stat/fstat |
25845 | @unnumberedsubsubsec stat/fstat | |
25846 | @cindex fstat, file-i/o system call | |
25847 | @cindex stat, file-i/o system call | |
25848 | ||
fc320d37 SL |
25849 | @table @asis |
25850 | @item Synopsis: | |
0ce1b118 | 25851 | @smallexample |
0ce1b118 CV |
25852 | int stat(const char *pathname, struct stat *buf); |
25853 | int fstat(int fd, struct stat *buf); | |
fc320d37 | 25854 | @end smallexample |
0ce1b118 | 25855 | |
fc320d37 SL |
25856 | @item Request: |
25857 | @samp{Fstat,@var{pathnameptr}/@var{len},@var{bufptr}}@* | |
25858 | @samp{Ffstat,@var{fd},@var{bufptr}} | |
0ce1b118 | 25859 | |
fc320d37 | 25860 | @item Return value: |
0ce1b118 CV |
25861 | On success, zero is returned. On error, -1 is returned. |
25862 | ||
fc320d37 | 25863 | @item Errors: |
0ce1b118 CV |
25864 | |
25865 | @table @code | |
b383017d | 25866 | @item EBADF |
fc320d37 | 25867 | @var{fd} is not a valid open file. |
0ce1b118 | 25868 | |
b383017d | 25869 | @item ENOENT |
fc320d37 | 25870 | A directory component in @var{pathname} does not exist or the |
0ce1b118 CV |
25871 | path is an empty string. |
25872 | ||
b383017d | 25873 | @item ENOTDIR |
0ce1b118 CV |
25874 | A component of the path is not a directory. |
25875 | ||
b383017d | 25876 | @item EFAULT |
fc320d37 | 25877 | @var{pathnameptr} is an invalid pointer value. |
0ce1b118 | 25878 | |
b383017d | 25879 | @item EACCES |
0ce1b118 CV |
25880 | No access to the file or the path of the file. |
25881 | ||
25882 | @item ENAMETOOLONG | |
fc320d37 | 25883 | @var{pathname} was too long. |
0ce1b118 | 25884 | |
b383017d | 25885 | @item EINTR |
0ce1b118 CV |
25886 | The call was interrupted by the user. |
25887 | @end table | |
25888 | ||
fc320d37 SL |
25889 | @end table |
25890 | ||
0ce1b118 CV |
25891 | @node gettimeofday |
25892 | @unnumberedsubsubsec gettimeofday | |
25893 | @cindex gettimeofday, file-i/o system call | |
25894 | ||
fc320d37 SL |
25895 | @table @asis |
25896 | @item Synopsis: | |
0ce1b118 | 25897 | @smallexample |
0ce1b118 | 25898 | int gettimeofday(struct timeval *tv, void *tz); |
fc320d37 | 25899 | @end smallexample |
0ce1b118 | 25900 | |
fc320d37 SL |
25901 | @item Request: |
25902 | @samp{Fgettimeofday,@var{tvptr},@var{tzptr}} | |
0ce1b118 | 25903 | |
fc320d37 | 25904 | @item Return value: |
0ce1b118 CV |
25905 | On success, 0 is returned, -1 otherwise. |
25906 | ||
fc320d37 | 25907 | @item Errors: |
0ce1b118 CV |
25908 | |
25909 | @table @code | |
b383017d | 25910 | @item EINVAL |
fc320d37 | 25911 | @var{tz} is a non-NULL pointer. |
0ce1b118 | 25912 | |
b383017d | 25913 | @item EFAULT |
fc320d37 SL |
25914 | @var{tvptr} and/or @var{tzptr} is an invalid pointer value. |
25915 | @end table | |
25916 | ||
0ce1b118 CV |
25917 | @end table |
25918 | ||
25919 | @node isatty | |
25920 | @unnumberedsubsubsec isatty | |
25921 | @cindex isatty, file-i/o system call | |
25922 | ||
fc320d37 SL |
25923 | @table @asis |
25924 | @item Synopsis: | |
0ce1b118 | 25925 | @smallexample |
0ce1b118 | 25926 | int isatty(int fd); |
fc320d37 | 25927 | @end smallexample |
0ce1b118 | 25928 | |
fc320d37 SL |
25929 | @item Request: |
25930 | @samp{Fisatty,@var{fd}} | |
0ce1b118 | 25931 | |
fc320d37 SL |
25932 | @item Return value: |
25933 | Returns 1 if @var{fd} refers to the @value{GDBN} console, 0 otherwise. | |
0ce1b118 | 25934 | |
fc320d37 | 25935 | @item Errors: |
0ce1b118 CV |
25936 | |
25937 | @table @code | |
b383017d | 25938 | @item EINTR |
0ce1b118 CV |
25939 | The call was interrupted by the user. |
25940 | @end table | |
25941 | ||
fc320d37 SL |
25942 | @end table |
25943 | ||
25944 | Note that the @code{isatty} call is treated as a special case: it returns | |
25945 | 1 to the target if the file descriptor is attached | |
25946 | to the @value{GDBN} console, 0 otherwise. Implementing through system calls | |
25947 | would require implementing @code{ioctl} and would be more complex than | |
25948 | needed. | |
25949 | ||
25950 | ||
0ce1b118 CV |
25951 | @node system |
25952 | @unnumberedsubsubsec system | |
25953 | @cindex system, file-i/o system call | |
25954 | ||
fc320d37 SL |
25955 | @table @asis |
25956 | @item Synopsis: | |
0ce1b118 | 25957 | @smallexample |
0ce1b118 | 25958 | int system(const char *command); |
fc320d37 | 25959 | @end smallexample |
0ce1b118 | 25960 | |
fc320d37 SL |
25961 | @item Request: |
25962 | @samp{Fsystem,@var{commandptr}/@var{len}} | |
0ce1b118 | 25963 | |
fc320d37 | 25964 | @item Return value: |
5600ea19 NS |
25965 | If @var{len} is zero, the return value indicates whether a shell is |
25966 | available. A zero return value indicates a shell is not available. | |
25967 | For non-zero @var{len}, the value returned is -1 on error and the | |
25968 | return status of the command otherwise. Only the exit status of the | |
25969 | command is returned, which is extracted from the host's @code{system} | |
25970 | return value by calling @code{WEXITSTATUS(retval)}. In case | |
25971 | @file{/bin/sh} could not be executed, 127 is returned. | |
0ce1b118 | 25972 | |
fc320d37 | 25973 | @item Errors: |
0ce1b118 CV |
25974 | |
25975 | @table @code | |
b383017d | 25976 | @item EINTR |
0ce1b118 CV |
25977 | The call was interrupted by the user. |
25978 | @end table | |
25979 | ||
fc320d37 SL |
25980 | @end table |
25981 | ||
25982 | @value{GDBN} takes over the full task of calling the necessary host calls | |
25983 | to perform the @code{system} call. The return value of @code{system} on | |
25984 | the host is simplified before it's returned | |
25985 | to the target. Any termination signal information from the child process | |
25986 | is discarded, and the return value consists | |
25987 | entirely of the exit status of the called command. | |
25988 | ||
25989 | Due to security concerns, the @code{system} call is by default refused | |
25990 | by @value{GDBN}. The user has to allow this call explicitly with the | |
25991 | @code{set remote system-call-allowed 1} command. | |
25992 | ||
25993 | @table @code | |
25994 | @item set remote system-call-allowed | |
25995 | @kindex set remote system-call-allowed | |
25996 | Control whether to allow the @code{system} calls in the File I/O | |
25997 | protocol for the remote target. The default is zero (disabled). | |
25998 | ||
25999 | @item show remote system-call-allowed | |
26000 | @kindex show remote system-call-allowed | |
26001 | Show whether the @code{system} calls are allowed in the File I/O | |
26002 | protocol. | |
26003 | @end table | |
26004 | ||
db2e3e2e BW |
26005 | @node Protocol-specific Representation of Datatypes |
26006 | @subsection Protocol-specific Representation of Datatypes | |
26007 | @cindex protocol-specific representation of datatypes, in file-i/o protocol | |
0ce1b118 CV |
26008 | |
26009 | @menu | |
79a6e687 BW |
26010 | * Integral Datatypes:: |
26011 | * Pointer Values:: | |
26012 | * Memory Transfer:: | |
0ce1b118 CV |
26013 | * struct stat:: |
26014 | * struct timeval:: | |
26015 | @end menu | |
26016 | ||
79a6e687 BW |
26017 | @node Integral Datatypes |
26018 | @unnumberedsubsubsec Integral Datatypes | |
0ce1b118 CV |
26019 | @cindex integral datatypes, in file-i/o protocol |
26020 | ||
fc320d37 SL |
26021 | The integral datatypes used in the system calls are @code{int}, |
26022 | @code{unsigned int}, @code{long}, @code{unsigned long}, | |
26023 | @code{mode_t}, and @code{time_t}. | |
0ce1b118 | 26024 | |
fc320d37 | 26025 | @code{int}, @code{unsigned int}, @code{mode_t} and @code{time_t} are |
0ce1b118 CV |
26026 | implemented as 32 bit values in this protocol. |
26027 | ||
fc320d37 | 26028 | @code{long} and @code{unsigned long} are implemented as 64 bit types. |
b383017d | 26029 | |
0ce1b118 CV |
26030 | @xref{Limits}, for corresponding MIN and MAX values (similar to those |
26031 | in @file{limits.h}) to allow range checking on host and target. | |
26032 | ||
26033 | @code{time_t} datatypes are defined as seconds since the Epoch. | |
26034 | ||
26035 | All integral datatypes transferred as part of a memory read or write of a | |
26036 | structured datatype e.g.@: a @code{struct stat} have to be given in big endian | |
26037 | byte order. | |
26038 | ||
79a6e687 BW |
26039 | @node Pointer Values |
26040 | @unnumberedsubsubsec Pointer Values | |
0ce1b118 CV |
26041 | @cindex pointer values, in file-i/o protocol |
26042 | ||
26043 | Pointers to target data are transmitted as they are. An exception | |
26044 | is made for pointers to buffers for which the length isn't | |
26045 | transmitted as part of the function call, namely strings. Strings | |
26046 | are transmitted as a pointer/length pair, both as hex values, e.g.@: | |
26047 | ||
26048 | @smallexample | |
26049 | @code{1aaf/12} | |
26050 | @end smallexample | |
26051 | ||
26052 | @noindent | |
26053 | which is a pointer to data of length 18 bytes at position 0x1aaf. | |
26054 | The length is defined as the full string length in bytes, including | |
fc320d37 SL |
26055 | the trailing null byte. For example, the string @code{"hello world"} |
26056 | at address 0x123456 is transmitted as | |
0ce1b118 CV |
26057 | |
26058 | @smallexample | |
fc320d37 | 26059 | @code{123456/d} |
0ce1b118 CV |
26060 | @end smallexample |
26061 | ||
79a6e687 BW |
26062 | @node Memory Transfer |
26063 | @unnumberedsubsubsec Memory Transfer | |
fc320d37 SL |
26064 | @cindex memory transfer, in file-i/o protocol |
26065 | ||
26066 | Structured data which is transferred using a memory read or write (for | |
db2e3e2e | 26067 | example, a @code{struct stat}) is expected to be in a protocol-specific format |
fc320d37 SL |
26068 | with all scalar multibyte datatypes being big endian. Translation to |
26069 | this representation needs to be done both by the target before the @code{F} | |
26070 | packet is sent, and by @value{GDBN} before | |
26071 | it transfers memory to the target. Transferred pointers to structured | |
26072 | data should point to the already-coerced data at any time. | |
0ce1b118 | 26073 | |
0ce1b118 CV |
26074 | |
26075 | @node struct stat | |
26076 | @unnumberedsubsubsec struct stat | |
26077 | @cindex struct stat, in file-i/o protocol | |
26078 | ||
fc320d37 SL |
26079 | The buffer of type @code{struct stat} used by the target and @value{GDBN} |
26080 | is defined as follows: | |
0ce1b118 CV |
26081 | |
26082 | @smallexample | |
26083 | struct stat @{ | |
26084 | unsigned int st_dev; /* device */ | |
26085 | unsigned int st_ino; /* inode */ | |
26086 | mode_t st_mode; /* protection */ | |
26087 | unsigned int st_nlink; /* number of hard links */ | |
26088 | unsigned int st_uid; /* user ID of owner */ | |
26089 | unsigned int st_gid; /* group ID of owner */ | |
26090 | unsigned int st_rdev; /* device type (if inode device) */ | |
26091 | unsigned long st_size; /* total size, in bytes */ | |
26092 | unsigned long st_blksize; /* blocksize for filesystem I/O */ | |
26093 | unsigned long st_blocks; /* number of blocks allocated */ | |
26094 | time_t st_atime; /* time of last access */ | |
26095 | time_t st_mtime; /* time of last modification */ | |
26096 | time_t st_ctime; /* time of last change */ | |
26097 | @}; | |
26098 | @end smallexample | |
26099 | ||
fc320d37 | 26100 | The integral datatypes conform to the definitions given in the |
79a6e687 | 26101 | appropriate section (see @ref{Integral Datatypes}, for details) so this |
0ce1b118 CV |
26102 | structure is of size 64 bytes. |
26103 | ||
26104 | The values of several fields have a restricted meaning and/or | |
26105 | range of values. | |
26106 | ||
fc320d37 | 26107 | @table @code |
0ce1b118 | 26108 | |
fc320d37 SL |
26109 | @item st_dev |
26110 | A value of 0 represents a file, 1 the console. | |
0ce1b118 | 26111 | |
fc320d37 SL |
26112 | @item st_ino |
26113 | No valid meaning for the target. Transmitted unchanged. | |
0ce1b118 | 26114 | |
fc320d37 SL |
26115 | @item st_mode |
26116 | Valid mode bits are described in @ref{Constants}. Any other | |
26117 | bits have currently no meaning for the target. | |
0ce1b118 | 26118 | |
fc320d37 SL |
26119 | @item st_uid |
26120 | @itemx st_gid | |
26121 | @itemx st_rdev | |
26122 | No valid meaning for the target. Transmitted unchanged. | |
0ce1b118 | 26123 | |
fc320d37 SL |
26124 | @item st_atime |
26125 | @itemx st_mtime | |
26126 | @itemx st_ctime | |
26127 | These values have a host and file system dependent | |
26128 | accuracy. Especially on Windows hosts, the file system may not | |
26129 | support exact timing values. | |
26130 | @end table | |
0ce1b118 | 26131 | |
fc320d37 SL |
26132 | The target gets a @code{struct stat} of the above representation and is |
26133 | responsible for coercing it to the target representation before | |
0ce1b118 CV |
26134 | continuing. |
26135 | ||
fc320d37 SL |
26136 | Note that due to size differences between the host, target, and protocol |
26137 | representations of @code{struct stat} members, these members could eventually | |
0ce1b118 CV |
26138 | get truncated on the target. |
26139 | ||
26140 | @node struct timeval | |
26141 | @unnumberedsubsubsec struct timeval | |
26142 | @cindex struct timeval, in file-i/o protocol | |
26143 | ||
fc320d37 | 26144 | The buffer of type @code{struct timeval} used by the File-I/O protocol |
0ce1b118 CV |
26145 | is defined as follows: |
26146 | ||
26147 | @smallexample | |
b383017d | 26148 | struct timeval @{ |
0ce1b118 CV |
26149 | time_t tv_sec; /* second */ |
26150 | long tv_usec; /* microsecond */ | |
26151 | @}; | |
26152 | @end smallexample | |
26153 | ||
fc320d37 | 26154 | The integral datatypes conform to the definitions given in the |
79a6e687 | 26155 | appropriate section (see @ref{Integral Datatypes}, for details) so this |
0ce1b118 CV |
26156 | structure is of size 8 bytes. |
26157 | ||
26158 | @node Constants | |
26159 | @subsection Constants | |
26160 | @cindex constants, in file-i/o protocol | |
26161 | ||
26162 | The following values are used for the constants inside of the | |
fc320d37 | 26163 | protocol. @value{GDBN} and target are responsible for translating these |
0ce1b118 CV |
26164 | values before and after the call as needed. |
26165 | ||
26166 | @menu | |
79a6e687 BW |
26167 | * Open Flags:: |
26168 | * mode_t Values:: | |
26169 | * Errno Values:: | |
26170 | * Lseek Flags:: | |
0ce1b118 CV |
26171 | * Limits:: |
26172 | @end menu | |
26173 | ||
79a6e687 BW |
26174 | @node Open Flags |
26175 | @unnumberedsubsubsec Open Flags | |
0ce1b118 CV |
26176 | @cindex open flags, in file-i/o protocol |
26177 | ||
26178 | All values are given in hexadecimal representation. | |
26179 | ||
26180 | @smallexample | |
26181 | O_RDONLY 0x0 | |
26182 | O_WRONLY 0x1 | |
26183 | O_RDWR 0x2 | |
26184 | O_APPEND 0x8 | |
26185 | O_CREAT 0x200 | |
26186 | O_TRUNC 0x400 | |
26187 | O_EXCL 0x800 | |
26188 | @end smallexample | |
26189 | ||
79a6e687 BW |
26190 | @node mode_t Values |
26191 | @unnumberedsubsubsec mode_t Values | |
0ce1b118 CV |
26192 | @cindex mode_t values, in file-i/o protocol |
26193 | ||
26194 | All values are given in octal representation. | |
26195 | ||
26196 | @smallexample | |
26197 | S_IFREG 0100000 | |
26198 | S_IFDIR 040000 | |
26199 | S_IRUSR 0400 | |
26200 | S_IWUSR 0200 | |
26201 | S_IXUSR 0100 | |
26202 | S_IRGRP 040 | |
26203 | S_IWGRP 020 | |
26204 | S_IXGRP 010 | |
26205 | S_IROTH 04 | |
26206 | S_IWOTH 02 | |
26207 | S_IXOTH 01 | |
26208 | @end smallexample | |
26209 | ||
79a6e687 BW |
26210 | @node Errno Values |
26211 | @unnumberedsubsubsec Errno Values | |
0ce1b118 CV |
26212 | @cindex errno values, in file-i/o protocol |
26213 | ||
26214 | All values are given in decimal representation. | |
26215 | ||
26216 | @smallexample | |
26217 | EPERM 1 | |
26218 | ENOENT 2 | |
26219 | EINTR 4 | |
26220 | EBADF 9 | |
26221 | EACCES 13 | |
26222 | EFAULT 14 | |
26223 | EBUSY 16 | |
26224 | EEXIST 17 | |
26225 | ENODEV 19 | |
26226 | ENOTDIR 20 | |
26227 | EISDIR 21 | |
26228 | EINVAL 22 | |
26229 | ENFILE 23 | |
26230 | EMFILE 24 | |
26231 | EFBIG 27 | |
26232 | ENOSPC 28 | |
26233 | ESPIPE 29 | |
26234 | EROFS 30 | |
26235 | ENAMETOOLONG 91 | |
26236 | EUNKNOWN 9999 | |
26237 | @end smallexample | |
26238 | ||
fc320d37 | 26239 | @code{EUNKNOWN} is used as a fallback error value if a host system returns |
0ce1b118 CV |
26240 | any error value not in the list of supported error numbers. |
26241 | ||
79a6e687 BW |
26242 | @node Lseek Flags |
26243 | @unnumberedsubsubsec Lseek Flags | |
0ce1b118 CV |
26244 | @cindex lseek flags, in file-i/o protocol |
26245 | ||
26246 | @smallexample | |
26247 | SEEK_SET 0 | |
26248 | SEEK_CUR 1 | |
26249 | SEEK_END 2 | |
26250 | @end smallexample | |
26251 | ||
26252 | @node Limits | |
26253 | @unnumberedsubsubsec Limits | |
26254 | @cindex limits, in file-i/o protocol | |
26255 | ||
26256 | All values are given in decimal representation. | |
26257 | ||
26258 | @smallexample | |
26259 | INT_MIN -2147483648 | |
26260 | INT_MAX 2147483647 | |
26261 | UINT_MAX 4294967295 | |
26262 | LONG_MIN -9223372036854775808 | |
26263 | LONG_MAX 9223372036854775807 | |
26264 | ULONG_MAX 18446744073709551615 | |
26265 | @end smallexample | |
26266 | ||
26267 | @node File-I/O Examples | |
26268 | @subsection File-I/O Examples | |
26269 | @cindex file-i/o examples | |
26270 | ||
26271 | Example sequence of a write call, file descriptor 3, buffer is at target | |
26272 | address 0x1234, 6 bytes should be written: | |
26273 | ||
26274 | @smallexample | |
26275 | <- @code{Fwrite,3,1234,6} | |
26276 | @emph{request memory read from target} | |
26277 | -> @code{m1234,6} | |
26278 | <- XXXXXX | |
26279 | @emph{return "6 bytes written"} | |
26280 | -> @code{F6} | |
26281 | @end smallexample | |
26282 | ||
26283 | Example sequence of a read call, file descriptor 3, buffer is at target | |
26284 | address 0x1234, 6 bytes should be read: | |
26285 | ||
26286 | @smallexample | |
26287 | <- @code{Fread,3,1234,6} | |
26288 | @emph{request memory write to target} | |
26289 | -> @code{X1234,6:XXXXXX} | |
26290 | @emph{return "6 bytes read"} | |
26291 | -> @code{F6} | |
26292 | @end smallexample | |
26293 | ||
26294 | Example sequence of a read call, call fails on the host due to invalid | |
fc320d37 | 26295 | file descriptor (@code{EBADF}): |
0ce1b118 CV |
26296 | |
26297 | @smallexample | |
26298 | <- @code{Fread,3,1234,6} | |
26299 | -> @code{F-1,9} | |
26300 | @end smallexample | |
26301 | ||
c8aa23ab | 26302 | Example sequence of a read call, user presses @kbd{Ctrl-c} before syscall on |
0ce1b118 CV |
26303 | host is called: |
26304 | ||
26305 | @smallexample | |
26306 | <- @code{Fread,3,1234,6} | |
26307 | -> @code{F-1,4,C} | |
26308 | <- @code{T02} | |
26309 | @end smallexample | |
26310 | ||
c8aa23ab | 26311 | Example sequence of a read call, user presses @kbd{Ctrl-c} after syscall on |
0ce1b118 CV |
26312 | host is called: |
26313 | ||
26314 | @smallexample | |
26315 | <- @code{Fread,3,1234,6} | |
26316 | -> @code{X1234,6:XXXXXX} | |
26317 | <- @code{T02} | |
26318 | @end smallexample | |
26319 | ||
cfa9d6d9 DJ |
26320 | @node Library List Format |
26321 | @section Library List Format | |
26322 | @cindex library list format, remote protocol | |
26323 | ||
26324 | On some platforms, a dynamic loader (e.g.@: @file{ld.so}) runs in the | |
26325 | same process as your application to manage libraries. In this case, | |
26326 | @value{GDBN} can use the loader's symbol table and normal memory | |
26327 | operations to maintain a list of shared libraries. On other | |
26328 | platforms, the operating system manages loaded libraries. | |
26329 | @value{GDBN} can not retrieve the list of currently loaded libraries | |
26330 | through memory operations, so it uses the @samp{qXfer:libraries:read} | |
26331 | packet (@pxref{qXfer library list read}) instead. The remote stub | |
26332 | queries the target's operating system and reports which libraries | |
26333 | are loaded. | |
26334 | ||
26335 | The @samp{qXfer:libraries:read} packet returns an XML document which | |
26336 | lists loaded libraries and their offsets. Each library has an | |
1fddbabb PA |
26337 | associated name and one or more segment or section base addresses, |
26338 | which report where the library was loaded in memory. | |
26339 | ||
26340 | For the common case of libraries that are fully linked binaries, the | |
26341 | library should have a list of segments. If the target supports | |
26342 | dynamic linking of a relocatable object file, its library XML element | |
26343 | should instead include a list of allocated sections. The segment or | |
26344 | section bases are start addresses, not relocation offsets; they do not | |
26345 | depend on the library's link-time base addresses. | |
cfa9d6d9 | 26346 | |
9cceb671 DJ |
26347 | @value{GDBN} must be linked with the Expat library to support XML |
26348 | library lists. @xref{Expat}. | |
26349 | ||
cfa9d6d9 DJ |
26350 | A simple memory map, with one loaded library relocated by a single |
26351 | offset, looks like this: | |
26352 | ||
26353 | @smallexample | |
26354 | <library-list> | |
26355 | <library name="/lib/libc.so.6"> | |
26356 | <segment address="0x10000000"/> | |
26357 | </library> | |
26358 | </library-list> | |
26359 | @end smallexample | |
26360 | ||
1fddbabb PA |
26361 | Another simple memory map, with one loaded library with three |
26362 | allocated sections (.text, .data, .bss), looks like this: | |
26363 | ||
26364 | @smallexample | |
26365 | <library-list> | |
26366 | <library name="sharedlib.o"> | |
26367 | <section address="0x10000000"/> | |
26368 | <section address="0x20000000"/> | |
26369 | <section address="0x30000000"/> | |
26370 | </library> | |
26371 | </library-list> | |
26372 | @end smallexample | |
26373 | ||
cfa9d6d9 DJ |
26374 | The format of a library list is described by this DTD: |
26375 | ||
26376 | @smallexample | |
26377 | <!-- library-list: Root element with versioning --> | |
26378 | <!ELEMENT library-list (library)*> | |
26379 | <!ATTLIST library-list version CDATA #FIXED "1.0"> | |
1fddbabb | 26380 | <!ELEMENT library (segment*, section*)> |
cfa9d6d9 DJ |
26381 | <!ATTLIST library name CDATA #REQUIRED> |
26382 | <!ELEMENT segment EMPTY> | |
26383 | <!ATTLIST segment address CDATA #REQUIRED> | |
1fddbabb PA |
26384 | <!ELEMENT section EMPTY> |
26385 | <!ATTLIST section address CDATA #REQUIRED> | |
cfa9d6d9 DJ |
26386 | @end smallexample |
26387 | ||
1fddbabb PA |
26388 | In addition, segments and section descriptors cannot be mixed within a |
26389 | single library element, and you must supply at least one segment or | |
26390 | section for each library. | |
26391 | ||
79a6e687 BW |
26392 | @node Memory Map Format |
26393 | @section Memory Map Format | |
68437a39 DJ |
26394 | @cindex memory map format |
26395 | ||
26396 | To be able to write into flash memory, @value{GDBN} needs to obtain a | |
26397 | memory map from the target. This section describes the format of the | |
26398 | memory map. | |
26399 | ||
26400 | The memory map is obtained using the @samp{qXfer:memory-map:read} | |
26401 | (@pxref{qXfer memory map read}) packet and is an XML document that | |
9cceb671 DJ |
26402 | lists memory regions. |
26403 | ||
26404 | @value{GDBN} must be linked with the Expat library to support XML | |
26405 | memory maps. @xref{Expat}. | |
26406 | ||
26407 | The top-level structure of the document is shown below: | |
68437a39 DJ |
26408 | |
26409 | @smallexample | |
26410 | <?xml version="1.0"?> | |
26411 | <!DOCTYPE memory-map | |
26412 | PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN" | |
26413 | "http://sourceware.org/gdb/gdb-memory-map.dtd"> | |
26414 | <memory-map> | |
26415 | region... | |
26416 | </memory-map> | |
26417 | @end smallexample | |
26418 | ||
26419 | Each region can be either: | |
26420 | ||
26421 | @itemize | |
26422 | ||
26423 | @item | |
26424 | A region of RAM starting at @var{addr} and extending for @var{length} | |
26425 | bytes from there: | |
26426 | ||
26427 | @smallexample | |
26428 | <memory type="ram" start="@var{addr}" length="@var{length}"/> | |
26429 | @end smallexample | |
26430 | ||
26431 | ||
26432 | @item | |
26433 | A region of read-only memory: | |
26434 | ||
26435 | @smallexample | |
26436 | <memory type="rom" start="@var{addr}" length="@var{length}"/> | |
26437 | @end smallexample | |
26438 | ||
26439 | ||
26440 | @item | |
26441 | A region of flash memory, with erasure blocks @var{blocksize} | |
26442 | bytes in length: | |
26443 | ||
26444 | @smallexample | |
26445 | <memory type="flash" start="@var{addr}" length="@var{length}"> | |
26446 | <property name="blocksize">@var{blocksize}</property> | |
26447 | </memory> | |
26448 | @end smallexample | |
26449 | ||
26450 | @end itemize | |
26451 | ||
26452 | Regions must not overlap. @value{GDBN} assumes that areas of memory not covered | |
26453 | by the memory map are RAM, and uses the ordinary @samp{M} and @samp{X} | |
26454 | packets to write to addresses in such ranges. | |
26455 | ||
26456 | The formal DTD for memory map format is given below: | |
26457 | ||
26458 | @smallexample | |
26459 | <!-- ................................................... --> | |
26460 | <!-- Memory Map XML DTD ................................ --> | |
26461 | <!-- File: memory-map.dtd .............................. --> | |
26462 | <!-- .................................... .............. --> | |
26463 | <!-- memory-map.dtd --> | |
26464 | <!-- memory-map: Root element with versioning --> | |
26465 | <!ELEMENT memory-map (memory | property)> | |
26466 | <!ATTLIST memory-map version CDATA #FIXED "1.0.0"> | |
26467 | <!ELEMENT memory (property)> | |
26468 | <!-- memory: Specifies a memory region, | |
26469 | and its type, or device. --> | |
26470 | <!ATTLIST memory type CDATA #REQUIRED | |
26471 | start CDATA #REQUIRED | |
26472 | length CDATA #REQUIRED | |
26473 | device CDATA #IMPLIED> | |
26474 | <!-- property: Generic attribute tag --> | |
26475 | <!ELEMENT property (#PCDATA | property)*> | |
26476 | <!ATTLIST property name CDATA #REQUIRED> | |
26477 | @end smallexample | |
26478 | ||
f418dd93 DJ |
26479 | @include agentexpr.texi |
26480 | ||
23181151 DJ |
26481 | @node Target Descriptions |
26482 | @appendix Target Descriptions | |
26483 | @cindex target descriptions | |
26484 | ||
26485 | @strong{Warning:} target descriptions are still under active development, | |
26486 | and the contents and format may change between @value{GDBN} releases. | |
26487 | The format is expected to stabilize in the future. | |
26488 | ||
26489 | One of the challenges of using @value{GDBN} to debug embedded systems | |
26490 | is that there are so many minor variants of each processor | |
26491 | architecture in use. It is common practice for vendors to start with | |
26492 | a standard processor core --- ARM, PowerPC, or MIPS, for example --- | |
26493 | and then make changes to adapt it to a particular market niche. Some | |
26494 | architectures have hundreds of variants, available from dozens of | |
26495 | vendors. This leads to a number of problems: | |
26496 | ||
26497 | @itemize @bullet | |
26498 | @item | |
26499 | With so many different customized processors, it is difficult for | |
26500 | the @value{GDBN} maintainers to keep up with the changes. | |
26501 | @item | |
26502 | Since individual variants may have short lifetimes or limited | |
26503 | audiences, it may not be worthwhile to carry information about every | |
26504 | variant in the @value{GDBN} source tree. | |
26505 | @item | |
26506 | When @value{GDBN} does support the architecture of the embedded system | |
26507 | at hand, the task of finding the correct architecture name to give the | |
26508 | @command{set architecture} command can be error-prone. | |
26509 | @end itemize | |
26510 | ||
26511 | To address these problems, the @value{GDBN} remote protocol allows a | |
26512 | target system to not only identify itself to @value{GDBN}, but to | |
26513 | actually describe its own features. This lets @value{GDBN} support | |
26514 | processor variants it has never seen before --- to the extent that the | |
26515 | descriptions are accurate, and that @value{GDBN} understands them. | |
26516 | ||
9cceb671 DJ |
26517 | @value{GDBN} must be linked with the Expat library to support XML |
26518 | target descriptions. @xref{Expat}. | |
123dc839 | 26519 | |
23181151 DJ |
26520 | @menu |
26521 | * Retrieving Descriptions:: How descriptions are fetched from a target. | |
26522 | * Target Description Format:: The contents of a target description. | |
123dc839 DJ |
26523 | * Predefined Target Types:: Standard types available for target |
26524 | descriptions. | |
26525 | * Standard Target Features:: Features @value{GDBN} knows about. | |
23181151 DJ |
26526 | @end menu |
26527 | ||
26528 | @node Retrieving Descriptions | |
26529 | @section Retrieving Descriptions | |
26530 | ||
26531 | Target descriptions can be read from the target automatically, or | |
26532 | specified by the user manually. The default behavior is to read the | |
26533 | description from the target. @value{GDBN} retrieves it via the remote | |
26534 | protocol using @samp{qXfer} requests (@pxref{General Query Packets, | |
26535 | qXfer}). The @var{annex} in the @samp{qXfer} packet will be | |
26536 | @samp{target.xml}. The contents of the @samp{target.xml} annex are an | |
26537 | XML document, of the form described in @ref{Target Description | |
26538 | Format}. | |
26539 | ||
26540 | Alternatively, you can specify a file to read for the target description. | |
26541 | If a file is set, the target will not be queried. The commands to | |
26542 | specify a file are: | |
26543 | ||
26544 | @table @code | |
26545 | @cindex set tdesc filename | |
26546 | @item set tdesc filename @var{path} | |
26547 | Read the target description from @var{path}. | |
26548 | ||
26549 | @cindex unset tdesc filename | |
26550 | @item unset tdesc filename | |
26551 | Do not read the XML target description from a file. @value{GDBN} | |
26552 | will use the description supplied by the current target. | |
26553 | ||
26554 | @cindex show tdesc filename | |
26555 | @item show tdesc filename | |
26556 | Show the filename to read for a target description, if any. | |
26557 | @end table | |
26558 | ||
26559 | ||
26560 | @node Target Description Format | |
26561 | @section Target Description Format | |
26562 | @cindex target descriptions, XML format | |
26563 | ||
26564 | A target description annex is an @uref{http://www.w3.org/XML/, XML} | |
26565 | document which complies with the Document Type Definition provided in | |
26566 | the @value{GDBN} sources in @file{gdb/features/gdb-target.dtd}. This | |
26567 | means you can use generally available tools like @command{xmllint} to | |
26568 | check that your feature descriptions are well-formed and valid. | |
26569 | However, to help people unfamiliar with XML write descriptions for | |
26570 | their targets, we also describe the grammar here. | |
26571 | ||
123dc839 DJ |
26572 | Target descriptions can identify the architecture of the remote target |
26573 | and (for some architectures) provide information about custom register | |
26574 | sets. @value{GDBN} can use this information to autoconfigure for your | |
26575 | target, or to warn you if you connect to an unsupported target. | |
23181151 DJ |
26576 | |
26577 | Here is a simple target description: | |
26578 | ||
123dc839 | 26579 | @smallexample |
1780a0ed | 26580 | <target version="1.0"> |
23181151 DJ |
26581 | <architecture>i386:x86-64</architecture> |
26582 | </target> | |
123dc839 | 26583 | @end smallexample |
23181151 DJ |
26584 | |
26585 | @noindent | |
26586 | This minimal description only says that the target uses | |
26587 | the x86-64 architecture. | |
26588 | ||
123dc839 DJ |
26589 | A target description has the following overall form, with [ ] marking |
26590 | optional elements and @dots{} marking repeatable elements. The elements | |
26591 | are explained further below. | |
23181151 | 26592 | |
123dc839 | 26593 | @smallexample |
23181151 DJ |
26594 | <?xml version="1.0"?> |
26595 | <!DOCTYPE target SYSTEM "gdb-target.dtd"> | |
1780a0ed | 26596 | <target version="1.0"> |
123dc839 DJ |
26597 | @r{[}@var{architecture}@r{]} |
26598 | @r{[}@var{feature}@dots{}@r{]} | |
23181151 | 26599 | </target> |
123dc839 | 26600 | @end smallexample |
23181151 DJ |
26601 | |
26602 | @noindent | |
26603 | The description is generally insensitive to whitespace and line | |
26604 | breaks, under the usual common-sense rules. The XML version | |
26605 | declaration and document type declaration can generally be omitted | |
26606 | (@value{GDBN} does not require them), but specifying them may be | |
1780a0ed DJ |
26607 | useful for XML validation tools. The @samp{version} attribute for |
26608 | @samp{<target>} may also be omitted, but we recommend | |
26609 | including it; if future versions of @value{GDBN} use an incompatible | |
26610 | revision of @file{gdb-target.dtd}, they will detect and report | |
26611 | the version mismatch. | |
23181151 | 26612 | |
108546a0 DJ |
26613 | @subsection Inclusion |
26614 | @cindex target descriptions, inclusion | |
26615 | @cindex XInclude | |
26616 | @ifnotinfo | |
26617 | @cindex <xi:include> | |
26618 | @end ifnotinfo | |
26619 | ||
26620 | It can sometimes be valuable to split a target description up into | |
26621 | several different annexes, either for organizational purposes, or to | |
26622 | share files between different possible target descriptions. You can | |
26623 | divide a description into multiple files by replacing any element of | |
26624 | the target description with an inclusion directive of the form: | |
26625 | ||
123dc839 | 26626 | @smallexample |
108546a0 | 26627 | <xi:include href="@var{document}"/> |
123dc839 | 26628 | @end smallexample |
108546a0 DJ |
26629 | |
26630 | @noindent | |
26631 | When @value{GDBN} encounters an element of this form, it will retrieve | |
26632 | the named XML @var{document}, and replace the inclusion directive with | |
26633 | the contents of that document. If the current description was read | |
26634 | using @samp{qXfer}, then so will be the included document; | |
26635 | @var{document} will be interpreted as the name of an annex. If the | |
26636 | current description was read from a file, @value{GDBN} will look for | |
26637 | @var{document} as a file in the same directory where it found the | |
26638 | original description. | |
26639 | ||
123dc839 DJ |
26640 | @subsection Architecture |
26641 | @cindex <architecture> | |
26642 | ||
26643 | An @samp{<architecture>} element has this form: | |
26644 | ||
26645 | @smallexample | |
26646 | <architecture>@var{arch}</architecture> | |
26647 | @end smallexample | |
26648 | ||
26649 | @var{arch} is an architecture name from the same selection | |
26650 | accepted by @code{set architecture} (@pxref{Targets, ,Specifying a | |
26651 | Debugging Target}). | |
26652 | ||
26653 | @subsection Features | |
26654 | @cindex <feature> | |
26655 | ||
26656 | Each @samp{<feature>} describes some logical portion of the target | |
26657 | system. Features are currently used to describe available CPU | |
26658 | registers and the types of their contents. A @samp{<feature>} element | |
26659 | has this form: | |
26660 | ||
26661 | @smallexample | |
26662 | <feature name="@var{name}"> | |
26663 | @r{[}@var{type}@dots{}@r{]} | |
26664 | @var{reg}@dots{} | |
26665 | </feature> | |
26666 | @end smallexample | |
26667 | ||
26668 | @noindent | |
26669 | Each feature's name should be unique within the description. The name | |
26670 | of a feature does not matter unless @value{GDBN} has some special | |
26671 | knowledge of the contents of that feature; if it does, the feature | |
26672 | should have its standard name. @xref{Standard Target Features}. | |
26673 | ||
26674 | @subsection Types | |
26675 | ||
26676 | Any register's value is a collection of bits which @value{GDBN} must | |
26677 | interpret. The default interpretation is a two's complement integer, | |
26678 | but other types can be requested by name in the register description. | |
26679 | Some predefined types are provided by @value{GDBN} (@pxref{Predefined | |
26680 | Target Types}), and the description can define additional composite types. | |
26681 | ||
26682 | Each type element must have an @samp{id} attribute, which gives | |
26683 | a unique (within the containing @samp{<feature>}) name to the type. | |
26684 | Types must be defined before they are used. | |
26685 | ||
26686 | @cindex <vector> | |
26687 | Some targets offer vector registers, which can be treated as arrays | |
26688 | of scalar elements. These types are written as @samp{<vector>} elements, | |
26689 | specifying the array element type, @var{type}, and the number of elements, | |
26690 | @var{count}: | |
26691 | ||
26692 | @smallexample | |
26693 | <vector id="@var{id}" type="@var{type}" count="@var{count}"/> | |
26694 | @end smallexample | |
26695 | ||
26696 | @cindex <union> | |
26697 | If a register's value is usefully viewed in multiple ways, define it | |
26698 | with a union type containing the useful representations. The | |
26699 | @samp{<union>} element contains one or more @samp{<field>} elements, | |
26700 | each of which has a @var{name} and a @var{type}: | |
26701 | ||
26702 | @smallexample | |
26703 | <union id="@var{id}"> | |
26704 | <field name="@var{name}" type="@var{type}"/> | |
26705 | @dots{} | |
26706 | </union> | |
26707 | @end smallexample | |
26708 | ||
26709 | @subsection Registers | |
26710 | @cindex <reg> | |
26711 | ||
26712 | Each register is represented as an element with this form: | |
26713 | ||
26714 | @smallexample | |
26715 | <reg name="@var{name}" | |
26716 | bitsize="@var{size}" | |
26717 | @r{[}regnum="@var{num}"@r{]} | |
26718 | @r{[}save-restore="@var{save-restore}"@r{]} | |
26719 | @r{[}type="@var{type}"@r{]} | |
26720 | @r{[}group="@var{group}"@r{]}/> | |
26721 | @end smallexample | |
26722 | ||
26723 | @noindent | |
26724 | The components are as follows: | |
26725 | ||
26726 | @table @var | |
26727 | ||
26728 | @item name | |
26729 | The register's name; it must be unique within the target description. | |
26730 | ||
26731 | @item bitsize | |
26732 | The register's size, in bits. | |
26733 | ||
26734 | @item regnum | |
26735 | The register's number. If omitted, a register's number is one greater | |
26736 | than that of the previous register (either in the current feature or in | |
26737 | a preceeding feature); the first register in the target description | |
26738 | defaults to zero. This register number is used to read or write | |
26739 | the register; e.g.@: it is used in the remote @code{p} and @code{P} | |
26740 | packets, and registers appear in the @code{g} and @code{G} packets | |
26741 | in order of increasing register number. | |
26742 | ||
26743 | @item save-restore | |
26744 | Whether the register should be preserved across inferior function | |
26745 | calls; this must be either @code{yes} or @code{no}. The default is | |
26746 | @code{yes}, which is appropriate for most registers except for | |
26747 | some system control registers; this is not related to the target's | |
26748 | ABI. | |
26749 | ||
26750 | @item type | |
26751 | The type of the register. @var{type} may be a predefined type, a type | |
26752 | defined in the current feature, or one of the special types @code{int} | |
26753 | and @code{float}. @code{int} is an integer type of the correct size | |
26754 | for @var{bitsize}, and @code{float} is a floating point type (in the | |
26755 | architecture's normal floating point format) of the correct size for | |
26756 | @var{bitsize}. The default is @code{int}. | |
26757 | ||
26758 | @item group | |
26759 | The register group to which this register belongs. @var{group} must | |
26760 | be either @code{general}, @code{float}, or @code{vector}. If no | |
26761 | @var{group} is specified, @value{GDBN} will not display the register | |
26762 | in @code{info registers}. | |
26763 | ||
26764 | @end table | |
26765 | ||
26766 | @node Predefined Target Types | |
26767 | @section Predefined Target Types | |
26768 | @cindex target descriptions, predefined types | |
26769 | ||
26770 | Type definitions in the self-description can build up composite types | |
26771 | from basic building blocks, but can not define fundamental types. Instead, | |
26772 | standard identifiers are provided by @value{GDBN} for the fundamental | |
26773 | types. The currently supported types are: | |
26774 | ||
26775 | @table @code | |
26776 | ||
26777 | @item int8 | |
26778 | @itemx int16 | |
26779 | @itemx int32 | |
26780 | @itemx int64 | |
7cc46491 | 26781 | @itemx int128 |
123dc839 DJ |
26782 | Signed integer types holding the specified number of bits. |
26783 | ||
26784 | @item uint8 | |
26785 | @itemx uint16 | |
26786 | @itemx uint32 | |
26787 | @itemx uint64 | |
7cc46491 | 26788 | @itemx uint128 |
123dc839 DJ |
26789 | Unsigned integer types holding the specified number of bits. |
26790 | ||
26791 | @item code_ptr | |
26792 | @itemx data_ptr | |
26793 | Pointers to unspecified code and data. The program counter and | |
26794 | any dedicated return address register may be marked as code | |
26795 | pointers; printing a code pointer converts it into a symbolic | |
26796 | address. The stack pointer and any dedicated address registers | |
26797 | may be marked as data pointers. | |
26798 | ||
6e3bbd1a PB |
26799 | @item ieee_single |
26800 | Single precision IEEE floating point. | |
26801 | ||
26802 | @item ieee_double | |
26803 | Double precision IEEE floating point. | |
26804 | ||
123dc839 DJ |
26805 | @item arm_fpa_ext |
26806 | The 12-byte extended precision format used by ARM FPA registers. | |
26807 | ||
26808 | @end table | |
26809 | ||
26810 | @node Standard Target Features | |
26811 | @section Standard Target Features | |
26812 | @cindex target descriptions, standard features | |
26813 | ||
26814 | A target description must contain either no registers or all the | |
26815 | target's registers. If the description contains no registers, then | |
26816 | @value{GDBN} will assume a default register layout, selected based on | |
26817 | the architecture. If the description contains any registers, the | |
26818 | default layout will not be used; the standard registers must be | |
26819 | described in the target description, in such a way that @value{GDBN} | |
26820 | can recognize them. | |
26821 | ||
26822 | This is accomplished by giving specific names to feature elements | |
26823 | which contain standard registers. @value{GDBN} will look for features | |
26824 | with those names and verify that they contain the expected registers; | |
26825 | if any known feature is missing required registers, or if any required | |
26826 | feature is missing, @value{GDBN} will reject the target | |
26827 | description. You can add additional registers to any of the | |
26828 | standard features --- @value{GDBN} will display them just as if | |
26829 | they were added to an unrecognized feature. | |
26830 | ||
26831 | This section lists the known features and their expected contents. | |
26832 | Sample XML documents for these features are included in the | |
26833 | @value{GDBN} source tree, in the directory @file{gdb/features}. | |
26834 | ||
26835 | Names recognized by @value{GDBN} should include the name of the | |
26836 | company or organization which selected the name, and the overall | |
26837 | architecture to which the feature applies; so e.g.@: the feature | |
26838 | containing ARM core registers is named @samp{org.gnu.gdb.arm.core}. | |
26839 | ||
ff6f572f DJ |
26840 | The names of registers are not case sensitive for the purpose |
26841 | of recognizing standard features, but @value{GDBN} will only display | |
26842 | registers using the capitalization used in the description. | |
26843 | ||
e9c17194 VP |
26844 | @menu |
26845 | * ARM Features:: | |
26846 | * M68K Features:: | |
26847 | @end menu | |
26848 | ||
26849 | ||
26850 | @node ARM Features | |
123dc839 DJ |
26851 | @subsection ARM Features |
26852 | @cindex target descriptions, ARM features | |
26853 | ||
26854 | The @samp{org.gnu.gdb.arm.core} feature is required for ARM targets. | |
26855 | It should contain registers @samp{r0} through @samp{r13}, @samp{sp}, | |
26856 | @samp{lr}, @samp{pc}, and @samp{cpsr}. | |
26857 | ||
26858 | The @samp{org.gnu.gdb.arm.fpa} feature is optional. If present, it | |
26859 | should contain registers @samp{f0} through @samp{f7} and @samp{fps}. | |
26860 | ||
ff6f572f DJ |
26861 | The @samp{org.gnu.gdb.xscale.iwmmxt} feature is optional. If present, |
26862 | it should contain at least registers @samp{wR0} through @samp{wR15} and | |
26863 | @samp{wCGR0} through @samp{wCGR3}. The @samp{wCID}, @samp{wCon}, | |
26864 | @samp{wCSSF}, and @samp{wCASF} registers are optional. | |
23181151 | 26865 | |
f8b73d13 DJ |
26866 | @subsection MIPS Features |
26867 | @cindex target descriptions, MIPS features | |
26868 | ||
26869 | The @samp{org.gnu.gdb.mips.cpu} feature is required for MIPS targets. | |
26870 | It should contain registers @samp{r0} through @samp{r31}, @samp{lo}, | |
26871 | @samp{hi}, and @samp{pc}. They may be 32-bit or 64-bit depending | |
26872 | on the target. | |
26873 | ||
26874 | The @samp{org.gnu.gdb.mips.cp0} feature is also required. It should | |
26875 | contain at least the @samp{status}, @samp{badvaddr}, and @samp{cause} | |
26876 | registers. They may be 32-bit or 64-bit depending on the target. | |
26877 | ||
26878 | The @samp{org.gnu.gdb.mips.fpu} feature is currently required, though | |
26879 | it may be optional in a future version of @value{GDBN}. It should | |
26880 | contain registers @samp{f0} through @samp{f31}, @samp{fcsr}, and | |
26881 | @samp{fir}. They may be 32-bit or 64-bit depending on the target. | |
26882 | ||
822b6570 DJ |
26883 | The @samp{org.gnu.gdb.mips.linux} feature is optional. It should |
26884 | contain a single register, @samp{restart}, which is used by the | |
26885 | Linux kernel to control restartable syscalls. | |
26886 | ||
e9c17194 VP |
26887 | @node M68K Features |
26888 | @subsection M68K Features | |
26889 | @cindex target descriptions, M68K features | |
26890 | ||
26891 | @table @code | |
26892 | @item @samp{org.gnu.gdb.m68k.core} | |
26893 | @itemx @samp{org.gnu.gdb.coldfire.core} | |
26894 | @itemx @samp{org.gnu.gdb.fido.core} | |
26895 | One of those features must be always present. | |
26896 | The feature that is present determines which flavor of m86k is | |
26897 | used. The feature that is present should contain registers | |
26898 | @samp{d0} through @samp{d7}, @samp{a0} through @samp{a5}, @samp{fp}, | |
26899 | @samp{sp}, @samp{ps} and @samp{pc}. | |
26900 | ||
26901 | @item @samp{org.gnu.gdb.coldfire.fp} | |
26902 | This feature is optional. If present, it should contain registers | |
26903 | @samp{fp0} through @samp{fp7}, @samp{fpcontrol}, @samp{fpstatus} and | |
26904 | @samp{fpiaddr}. | |
26905 | @end table | |
26906 | ||
7cc46491 DJ |
26907 | @subsection PowerPC Features |
26908 | @cindex target descriptions, PowerPC features | |
26909 | ||
26910 | The @samp{org.gnu.gdb.power.core} feature is required for PowerPC | |
26911 | targets. It should contain registers @samp{r0} through @samp{r31}, | |
26912 | @samp{pc}, @samp{msr}, @samp{cr}, @samp{lr}, @samp{ctr}, and | |
26913 | @samp{xer}. They may be 32-bit or 64-bit depending on the target. | |
26914 | ||
26915 | The @samp{org.gnu.gdb.power.fpu} feature is optional. It should | |
26916 | contain registers @samp{f0} through @samp{f31} and @samp{fpscr}. | |
26917 | ||
26918 | The @samp{org.gnu.gdb.power.altivec} feature is optional. It should | |
26919 | contain registers @samp{vr0} through @samp{vr31}, @samp{vscr}, | |
26920 | and @samp{vrsave}. | |
26921 | ||
26922 | The @samp{org.gnu.gdb.power.spe} feature is optional. It should | |
26923 | contain registers @samp{ev0h} through @samp{ev31h}, @samp{acc}, and | |
26924 | @samp{spefscr}. SPE targets should provide 32-bit registers in | |
26925 | @samp{org.gnu.gdb.power.core} and provide the upper halves in | |
26926 | @samp{ev0h} through @samp{ev31h}. @value{GDBN} will combine | |
26927 | these to present registers @samp{ev0} through @samp{ev31} to the | |
26928 | user. | |
26929 | ||
aab4e0ec | 26930 | @include gpl.texi |
eb12ee30 | 26931 | |
2154891a | 26932 | @raisesections |
6826cf00 | 26933 | @include fdl.texi |
2154891a | 26934 | @lowersections |
6826cf00 | 26935 | |
6d2ebf8b | 26936 | @node Index |
c906108c SS |
26937 | @unnumbered Index |
26938 | ||
26939 | @printindex cp | |
26940 | ||
26941 | @tex | |
26942 | % I think something like @colophon should be in texinfo. In the | |
26943 | % meantime: | |
26944 | \long\def\colophon{\hbox to0pt{}\vfill | |
26945 | \centerline{The body of this manual is set in} | |
26946 | \centerline{\fontname\tenrm,} | |
26947 | \centerline{with headings in {\bf\fontname\tenbf}} | |
26948 | \centerline{and examples in {\tt\fontname\tentt}.} | |
26949 | \centerline{{\it\fontname\tenit\/},} | |
26950 | \centerline{{\bf\fontname\tenbf}, and} | |
26951 | \centerline{{\sl\fontname\tensl\/}} | |
26952 | \centerline{are used for emphasis.}\vfill} | |
26953 | \page\colophon | |
26954 | % Blame: doc@cygnus.com, 1991. | |
26955 | @end tex | |
26956 | ||
c906108c | 26957 | @bye |