| 1 | \input texinfo @c -*-texinfo-*- |
| 2 | @c Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998, |
| 3 | @c 1999, 2000, 2001, 2002 |
| 4 | @c Free Software Foundation, Inc. |
| 5 | @c |
| 6 | @c %**start of header |
| 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 |
| 13 | @settitle Debugging with @value{GDBN} |
| 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 | |
| 25 | @c readline appendices use @vindex, @findex and @ftable, |
| 26 | @c annotate.texi and gdbmi use @findex. |
| 27 | @syncodeindex vr cp |
| 28 | @syncodeindex fn cp |
| 29 | |
| 30 | @c !!set GDB manual's edition---not the same as GDB version! |
| 31 | @set EDITION Ninth |
| 32 | |
| 33 | @c !!set GDB manual's revision date |
| 34 | @set DATE December 2001 |
| 35 | |
| 36 | @c THIS MANUAL REQUIRES TEXINFO 4.0 OR LATER. |
| 37 | |
| 38 | @c This is a dir.info fragment to support semi-automated addition of |
| 39 | @c manuals to an info tree. |
| 40 | @dircategory Programming & development tools. |
| 41 | @direntry |
| 42 | * Gdb: (gdb). The @sc{gnu} debugger. |
| 43 | @end direntry |
| 44 | |
| 45 | @ifinfo |
| 46 | This file documents the @sc{gnu} debugger @value{GDBN}. |
| 47 | |
| 48 | |
| 49 | This is the @value{EDITION} Edition, @value{DATE}, |
| 50 | of @cite{Debugging with @value{GDBN}: the @sc{gnu} Source-Level Debugger} |
| 51 | for @value{GDBN} Version @value{GDBVN}. |
| 52 | |
| 53 | Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998,@* |
| 54 | 1999, 2000, 2001, 2002 Free Software Foundation, Inc. |
| 55 | |
| 56 | Permission is granted to copy, distribute and/or modify this document |
| 57 | under the terms of the GNU Free Documentation License, Version 1.1 or |
| 58 | any later version published by the Free Software Foundation; with the |
| 59 | Invariant Sections being ``Free Software'' and ``Free Software Needs |
| 60 | Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,'' |
| 61 | and with the Back-Cover Texts as in (a) below. |
| 62 | |
| 63 | (a) The Free Software Foundation's Back-Cover Text is: ``You have |
| 64 | freedom to copy and modify this GNU Manual, like GNU software. Copies |
| 65 | published by the Free Software Foundation raise funds for GNU |
| 66 | development.'' |
| 67 | @end ifinfo |
| 68 | |
| 69 | @titlepage |
| 70 | @title Debugging with @value{GDBN} |
| 71 | @subtitle The @sc{gnu} Source-Level Debugger |
| 72 | @sp 1 |
| 73 | @subtitle @value{EDITION} Edition, for @value{GDBN} version @value{GDBVN} |
| 74 | @subtitle @value{DATE} |
| 75 | @author Richard Stallman, Roland Pesch, Stan Shebs, et al. |
| 76 | @page |
| 77 | @tex |
| 78 | {\parskip=0pt |
| 79 | \hfill (Send bugs and comments on @value{GDBN} to bug-gdb\@gnu.org.)\par |
| 80 | \hfill {\it Debugging with @value{GDBN}}\par |
| 81 | \hfill \TeX{}info \texinfoversion\par |
| 82 | } |
| 83 | @end tex |
| 84 | |
| 85 | @vskip 0pt plus 1filll |
| 86 | Copyright @copyright{} 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, |
| 87 | 1996, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc. |
| 88 | @sp 2 |
| 89 | Published by the Free Software Foundation @* |
| 90 | 59 Temple Place - Suite 330, @* |
| 91 | Boston, MA 02111-1307 USA @* |
| 92 | ISBN 1-882114-77-9 @* |
| 93 | |
| 94 | Permission is granted to copy, distribute and/or modify this document |
| 95 | under the terms of the GNU Free Documentation License, Version 1.1 or |
| 96 | any later version published by the Free Software Foundation; with the |
| 97 | Invariant Sections being ``Free Software'' and ``Free Software Needs |
| 98 | Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,'' |
| 99 | and with the Back-Cover Texts as in (a) below. |
| 100 | |
| 101 | (a) The Free Software Foundation's Back-Cover Text is: ``You have |
| 102 | freedom to copy and modify this GNU Manual, like GNU software. Copies |
| 103 | published by the Free Software Foundation raise funds for GNU |
| 104 | development.'' |
| 105 | @end titlepage |
| 106 | @page |
| 107 | |
| 108 | @ifnottex |
| 109 | @node Top, Summary, (dir), (dir) |
| 110 | |
| 111 | @top Debugging with @value{GDBN} |
| 112 | |
| 113 | This file describes @value{GDBN}, the @sc{gnu} symbolic debugger. |
| 114 | |
| 115 | This is the @value{EDITION} Edition, @value{DATE}, for @value{GDBN} Version |
| 116 | @value{GDBVN}. |
| 117 | |
| 118 | Copyright (C) 1988-2002 Free Software Foundation, Inc. |
| 119 | |
| 120 | @menu |
| 121 | * Summary:: Summary of @value{GDBN} |
| 122 | * Sample Session:: A sample @value{GDBN} session |
| 123 | |
| 124 | * Invocation:: Getting in and out of @value{GDBN} |
| 125 | * Commands:: @value{GDBN} commands |
| 126 | * Running:: Running programs under @value{GDBN} |
| 127 | * Stopping:: Stopping and continuing |
| 128 | * Stack:: Examining the stack |
| 129 | * Source:: Examining source files |
| 130 | * Data:: Examining data |
| 131 | * Tracepoints:: Debugging remote targets non-intrusively |
| 132 | * Overlays:: Debugging programs that use overlays |
| 133 | |
| 134 | * Languages:: Using @value{GDBN} with different languages |
| 135 | |
| 136 | * Symbols:: Examining the symbol table |
| 137 | * Altering:: Altering execution |
| 138 | * GDB Files:: @value{GDBN} files |
| 139 | * Targets:: Specifying a debugging target |
| 140 | * Remote Debugging:: Debugging remote programs |
| 141 | * Configurations:: Configuration-specific information |
| 142 | * Controlling GDB:: Controlling @value{GDBN} |
| 143 | * Sequences:: Canned sequences of commands |
| 144 | * TUI:: @value{GDBN} Text User Interface |
| 145 | * Emacs:: Using @value{GDBN} under @sc{gnu} Emacs |
| 146 | * Annotations:: @value{GDBN}'s annotation interface. |
| 147 | * GDB/MI:: @value{GDBN}'s Machine Interface. |
| 148 | |
| 149 | * GDB Bugs:: Reporting bugs in @value{GDBN} |
| 150 | * Formatting Documentation:: How to format and print @value{GDBN} documentation |
| 151 | |
| 152 | * Command Line Editing:: Command Line Editing |
| 153 | * Using History Interactively:: Using History Interactively |
| 154 | * Installing GDB:: Installing GDB |
| 155 | * Maintenance Commands:: Maintenance Commands |
| 156 | * Remote Protocol:: GDB Remote Serial Protocol |
| 157 | * GNU Free Documentation License:: The license for this documentation |
| 158 | * Index:: Index |
| 159 | @end menu |
| 160 | |
| 161 | @end ifnottex |
| 162 | |
| 163 | @contents |
| 164 | |
| 165 | @node Summary |
| 166 | @unnumbered Summary of @value{GDBN} |
| 167 | |
| 168 | The purpose of a debugger such as @value{GDBN} is to allow you to see what is |
| 169 | going on ``inside'' another program while it executes---or what another |
| 170 | program was doing at the moment it crashed. |
| 171 | |
| 172 | @value{GDBN} can do four main kinds of things (plus other things in support of |
| 173 | these) to help you catch bugs in the act: |
| 174 | |
| 175 | @itemize @bullet |
| 176 | @item |
| 177 | Start your program, specifying anything that might affect its behavior. |
| 178 | |
| 179 | @item |
| 180 | Make your program stop on specified conditions. |
| 181 | |
| 182 | @item |
| 183 | Examine what has happened, when your program has stopped. |
| 184 | |
| 185 | @item |
| 186 | Change things in your program, so you can experiment with correcting the |
| 187 | effects of one bug and go on to learn about another. |
| 188 | @end itemize |
| 189 | |
| 190 | You can use @value{GDBN} to debug programs written in C and C++. |
| 191 | For more information, see @ref{Support,,Supported languages}. |
| 192 | For more information, see @ref{C,,C and C++}. |
| 193 | |
| 194 | @cindex Chill |
| 195 | @cindex Modula-2 |
| 196 | Support for Modula-2 and Chill is partial. For information on Modula-2, |
| 197 | see @ref{Modula-2,,Modula-2}. For information on Chill, see @ref{Chill}. |
| 198 | |
| 199 | @cindex Pascal |
| 200 | Debugging Pascal programs which use sets, subranges, file variables, or |
| 201 | nested functions does not currently work. @value{GDBN} does not support |
| 202 | entering expressions, printing values, or similar features using Pascal |
| 203 | syntax. |
| 204 | |
| 205 | @cindex Fortran |
| 206 | @value{GDBN} can be used to debug programs written in Fortran, although |
| 207 | it may be necessary to refer to some variables with a trailing |
| 208 | underscore. |
| 209 | |
| 210 | @menu |
| 211 | * Free Software:: Freely redistributable software |
| 212 | * Contributors:: Contributors to GDB |
| 213 | @end menu |
| 214 | |
| 215 | @node Free Software |
| 216 | @unnumberedsec Free software |
| 217 | |
| 218 | @value{GDBN} is @dfn{free software}, protected by the @sc{gnu} |
| 219 | General Public License |
| 220 | (GPL). The GPL gives you the freedom to copy or adapt a licensed |
| 221 | program---but every person getting a copy also gets with it the |
| 222 | freedom to modify that copy (which means that they must get access to |
| 223 | the source code), and the freedom to distribute further copies. |
| 224 | Typical software companies use copyrights to limit your freedoms; the |
| 225 | Free Software Foundation uses the GPL to preserve these freedoms. |
| 226 | |
| 227 | Fundamentally, the General Public License is a license which says that |
| 228 | you have these freedoms and that you cannot take these freedoms away |
| 229 | from anyone else. |
| 230 | |
| 231 | @unnumberedsec Free Software Needs Free Documentation |
| 232 | |
| 233 | The biggest deficiency in the free software community today is not in |
| 234 | the software---it is the lack of good free documentation that we can |
| 235 | include with the free software. Many of our most important |
| 236 | programs do not come with free reference manuals and free introductory |
| 237 | texts. Documentation is an essential part of any software package; |
| 238 | when an important free software package does not come with a free |
| 239 | manual and a free tutorial, that is a major gap. We have many such |
| 240 | gaps today. |
| 241 | |
| 242 | Consider Perl, for instance. The tutorial manuals that people |
| 243 | normally use are non-free. How did this come about? Because the |
| 244 | authors of those manuals published them with restrictive terms---no |
| 245 | copying, no modification, source files not available---which exclude |
| 246 | them from the free software world. |
| 247 | |
| 248 | That wasn't the first time this sort of thing happened, and it was far |
| 249 | from the last. Many times we have heard a GNU user eagerly describe a |
| 250 | manual that he is writing, his intended contribution to the community, |
| 251 | only to learn that he had ruined everything by signing a publication |
| 252 | contract to make it non-free. |
| 253 | |
| 254 | Free documentation, like free software, is a matter of freedom, not |
| 255 | price. The problem with the non-free manual is not that publishers |
| 256 | charge a price for printed copies---that in itself is fine. (The Free |
| 257 | Software Foundation sells printed copies of manuals, too.) The |
| 258 | problem is the restrictions on the use of the manual. Free manuals |
| 259 | are available in source code form, and give you permission to copy and |
| 260 | modify. Non-free manuals do not allow this. |
| 261 | |
| 262 | The criteria of freedom for a free manual are roughly the same as for |
| 263 | free software. Redistribution (including the normal kinds of |
| 264 | commercial redistribution) must be permitted, so that the manual can |
| 265 | accompany every copy of the program, both on-line and on paper. |
| 266 | |
| 267 | Permission for modification of the technical content is crucial too. |
| 268 | When people modify the software, adding or changing features, if they |
| 269 | are conscientious they will change the manual too---so they can |
| 270 | provide accurate and clear documentation for the modified program. A |
| 271 | manual that leaves you no choice but to write a new manual to document |
| 272 | a changed version of the program is not really available to our |
| 273 | community. |
| 274 | |
| 275 | Some kinds of limits on the way modification is handled are |
| 276 | acceptable. For example, requirements to preserve the original |
| 277 | author's copyright notice, the distribution terms, or the list of |
| 278 | authors, are ok. It is also no problem to require modified versions |
| 279 | to include notice that they were modified. Even entire sections that |
| 280 | may not be deleted or changed are acceptable, as long as they deal |
| 281 | with nontechnical topics (like this one). These kinds of restrictions |
| 282 | are acceptable because they don't obstruct the community's normal use |
| 283 | of the manual. |
| 284 | |
| 285 | However, it must be possible to modify all the @emph{technical} |
| 286 | content of the manual, and then distribute the result in all the usual |
| 287 | media, through all the usual channels. Otherwise, the restrictions |
| 288 | obstruct the use of the manual, it is not free, and we need another |
| 289 | manual to replace it. |
| 290 | |
| 291 | Please spread the word about this issue. Our community continues to |
| 292 | lose manuals to proprietary publishing. If we spread the word that |
| 293 | free software needs free reference manuals and free tutorials, perhaps |
| 294 | the next person who wants to contribute by writing documentation will |
| 295 | realize, before it is too late, that only free manuals contribute to |
| 296 | the free software community. |
| 297 | |
| 298 | If you are writing documentation, please insist on publishing it under |
| 299 | the GNU Free Documentation License or another free documentation |
| 300 | license. Remember that this decision requires your approval---you |
| 301 | don't have to let the publisher decide. Some commercial publishers |
| 302 | will use a free license if you insist, but they will not propose the |
| 303 | option; it is up to you to raise the issue and say firmly that this is |
| 304 | what you want. If the publisher you are dealing with refuses, please |
| 305 | try other publishers. If you're not sure whether a proposed license |
| 306 | is free, write to @email{licensing@@gnu.org}. |
| 307 | |
| 308 | You can encourage commercial publishers to sell more free, copylefted |
| 309 | manuals and tutorials by buying them, and particularly by buying |
| 310 | copies from the publishers that paid for their writing or for major |
| 311 | improvements. Meanwhile, try to avoid buying non-free documentation |
| 312 | at all. Check the distribution terms of a manual before you buy it, |
| 313 | and insist that whoever seeks your business must respect your freedom. |
| 314 | Check the history of the book, and try to reward the publishers that |
| 315 | have paid or pay the authors to work on it. |
| 316 | |
| 317 | The Free Software Foundation maintains a list of free documentation |
| 318 | published by other publishers, at |
| 319 | @url{http://www.fsf.org/doc/other-free-books.html}. |
| 320 | |
| 321 | @node Contributors |
| 322 | @unnumberedsec Contributors to @value{GDBN} |
| 323 | |
| 324 | Richard Stallman was the original author of @value{GDBN}, and of many |
| 325 | other @sc{gnu} programs. Many others have contributed to its |
| 326 | development. This section attempts to credit major contributors. One |
| 327 | of the virtues of free software is that everyone is free to contribute |
| 328 | to it; with regret, we cannot actually acknowledge everyone here. The |
| 329 | file @file{ChangeLog} in the @value{GDBN} distribution approximates a |
| 330 | blow-by-blow account. |
| 331 | |
| 332 | Changes much prior to version 2.0 are lost in the mists of time. |
| 333 | |
| 334 | @quotation |
| 335 | @emph{Plea:} Additions to this section are particularly welcome. If you |
| 336 | or your friends (or enemies, to be evenhanded) have been unfairly |
| 337 | omitted from this list, we would like to add your names! |
| 338 | @end quotation |
| 339 | |
| 340 | So that they may not regard their many labors as thankless, we |
| 341 | particularly thank those who shepherded @value{GDBN} through major |
| 342 | releases: |
| 343 | Andrew Cagney (releases 5.0 and 5.1); |
| 344 | Jim Blandy (release 4.18); |
| 345 | Jason Molenda (release 4.17); |
| 346 | Stan Shebs (release 4.14); |
| 347 | Fred Fish (releases 4.16, 4.15, 4.13, 4.12, 4.11, 4.10, and 4.9); |
| 348 | Stu Grossman and John Gilmore (releases 4.8, 4.7, 4.6, 4.5, and 4.4); |
| 349 | John Gilmore (releases 4.3, 4.2, 4.1, 4.0, and 3.9); |
| 350 | Jim Kingdon (releases 3.5, 3.4, and 3.3); |
| 351 | and Randy Smith (releases 3.2, 3.1, and 3.0). |
| 352 | |
| 353 | Richard Stallman, assisted at various times by Peter TerMaat, Chris |
| 354 | Hanson, and Richard Mlynarik, handled releases through 2.8. |
| 355 | |
| 356 | Michael Tiemann is the author of most of the @sc{gnu} C@t{++} support |
| 357 | in @value{GDBN}, with significant additional contributions from Per |
| 358 | Bothner and Daniel Berlin. James Clark wrote the @sc{gnu} C@t{++} |
| 359 | demangler. Early work on C@t{++} was by Peter TerMaat (who also did |
| 360 | much general update work leading to release 3.0). |
| 361 | |
| 362 | @value{GDBN} uses the BFD subroutine library to examine multiple |
| 363 | object-file formats; BFD was a joint project of David V. |
| 364 | Henkel-Wallace, Rich Pixley, Steve Chamberlain, and John Gilmore. |
| 365 | |
| 366 | David Johnson wrote the original COFF support; Pace Willison did |
| 367 | the original support for encapsulated COFF. |
| 368 | |
| 369 | Brent Benson of Harris Computer Systems contributed DWARF2 support. |
| 370 | |
| 371 | Adam de Boor and Bradley Davis contributed the ISI Optimum V support. |
| 372 | Per Bothner, Noboyuki Hikichi, and Alessandro Forin contributed MIPS |
| 373 | support. |
| 374 | Jean-Daniel Fekete contributed Sun 386i support. |
| 375 | Chris Hanson improved the HP9000 support. |
| 376 | Noboyuki Hikichi and Tomoyuki Hasei contributed Sony/News OS 3 support. |
| 377 | David Johnson contributed Encore Umax support. |
| 378 | Jyrki Kuoppala contributed Altos 3068 support. |
| 379 | Jeff Law contributed HP PA and SOM support. |
| 380 | Keith Packard contributed NS32K support. |
| 381 | Doug Rabson contributed Acorn Risc Machine support. |
| 382 | Bob Rusk contributed Harris Nighthawk CX-UX support. |
| 383 | Chris Smith contributed Convex support (and Fortran debugging). |
| 384 | Jonathan Stone contributed Pyramid support. |
| 385 | Michael Tiemann contributed SPARC support. |
| 386 | Tim Tucker contributed support for the Gould NP1 and Gould Powernode. |
| 387 | Pace Willison contributed Intel 386 support. |
| 388 | Jay Vosburgh contributed Symmetry support. |
| 389 | |
| 390 | Andreas Schwab contributed M68K Linux support. |
| 391 | |
| 392 | Rich Schaefer and Peter Schauer helped with support of SunOS shared |
| 393 | libraries. |
| 394 | |
| 395 | Jay Fenlason and Roland McGrath ensured that @value{GDBN} and GAS agree |
| 396 | about several machine instruction sets. |
| 397 | |
| 398 | Patrick Duval, Ted Goldstein, Vikram Koka and Glenn Engel helped develop |
| 399 | remote debugging. Intel Corporation, Wind River Systems, AMD, and ARM |
| 400 | contributed remote debugging modules for the i960, VxWorks, A29K UDI, |
| 401 | and RDI targets, respectively. |
| 402 | |
| 403 | Brian Fox is the author of the readline libraries providing |
| 404 | command-line editing and command history. |
| 405 | |
| 406 | Andrew Beers of SUNY Buffalo wrote the language-switching code, the |
| 407 | Modula-2 support, and contributed the Languages chapter of this manual. |
| 408 | |
| 409 | Fred Fish wrote most of the support for Unix System Vr4. |
| 410 | He also enhanced the command-completion support to cover C@t{++} overloaded |
| 411 | symbols. |
| 412 | |
| 413 | Hitachi America, Ltd. sponsored the support for H8/300, H8/500, and |
| 414 | Super-H processors. |
| 415 | |
| 416 | NEC sponsored the support for the v850, Vr4xxx, and Vr5xxx processors. |
| 417 | |
| 418 | Mitsubishi sponsored the support for D10V, D30V, and M32R/D processors. |
| 419 | |
| 420 | Toshiba sponsored the support for the TX39 Mips processor. |
| 421 | |
| 422 | Matsushita sponsored the support for the MN10200 and MN10300 processors. |
| 423 | |
| 424 | Fujitsu sponsored the support for SPARClite and FR30 processors. |
| 425 | |
| 426 | Kung Hsu, Jeff Law, and Rick Sladkey added support for hardware |
| 427 | watchpoints. |
| 428 | |
| 429 | Michael Snyder added support for tracepoints. |
| 430 | |
| 431 | Stu Grossman wrote gdbserver. |
| 432 | |
| 433 | Jim Kingdon, Peter Schauer, Ian Taylor, and Stu Grossman made |
| 434 | nearly innumerable bug fixes and cleanups throughout @value{GDBN}. |
| 435 | |
| 436 | The following people at the Hewlett-Packard Company contributed |
| 437 | support for the PA-RISC 2.0 architecture, HP-UX 10.20, 10.30, and 11.0 |
| 438 | (narrow mode), HP's implementation of kernel threads, HP's aC@t{++} |
| 439 | compiler, and the terminal user interface: Ben Krepp, Richard Title, |
| 440 | John Bishop, Susan Macchia, Kathy Mann, Satish Pai, India Paul, Steve |
| 441 | Rehrauer, and Elena Zannoni. Kim Haase provided HP-specific |
| 442 | information in this manual. |
| 443 | |
| 444 | DJ Delorie ported @value{GDBN} to MS-DOS, for the DJGPP project. |
| 445 | Robert Hoehne made significant contributions to the DJGPP port. |
| 446 | |
| 447 | Cygnus Solutions has sponsored @value{GDBN} maintenance and much of its |
| 448 | development since 1991. Cygnus engineers who have worked on @value{GDBN} |
| 449 | fulltime include Mark Alexander, Jim Blandy, Per Bothner, Kevin |
| 450 | Buettner, Edith Epstein, Chris Faylor, Fred Fish, Martin Hunt, Jim |
| 451 | Ingham, John Gilmore, Stu Grossman, Kung Hsu, Jim Kingdon, John Metzler, |
| 452 | Fernando Nasser, Geoffrey Noer, Dawn Perchik, Rich Pixley, Zdenek |
| 453 | Radouch, Keith Seitz, Stan Shebs, David Taylor, and Elena Zannoni. In |
| 454 | addition, Dave Brolley, Ian Carmichael, Steve Chamberlain, Nick Clifton, |
| 455 | JT Conklin, Stan Cox, DJ Delorie, Ulrich Drepper, Frank Eigler, Doug |
| 456 | Evans, Sean Fagan, David Henkel-Wallace, Richard Henderson, Jeff |
| 457 | Holcomb, Jeff Law, Jim Lemke, Tom Lord, Bob Manson, Michael Meissner, |
| 458 | Jason Merrill, Catherine Moore, Drew Moseley, Ken Raeburn, Gavin |
| 459 | Romig-Koch, Rob Savoye, Jamie Smith, Mike Stump, Ian Taylor, Angela |
| 460 | Thomas, Michael Tiemann, Tom Tromey, Ron Unrau, Jim Wilson, and David |
| 461 | Zuhn have made contributions both large and small. |
| 462 | |
| 463 | |
| 464 | @node Sample Session |
| 465 | @chapter A Sample @value{GDBN} Session |
| 466 | |
| 467 | You can use this manual at your leisure to read all about @value{GDBN}. |
| 468 | However, a handful of commands are enough to get started using the |
| 469 | debugger. This chapter illustrates those commands. |
| 470 | |
| 471 | @iftex |
| 472 | In this sample session, we emphasize user input like this: @b{input}, |
| 473 | to make it easier to pick out from the surrounding output. |
| 474 | @end iftex |
| 475 | |
| 476 | @c FIXME: this example may not be appropriate for some configs, where |
| 477 | @c FIXME...primary interest is in remote use. |
| 478 | |
| 479 | One of the preliminary versions of @sc{gnu} @code{m4} (a generic macro |
| 480 | processor) exhibits the following bug: sometimes, when we change its |
| 481 | quote strings from the default, the commands used to capture one macro |
| 482 | definition within another stop working. In the following short @code{m4} |
| 483 | session, we define a macro @code{foo} which expands to @code{0000}; we |
| 484 | then use the @code{m4} built-in @code{defn} to define @code{bar} as the |
| 485 | same thing. However, when we change the open quote string to |
| 486 | @code{<QUOTE>} and the close quote string to @code{<UNQUOTE>}, the same |
| 487 | procedure fails to define a new synonym @code{baz}: |
| 488 | |
| 489 | @smallexample |
| 490 | $ @b{cd gnu/m4} |
| 491 | $ @b{./m4} |
| 492 | @b{define(foo,0000)} |
| 493 | |
| 494 | @b{foo} |
| 495 | 0000 |
| 496 | @b{define(bar,defn(`foo'))} |
| 497 | |
| 498 | @b{bar} |
| 499 | 0000 |
| 500 | @b{changequote(<QUOTE>,<UNQUOTE>)} |
| 501 | |
| 502 | @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))} |
| 503 | @b{baz} |
| 504 | @b{C-d} |
| 505 | m4: End of input: 0: fatal error: EOF in string |
| 506 | @end smallexample |
| 507 | |
| 508 | @noindent |
| 509 | Let us use @value{GDBN} to try to see what is going on. |
| 510 | |
| 511 | @smallexample |
| 512 | $ @b{@value{GDBP} m4} |
| 513 | @c FIXME: this falsifies the exact text played out, to permit smallbook |
| 514 | @c FIXME... format to come out better. |
| 515 | @value{GDBN} is free software and you are welcome to distribute copies |
| 516 | of it under certain conditions; type "show copying" to see |
| 517 | the conditions. |
| 518 | There is absolutely no warranty for @value{GDBN}; type "show warranty" |
| 519 | for details. |
| 520 | |
| 521 | @value{GDBN} @value{GDBVN}, Copyright 1999 Free Software Foundation, Inc... |
| 522 | (@value{GDBP}) |
| 523 | @end smallexample |
| 524 | |
| 525 | @noindent |
| 526 | @value{GDBN} reads only enough symbol data to know where to find the |
| 527 | rest when needed; as a result, the first prompt comes up very quickly. |
| 528 | We now tell @value{GDBN} to use a narrower display width than usual, so |
| 529 | that examples fit in this manual. |
| 530 | |
| 531 | @smallexample |
| 532 | (@value{GDBP}) @b{set width 70} |
| 533 | @end smallexample |
| 534 | |
| 535 | @noindent |
| 536 | We need to see how the @code{m4} built-in @code{changequote} works. |
| 537 | Having looked at the source, we know the relevant subroutine is |
| 538 | @code{m4_changequote}, so we set a breakpoint there with the @value{GDBN} |
| 539 | @code{break} command. |
| 540 | |
| 541 | @smallexample |
| 542 | (@value{GDBP}) @b{break m4_changequote} |
| 543 | Breakpoint 1 at 0x62f4: file builtin.c, line 879. |
| 544 | @end smallexample |
| 545 | |
| 546 | @noindent |
| 547 | Using the @code{run} command, we start @code{m4} running under @value{GDBN} |
| 548 | control; as long as control does not reach the @code{m4_changequote} |
| 549 | subroutine, the program runs as usual: |
| 550 | |
| 551 | @smallexample |
| 552 | (@value{GDBP}) @b{run} |
| 553 | Starting program: /work/Editorial/gdb/gnu/m4/m4 |
| 554 | @b{define(foo,0000)} |
| 555 | |
| 556 | @b{foo} |
| 557 | 0000 |
| 558 | @end smallexample |
| 559 | |
| 560 | @noindent |
| 561 | To trigger the breakpoint, we call @code{changequote}. @value{GDBN} |
| 562 | suspends execution of @code{m4}, displaying information about the |
| 563 | context where it stops. |
| 564 | |
| 565 | @smallexample |
| 566 | @b{changequote(<QUOTE>,<UNQUOTE>)} |
| 567 | |
| 568 | Breakpoint 1, m4_changequote (argc=3, argv=0x33c70) |
| 569 | at builtin.c:879 |
| 570 | 879 if (bad_argc(TOKEN_DATA_TEXT(argv[0]),argc,1,3)) |
| 571 | @end smallexample |
| 572 | |
| 573 | @noindent |
| 574 | Now we use the command @code{n} (@code{next}) to advance execution to |
| 575 | the next line of the current function. |
| 576 | |
| 577 | @smallexample |
| 578 | (@value{GDBP}) @b{n} |
| 579 | 882 set_quotes((argc >= 2) ? TOKEN_DATA_TEXT(argv[1])\ |
| 580 | : nil, |
| 581 | @end smallexample |
| 582 | |
| 583 | @noindent |
| 584 | @code{set_quotes} looks like a promising subroutine. We can go into it |
| 585 | by using the command @code{s} (@code{step}) instead of @code{next}. |
| 586 | @code{step} goes to the next line to be executed in @emph{any} |
| 587 | subroutine, so it steps into @code{set_quotes}. |
| 588 | |
| 589 | @smallexample |
| 590 | (@value{GDBP}) @b{s} |
| 591 | set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>") |
| 592 | at input.c:530 |
| 593 | 530 if (lquote != def_lquote) |
| 594 | @end smallexample |
| 595 | |
| 596 | @noindent |
| 597 | The display that shows the subroutine where @code{m4} is now |
| 598 | suspended (and its arguments) is called a stack frame display. It |
| 599 | shows a summary of the stack. We can use the @code{backtrace} |
| 600 | command (which can also be spelled @code{bt}), to see where we are |
| 601 | in the stack as a whole: the @code{backtrace} command displays a |
| 602 | stack frame for each active subroutine. |
| 603 | |
| 604 | @smallexample |
| 605 | (@value{GDBP}) @b{bt} |
| 606 | #0 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>") |
| 607 | at input.c:530 |
| 608 | #1 0x6344 in m4_changequote (argc=3, argv=0x33c70) |
| 609 | at builtin.c:882 |
| 610 | #2 0x8174 in expand_macro (sym=0x33320) at macro.c:242 |
| 611 | #3 0x7a88 in expand_token (obs=0x0, t=209696, td=0xf7fffa30) |
| 612 | at macro.c:71 |
| 613 | #4 0x79dc in expand_input () at macro.c:40 |
| 614 | #5 0x2930 in main (argc=0, argv=0xf7fffb20) at m4.c:195 |
| 615 | @end smallexample |
| 616 | |
| 617 | @noindent |
| 618 | We step through a few more lines to see what happens. The first two |
| 619 | times, we can use @samp{s}; the next two times we use @code{n} to avoid |
| 620 | falling into the @code{xstrdup} subroutine. |
| 621 | |
| 622 | @smallexample |
| 623 | (@value{GDBP}) @b{s} |
| 624 | 0x3b5c 532 if (rquote != def_rquote) |
| 625 | (@value{GDBP}) @b{s} |
| 626 | 0x3b80 535 lquote = (lq == nil || *lq == '\0') ? \ |
| 627 | def_lquote : xstrdup(lq); |
| 628 | (@value{GDBP}) @b{n} |
| 629 | 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\ |
| 630 | : xstrdup(rq); |
| 631 | (@value{GDBP}) @b{n} |
| 632 | 538 len_lquote = strlen(rquote); |
| 633 | @end smallexample |
| 634 | |
| 635 | @noindent |
| 636 | The last line displayed looks a little odd; we can examine the variables |
| 637 | @code{lquote} and @code{rquote} to see if they are in fact the new left |
| 638 | and right quotes we specified. We use the command @code{p} |
| 639 | (@code{print}) to see their values. |
| 640 | |
| 641 | @smallexample |
| 642 | (@value{GDBP}) @b{p lquote} |
| 643 | $1 = 0x35d40 "<QUOTE>" |
| 644 | (@value{GDBP}) @b{p rquote} |
| 645 | $2 = 0x35d50 "<UNQUOTE>" |
| 646 | @end smallexample |
| 647 | |
| 648 | @noindent |
| 649 | @code{lquote} and @code{rquote} are indeed the new left and right quotes. |
| 650 | To look at some context, we can display ten lines of source |
| 651 | surrounding the current line with the @code{l} (@code{list}) command. |
| 652 | |
| 653 | @smallexample |
| 654 | (@value{GDBP}) @b{l} |
| 655 | 533 xfree(rquote); |
| 656 | 534 |
| 657 | 535 lquote = (lq == nil || *lq == '\0') ? def_lquote\ |
| 658 | : xstrdup (lq); |
| 659 | 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\ |
| 660 | : xstrdup (rq); |
| 661 | 537 |
| 662 | 538 len_lquote = strlen(rquote); |
| 663 | 539 len_rquote = strlen(lquote); |
| 664 | 540 @} |
| 665 | 541 |
| 666 | 542 void |
| 667 | @end smallexample |
| 668 | |
| 669 | @noindent |
| 670 | Let us step past the two lines that set @code{len_lquote} and |
| 671 | @code{len_rquote}, and then examine the values of those variables. |
| 672 | |
| 673 | @smallexample |
| 674 | (@value{GDBP}) @b{n} |
| 675 | 539 len_rquote = strlen(lquote); |
| 676 | (@value{GDBP}) @b{n} |
| 677 | 540 @} |
| 678 | (@value{GDBP}) @b{p len_lquote} |
| 679 | $3 = 9 |
| 680 | (@value{GDBP}) @b{p len_rquote} |
| 681 | $4 = 7 |
| 682 | @end smallexample |
| 683 | |
| 684 | @noindent |
| 685 | That certainly looks wrong, assuming @code{len_lquote} and |
| 686 | @code{len_rquote} are meant to be the lengths of @code{lquote} and |
| 687 | @code{rquote} respectively. We can set them to better values using |
| 688 | the @code{p} command, since it can print the value of |
| 689 | any expression---and that expression can include subroutine calls and |
| 690 | assignments. |
| 691 | |
| 692 | @smallexample |
| 693 | (@value{GDBP}) @b{p len_lquote=strlen(lquote)} |
| 694 | $5 = 7 |
| 695 | (@value{GDBP}) @b{p len_rquote=strlen(rquote)} |
| 696 | $6 = 9 |
| 697 | @end smallexample |
| 698 | |
| 699 | @noindent |
| 700 | Is that enough to fix the problem of using the new quotes with the |
| 701 | @code{m4} built-in @code{defn}? We can allow @code{m4} to continue |
| 702 | executing with the @code{c} (@code{continue}) command, and then try the |
| 703 | example that caused trouble initially: |
| 704 | |
| 705 | @smallexample |
| 706 | (@value{GDBP}) @b{c} |
| 707 | Continuing. |
| 708 | |
| 709 | @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))} |
| 710 | |
| 711 | baz |
| 712 | 0000 |
| 713 | @end smallexample |
| 714 | |
| 715 | @noindent |
| 716 | Success! The new quotes now work just as well as the default ones. The |
| 717 | problem seems to have been just the two typos defining the wrong |
| 718 | lengths. We allow @code{m4} exit by giving it an EOF as input: |
| 719 | |
| 720 | @smallexample |
| 721 | @b{C-d} |
| 722 | Program exited normally. |
| 723 | @end smallexample |
| 724 | |
| 725 | @noindent |
| 726 | The message @samp{Program exited normally.} is from @value{GDBN}; it |
| 727 | indicates @code{m4} has finished executing. We can end our @value{GDBN} |
| 728 | session with the @value{GDBN} @code{quit} command. |
| 729 | |
| 730 | @smallexample |
| 731 | (@value{GDBP}) @b{quit} |
| 732 | @end smallexample |
| 733 | |
| 734 | @node Invocation |
| 735 | @chapter Getting In and Out of @value{GDBN} |
| 736 | |
| 737 | This chapter discusses how to start @value{GDBN}, and how to get out of it. |
| 738 | The essentials are: |
| 739 | @itemize @bullet |
| 740 | @item |
| 741 | type @samp{@value{GDBP}} to start @value{GDBN}. |
| 742 | @item |
| 743 | type @kbd{quit} or @kbd{C-d} to exit. |
| 744 | @end itemize |
| 745 | |
| 746 | @menu |
| 747 | * Invoking GDB:: How to start @value{GDBN} |
| 748 | * Quitting GDB:: How to quit @value{GDBN} |
| 749 | * Shell Commands:: How to use shell commands inside @value{GDBN} |
| 750 | @end menu |
| 751 | |
| 752 | @node Invoking GDB |
| 753 | @section Invoking @value{GDBN} |
| 754 | |
| 755 | Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started, |
| 756 | @value{GDBN} reads commands from the terminal until you tell it to exit. |
| 757 | |
| 758 | You can also run @code{@value{GDBP}} with a variety of arguments and options, |
| 759 | to specify more of your debugging environment at the outset. |
| 760 | |
| 761 | The command-line options described here are designed |
| 762 | to cover a variety of situations; in some environments, some of these |
| 763 | options may effectively be unavailable. |
| 764 | |
| 765 | The most usual way to start @value{GDBN} is with one argument, |
| 766 | specifying an executable program: |
| 767 | |
| 768 | @example |
| 769 | @value{GDBP} @var{program} |
| 770 | @end example |
| 771 | |
| 772 | @noindent |
| 773 | You can also start with both an executable program and a core file |
| 774 | specified: |
| 775 | |
| 776 | @example |
| 777 | @value{GDBP} @var{program} @var{core} |
| 778 | @end example |
| 779 | |
| 780 | You can, instead, specify a process ID as a second argument, if you want |
| 781 | to debug a running process: |
| 782 | |
| 783 | @example |
| 784 | @value{GDBP} @var{program} 1234 |
| 785 | @end example |
| 786 | |
| 787 | @noindent |
| 788 | would attach @value{GDBN} to process @code{1234} (unless you also have a file |
| 789 | named @file{1234}; @value{GDBN} does check for a core file first). |
| 790 | |
| 791 | Taking advantage of the second command-line argument requires a fairly |
| 792 | complete operating system; when you use @value{GDBN} as a remote |
| 793 | debugger attached to a bare board, there may not be any notion of |
| 794 | ``process'', and there is often no way to get a core dump. @value{GDBN} |
| 795 | will warn you if it is unable to attach or to read core dumps. |
| 796 | |
| 797 | You can optionally have @code{@value{GDBP}} pass any arguments after the |
| 798 | executable file to the inferior using @code{--args}. This option stops |
| 799 | option processing. |
| 800 | @example |
| 801 | gdb --args gcc -O2 -c foo.c |
| 802 | @end example |
| 803 | This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set |
| 804 | @code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}. |
| 805 | |
| 806 | You can run @code{@value{GDBP}} without printing the front material, which describes |
| 807 | @value{GDBN}'s non-warranty, by specifying @code{-silent}: |
| 808 | |
| 809 | @smallexample |
| 810 | @value{GDBP} -silent |
| 811 | @end smallexample |
| 812 | |
| 813 | @noindent |
| 814 | You can further control how @value{GDBN} starts up by using command-line |
| 815 | options. @value{GDBN} itself can remind you of the options available. |
| 816 | |
| 817 | @noindent |
| 818 | Type |
| 819 | |
| 820 | @example |
| 821 | @value{GDBP} -help |
| 822 | @end example |
| 823 | |
| 824 | @noindent |
| 825 | to display all available options and briefly describe their use |
| 826 | (@samp{@value{GDBP} -h} is a shorter equivalent). |
| 827 | |
| 828 | All options and command line arguments you give are processed |
| 829 | in sequential order. The order makes a difference when the |
| 830 | @samp{-x} option is used. |
| 831 | |
| 832 | |
| 833 | @menu |
| 834 | * File Options:: Choosing files |
| 835 | * Mode Options:: Choosing modes |
| 836 | @end menu |
| 837 | |
| 838 | @node File Options |
| 839 | @subsection Choosing files |
| 840 | |
| 841 | When @value{GDBN} starts, it reads any arguments other than options as |
| 842 | specifying an executable file and core file (or process ID). This is |
| 843 | the same as if the arguments were specified by the @samp{-se} and |
| 844 | @samp{-c} (or @samp{-p} options respectively. (@value{GDBN} reads the |
| 845 | first argument that does not have an associated option flag as |
| 846 | equivalent to the @samp{-se} option followed by that argument; and the |
| 847 | second argument that does not have an associated option flag, if any, as |
| 848 | equivalent to the @samp{-c}/@samp{-p} option followed by that argument.) |
| 849 | If the second argument begins with a decimal digit, @value{GDBN} will |
| 850 | first attempt to attach to it as a process, and if that fails, attempt |
| 851 | to open it as a corefile. If you have a corefile whose name begins with |
| 852 | a digit, you can prevent @value{GDBN} from treating it as a pid by |
| 853 | prefixing it with @file{./}, eg. @file{./12345}. |
| 854 | |
| 855 | If @value{GDBN} has not been configured to included core file support, |
| 856 | such as for most embedded targets, then it will complain about a second |
| 857 | argument and ignore it. |
| 858 | |
| 859 | Many options have both long and short forms; both are shown in the |
| 860 | following list. @value{GDBN} also recognizes the long forms if you truncate |
| 861 | them, so long as enough of the option is present to be unambiguous. |
| 862 | (If you prefer, you can flag option arguments with @samp{--} rather |
| 863 | than @samp{-}, though we illustrate the more usual convention.) |
| 864 | |
| 865 | @c NOTE: the @cindex entries here use double dashes ON PURPOSE. This |
| 866 | @c way, both those who look for -foo and --foo in the index, will find |
| 867 | @c it. |
| 868 | |
| 869 | @table @code |
| 870 | @item -symbols @var{file} |
| 871 | @itemx -s @var{file} |
| 872 | @cindex @code{--symbols} |
| 873 | @cindex @code{-s} |
| 874 | Read symbol table from file @var{file}. |
| 875 | |
| 876 | @item -exec @var{file} |
| 877 | @itemx -e @var{file} |
| 878 | @cindex @code{--exec} |
| 879 | @cindex @code{-e} |
| 880 | Use file @var{file} as the executable file to execute when appropriate, |
| 881 | and for examining pure data in conjunction with a core dump. |
| 882 | |
| 883 | @item -se @var{file} |
| 884 | @cindex @code{--se} |
| 885 | Read symbol table from file @var{file} and use it as the executable |
| 886 | file. |
| 887 | |
| 888 | @item -core @var{file} |
| 889 | @itemx -c @var{file} |
| 890 | @cindex @code{--core} |
| 891 | @cindex @code{-c} |
| 892 | Use file @var{file} as a core dump to examine. |
| 893 | |
| 894 | @item -c @var{number} |
| 895 | @item -pid @var{number} |
| 896 | @itemx -p @var{number} |
| 897 | @cindex @code{--pid} |
| 898 | @cindex @code{-p} |
| 899 | Connect to process ID @var{number}, as with the @code{attach} command. |
| 900 | If there is no such process, @value{GDBN} will attempt to open a core |
| 901 | file named @var{number}. |
| 902 | |
| 903 | @item -command @var{file} |
| 904 | @itemx -x @var{file} |
| 905 | @cindex @code{--command} |
| 906 | @cindex @code{-x} |
| 907 | Execute @value{GDBN} commands from file @var{file}. @xref{Command |
| 908 | Files,, Command files}. |
| 909 | |
| 910 | @item -directory @var{directory} |
| 911 | @itemx -d @var{directory} |
| 912 | @cindex @code{--directory} |
| 913 | @cindex @code{-d} |
| 914 | Add @var{directory} to the path to search for source files. |
| 915 | |
| 916 | @item -m |
| 917 | @itemx -mapped |
| 918 | @cindex @code{--mapped} |
| 919 | @cindex @code{-m} |
| 920 | @emph{Warning: this option depends on operating system facilities that are not |
| 921 | supported on all systems.}@* |
| 922 | If memory-mapped files are available on your system through the @code{mmap} |
| 923 | system call, you can use this option |
| 924 | to have @value{GDBN} write the symbols from your |
| 925 | program into a reusable file in the current directory. If the program you are debugging is |
| 926 | called @file{/tmp/fred}, the mapped symbol file is @file{/tmp/fred.syms}. |
| 927 | Future @value{GDBN} debugging sessions notice the presence of this file, |
| 928 | and can quickly map in symbol information from it, rather than reading |
| 929 | the symbol table from the executable program. |
| 930 | |
| 931 | The @file{.syms} file is specific to the host machine where @value{GDBN} |
| 932 | is run. It holds an exact image of the internal @value{GDBN} symbol |
| 933 | table. It cannot be shared across multiple host platforms. |
| 934 | |
| 935 | @item -r |
| 936 | @itemx -readnow |
| 937 | @cindex @code{--readnow} |
| 938 | @cindex @code{-r} |
| 939 | Read each symbol file's entire symbol table immediately, rather than |
| 940 | the default, which is to read it incrementally as it is needed. |
| 941 | This makes startup slower, but makes future operations faster. |
| 942 | |
| 943 | @end table |
| 944 | |
| 945 | You typically combine the @code{-mapped} and @code{-readnow} options in |
| 946 | order to build a @file{.syms} file that contains complete symbol |
| 947 | information. (@xref{Files,,Commands to specify files}, for information |
| 948 | on @file{.syms} files.) A simple @value{GDBN} invocation to do nothing |
| 949 | but build a @file{.syms} file for future use is: |
| 950 | |
| 951 | @example |
| 952 | gdb -batch -nx -mapped -readnow programname |
| 953 | @end example |
| 954 | |
| 955 | @node Mode Options |
| 956 | @subsection Choosing modes |
| 957 | |
| 958 | You can run @value{GDBN} in various alternative modes---for example, in |
| 959 | batch mode or quiet mode. |
| 960 | |
| 961 | @table @code |
| 962 | @item -nx |
| 963 | @itemx -n |
| 964 | @cindex @code{--nx} |
| 965 | @cindex @code{-n} |
| 966 | Do not execute commands found in any initialization files. Normally, |
| 967 | @value{GDBN} executes the commands in these files after all the command |
| 968 | options and arguments have been processed. @xref{Command Files,,Command |
| 969 | files}. |
| 970 | |
| 971 | @item -quiet |
| 972 | @itemx -silent |
| 973 | @itemx -q |
| 974 | @cindex @code{--quiet} |
| 975 | @cindex @code{--silent} |
| 976 | @cindex @code{-q} |
| 977 | ``Quiet''. Do not print the introductory and copyright messages. These |
| 978 | messages are also suppressed in batch mode. |
| 979 | |
| 980 | @item -batch |
| 981 | @cindex @code{--batch} |
| 982 | Run in batch mode. Exit with status @code{0} after processing all the |
| 983 | command files specified with @samp{-x} (and all commands from |
| 984 | initialization files, if not inhibited with @samp{-n}). Exit with |
| 985 | nonzero status if an error occurs in executing the @value{GDBN} commands |
| 986 | in the command files. |
| 987 | |
| 988 | Batch mode may be useful for running @value{GDBN} as a filter, for |
| 989 | example to download and run a program on another computer; in order to |
| 990 | make this more useful, the message |
| 991 | |
| 992 | @example |
| 993 | Program exited normally. |
| 994 | @end example |
| 995 | |
| 996 | @noindent |
| 997 | (which is ordinarily issued whenever a program running under |
| 998 | @value{GDBN} control terminates) is not issued when running in batch |
| 999 | mode. |
| 1000 | |
| 1001 | @item -nowindows |
| 1002 | @itemx -nw |
| 1003 | @cindex @code{--nowindows} |
| 1004 | @cindex @code{-nw} |
| 1005 | ``No windows''. If @value{GDBN} comes with a graphical user interface |
| 1006 | (GUI) built in, then this option tells @value{GDBN} to only use the command-line |
| 1007 | interface. If no GUI is available, this option has no effect. |
| 1008 | |
| 1009 | @item -windows |
| 1010 | @itemx -w |
| 1011 | @cindex @code{--windows} |
| 1012 | @cindex @code{-w} |
| 1013 | If @value{GDBN} includes a GUI, then this option requires it to be |
| 1014 | used if possible. |
| 1015 | |
| 1016 | @item -cd @var{directory} |
| 1017 | @cindex @code{--cd} |
| 1018 | Run @value{GDBN} using @var{directory} as its working directory, |
| 1019 | instead of the current directory. |
| 1020 | |
| 1021 | @item -fullname |
| 1022 | @itemx -f |
| 1023 | @cindex @code{--fullname} |
| 1024 | @cindex @code{-f} |
| 1025 | @sc{gnu} Emacs sets this option when it runs @value{GDBN} as a |
| 1026 | subprocess. It tells @value{GDBN} to output the full file name and line |
| 1027 | number in a standard, recognizable fashion each time a stack frame is |
| 1028 | displayed (which includes each time your program stops). This |
| 1029 | recognizable format looks like two @samp{\032} characters, followed by |
| 1030 | the file name, line number and character position separated by colons, |
| 1031 | and a newline. The Emacs-to-@value{GDBN} interface program uses the two |
| 1032 | @samp{\032} characters as a signal to display the source code for the |
| 1033 | frame. |
| 1034 | |
| 1035 | @item -epoch |
| 1036 | @cindex @code{--epoch} |
| 1037 | The Epoch Emacs-@value{GDBN} interface sets this option when it runs |
| 1038 | @value{GDBN} as a subprocess. It tells @value{GDBN} to modify its print |
| 1039 | routines so as to allow Epoch to display values of expressions in a |
| 1040 | separate window. |
| 1041 | |
| 1042 | @item -annotate @var{level} |
| 1043 | @cindex @code{--annotate} |
| 1044 | This option sets the @dfn{annotation level} inside @value{GDBN}. Its |
| 1045 | effect is identical to using @samp{set annotate @var{level}} |
| 1046 | (@pxref{Annotations}). |
| 1047 | Annotation level controls how much information does @value{GDBN} print |
| 1048 | together with its prompt, values of expressions, source lines, and other |
| 1049 | types of output. Level 0 is the normal, level 1 is for use when |
| 1050 | @value{GDBN} is run as a subprocess of @sc{gnu} Emacs, level 2 is the |
| 1051 | maximum annotation suitable for programs that control @value{GDBN}. |
| 1052 | |
| 1053 | @item -async |
| 1054 | @cindex @code{--async} |
| 1055 | Use the asynchronous event loop for the command-line interface. |
| 1056 | @value{GDBN} processes all events, such as user keyboard input, via a |
| 1057 | special event loop. This allows @value{GDBN} to accept and process user |
| 1058 | commands in parallel with the debugged process being |
| 1059 | run@footnote{@value{GDBN} built with @sc{djgpp} tools for |
| 1060 | MS-DOS/MS-Windows supports this mode of operation, but the event loop is |
| 1061 | suspended when the debuggee runs.}, so you don't need to wait for |
| 1062 | control to return to @value{GDBN} before you type the next command. |
| 1063 | (@emph{Note:} as of version 5.1, the target side of the asynchronous |
| 1064 | operation is not yet in place, so @samp{-async} does not work fully |
| 1065 | yet.) |
| 1066 | @c FIXME: when the target side of the event loop is done, the above NOTE |
| 1067 | @c should be removed. |
| 1068 | |
| 1069 | When the standard input is connected to a terminal device, @value{GDBN} |
| 1070 | uses the asynchronous event loop by default, unless disabled by the |
| 1071 | @samp{-noasync} option. |
| 1072 | |
| 1073 | @item -noasync |
| 1074 | @cindex @code{--noasync} |
| 1075 | Disable the asynchronous event loop for the command-line interface. |
| 1076 | |
| 1077 | @item --args |
| 1078 | @cindex @code{--args} |
| 1079 | Change interpretation of command line so that arguments following the |
| 1080 | executable file are passed as command line arguments to the inferior. |
| 1081 | This option stops option processing. |
| 1082 | |
| 1083 | @item -baud @var{bps} |
| 1084 | @itemx -b @var{bps} |
| 1085 | @cindex @code{--baud} |
| 1086 | @cindex @code{-b} |
| 1087 | Set the line speed (baud rate or bits per second) of any serial |
| 1088 | interface used by @value{GDBN} for remote debugging. |
| 1089 | |
| 1090 | @item -tty @var{device} |
| 1091 | @itemx -t @var{device} |
| 1092 | @cindex @code{--tty} |
| 1093 | @cindex @code{-t} |
| 1094 | Run using @var{device} for your program's standard input and output. |
| 1095 | @c FIXME: kingdon thinks there is more to -tty. Investigate. |
| 1096 | |
| 1097 | @c resolve the situation of these eventually |
| 1098 | @item -tui |
| 1099 | @cindex @code{--tui} |
| 1100 | Activate the Terminal User Interface when starting. |
| 1101 | The Terminal User Interface manages several text windows on the terminal, |
| 1102 | showing source, assembly, registers and @value{GDBN} command outputs |
| 1103 | (@pxref{TUI, ,@value{GDBN} Text User Interface}). |
| 1104 | Do not use this option if you run @value{GDBN} from Emacs |
| 1105 | (@pxref{Emacs, ,Using @value{GDBN} under @sc{gnu} Emacs}). |
| 1106 | |
| 1107 | @c @item -xdb |
| 1108 | @c @cindex @code{--xdb} |
| 1109 | @c Run in XDB compatibility mode, allowing the use of certain XDB commands. |
| 1110 | @c For information, see the file @file{xdb_trans.html}, which is usually |
| 1111 | @c installed in the directory @code{/opt/langtools/wdb/doc} on HP-UX |
| 1112 | @c systems. |
| 1113 | |
| 1114 | @item -interpreter @var{interp} |
| 1115 | @cindex @code{--interpreter} |
| 1116 | Use the interpreter @var{interp} for interface with the controlling |
| 1117 | program or device. This option is meant to be set by programs which |
| 1118 | communicate with @value{GDBN} using it as a back end. |
| 1119 | |
| 1120 | @samp{--interpreter=mi} (or @samp{--interpreter=mi1}) causes |
| 1121 | @value{GDBN} to use the @dfn{gdb/mi interface} (@pxref{GDB/MI, , The |
| 1122 | @sc{gdb/mi} Interface}). The older @sc{gdb/mi} interface, included in |
| 1123 | @value{GDBN} version 5.0 can be selected with @samp{--interpreter=mi0}. |
| 1124 | |
| 1125 | @item -write |
| 1126 | @cindex @code{--write} |
| 1127 | Open the executable and core files for both reading and writing. This |
| 1128 | is equivalent to the @samp{set write on} command inside @value{GDBN} |
| 1129 | (@pxref{Patching}). |
| 1130 | |
| 1131 | @item -statistics |
| 1132 | @cindex @code{--statistics} |
| 1133 | This option causes @value{GDBN} to print statistics about time and |
| 1134 | memory usage after it completes each command and returns to the prompt. |
| 1135 | |
| 1136 | @item -version |
| 1137 | @cindex @code{--version} |
| 1138 | This option causes @value{GDBN} to print its version number and |
| 1139 | no-warranty blurb, and exit. |
| 1140 | |
| 1141 | @end table |
| 1142 | |
| 1143 | @node Quitting GDB |
| 1144 | @section Quitting @value{GDBN} |
| 1145 | @cindex exiting @value{GDBN} |
| 1146 | @cindex leaving @value{GDBN} |
| 1147 | |
| 1148 | @table @code |
| 1149 | @kindex quit @r{[}@var{expression}@r{]} |
| 1150 | @kindex q @r{(@code{quit})} |
| 1151 | @item quit @r{[}@var{expression}@r{]} |
| 1152 | @itemx q |
| 1153 | To exit @value{GDBN}, use the @code{quit} command (abbreviated |
| 1154 | @code{q}), or type an end-of-file character (usually @kbd{C-d}). If you |
| 1155 | do not supply @var{expression}, @value{GDBN} will terminate normally; |
| 1156 | otherwise it will terminate using the result of @var{expression} as the |
| 1157 | error code. |
| 1158 | @end table |
| 1159 | |
| 1160 | @cindex interrupt |
| 1161 | An interrupt (often @kbd{C-c}) does not exit from @value{GDBN}, but rather |
| 1162 | terminates the action of any @value{GDBN} command that is in progress and |
| 1163 | returns to @value{GDBN} command level. It is safe to type the interrupt |
| 1164 | character at any time because @value{GDBN} does not allow it to take effect |
| 1165 | until a time when it is safe. |
| 1166 | |
| 1167 | If you have been using @value{GDBN} to control an attached process or |
| 1168 | device, you can release it with the @code{detach} command |
| 1169 | (@pxref{Attach, ,Debugging an already-running process}). |
| 1170 | |
| 1171 | @node Shell Commands |
| 1172 | @section Shell commands |
| 1173 | |
| 1174 | If you need to execute occasional shell commands during your |
| 1175 | debugging session, there is no need to leave or suspend @value{GDBN}; you can |
| 1176 | just use the @code{shell} command. |
| 1177 | |
| 1178 | @table @code |
| 1179 | @kindex shell |
| 1180 | @cindex shell escape |
| 1181 | @item shell @var{command string} |
| 1182 | Invoke a standard shell to execute @var{command string}. |
| 1183 | If it exists, the environment variable @code{SHELL} determines which |
| 1184 | shell to run. Otherwise @value{GDBN} uses the default shell |
| 1185 | (@file{/bin/sh} on Unix systems, @file{COMMAND.COM} on MS-DOS, etc.). |
| 1186 | @end table |
| 1187 | |
| 1188 | The utility @code{make} is often needed in development environments. |
| 1189 | You do not have to use the @code{shell} command for this purpose in |
| 1190 | @value{GDBN}: |
| 1191 | |
| 1192 | @table @code |
| 1193 | @kindex make |
| 1194 | @cindex calling make |
| 1195 | @item make @var{make-args} |
| 1196 | Execute the @code{make} program with the specified |
| 1197 | arguments. This is equivalent to @samp{shell make @var{make-args}}. |
| 1198 | @end table |
| 1199 | |
| 1200 | @node Commands |
| 1201 | @chapter @value{GDBN} Commands |
| 1202 | |
| 1203 | You can abbreviate a @value{GDBN} command to the first few letters of the command |
| 1204 | name, if that abbreviation is unambiguous; and you can repeat certain |
| 1205 | @value{GDBN} commands by typing just @key{RET}. You can also use the @key{TAB} |
| 1206 | key to get @value{GDBN} to fill out the rest of a word in a command (or to |
| 1207 | show you the alternatives available, if there is more than one possibility). |
| 1208 | |
| 1209 | @menu |
| 1210 | * Command Syntax:: How to give commands to @value{GDBN} |
| 1211 | * Completion:: Command completion |
| 1212 | * Help:: How to ask @value{GDBN} for help |
| 1213 | @end menu |
| 1214 | |
| 1215 | @node Command Syntax |
| 1216 | @section Command syntax |
| 1217 | |
| 1218 | A @value{GDBN} command is a single line of input. There is no limit on |
| 1219 | how long it can be. It starts with a command name, which is followed by |
| 1220 | arguments whose meaning depends on the command name. For example, the |
| 1221 | command @code{step} accepts an argument which is the number of times to |
| 1222 | step, as in @samp{step 5}. You can also use the @code{step} command |
| 1223 | with no arguments. Some commands do not allow any arguments. |
| 1224 | |
| 1225 | @cindex abbreviation |
| 1226 | @value{GDBN} command names may always be truncated if that abbreviation is |
| 1227 | unambiguous. Other possible command abbreviations are listed in the |
| 1228 | documentation for individual commands. In some cases, even ambiguous |
| 1229 | abbreviations are allowed; for example, @code{s} is specially defined as |
| 1230 | equivalent to @code{step} even though there are other commands whose |
| 1231 | names start with @code{s}. You can test abbreviations by using them as |
| 1232 | arguments to the @code{help} command. |
| 1233 | |
| 1234 | @cindex repeating commands |
| 1235 | @kindex RET @r{(repeat last command)} |
| 1236 | A blank line as input to @value{GDBN} (typing just @key{RET}) means to |
| 1237 | repeat the previous command. Certain commands (for example, @code{run}) |
| 1238 | will not repeat this way; these are commands whose unintentional |
| 1239 | repetition might cause trouble and which you are unlikely to want to |
| 1240 | repeat. |
| 1241 | |
| 1242 | The @code{list} and @code{x} commands, when you repeat them with |
| 1243 | @key{RET}, construct new arguments rather than repeating |
| 1244 | exactly as typed. This permits easy scanning of source or memory. |
| 1245 | |
| 1246 | @value{GDBN} can also use @key{RET} in another way: to partition lengthy |
| 1247 | output, in a way similar to the common utility @code{more} |
| 1248 | (@pxref{Screen Size,,Screen size}). Since it is easy to press one |
| 1249 | @key{RET} too many in this situation, @value{GDBN} disables command |
| 1250 | repetition after any command that generates this sort of display. |
| 1251 | |
| 1252 | @kindex # @r{(a comment)} |
| 1253 | @cindex comment |
| 1254 | Any text from a @kbd{#} to the end of the line is a comment; it does |
| 1255 | nothing. This is useful mainly in command files (@pxref{Command |
| 1256 | Files,,Command files}). |
| 1257 | |
| 1258 | @cindex repeating command sequences |
| 1259 | @kindex C-o @r{(operate-and-get-next)} |
| 1260 | The @kbd{C-o} binding is useful for repeating a complex sequence of |
| 1261 | commands. This command accepts the current line, like @kbd{RET}, and |
| 1262 | then fetches the next line relative to the current line from the history |
| 1263 | for editing. |
| 1264 | |
| 1265 | @node Completion |
| 1266 | @section Command completion |
| 1267 | |
| 1268 | @cindex completion |
| 1269 | @cindex word completion |
| 1270 | @value{GDBN} can fill in the rest of a word in a command for you, if there is |
| 1271 | only one possibility; it can also show you what the valid possibilities |
| 1272 | are for the next word in a command, at any time. This works for @value{GDBN} |
| 1273 | commands, @value{GDBN} subcommands, and the names of symbols in your program. |
| 1274 | |
| 1275 | Press the @key{TAB} key whenever you want @value{GDBN} to fill out the rest |
| 1276 | of a word. If there is only one possibility, @value{GDBN} fills in the |
| 1277 | word, and waits for you to finish the command (or press @key{RET} to |
| 1278 | enter it). For example, if you type |
| 1279 | |
| 1280 | @c FIXME "@key" does not distinguish its argument sufficiently to permit |
| 1281 | @c complete accuracy in these examples; space introduced for clarity. |
| 1282 | @c If texinfo enhancements make it unnecessary, it would be nice to |
| 1283 | @c replace " @key" by "@key" in the following... |
| 1284 | @example |
| 1285 | (@value{GDBP}) info bre @key{TAB} |
| 1286 | @end example |
| 1287 | |
| 1288 | @noindent |
| 1289 | @value{GDBN} fills in the rest of the word @samp{breakpoints}, since that is |
| 1290 | the only @code{info} subcommand beginning with @samp{bre}: |
| 1291 | |
| 1292 | @example |
| 1293 | (@value{GDBP}) info breakpoints |
| 1294 | @end example |
| 1295 | |
| 1296 | @noindent |
| 1297 | You can either press @key{RET} at this point, to run the @code{info |
| 1298 | breakpoints} command, or backspace and enter something else, if |
| 1299 | @samp{breakpoints} does not look like the command you expected. (If you |
| 1300 | were sure you wanted @code{info breakpoints} in the first place, you |
| 1301 | might as well just type @key{RET} immediately after @samp{info bre}, |
| 1302 | to exploit command abbreviations rather than command completion). |
| 1303 | |
| 1304 | If there is more than one possibility for the next word when you press |
| 1305 | @key{TAB}, @value{GDBN} sounds a bell. You can either supply more |
| 1306 | characters and try again, or just press @key{TAB} a second time; |
| 1307 | @value{GDBN} displays all the possible completions for that word. For |
| 1308 | example, you might want to set a breakpoint on a subroutine whose name |
| 1309 | begins with @samp{make_}, but when you type @kbd{b make_@key{TAB}} @value{GDBN} |
| 1310 | just sounds the bell. Typing @key{TAB} again displays all the |
| 1311 | function names in your program that begin with those characters, for |
| 1312 | example: |
| 1313 | |
| 1314 | @example |
| 1315 | (@value{GDBP}) b make_ @key{TAB} |
| 1316 | @exdent @value{GDBN} sounds bell; press @key{TAB} again, to see: |
| 1317 | make_a_section_from_file make_environ |
| 1318 | make_abs_section make_function_type |
| 1319 | make_blockvector make_pointer_type |
| 1320 | make_cleanup make_reference_type |
| 1321 | make_command make_symbol_completion_list |
| 1322 | (@value{GDBP}) b make_ |
| 1323 | @end example |
| 1324 | |
| 1325 | @noindent |
| 1326 | After displaying the available possibilities, @value{GDBN} copies your |
| 1327 | partial input (@samp{b make_} in the example) so you can finish the |
| 1328 | command. |
| 1329 | |
| 1330 | If you just want to see the list of alternatives in the first place, you |
| 1331 | can press @kbd{M-?} rather than pressing @key{TAB} twice. @kbd{M-?} |
| 1332 | means @kbd{@key{META} ?}. You can type this either by holding down a |
| 1333 | key designated as the @key{META} shift on your keyboard (if there is |
| 1334 | one) while typing @kbd{?}, or as @key{ESC} followed by @kbd{?}. |
| 1335 | |
| 1336 | @cindex quotes in commands |
| 1337 | @cindex completion of quoted strings |
| 1338 | Sometimes the string you need, while logically a ``word'', may contain |
| 1339 | parentheses or other characters that @value{GDBN} normally excludes from |
| 1340 | its notion of a word. To permit word completion to work in this |
| 1341 | situation, you may enclose words in @code{'} (single quote marks) in |
| 1342 | @value{GDBN} commands. |
| 1343 | |
| 1344 | The most likely situation where you might need this is in typing the |
| 1345 | name of a C@t{++} function. This is because C@t{++} allows function |
| 1346 | overloading (multiple definitions of the same function, distinguished |
| 1347 | by argument type). For example, when you want to set a breakpoint you |
| 1348 | may need to distinguish whether you mean the version of @code{name} |
| 1349 | that takes an @code{int} parameter, @code{name(int)}, or the version |
| 1350 | that takes a @code{float} parameter, @code{name(float)}. To use the |
| 1351 | word-completion facilities in this situation, type a single quote |
| 1352 | @code{'} at the beginning of the function name. This alerts |
| 1353 | @value{GDBN} that it may need to consider more information than usual |
| 1354 | when you press @key{TAB} or @kbd{M-?} to request word completion: |
| 1355 | |
| 1356 | @example |
| 1357 | (@value{GDBP}) b 'bubble( @kbd{M-?} |
| 1358 | bubble(double,double) bubble(int,int) |
| 1359 | (@value{GDBP}) b 'bubble( |
| 1360 | @end example |
| 1361 | |
| 1362 | In some cases, @value{GDBN} can tell that completing a name requires using |
| 1363 | quotes. When this happens, @value{GDBN} inserts the quote for you (while |
| 1364 | completing as much as it can) if you do not type the quote in the first |
| 1365 | place: |
| 1366 | |
| 1367 | @example |
| 1368 | (@value{GDBP}) b bub @key{TAB} |
| 1369 | @exdent @value{GDBN} alters your input line to the following, and rings a bell: |
| 1370 | (@value{GDBP}) b 'bubble( |
| 1371 | @end example |
| 1372 | |
| 1373 | @noindent |
| 1374 | In general, @value{GDBN} can tell that a quote is needed (and inserts it) if |
| 1375 | you have not yet started typing the argument list when you ask for |
| 1376 | completion on an overloaded symbol. |
| 1377 | |
| 1378 | For more information about overloaded functions, see @ref{C plus plus |
| 1379 | expressions, ,C@t{++} expressions}. You can use the command @code{set |
| 1380 | overload-resolution off} to disable overload resolution; |
| 1381 | see @ref{Debugging C plus plus, ,@value{GDBN} features for C@t{++}}. |
| 1382 | |
| 1383 | |
| 1384 | @node Help |
| 1385 | @section Getting help |
| 1386 | @cindex online documentation |
| 1387 | @kindex help |
| 1388 | |
| 1389 | You can always ask @value{GDBN} itself for information on its commands, |
| 1390 | using the command @code{help}. |
| 1391 | |
| 1392 | @table @code |
| 1393 | @kindex h @r{(@code{help})} |
| 1394 | @item help |
| 1395 | @itemx h |
| 1396 | You can use @code{help} (abbreviated @code{h}) with no arguments to |
| 1397 | display a short list of named classes of commands: |
| 1398 | |
| 1399 | @smallexample |
| 1400 | (@value{GDBP}) help |
| 1401 | List of classes of commands: |
| 1402 | |
| 1403 | aliases -- Aliases of other commands |
| 1404 | breakpoints -- Making program stop at certain points |
| 1405 | data -- Examining data |
| 1406 | files -- Specifying and examining files |
| 1407 | internals -- Maintenance commands |
| 1408 | obscure -- Obscure features |
| 1409 | running -- Running the program |
| 1410 | stack -- Examining the stack |
| 1411 | status -- Status inquiries |
| 1412 | support -- Support facilities |
| 1413 | tracepoints -- Tracing of program execution without@* |
| 1414 | stopping the program |
| 1415 | user-defined -- User-defined commands |
| 1416 | |
| 1417 | Type "help" followed by a class name for a list of |
| 1418 | commands in that class. |
| 1419 | Type "help" followed by command name for full |
| 1420 | documentation. |
| 1421 | Command name abbreviations are allowed if unambiguous. |
| 1422 | (@value{GDBP}) |
| 1423 | @end smallexample |
| 1424 | @c the above line break eliminates huge line overfull... |
| 1425 | |
| 1426 | @item help @var{class} |
| 1427 | Using one of the general help classes as an argument, you can get a |
| 1428 | list of the individual commands in that class. For example, here is the |
| 1429 | help display for the class @code{status}: |
| 1430 | |
| 1431 | @smallexample |
| 1432 | (@value{GDBP}) help status |
| 1433 | Status inquiries. |
| 1434 | |
| 1435 | List of commands: |
| 1436 | |
| 1437 | @c Line break in "show" line falsifies real output, but needed |
| 1438 | @c to fit in smallbook page size. |
| 1439 | info -- Generic command for showing things |
| 1440 | about the program being debugged |
| 1441 | show -- Generic command for showing things |
| 1442 | about the debugger |
| 1443 | |
| 1444 | Type "help" followed by command name for full |
| 1445 | documentation. |
| 1446 | Command name abbreviations are allowed if unambiguous. |
| 1447 | (@value{GDBP}) |
| 1448 | @end smallexample |
| 1449 | |
| 1450 | @item help @var{command} |
| 1451 | With a command name as @code{help} argument, @value{GDBN} displays a |
| 1452 | short paragraph on how to use that command. |
| 1453 | |
| 1454 | @kindex apropos |
| 1455 | @item apropos @var{args} |
| 1456 | The @code{apropos @var{args}} command searches through all of the @value{GDBN} |
| 1457 | commands, and their documentation, for the regular expression specified in |
| 1458 | @var{args}. It prints out all matches found. For example: |
| 1459 | |
| 1460 | @smallexample |
| 1461 | apropos reload |
| 1462 | @end smallexample |
| 1463 | |
| 1464 | @noindent |
| 1465 | results in: |
| 1466 | |
| 1467 | @smallexample |
| 1468 | @c @group |
| 1469 | set symbol-reloading -- Set dynamic symbol table reloading |
| 1470 | multiple times in one run |
| 1471 | show symbol-reloading -- Show dynamic symbol table reloading |
| 1472 | multiple times in one run |
| 1473 | @c @end group |
| 1474 | @end smallexample |
| 1475 | |
| 1476 | @kindex complete |
| 1477 | @item complete @var{args} |
| 1478 | The @code{complete @var{args}} command lists all the possible completions |
| 1479 | for the beginning of a command. Use @var{args} to specify the beginning of the |
| 1480 | command you want completed. For example: |
| 1481 | |
| 1482 | @smallexample |
| 1483 | complete i |
| 1484 | @end smallexample |
| 1485 | |
| 1486 | @noindent results in: |
| 1487 | |
| 1488 | @smallexample |
| 1489 | @group |
| 1490 | if |
| 1491 | ignore |
| 1492 | info |
| 1493 | inspect |
| 1494 | @end group |
| 1495 | @end smallexample |
| 1496 | |
| 1497 | @noindent This is intended for use by @sc{gnu} Emacs. |
| 1498 | @end table |
| 1499 | |
| 1500 | In addition to @code{help}, you can use the @value{GDBN} commands @code{info} |
| 1501 | and @code{show} to inquire about the state of your program, or the state |
| 1502 | of @value{GDBN} itself. Each command supports many topics of inquiry; this |
| 1503 | manual introduces each of them in the appropriate context. The listings |
| 1504 | under @code{info} and under @code{show} in the Index point to |
| 1505 | all the sub-commands. @xref{Index}. |
| 1506 | |
| 1507 | @c @group |
| 1508 | @table @code |
| 1509 | @kindex info |
| 1510 | @kindex i @r{(@code{info})} |
| 1511 | @item info |
| 1512 | This command (abbreviated @code{i}) is for describing the state of your |
| 1513 | program. For example, you can list the arguments given to your program |
| 1514 | with @code{info args}, list the registers currently in use with @code{info |
| 1515 | registers}, or list the breakpoints you have set with @code{info breakpoints}. |
| 1516 | You can get a complete list of the @code{info} sub-commands with |
| 1517 | @w{@code{help info}}. |
| 1518 | |
| 1519 | @kindex set |
| 1520 | @item set |
| 1521 | You can assign the result of an expression to an environment variable with |
| 1522 | @code{set}. For example, you can set the @value{GDBN} prompt to a $-sign with |
| 1523 | @code{set prompt $}. |
| 1524 | |
| 1525 | @kindex show |
| 1526 | @item show |
| 1527 | In contrast to @code{info}, @code{show} is for describing the state of |
| 1528 | @value{GDBN} itself. |
| 1529 | You can change most of the things you can @code{show}, by using the |
| 1530 | related command @code{set}; for example, you can control what number |
| 1531 | system is used for displays with @code{set radix}, or simply inquire |
| 1532 | which is currently in use with @code{show radix}. |
| 1533 | |
| 1534 | @kindex info set |
| 1535 | To display all the settable parameters and their current |
| 1536 | values, you can use @code{show} with no arguments; you may also use |
| 1537 | @code{info set}. Both commands produce the same display. |
| 1538 | @c FIXME: "info set" violates the rule that "info" is for state of |
| 1539 | @c FIXME...program. Ck w/ GNU: "info set" to be called something else, |
| 1540 | @c FIXME...or change desc of rule---eg "state of prog and debugging session"? |
| 1541 | @end table |
| 1542 | @c @end group |
| 1543 | |
| 1544 | Here are three miscellaneous @code{show} subcommands, all of which are |
| 1545 | exceptional in lacking corresponding @code{set} commands: |
| 1546 | |
| 1547 | @table @code |
| 1548 | @kindex show version |
| 1549 | @cindex version number |
| 1550 | @item show version |
| 1551 | Show what version of @value{GDBN} is running. You should include this |
| 1552 | information in @value{GDBN} bug-reports. If multiple versions of |
| 1553 | @value{GDBN} are in use at your site, you may need to determine which |
| 1554 | version of @value{GDBN} you are running; as @value{GDBN} evolves, new |
| 1555 | commands are introduced, and old ones may wither away. Also, many |
| 1556 | system vendors ship variant versions of @value{GDBN}, and there are |
| 1557 | variant versions of @value{GDBN} in @sc{gnu}/Linux distributions as well. |
| 1558 | The version number is the same as the one announced when you start |
| 1559 | @value{GDBN}. |
| 1560 | |
| 1561 | @kindex show copying |
| 1562 | @item show copying |
| 1563 | Display information about permission for copying @value{GDBN}. |
| 1564 | |
| 1565 | @kindex show warranty |
| 1566 | @item show warranty |
| 1567 | Display the @sc{gnu} ``NO WARRANTY'' statement, or a warranty, |
| 1568 | if your version of @value{GDBN} comes with one. |
| 1569 | |
| 1570 | @end table |
| 1571 | |
| 1572 | @node Running |
| 1573 | @chapter Running Programs Under @value{GDBN} |
| 1574 | |
| 1575 | When you run a program under @value{GDBN}, you must first generate |
| 1576 | debugging information when you compile it. |
| 1577 | |
| 1578 | You may start @value{GDBN} with its arguments, if any, in an environment |
| 1579 | of your choice. If you are doing native debugging, you may redirect |
| 1580 | your program's input and output, debug an already running process, or |
| 1581 | kill a child process. |
| 1582 | |
| 1583 | @menu |
| 1584 | * Compilation:: Compiling for debugging |
| 1585 | * Starting:: Starting your program |
| 1586 | * Arguments:: Your program's arguments |
| 1587 | * Environment:: Your program's environment |
| 1588 | |
| 1589 | * Working Directory:: Your program's working directory |
| 1590 | * Input/Output:: Your program's input and output |
| 1591 | * Attach:: Debugging an already-running process |
| 1592 | * Kill Process:: Killing the child process |
| 1593 | |
| 1594 | * Threads:: Debugging programs with multiple threads |
| 1595 | * Processes:: Debugging programs with multiple processes |
| 1596 | @end menu |
| 1597 | |
| 1598 | @node Compilation |
| 1599 | @section Compiling for debugging |
| 1600 | |
| 1601 | In order to debug a program effectively, you need to generate |
| 1602 | debugging information when you compile it. This debugging information |
| 1603 | is stored in the object file; it describes the data type of each |
| 1604 | variable or function and the correspondence between source line numbers |
| 1605 | and addresses in the executable code. |
| 1606 | |
| 1607 | To request debugging information, specify the @samp{-g} option when you run |
| 1608 | the compiler. |
| 1609 | |
| 1610 | Many C compilers are unable to handle the @samp{-g} and @samp{-O} |
| 1611 | options together. Using those compilers, you cannot generate optimized |
| 1612 | executables containing debugging information. |
| 1613 | |
| 1614 | @value{NGCC}, the @sc{gnu} C compiler, supports @samp{-g} with or |
| 1615 | without @samp{-O}, making it possible to debug optimized code. We |
| 1616 | recommend that you @emph{always} use @samp{-g} whenever you compile a |
| 1617 | program. You may think your program is correct, but there is no sense |
| 1618 | in pushing your luck. |
| 1619 | |
| 1620 | @cindex optimized code, debugging |
| 1621 | @cindex debugging optimized code |
| 1622 | When you debug a program compiled with @samp{-g -O}, remember that the |
| 1623 | optimizer is rearranging your code; the debugger shows you what is |
| 1624 | really there. Do not be too surprised when the execution path does not |
| 1625 | exactly match your source file! An extreme example: if you define a |
| 1626 | variable, but never use it, @value{GDBN} never sees that |
| 1627 | variable---because the compiler optimizes it out of existence. |
| 1628 | |
| 1629 | Some things do not work as well with @samp{-g -O} as with just |
| 1630 | @samp{-g}, particularly on machines with instruction scheduling. If in |
| 1631 | doubt, recompile with @samp{-g} alone, and if this fixes the problem, |
| 1632 | please report it to us as a bug (including a test case!). |
| 1633 | |
| 1634 | Older versions of the @sc{gnu} C compiler permitted a variant option |
| 1635 | @w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this |
| 1636 | format; if your @sc{gnu} C compiler has this option, do not use it. |
| 1637 | |
| 1638 | @need 2000 |
| 1639 | @node Starting |
| 1640 | @section Starting your program |
| 1641 | @cindex starting |
| 1642 | @cindex running |
| 1643 | |
| 1644 | @table @code |
| 1645 | @kindex run |
| 1646 | @kindex r @r{(@code{run})} |
| 1647 | @item run |
| 1648 | @itemx r |
| 1649 | Use the @code{run} command to start your program under @value{GDBN}. |
| 1650 | You must first specify the program name (except on VxWorks) with an |
| 1651 | argument to @value{GDBN} (@pxref{Invocation, ,Getting In and Out of |
| 1652 | @value{GDBN}}), or by using the @code{file} or @code{exec-file} command |
| 1653 | (@pxref{Files, ,Commands to specify files}). |
| 1654 | |
| 1655 | @end table |
| 1656 | |
| 1657 | If you are running your program in an execution environment that |
| 1658 | supports processes, @code{run} creates an inferior process and makes |
| 1659 | that process run your program. (In environments without processes, |
| 1660 | @code{run} jumps to the start of your program.) |
| 1661 | |
| 1662 | The execution of a program is affected by certain information it |
| 1663 | receives from its superior. @value{GDBN} provides ways to specify this |
| 1664 | information, which you must do @emph{before} starting your program. (You |
| 1665 | can change it after starting your program, but such changes only affect |
| 1666 | your program the next time you start it.) This information may be |
| 1667 | divided into four categories: |
| 1668 | |
| 1669 | @table @asis |
| 1670 | @item The @emph{arguments.} |
| 1671 | Specify the arguments to give your program as the arguments of the |
| 1672 | @code{run} command. If a shell is available on your target, the shell |
| 1673 | is used to pass the arguments, so that you may use normal conventions |
| 1674 | (such as wildcard expansion or variable substitution) in describing |
| 1675 | the arguments. |
| 1676 | In Unix systems, you can control which shell is used with the |
| 1677 | @code{SHELL} environment variable. |
| 1678 | @xref{Arguments, ,Your program's arguments}. |
| 1679 | |
| 1680 | @item The @emph{environment.} |
| 1681 | Your program normally inherits its environment from @value{GDBN}, but you can |
| 1682 | use the @value{GDBN} commands @code{set environment} and @code{unset |
| 1683 | environment} to change parts of the environment that affect |
| 1684 | your program. @xref{Environment, ,Your program's environment}. |
| 1685 | |
| 1686 | @item The @emph{working directory.} |
| 1687 | Your program inherits its working directory from @value{GDBN}. You can set |
| 1688 | the @value{GDBN} working directory with the @code{cd} command in @value{GDBN}. |
| 1689 | @xref{Working Directory, ,Your program's working directory}. |
| 1690 | |
| 1691 | @item The @emph{standard input and output.} |
| 1692 | Your program normally uses the same device for standard input and |
| 1693 | standard output as @value{GDBN} is using. You can redirect input and output |
| 1694 | in the @code{run} command line, or you can use the @code{tty} command to |
| 1695 | set a different device for your program. |
| 1696 | @xref{Input/Output, ,Your program's input and output}. |
| 1697 | |
| 1698 | @cindex pipes |
| 1699 | @emph{Warning:} While input and output redirection work, you cannot use |
| 1700 | pipes to pass the output of the program you are debugging to another |
| 1701 | program; if you attempt this, @value{GDBN} is likely to wind up debugging the |
| 1702 | wrong program. |
| 1703 | @end table |
| 1704 | |
| 1705 | When you issue the @code{run} command, your program begins to execute |
| 1706 | immediately. @xref{Stopping, ,Stopping and continuing}, for discussion |
| 1707 | of how to arrange for your program to stop. Once your program has |
| 1708 | stopped, you may call functions in your program, using the @code{print} |
| 1709 | or @code{call} commands. @xref{Data, ,Examining Data}. |
| 1710 | |
| 1711 | If the modification time of your symbol file has changed since the last |
| 1712 | time @value{GDBN} read its symbols, @value{GDBN} discards its symbol |
| 1713 | table, and reads it again. When it does this, @value{GDBN} tries to retain |
| 1714 | your current breakpoints. |
| 1715 | |
| 1716 | @node Arguments |
| 1717 | @section Your program's arguments |
| 1718 | |
| 1719 | @cindex arguments (to your program) |
| 1720 | The arguments to your program can be specified by the arguments of the |
| 1721 | @code{run} command. |
| 1722 | They are passed to a shell, which expands wildcard characters and |
| 1723 | performs redirection of I/O, and thence to your program. Your |
| 1724 | @code{SHELL} environment variable (if it exists) specifies what shell |
| 1725 | @value{GDBN} uses. If you do not define @code{SHELL}, @value{GDBN} uses |
| 1726 | the default shell (@file{/bin/sh} on Unix). |
| 1727 | |
| 1728 | On non-Unix systems, the program is usually invoked directly by |
| 1729 | @value{GDBN}, which emulates I/O redirection via the appropriate system |
| 1730 | calls, and the wildcard characters are expanded by the startup code of |
| 1731 | the program, not by the shell. |
| 1732 | |
| 1733 | @code{run} with no arguments uses the same arguments used by the previous |
| 1734 | @code{run}, or those set by the @code{set args} command. |
| 1735 | |
| 1736 | @table @code |
| 1737 | @kindex set args |
| 1738 | @item set args |
| 1739 | Specify the arguments to be used the next time your program is run. If |
| 1740 | @code{set args} has no arguments, @code{run} executes your program |
| 1741 | with no arguments. Once you have run your program with arguments, |
| 1742 | using @code{set args} before the next @code{run} is the only way to run |
| 1743 | it again without arguments. |
| 1744 | |
| 1745 | @kindex show args |
| 1746 | @item show args |
| 1747 | Show the arguments to give your program when it is started. |
| 1748 | @end table |
| 1749 | |
| 1750 | @node Environment |
| 1751 | @section Your program's environment |
| 1752 | |
| 1753 | @cindex environment (of your program) |
| 1754 | The @dfn{environment} consists of a set of environment variables and |
| 1755 | their values. Environment variables conventionally record such things as |
| 1756 | your user name, your home directory, your terminal type, and your search |
| 1757 | path for programs to run. Usually you set up environment variables with |
| 1758 | the shell and they are inherited by all the other programs you run. When |
| 1759 | debugging, it can be useful to try running your program with a modified |
| 1760 | environment without having to start @value{GDBN} over again. |
| 1761 | |
| 1762 | @table @code |
| 1763 | @kindex path |
| 1764 | @item path @var{directory} |
| 1765 | Add @var{directory} to the front of the @code{PATH} environment variable |
| 1766 | (the search path for executables) that will be passed to your program. |
| 1767 | The value of @code{PATH} used by @value{GDBN} does not change. |
| 1768 | You may specify several directory names, separated by whitespace or by a |
| 1769 | system-dependent separator character (@samp{:} on Unix, @samp{;} on |
| 1770 | MS-DOS and MS-Windows). If @var{directory} is already in the path, it |
| 1771 | is moved to the front, so it is searched sooner. |
| 1772 | |
| 1773 | You can use the string @samp{$cwd} to refer to whatever is the current |
| 1774 | working directory at the time @value{GDBN} searches the path. If you |
| 1775 | use @samp{.} instead, it refers to the directory where you executed the |
| 1776 | @code{path} command. @value{GDBN} replaces @samp{.} in the |
| 1777 | @var{directory} argument (with the current path) before adding |
| 1778 | @var{directory} to the search path. |
| 1779 | @c 'path' is explicitly nonrepeatable, but RMS points out it is silly to |
| 1780 | @c document that, since repeating it would be a no-op. |
| 1781 | |
| 1782 | @kindex show paths |
| 1783 | @item show paths |
| 1784 | Display the list of search paths for executables (the @code{PATH} |
| 1785 | environment variable). |
| 1786 | |
| 1787 | @kindex show environment |
| 1788 | @item show environment @r{[}@var{varname}@r{]} |
| 1789 | Print the value of environment variable @var{varname} to be given to |
| 1790 | your program when it starts. If you do not supply @var{varname}, |
| 1791 | print the names and values of all environment variables to be given to |
| 1792 | your program. You can abbreviate @code{environment} as @code{env}. |
| 1793 | |
| 1794 | @kindex set environment |
| 1795 | @item set environment @var{varname} @r{[}=@var{value}@r{]} |
| 1796 | Set environment variable @var{varname} to @var{value}. The value |
| 1797 | changes for your program only, not for @value{GDBN} itself. @var{value} may |
| 1798 | be any string; the values of environment variables are just strings, and |
| 1799 | any interpretation is supplied by your program itself. The @var{value} |
| 1800 | parameter is optional; if it is eliminated, the variable is set to a |
| 1801 | null value. |
| 1802 | @c "any string" here does not include leading, trailing |
| 1803 | @c blanks. Gnu asks: does anyone care? |
| 1804 | |
| 1805 | For example, this command: |
| 1806 | |
| 1807 | @example |
| 1808 | set env USER = foo |
| 1809 | @end example |
| 1810 | |
| 1811 | @noindent |
| 1812 | tells the debugged program, when subsequently run, that its user is named |
| 1813 | @samp{foo}. (The spaces around @samp{=} are used for clarity here; they |
| 1814 | are not actually required.) |
| 1815 | |
| 1816 | @kindex unset environment |
| 1817 | @item unset environment @var{varname} |
| 1818 | Remove variable @var{varname} from the environment to be passed to your |
| 1819 | program. This is different from @samp{set env @var{varname} =}; |
| 1820 | @code{unset environment} removes the variable from the environment, |
| 1821 | rather than assigning it an empty value. |
| 1822 | @end table |
| 1823 | |
| 1824 | @emph{Warning:} On Unix systems, @value{GDBN} runs your program using |
| 1825 | the shell indicated |
| 1826 | by your @code{SHELL} environment variable if it exists (or |
| 1827 | @code{/bin/sh} if not). If your @code{SHELL} variable names a shell |
| 1828 | that runs an initialization file---such as @file{.cshrc} for C-shell, or |
| 1829 | @file{.bashrc} for BASH---any variables you set in that file affect |
| 1830 | your program. You may wish to move setting of environment variables to |
| 1831 | files that are only run when you sign on, such as @file{.login} or |
| 1832 | @file{.profile}. |
| 1833 | |
| 1834 | @node Working Directory |
| 1835 | @section Your program's working directory |
| 1836 | |
| 1837 | @cindex working directory (of your program) |
| 1838 | Each time you start your program with @code{run}, it inherits its |
| 1839 | working directory from the current working directory of @value{GDBN}. |
| 1840 | The @value{GDBN} working directory is initially whatever it inherited |
| 1841 | from its parent process (typically the shell), but you can specify a new |
| 1842 | working directory in @value{GDBN} with the @code{cd} command. |
| 1843 | |
| 1844 | The @value{GDBN} working directory also serves as a default for the commands |
| 1845 | that specify files for @value{GDBN} to operate on. @xref{Files, ,Commands to |
| 1846 | specify files}. |
| 1847 | |
| 1848 | @table @code |
| 1849 | @kindex cd |
| 1850 | @item cd @var{directory} |
| 1851 | Set the @value{GDBN} working directory to @var{directory}. |
| 1852 | |
| 1853 | @kindex pwd |
| 1854 | @item pwd |
| 1855 | Print the @value{GDBN} working directory. |
| 1856 | @end table |
| 1857 | |
| 1858 | @node Input/Output |
| 1859 | @section Your program's input and output |
| 1860 | |
| 1861 | @cindex redirection |
| 1862 | @cindex i/o |
| 1863 | @cindex terminal |
| 1864 | By default, the program you run under @value{GDBN} does input and output to |
| 1865 | the same terminal that @value{GDBN} uses. @value{GDBN} switches the terminal |
| 1866 | to its own terminal modes to interact with you, but it records the terminal |
| 1867 | modes your program was using and switches back to them when you continue |
| 1868 | running your program. |
| 1869 | |
| 1870 | @table @code |
| 1871 | @kindex info terminal |
| 1872 | @item info terminal |
| 1873 | Displays information recorded by @value{GDBN} about the terminal modes your |
| 1874 | program is using. |
| 1875 | @end table |
| 1876 | |
| 1877 | You can redirect your program's input and/or output using shell |
| 1878 | redirection with the @code{run} command. For example, |
| 1879 | |
| 1880 | @example |
| 1881 | run > outfile |
| 1882 | @end example |
| 1883 | |
| 1884 | @noindent |
| 1885 | starts your program, diverting its output to the file @file{outfile}. |
| 1886 | |
| 1887 | @kindex tty |
| 1888 | @cindex controlling terminal |
| 1889 | Another way to specify where your program should do input and output is |
| 1890 | with the @code{tty} command. This command accepts a file name as |
| 1891 | argument, and causes this file to be the default for future @code{run} |
| 1892 | commands. It also resets the controlling terminal for the child |
| 1893 | process, for future @code{run} commands. For example, |
| 1894 | |
| 1895 | @example |
| 1896 | tty /dev/ttyb |
| 1897 | @end example |
| 1898 | |
| 1899 | @noindent |
| 1900 | directs that processes started with subsequent @code{run} commands |
| 1901 | default to do input and output on the terminal @file{/dev/ttyb} and have |
| 1902 | that as their controlling terminal. |
| 1903 | |
| 1904 | An explicit redirection in @code{run} overrides the @code{tty} command's |
| 1905 | effect on the input/output device, but not its effect on the controlling |
| 1906 | terminal. |
| 1907 | |
| 1908 | When you use the @code{tty} command or redirect input in the @code{run} |
| 1909 | command, only the input @emph{for your program} is affected. The input |
| 1910 | for @value{GDBN} still comes from your terminal. |
| 1911 | |
| 1912 | @node Attach |
| 1913 | @section Debugging an already-running process |
| 1914 | @kindex attach |
| 1915 | @cindex attach |
| 1916 | |
| 1917 | @table @code |
| 1918 | @item attach @var{process-id} |
| 1919 | This command attaches to a running process---one that was started |
| 1920 | outside @value{GDBN}. (@code{info files} shows your active |
| 1921 | targets.) The command takes as argument a process ID. The usual way to |
| 1922 | find out the process-id of a Unix process is with the @code{ps} utility, |
| 1923 | or with the @samp{jobs -l} shell command. |
| 1924 | |
| 1925 | @code{attach} does not repeat if you press @key{RET} a second time after |
| 1926 | executing the command. |
| 1927 | @end table |
| 1928 | |
| 1929 | To use @code{attach}, your program must be running in an environment |
| 1930 | which supports processes; for example, @code{attach} does not work for |
| 1931 | programs on bare-board targets that lack an operating system. You must |
| 1932 | also have permission to send the process a signal. |
| 1933 | |
| 1934 | When you use @code{attach}, the debugger finds the program running in |
| 1935 | the process first by looking in the current working directory, then (if |
| 1936 | the program is not found) by using the source file search path |
| 1937 | (@pxref{Source Path, ,Specifying source directories}). You can also use |
| 1938 | the @code{file} command to load the program. @xref{Files, ,Commands to |
| 1939 | Specify Files}. |
| 1940 | |
| 1941 | The first thing @value{GDBN} does after arranging to debug the specified |
| 1942 | process is to stop it. You can examine and modify an attached process |
| 1943 | with all the @value{GDBN} commands that are ordinarily available when |
| 1944 | you start processes with @code{run}. You can insert breakpoints; you |
| 1945 | can step and continue; you can modify storage. If you would rather the |
| 1946 | process continue running, you may use the @code{continue} command after |
| 1947 | attaching @value{GDBN} to the process. |
| 1948 | |
| 1949 | @table @code |
| 1950 | @kindex detach |
| 1951 | @item detach |
| 1952 | When you have finished debugging the attached process, you can use the |
| 1953 | @code{detach} command to release it from @value{GDBN} control. Detaching |
| 1954 | the process continues its execution. After the @code{detach} command, |
| 1955 | that process and @value{GDBN} become completely independent once more, and you |
| 1956 | are ready to @code{attach} another process or start one with @code{run}. |
| 1957 | @code{detach} does not repeat if you press @key{RET} again after |
| 1958 | executing the command. |
| 1959 | @end table |
| 1960 | |
| 1961 | If you exit @value{GDBN} or use the @code{run} command while you have an |
| 1962 | attached process, you kill that process. By default, @value{GDBN} asks |
| 1963 | for confirmation if you try to do either of these things; you can |
| 1964 | control whether or not you need to confirm by using the @code{set |
| 1965 | confirm} command (@pxref{Messages/Warnings, ,Optional warnings and |
| 1966 | messages}). |
| 1967 | |
| 1968 | @node Kill Process |
| 1969 | @section Killing the child process |
| 1970 | |
| 1971 | @table @code |
| 1972 | @kindex kill |
| 1973 | @item kill |
| 1974 | Kill the child process in which your program is running under @value{GDBN}. |
| 1975 | @end table |
| 1976 | |
| 1977 | This command is useful if you wish to debug a core dump instead of a |
| 1978 | running process. @value{GDBN} ignores any core dump file while your program |
| 1979 | is running. |
| 1980 | |
| 1981 | On some operating systems, a program cannot be executed outside @value{GDBN} |
| 1982 | while you have breakpoints set on it inside @value{GDBN}. You can use the |
| 1983 | @code{kill} command in this situation to permit running your program |
| 1984 | outside the debugger. |
| 1985 | |
| 1986 | The @code{kill} command is also useful if you wish to recompile and |
| 1987 | relink your program, since on many systems it is impossible to modify an |
| 1988 | executable file while it is running in a process. In this case, when you |
| 1989 | next type @code{run}, @value{GDBN} notices that the file has changed, and |
| 1990 | reads the symbol table again (while trying to preserve your current |
| 1991 | breakpoint settings). |
| 1992 | |
| 1993 | @node Threads |
| 1994 | @section Debugging programs with multiple threads |
| 1995 | |
| 1996 | @cindex threads of execution |
| 1997 | @cindex multiple threads |
| 1998 | @cindex switching threads |
| 1999 | In some operating systems, such as HP-UX and Solaris, a single program |
| 2000 | may have more than one @dfn{thread} of execution. The precise semantics |
| 2001 | of threads differ from one operating system to another, but in general |
| 2002 | the threads of a single program are akin to multiple processes---except |
| 2003 | that they share one address space (that is, they can all examine and |
| 2004 | modify the same variables). On the other hand, each thread has its own |
| 2005 | registers and execution stack, and perhaps private memory. |
| 2006 | |
| 2007 | @value{GDBN} provides these facilities for debugging multi-thread |
| 2008 | programs: |
| 2009 | |
| 2010 | @itemize @bullet |
| 2011 | @item automatic notification of new threads |
| 2012 | @item @samp{thread @var{threadno}}, a command to switch among threads |
| 2013 | @item @samp{info threads}, a command to inquire about existing threads |
| 2014 | @item @samp{thread apply [@var{threadno}] [@var{all}] @var{args}}, |
| 2015 | a command to apply a command to a list of threads |
| 2016 | @item thread-specific breakpoints |
| 2017 | @end itemize |
| 2018 | |
| 2019 | @quotation |
| 2020 | @emph{Warning:} These facilities are not yet available on every |
| 2021 | @value{GDBN} configuration where the operating system supports threads. |
| 2022 | If your @value{GDBN} does not support threads, these commands have no |
| 2023 | effect. For example, a system without thread support shows no output |
| 2024 | from @samp{info threads}, and always rejects the @code{thread} command, |
| 2025 | like this: |
| 2026 | |
| 2027 | @smallexample |
| 2028 | (@value{GDBP}) info threads |
| 2029 | (@value{GDBP}) thread 1 |
| 2030 | Thread ID 1 not known. Use the "info threads" command to |
| 2031 | see the IDs of currently known threads. |
| 2032 | @end smallexample |
| 2033 | @c FIXME to implementors: how hard would it be to say "sorry, this GDB |
| 2034 | @c doesn't support threads"? |
| 2035 | @end quotation |
| 2036 | |
| 2037 | @cindex focus of debugging |
| 2038 | @cindex current thread |
| 2039 | The @value{GDBN} thread debugging facility allows you to observe all |
| 2040 | threads while your program runs---but whenever @value{GDBN} takes |
| 2041 | control, one thread in particular is always the focus of debugging. |
| 2042 | This thread is called the @dfn{current thread}. Debugging commands show |
| 2043 | program information from the perspective of the current thread. |
| 2044 | |
| 2045 | @cindex @code{New} @var{systag} message |
| 2046 | @cindex thread identifier (system) |
| 2047 | @c FIXME-implementors!! It would be more helpful if the [New...] message |
| 2048 | @c included GDB's numeric thread handle, so you could just go to that |
| 2049 | @c thread without first checking `info threads'. |
| 2050 | Whenever @value{GDBN} detects a new thread in your program, it displays |
| 2051 | the target system's identification for the thread with a message in the |
| 2052 | form @samp{[New @var{systag}]}. @var{systag} is a thread identifier |
| 2053 | whose form varies depending on the particular system. For example, on |
| 2054 | LynxOS, you might see |
| 2055 | |
| 2056 | @example |
| 2057 | [New process 35 thread 27] |
| 2058 | @end example |
| 2059 | |
| 2060 | @noindent |
| 2061 | when @value{GDBN} notices a new thread. In contrast, on an SGI system, |
| 2062 | the @var{systag} is simply something like @samp{process 368}, with no |
| 2063 | further qualifier. |
| 2064 | |
| 2065 | @c FIXME!! (1) Does the [New...] message appear even for the very first |
| 2066 | @c thread of a program, or does it only appear for the |
| 2067 | @c second---i.e.@: when it becomes obvious we have a multithread |
| 2068 | @c program? |
| 2069 | @c (2) *Is* there necessarily a first thread always? Or do some |
| 2070 | @c multithread systems permit starting a program with multiple |
| 2071 | @c threads ab initio? |
| 2072 | |
| 2073 | @cindex thread number |
| 2074 | @cindex thread identifier (GDB) |
| 2075 | For debugging purposes, @value{GDBN} associates its own thread |
| 2076 | number---always a single integer---with each thread in your program. |
| 2077 | |
| 2078 | @table @code |
| 2079 | @kindex info threads |
| 2080 | @item info threads |
| 2081 | Display a summary of all threads currently in your |
| 2082 | program. @value{GDBN} displays for each thread (in this order): |
| 2083 | |
| 2084 | @enumerate |
| 2085 | @item the thread number assigned by @value{GDBN} |
| 2086 | |
| 2087 | @item the target system's thread identifier (@var{systag}) |
| 2088 | |
| 2089 | @item the current stack frame summary for that thread |
| 2090 | @end enumerate |
| 2091 | |
| 2092 | @noindent |
| 2093 | An asterisk @samp{*} to the left of the @value{GDBN} thread number |
| 2094 | indicates the current thread. |
| 2095 | |
| 2096 | For example, |
| 2097 | @end table |
| 2098 | @c end table here to get a little more width for example |
| 2099 | |
| 2100 | @smallexample |
| 2101 | (@value{GDBP}) info threads |
| 2102 | 3 process 35 thread 27 0x34e5 in sigpause () |
| 2103 | 2 process 35 thread 23 0x34e5 in sigpause () |
| 2104 | * 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8) |
| 2105 | at threadtest.c:68 |
| 2106 | @end smallexample |
| 2107 | |
| 2108 | On HP-UX systems: |
| 2109 | |
| 2110 | @cindex thread number |
| 2111 | @cindex thread identifier (GDB) |
| 2112 | For debugging purposes, @value{GDBN} associates its own thread |
| 2113 | number---a small integer assigned in thread-creation order---with each |
| 2114 | thread in your program. |
| 2115 | |
| 2116 | @cindex @code{New} @var{systag} message, on HP-UX |
| 2117 | @cindex thread identifier (system), on HP-UX |
| 2118 | @c FIXME-implementors!! It would be more helpful if the [New...] message |
| 2119 | @c included GDB's numeric thread handle, so you could just go to that |
| 2120 | @c thread without first checking `info threads'. |
| 2121 | Whenever @value{GDBN} detects a new thread in your program, it displays |
| 2122 | both @value{GDBN}'s thread number and the target system's identification for the thread with a message in the |
| 2123 | form @samp{[New @var{systag}]}. @var{systag} is a thread identifier |
| 2124 | whose form varies depending on the particular system. For example, on |
| 2125 | HP-UX, you see |
| 2126 | |
| 2127 | @example |
| 2128 | [New thread 2 (system thread 26594)] |
| 2129 | @end example |
| 2130 | |
| 2131 | @noindent |
| 2132 | when @value{GDBN} notices a new thread. |
| 2133 | |
| 2134 | @table @code |
| 2135 | @kindex info threads |
| 2136 | @item info threads |
| 2137 | Display a summary of all threads currently in your |
| 2138 | program. @value{GDBN} displays for each thread (in this order): |
| 2139 | |
| 2140 | @enumerate |
| 2141 | @item the thread number assigned by @value{GDBN} |
| 2142 | |
| 2143 | @item the target system's thread identifier (@var{systag}) |
| 2144 | |
| 2145 | @item the current stack frame summary for that thread |
| 2146 | @end enumerate |
| 2147 | |
| 2148 | @noindent |
| 2149 | An asterisk @samp{*} to the left of the @value{GDBN} thread number |
| 2150 | indicates the current thread. |
| 2151 | |
| 2152 | For example, |
| 2153 | @end table |
| 2154 | @c end table here to get a little more width for example |
| 2155 | |
| 2156 | @example |
| 2157 | (@value{GDBP}) info threads |
| 2158 | * 3 system thread 26607 worker (wptr=0x7b09c318 "@@") \@* |
| 2159 | at quicksort.c:137 |
| 2160 | 2 system thread 26606 0x7b0030d8 in __ksleep () \@* |
| 2161 | from /usr/lib/libc.2 |
| 2162 | 1 system thread 27905 0x7b003498 in _brk () \@* |
| 2163 | from /usr/lib/libc.2 |
| 2164 | @end example |
| 2165 | |
| 2166 | @table @code |
| 2167 | @kindex thread @var{threadno} |
| 2168 | @item thread @var{threadno} |
| 2169 | Make thread number @var{threadno} the current thread. The command |
| 2170 | argument @var{threadno} is the internal @value{GDBN} thread number, as |
| 2171 | shown in the first field of the @samp{info threads} display. |
| 2172 | @value{GDBN} responds by displaying the system identifier of the thread |
| 2173 | you selected, and its current stack frame summary: |
| 2174 | |
| 2175 | @smallexample |
| 2176 | @c FIXME!! This example made up; find a @value{GDBN} w/threads and get real one |
| 2177 | (@value{GDBP}) thread 2 |
| 2178 | [Switching to process 35 thread 23] |
| 2179 | 0x34e5 in sigpause () |
| 2180 | @end smallexample |
| 2181 | |
| 2182 | @noindent |
| 2183 | As with the @samp{[New @dots{}]} message, the form of the text after |
| 2184 | @samp{Switching to} depends on your system's conventions for identifying |
| 2185 | threads. |
| 2186 | |
| 2187 | @kindex thread apply |
| 2188 | @item thread apply [@var{threadno}] [@var{all}] @var{args} |
| 2189 | The @code{thread apply} command allows you to apply a command to one or |
| 2190 | more threads. Specify the numbers of the threads that you want affected |
| 2191 | with the command argument @var{threadno}. @var{threadno} is the internal |
| 2192 | @value{GDBN} thread number, as shown in the first field of the @samp{info |
| 2193 | threads} display. To apply a command to all threads, use |
| 2194 | @code{thread apply all} @var{args}. |
| 2195 | @end table |
| 2196 | |
| 2197 | @cindex automatic thread selection |
| 2198 | @cindex switching threads automatically |
| 2199 | @cindex threads, automatic switching |
| 2200 | Whenever @value{GDBN} stops your program, due to a breakpoint or a |
| 2201 | signal, it automatically selects the thread where that breakpoint or |
| 2202 | signal happened. @value{GDBN} alerts you to the context switch with a |
| 2203 | message of the form @samp{[Switching to @var{systag}]} to identify the |
| 2204 | thread. |
| 2205 | |
| 2206 | @xref{Thread Stops,,Stopping and starting multi-thread programs}, for |
| 2207 | more information about how @value{GDBN} behaves when you stop and start |
| 2208 | programs with multiple threads. |
| 2209 | |
| 2210 | @xref{Set Watchpoints,,Setting watchpoints}, for information about |
| 2211 | watchpoints in programs with multiple threads. |
| 2212 | |
| 2213 | @node Processes |
| 2214 | @section Debugging programs with multiple processes |
| 2215 | |
| 2216 | @cindex fork, debugging programs which call |
| 2217 | @cindex multiple processes |
| 2218 | @cindex processes, multiple |
| 2219 | On most systems, @value{GDBN} has no special support for debugging |
| 2220 | programs which create additional processes using the @code{fork} |
| 2221 | function. When a program forks, @value{GDBN} will continue to debug the |
| 2222 | parent process and the child process will run unimpeded. If you have |
| 2223 | set a breakpoint in any code which the child then executes, the child |
| 2224 | will get a @code{SIGTRAP} signal which (unless it catches the signal) |
| 2225 | will cause it to terminate. |
| 2226 | |
| 2227 | However, if you want to debug the child process there is a workaround |
| 2228 | which isn't too painful. Put a call to @code{sleep} in the code which |
| 2229 | the child process executes after the fork. It may be useful to sleep |
| 2230 | only if a certain environment variable is set, or a certain file exists, |
| 2231 | so that the delay need not occur when you don't want to run @value{GDBN} |
| 2232 | on the child. While the child is sleeping, use the @code{ps} program to |
| 2233 | get its process ID. Then tell @value{GDBN} (a new invocation of |
| 2234 | @value{GDBN} if you are also debugging the parent process) to attach to |
| 2235 | the child process (@pxref{Attach}). From that point on you can debug |
| 2236 | the child process just like any other process which you attached to. |
| 2237 | |
| 2238 | On HP-UX (11.x and later only?), @value{GDBN} provides support for |
| 2239 | debugging programs that create additional processes using the |
| 2240 | @code{fork} or @code{vfork} function. |
| 2241 | |
| 2242 | By default, when a program forks, @value{GDBN} will continue to debug |
| 2243 | the parent process and the child process will run unimpeded. |
| 2244 | |
| 2245 | If you want to follow the child process instead of the parent process, |
| 2246 | use the command @w{@code{set follow-fork-mode}}. |
| 2247 | |
| 2248 | @table @code |
| 2249 | @kindex set follow-fork-mode |
| 2250 | @item set follow-fork-mode @var{mode} |
| 2251 | Set the debugger response to a program call of @code{fork} or |
| 2252 | @code{vfork}. A call to @code{fork} or @code{vfork} creates a new |
| 2253 | process. The @var{mode} can be: |
| 2254 | |
| 2255 | @table @code |
| 2256 | @item parent |
| 2257 | The original process is debugged after a fork. The child process runs |
| 2258 | unimpeded. This is the default. |
| 2259 | |
| 2260 | @item child |
| 2261 | The new process is debugged after a fork. The parent process runs |
| 2262 | unimpeded. |
| 2263 | |
| 2264 | @item ask |
| 2265 | The debugger will ask for one of the above choices. |
| 2266 | @end table |
| 2267 | |
| 2268 | @item show follow-fork-mode |
| 2269 | Display the current debugger response to a @code{fork} or @code{vfork} call. |
| 2270 | @end table |
| 2271 | |
| 2272 | If you ask to debug a child process and a @code{vfork} is followed by an |
| 2273 | @code{exec}, @value{GDBN} executes the new target up to the first |
| 2274 | breakpoint in the new target. If you have a breakpoint set on |
| 2275 | @code{main} in your original program, the breakpoint will also be set on |
| 2276 | the child process's @code{main}. |
| 2277 | |
| 2278 | When a child process is spawned by @code{vfork}, you cannot debug the |
| 2279 | child or parent until an @code{exec} call completes. |
| 2280 | |
| 2281 | If you issue a @code{run} command to @value{GDBN} after an @code{exec} |
| 2282 | call executes, the new target restarts. To restart the parent process, |
| 2283 | use the @code{file} command with the parent executable name as its |
| 2284 | argument. |
| 2285 | |
| 2286 | You can use the @code{catch} command to make @value{GDBN} stop whenever |
| 2287 | a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set |
| 2288 | Catchpoints, ,Setting catchpoints}. |
| 2289 | |
| 2290 | @node Stopping |
| 2291 | @chapter Stopping and Continuing |
| 2292 | |
| 2293 | The principal purposes of using a debugger are so that you can stop your |
| 2294 | program before it terminates; or so that, if your program runs into |
| 2295 | trouble, you can investigate and find out why. |
| 2296 | |
| 2297 | Inside @value{GDBN}, your program may stop for any of several reasons, |
| 2298 | such as a signal, a breakpoint, or reaching a new line after a |
| 2299 | @value{GDBN} command such as @code{step}. You may then examine and |
| 2300 | change variables, set new breakpoints or remove old ones, and then |
| 2301 | continue execution. Usually, the messages shown by @value{GDBN} provide |
| 2302 | ample explanation of the status of your program---but you can also |
| 2303 | explicitly request this information at any time. |
| 2304 | |
| 2305 | @table @code |
| 2306 | @kindex info program |
| 2307 | @item info program |
| 2308 | Display information about the status of your program: whether it is |
| 2309 | running or not, what process it is, and why it stopped. |
| 2310 | @end table |
| 2311 | |
| 2312 | @menu |
| 2313 | * Breakpoints:: Breakpoints, watchpoints, and catchpoints |
| 2314 | * Continuing and Stepping:: Resuming execution |
| 2315 | * Signals:: Signals |
| 2316 | * Thread Stops:: Stopping and starting multi-thread programs |
| 2317 | @end menu |
| 2318 | |
| 2319 | @node Breakpoints |
| 2320 | @section Breakpoints, watchpoints, and catchpoints |
| 2321 | |
| 2322 | @cindex breakpoints |
| 2323 | A @dfn{breakpoint} makes your program stop whenever a certain point in |
| 2324 | the program is reached. For each breakpoint, you can add conditions to |
| 2325 | control in finer detail whether your program stops. You can set |
| 2326 | breakpoints with the @code{break} command and its variants (@pxref{Set |
| 2327 | Breaks, ,Setting breakpoints}), to specify the place where your program |
| 2328 | should stop by line number, function name or exact address in the |
| 2329 | program. |
| 2330 | |
| 2331 | In HP-UX, SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can set |
| 2332 | breakpoints in shared libraries before the executable is run. There is |
| 2333 | a minor limitation on HP-UX systems: you must wait until the executable |
| 2334 | is run in order to set breakpoints in shared library routines that are |
| 2335 | not called directly by the program (for example, routines that are |
| 2336 | arguments in a @code{pthread_create} call). |
| 2337 | |
| 2338 | @cindex watchpoints |
| 2339 | @cindex memory tracing |
| 2340 | @cindex breakpoint on memory address |
| 2341 | @cindex breakpoint on variable modification |
| 2342 | A @dfn{watchpoint} is a special breakpoint that stops your program |
| 2343 | when the value of an expression changes. You must use a different |
| 2344 | command to set watchpoints (@pxref{Set Watchpoints, ,Setting |
| 2345 | watchpoints}), but aside from that, you can manage a watchpoint like |
| 2346 | any other breakpoint: you enable, disable, and delete both breakpoints |
| 2347 | and watchpoints using the same commands. |
| 2348 | |
| 2349 | You can arrange to have values from your program displayed automatically |
| 2350 | whenever @value{GDBN} stops at a breakpoint. @xref{Auto Display,, |
| 2351 | Automatic display}. |
| 2352 | |
| 2353 | @cindex catchpoints |
| 2354 | @cindex breakpoint on events |
| 2355 | A @dfn{catchpoint} is another special breakpoint that stops your program |
| 2356 | when a certain kind of event occurs, such as the throwing of a C@t{++} |
| 2357 | exception or the loading of a library. As with watchpoints, you use a |
| 2358 | different command to set a catchpoint (@pxref{Set Catchpoints, ,Setting |
| 2359 | catchpoints}), but aside from that, you can manage a catchpoint like any |
| 2360 | other breakpoint. (To stop when your program receives a signal, use the |
| 2361 | @code{handle} command; see @ref{Signals, ,Signals}.) |
| 2362 | |
| 2363 | @cindex breakpoint numbers |
| 2364 | @cindex numbers for breakpoints |
| 2365 | @value{GDBN} assigns a number to each breakpoint, watchpoint, or |
| 2366 | catchpoint when you create it; these numbers are successive integers |
| 2367 | starting with one. In many of the commands for controlling various |
| 2368 | features of breakpoints you use the breakpoint number to say which |
| 2369 | breakpoint you want to change. Each breakpoint may be @dfn{enabled} or |
| 2370 | @dfn{disabled}; if disabled, it has no effect on your program until you |
| 2371 | enable it again. |
| 2372 | |
| 2373 | @cindex breakpoint ranges |
| 2374 | @cindex ranges of breakpoints |
| 2375 | Some @value{GDBN} commands accept a range of breakpoints on which to |
| 2376 | operate. A breakpoint range is either a single breakpoint number, like |
| 2377 | @samp{5}, or two such numbers, in increasing order, separated by a |
| 2378 | hyphen, like @samp{5-7}. When a breakpoint range is given to a command, |
| 2379 | all breakpoint in that range are operated on. |
| 2380 | |
| 2381 | @menu |
| 2382 | * Set Breaks:: Setting breakpoints |
| 2383 | * Set Watchpoints:: Setting watchpoints |
| 2384 | * Set Catchpoints:: Setting catchpoints |
| 2385 | * Delete Breaks:: Deleting breakpoints |
| 2386 | * Disabling:: Disabling breakpoints |
| 2387 | * Conditions:: Break conditions |
| 2388 | * Break Commands:: Breakpoint command lists |
| 2389 | * Breakpoint Menus:: Breakpoint menus |
| 2390 | * Error in Breakpoints:: ``Cannot insert breakpoints'' |
| 2391 | @end menu |
| 2392 | |
| 2393 | @node Set Breaks |
| 2394 | @subsection Setting breakpoints |
| 2395 | |
| 2396 | @c FIXME LMB what does GDB do if no code on line of breakpt? |
| 2397 | @c consider in particular declaration with/without initialization. |
| 2398 | @c |
| 2399 | @c FIXME 2 is there stuff on this already? break at fun start, already init? |
| 2400 | |
| 2401 | @kindex break |
| 2402 | @kindex b @r{(@code{break})} |
| 2403 | @vindex $bpnum@r{, convenience variable} |
| 2404 | @cindex latest breakpoint |
| 2405 | Breakpoints are set with the @code{break} command (abbreviated |
| 2406 | @code{b}). The debugger convenience variable @samp{$bpnum} records the |
| 2407 | number of the breakpoint you've set most recently; see @ref{Convenience |
| 2408 | Vars,, Convenience variables}, for a discussion of what you can do with |
| 2409 | convenience variables. |
| 2410 | |
| 2411 | You have several ways to say where the breakpoint should go. |
| 2412 | |
| 2413 | @table @code |
| 2414 | @item break @var{function} |
| 2415 | Set a breakpoint at entry to function @var{function}. |
| 2416 | When using source languages that permit overloading of symbols, such as |
| 2417 | C@t{++}, @var{function} may refer to more than one possible place to break. |
| 2418 | @xref{Breakpoint Menus,,Breakpoint menus}, for a discussion of that situation. |
| 2419 | |
| 2420 | @item break +@var{offset} |
| 2421 | @itemx break -@var{offset} |
| 2422 | Set a breakpoint some number of lines forward or back from the position |
| 2423 | at which execution stopped in the currently selected @dfn{stack frame}. |
| 2424 | (@xref{Frames, ,Frames}, for a description of stack frames.) |
| 2425 | |
| 2426 | @item break @var{linenum} |
| 2427 | Set a breakpoint at line @var{linenum} in the current source file. |
| 2428 | The current source file is the last file whose source text was printed. |
| 2429 | The breakpoint will stop your program just before it executes any of the |
| 2430 | code on that line. |
| 2431 | |
| 2432 | @item break @var{filename}:@var{linenum} |
| 2433 | Set a breakpoint at line @var{linenum} in source file @var{filename}. |
| 2434 | |
| 2435 | @item break @var{filename}:@var{function} |
| 2436 | Set a breakpoint at entry to function @var{function} found in file |
| 2437 | @var{filename}. Specifying a file name as well as a function name is |
| 2438 | superfluous except when multiple files contain similarly named |
| 2439 | functions. |
| 2440 | |
| 2441 | @item break *@var{address} |
| 2442 | Set a breakpoint at address @var{address}. You can use this to set |
| 2443 | breakpoints in parts of your program which do not have debugging |
| 2444 | information or source files. |
| 2445 | |
| 2446 | @item break |
| 2447 | When called without any arguments, @code{break} sets a breakpoint at |
| 2448 | the next instruction to be executed in the selected stack frame |
| 2449 | (@pxref{Stack, ,Examining the Stack}). In any selected frame but the |
| 2450 | innermost, this makes your program stop as soon as control |
| 2451 | returns to that frame. This is similar to the effect of a |
| 2452 | @code{finish} command in the frame inside the selected frame---except |
| 2453 | that @code{finish} does not leave an active breakpoint. If you use |
| 2454 | @code{break} without an argument in the innermost frame, @value{GDBN} stops |
| 2455 | the next time it reaches the current location; this may be useful |
| 2456 | inside loops. |
| 2457 | |
| 2458 | @value{GDBN} normally ignores breakpoints when it resumes execution, until at |
| 2459 | least one instruction has been executed. If it did not do this, you |
| 2460 | would be unable to proceed past a breakpoint without first disabling the |
| 2461 | breakpoint. This rule applies whether or not the breakpoint already |
| 2462 | existed when your program stopped. |
| 2463 | |
| 2464 | @item break @dots{} if @var{cond} |
| 2465 | Set a breakpoint with condition @var{cond}; evaluate the expression |
| 2466 | @var{cond} each time the breakpoint is reached, and stop only if the |
| 2467 | value is nonzero---that is, if @var{cond} evaluates as true. |
| 2468 | @samp{@dots{}} stands for one of the possible arguments described |
| 2469 | above (or no argument) specifying where to break. @xref{Conditions, |
| 2470 | ,Break conditions}, for more information on breakpoint conditions. |
| 2471 | |
| 2472 | @kindex tbreak |
| 2473 | @item tbreak @var{args} |
| 2474 | Set a breakpoint enabled only for one stop. @var{args} are the |
| 2475 | same as for the @code{break} command, and the breakpoint is set in the same |
| 2476 | way, but the breakpoint is automatically deleted after the first time your |
| 2477 | program stops there. @xref{Disabling, ,Disabling breakpoints}. |
| 2478 | |
| 2479 | @kindex hbreak |
| 2480 | @item hbreak @var{args} |
| 2481 | Set a hardware-assisted breakpoint. @var{args} are the same as for the |
| 2482 | @code{break} command and the breakpoint is set in the same way, but the |
| 2483 | breakpoint requires hardware support and some target hardware may not |
| 2484 | have this support. The main purpose of this is EPROM/ROM code |
| 2485 | debugging, so you can set a breakpoint at an instruction without |
| 2486 | changing the instruction. This can be used with the new trap-generation |
| 2487 | provided by SPARClite DSU and some x86-based targets. These targets |
| 2488 | will generate traps when a program accesses some data or instruction |
| 2489 | address that is assigned to the debug registers. However the hardware |
| 2490 | breakpoint registers can take a limited number of breakpoints. For |
| 2491 | example, on the DSU, only two data breakpoints can be set at a time, and |
| 2492 | @value{GDBN} will reject this command if more than two are used. Delete |
| 2493 | or disable unused hardware breakpoints before setting new ones |
| 2494 | (@pxref{Disabling, ,Disabling}). @xref{Conditions, ,Break conditions}. |
| 2495 | |
| 2496 | @kindex thbreak |
| 2497 | @item thbreak @var{args} |
| 2498 | Set a hardware-assisted breakpoint enabled only for one stop. @var{args} |
| 2499 | are the same as for the @code{hbreak} command and the breakpoint is set in |
| 2500 | the same way. However, like the @code{tbreak} command, |
| 2501 | the breakpoint is automatically deleted after the |
| 2502 | first time your program stops there. Also, like the @code{hbreak} |
| 2503 | command, the breakpoint requires hardware support and some target hardware |
| 2504 | may not have this support. @xref{Disabling, ,Disabling breakpoints}. |
| 2505 | See also @ref{Conditions, ,Break conditions}. |
| 2506 | |
| 2507 | @kindex rbreak |
| 2508 | @cindex regular expression |
| 2509 | @item rbreak @var{regex} |
| 2510 | Set breakpoints on all functions matching the regular expression |
| 2511 | @var{regex}. This command sets an unconditional breakpoint on all |
| 2512 | matches, printing a list of all breakpoints it set. Once these |
| 2513 | breakpoints are set, they are treated just like the breakpoints set with |
| 2514 | the @code{break} command. You can delete them, disable them, or make |
| 2515 | them conditional the same way as any other breakpoint. |
| 2516 | |
| 2517 | The syntax of the regular expression is the standard one used with tools |
| 2518 | like @file{grep}. Note that this is different from the syntax used by |
| 2519 | shells, so for instance @code{foo*} matches all functions that include |
| 2520 | an @code{fo} followed by zero or more @code{o}s. There is an implicit |
| 2521 | @code{.*} leading and trailing the regular expression you supply, so to |
| 2522 | match only functions that begin with @code{foo}, use @code{^foo}. |
| 2523 | |
| 2524 | When debugging C@t{++} programs, @code{rbreak} is useful for setting |
| 2525 | breakpoints on overloaded functions that are not members of any special |
| 2526 | classes. |
| 2527 | |
| 2528 | @kindex info breakpoints |
| 2529 | @cindex @code{$_} and @code{info breakpoints} |
| 2530 | @item info breakpoints @r{[}@var{n}@r{]} |
| 2531 | @itemx info break @r{[}@var{n}@r{]} |
| 2532 | @itemx info watchpoints @r{[}@var{n}@r{]} |
| 2533 | Print a table of all breakpoints, watchpoints, and catchpoints set and |
| 2534 | not deleted, with the following columns for each breakpoint: |
| 2535 | |
| 2536 | @table @emph |
| 2537 | @item Breakpoint Numbers |
| 2538 | @item Type |
| 2539 | Breakpoint, watchpoint, or catchpoint. |
| 2540 | @item Disposition |
| 2541 | Whether the breakpoint is marked to be disabled or deleted when hit. |
| 2542 | @item Enabled or Disabled |
| 2543 | Enabled breakpoints are marked with @samp{y}. @samp{n} marks breakpoints |
| 2544 | that are not enabled. |
| 2545 | @item Address |
| 2546 | Where the breakpoint is in your program, as a memory address. |
| 2547 | @item What |
| 2548 | Where the breakpoint is in the source for your program, as a file and |
| 2549 | line number. |
| 2550 | @end table |
| 2551 | |
| 2552 | @noindent |
| 2553 | If a breakpoint is conditional, @code{info break} shows the condition on |
| 2554 | the line following the affected breakpoint; breakpoint commands, if any, |
| 2555 | are listed after that. |
| 2556 | |
| 2557 | @noindent |
| 2558 | @code{info break} with a breakpoint |
| 2559 | number @var{n} as argument lists only that breakpoint. The |
| 2560 | convenience variable @code{$_} and the default examining-address for |
| 2561 | the @code{x} command are set to the address of the last breakpoint |
| 2562 | listed (@pxref{Memory, ,Examining memory}). |
| 2563 | |
| 2564 | @noindent |
| 2565 | @code{info break} displays a count of the number of times the breakpoint |
| 2566 | has been hit. This is especially useful in conjunction with the |
| 2567 | @code{ignore} command. You can ignore a large number of breakpoint |
| 2568 | hits, look at the breakpoint info to see how many times the breakpoint |
| 2569 | was hit, and then run again, ignoring one less than that number. This |
| 2570 | will get you quickly to the last hit of that breakpoint. |
| 2571 | @end table |
| 2572 | |
| 2573 | @value{GDBN} allows you to set any number of breakpoints at the same place in |
| 2574 | your program. There is nothing silly or meaningless about this. When |
| 2575 | the breakpoints are conditional, this is even useful |
| 2576 | (@pxref{Conditions, ,Break conditions}). |
| 2577 | |
| 2578 | @cindex negative breakpoint numbers |
| 2579 | @cindex internal @value{GDBN} breakpoints |
| 2580 | @value{GDBN} itself sometimes sets breakpoints in your program for |
| 2581 | special purposes, such as proper handling of @code{longjmp} (in C |
| 2582 | programs). These internal breakpoints are assigned negative numbers, |
| 2583 | starting with @code{-1}; @samp{info breakpoints} does not display them. |
| 2584 | You can see these breakpoints with the @value{GDBN} maintenance command |
| 2585 | @samp{maint info breakpoints} (@pxref{maint info breakpoints}). |
| 2586 | |
| 2587 | |
| 2588 | @node Set Watchpoints |
| 2589 | @subsection Setting watchpoints |
| 2590 | |
| 2591 | @cindex setting watchpoints |
| 2592 | @cindex software watchpoints |
| 2593 | @cindex hardware watchpoints |
| 2594 | You can use a watchpoint to stop execution whenever the value of an |
| 2595 | expression changes, without having to predict a particular place where |
| 2596 | this may happen. |
| 2597 | |
| 2598 | Depending on your system, watchpoints may be implemented in software or |
| 2599 | hardware. @value{GDBN} does software watchpointing by single-stepping your |
| 2600 | program and testing the variable's value each time, which is hundreds of |
| 2601 | times slower than normal execution. (But this may still be worth it, to |
| 2602 | catch errors where you have no clue what part of your program is the |
| 2603 | culprit.) |
| 2604 | |
| 2605 | On some systems, such as HP-UX, Linux and some other x86-based targets, |
| 2606 | @value{GDBN} includes support for |
| 2607 | hardware watchpoints, which do not slow down the running of your |
| 2608 | program. |
| 2609 | |
| 2610 | @table @code |
| 2611 | @kindex watch |
| 2612 | @item watch @var{expr} |
| 2613 | Set a watchpoint for an expression. @value{GDBN} will break when @var{expr} |
| 2614 | is written into by the program and its value changes. |
| 2615 | |
| 2616 | @kindex rwatch |
| 2617 | @item rwatch @var{expr} |
| 2618 | Set a watchpoint that will break when watch @var{expr} is read by the program. |
| 2619 | |
| 2620 | @kindex awatch |
| 2621 | @item awatch @var{expr} |
| 2622 | Set a watchpoint that will break when @var{expr} is either read or written into |
| 2623 | by the program. |
| 2624 | |
| 2625 | @kindex info watchpoints |
| 2626 | @item info watchpoints |
| 2627 | This command prints a list of watchpoints, breakpoints, and catchpoints; |
| 2628 | it is the same as @code{info break}. |
| 2629 | @end table |
| 2630 | |
| 2631 | @value{GDBN} sets a @dfn{hardware watchpoint} if possible. Hardware |
| 2632 | watchpoints execute very quickly, and the debugger reports a change in |
| 2633 | value at the exact instruction where the change occurs. If @value{GDBN} |
| 2634 | cannot set a hardware watchpoint, it sets a software watchpoint, which |
| 2635 | executes more slowly and reports the change in value at the next |
| 2636 | statement, not the instruction, after the change occurs. |
| 2637 | |
| 2638 | When you issue the @code{watch} command, @value{GDBN} reports |
| 2639 | |
| 2640 | @example |
| 2641 | Hardware watchpoint @var{num}: @var{expr} |
| 2642 | @end example |
| 2643 | |
| 2644 | @noindent |
| 2645 | if it was able to set a hardware watchpoint. |
| 2646 | |
| 2647 | Currently, the @code{awatch} and @code{rwatch} commands can only set |
| 2648 | hardware watchpoints, because accesses to data that don't change the |
| 2649 | value of the watched expression cannot be detected without examining |
| 2650 | every instruction as it is being executed, and @value{GDBN} does not do |
| 2651 | that currently. If @value{GDBN} finds that it is unable to set a |
| 2652 | hardware breakpoint with the @code{awatch} or @code{rwatch} command, it |
| 2653 | will print a message like this: |
| 2654 | |
| 2655 | @smallexample |
| 2656 | Expression cannot be implemented with read/access watchpoint. |
| 2657 | @end smallexample |
| 2658 | |
| 2659 | Sometimes, @value{GDBN} cannot set a hardware watchpoint because the |
| 2660 | data type of the watched expression is wider than what a hardware |
| 2661 | watchpoint on the target machine can handle. For example, some systems |
| 2662 | can only watch regions that are up to 4 bytes wide; on such systems you |
| 2663 | cannot set hardware watchpoints for an expression that yields a |
| 2664 | double-precision floating-point number (which is typically 8 bytes |
| 2665 | wide). As a work-around, it might be possible to break the large region |
| 2666 | into a series of smaller ones and watch them with separate watchpoints. |
| 2667 | |
| 2668 | If you set too many hardware watchpoints, @value{GDBN} might be unable |
| 2669 | to insert all of them when you resume the execution of your program. |
| 2670 | Since the precise number of active watchpoints is unknown until such |
| 2671 | time as the program is about to be resumed, @value{GDBN} might not be |
| 2672 | able to warn you about this when you set the watchpoints, and the |
| 2673 | warning will be printed only when the program is resumed: |
| 2674 | |
| 2675 | @smallexample |
| 2676 | Hardware watchpoint @var{num}: Could not insert watchpoint |
| 2677 | @end smallexample |
| 2678 | |
| 2679 | @noindent |
| 2680 | If this happens, delete or disable some of the watchpoints. |
| 2681 | |
| 2682 | The SPARClite DSU will generate traps when a program accesses some data |
| 2683 | or instruction address that is assigned to the debug registers. For the |
| 2684 | data addresses, DSU facilitates the @code{watch} command. However the |
| 2685 | hardware breakpoint registers can only take two data watchpoints, and |
| 2686 | both watchpoints must be the same kind. For example, you can set two |
| 2687 | watchpoints with @code{watch} commands, two with @code{rwatch} commands, |
| 2688 | @strong{or} two with @code{awatch} commands, but you cannot set one |
| 2689 | watchpoint with one command and the other with a different command. |
| 2690 | @value{GDBN} will reject the command if you try to mix watchpoints. |
| 2691 | Delete or disable unused watchpoint commands before setting new ones. |
| 2692 | |
| 2693 | If you call a function interactively using @code{print} or @code{call}, |
| 2694 | any watchpoints you have set will be inactive until @value{GDBN} reaches another |
| 2695 | kind of breakpoint or the call completes. |
| 2696 | |
| 2697 | @value{GDBN} automatically deletes watchpoints that watch local |
| 2698 | (automatic) variables, or expressions that involve such variables, when |
| 2699 | they go out of scope, that is, when the execution leaves the block in |
| 2700 | which these variables were defined. In particular, when the program |
| 2701 | being debugged terminates, @emph{all} local variables go out of scope, |
| 2702 | and so only watchpoints that watch global variables remain set. If you |
| 2703 | rerun the program, you will need to set all such watchpoints again. One |
| 2704 | way of doing that would be to set a code breakpoint at the entry to the |
| 2705 | @code{main} function and when it breaks, set all the watchpoints. |
| 2706 | |
| 2707 | @quotation |
| 2708 | @cindex watchpoints and threads |
| 2709 | @cindex threads and watchpoints |
| 2710 | @emph{Warning:} In multi-thread programs, watchpoints have only limited |
| 2711 | usefulness. With the current watchpoint implementation, @value{GDBN} |
| 2712 | can only watch the value of an expression @emph{in a single thread}. If |
| 2713 | you are confident that the expression can only change due to the current |
| 2714 | thread's activity (and if you are also confident that no other thread |
| 2715 | can become current), then you can use watchpoints as usual. However, |
| 2716 | @value{GDBN} may not notice when a non-current thread's activity changes |
| 2717 | the expression. |
| 2718 | |
| 2719 | @c FIXME: this is almost identical to the previous paragraph. |
| 2720 | @emph{HP-UX Warning:} In multi-thread programs, software watchpoints |
| 2721 | have only limited usefulness. If @value{GDBN} creates a software |
| 2722 | watchpoint, it can only watch the value of an expression @emph{in a |
| 2723 | single thread}. If you are confident that the expression can only |
| 2724 | change due to the current thread's activity (and if you are also |
| 2725 | confident that no other thread can become current), then you can use |
| 2726 | software watchpoints as usual. However, @value{GDBN} may not notice |
| 2727 | when a non-current thread's activity changes the expression. (Hardware |
| 2728 | watchpoints, in contrast, watch an expression in all threads.) |
| 2729 | @end quotation |
| 2730 | |
| 2731 | @node Set Catchpoints |
| 2732 | @subsection Setting catchpoints |
| 2733 | @cindex catchpoints, setting |
| 2734 | @cindex exception handlers |
| 2735 | @cindex event handling |
| 2736 | |
| 2737 | You can use @dfn{catchpoints} to cause the debugger to stop for certain |
| 2738 | kinds of program events, such as C@t{++} exceptions or the loading of a |
| 2739 | shared library. Use the @code{catch} command to set a catchpoint. |
| 2740 | |
| 2741 | @table @code |
| 2742 | @kindex catch |
| 2743 | @item catch @var{event} |
| 2744 | Stop when @var{event} occurs. @var{event} can be any of the following: |
| 2745 | @table @code |
| 2746 | @item throw |
| 2747 | @kindex catch throw |
| 2748 | The throwing of a C@t{++} exception. |
| 2749 | |
| 2750 | @item catch |
| 2751 | @kindex catch catch |
| 2752 | The catching of a C@t{++} exception. |
| 2753 | |
| 2754 | @item exec |
| 2755 | @kindex catch exec |
| 2756 | A call to @code{exec}. This is currently only available for HP-UX. |
| 2757 | |
| 2758 | @item fork |
| 2759 | @kindex catch fork |
| 2760 | A call to @code{fork}. This is currently only available for HP-UX. |
| 2761 | |
| 2762 | @item vfork |
| 2763 | @kindex catch vfork |
| 2764 | A call to @code{vfork}. This is currently only available for HP-UX. |
| 2765 | |
| 2766 | @item load |
| 2767 | @itemx load @var{libname} |
| 2768 | @kindex catch load |
| 2769 | The dynamic loading of any shared library, or the loading of the library |
| 2770 | @var{libname}. This is currently only available for HP-UX. |
| 2771 | |
| 2772 | @item unload |
| 2773 | @itemx unload @var{libname} |
| 2774 | @kindex catch unload |
| 2775 | The unloading of any dynamically loaded shared library, or the unloading |
| 2776 | of the library @var{libname}. This is currently only available for HP-UX. |
| 2777 | @end table |
| 2778 | |
| 2779 | @item tcatch @var{event} |
| 2780 | Set a catchpoint that is enabled only for one stop. The catchpoint is |
| 2781 | automatically deleted after the first time the event is caught. |
| 2782 | |
| 2783 | @end table |
| 2784 | |
| 2785 | Use the @code{info break} command to list the current catchpoints. |
| 2786 | |
| 2787 | There are currently some limitations to C@t{++} exception handling |
| 2788 | (@code{catch throw} and @code{catch catch}) in @value{GDBN}: |
| 2789 | |
| 2790 | @itemize @bullet |
| 2791 | @item |
| 2792 | If you call a function interactively, @value{GDBN} normally returns |
| 2793 | control to you when the function has finished executing. If the call |
| 2794 | raises an exception, however, the call may bypass the mechanism that |
| 2795 | returns control to you and cause your program either to abort or to |
| 2796 | simply continue running until it hits a breakpoint, catches a signal |
| 2797 | that @value{GDBN} is listening for, or exits. This is the case even if |
| 2798 | you set a catchpoint for the exception; catchpoints on exceptions are |
| 2799 | disabled within interactive calls. |
| 2800 | |
| 2801 | @item |
| 2802 | You cannot raise an exception interactively. |
| 2803 | |
| 2804 | @item |
| 2805 | You cannot install an exception handler interactively. |
| 2806 | @end itemize |
| 2807 | |
| 2808 | @cindex raise exceptions |
| 2809 | Sometimes @code{catch} is not the best way to debug exception handling: |
| 2810 | if you need to know exactly where an exception is raised, it is better to |
| 2811 | stop @emph{before} the exception handler is called, since that way you |
| 2812 | can see the stack before any unwinding takes place. If you set a |
| 2813 | breakpoint in an exception handler instead, it may not be easy to find |
| 2814 | out where the exception was raised. |
| 2815 | |
| 2816 | To stop just before an exception handler is called, you need some |
| 2817 | knowledge of the implementation. In the case of @sc{gnu} C@t{++}, exceptions are |
| 2818 | raised by calling a library function named @code{__raise_exception} |
| 2819 | which has the following ANSI C interface: |
| 2820 | |
| 2821 | @example |
| 2822 | /* @var{addr} is where the exception identifier is stored. |
| 2823 | @var{id} is the exception identifier. */ |
| 2824 | void __raise_exception (void **addr, void *id); |
| 2825 | @end example |
| 2826 | |
| 2827 | @noindent |
| 2828 | To make the debugger catch all exceptions before any stack |
| 2829 | unwinding takes place, set a breakpoint on @code{__raise_exception} |
| 2830 | (@pxref{Breakpoints, ,Breakpoints; watchpoints; and exceptions}). |
| 2831 | |
| 2832 | With a conditional breakpoint (@pxref{Conditions, ,Break conditions}) |
| 2833 | that depends on the value of @var{id}, you can stop your program when |
| 2834 | a specific exception is raised. You can use multiple conditional |
| 2835 | breakpoints to stop your program when any of a number of exceptions are |
| 2836 | raised. |
| 2837 | |
| 2838 | |
| 2839 | @node Delete Breaks |
| 2840 | @subsection Deleting breakpoints |
| 2841 | |
| 2842 | @cindex clearing breakpoints, watchpoints, catchpoints |
| 2843 | @cindex deleting breakpoints, watchpoints, catchpoints |
| 2844 | It is often necessary to eliminate a breakpoint, watchpoint, or |
| 2845 | catchpoint once it has done its job and you no longer want your program |
| 2846 | to stop there. This is called @dfn{deleting} the breakpoint. A |
| 2847 | breakpoint that has been deleted no longer exists; it is forgotten. |
| 2848 | |
| 2849 | With the @code{clear} command you can delete breakpoints according to |
| 2850 | where they are in your program. With the @code{delete} command you can |
| 2851 | delete individual breakpoints, watchpoints, or catchpoints by specifying |
| 2852 | their breakpoint numbers. |
| 2853 | |
| 2854 | It is not necessary to delete a breakpoint to proceed past it. @value{GDBN} |
| 2855 | automatically ignores breakpoints on the first instruction to be executed |
| 2856 | when you continue execution without changing the execution address. |
| 2857 | |
| 2858 | @table @code |
| 2859 | @kindex clear |
| 2860 | @item clear |
| 2861 | Delete any breakpoints at the next instruction to be executed in the |
| 2862 | selected stack frame (@pxref{Selection, ,Selecting a frame}). When |
| 2863 | the innermost frame is selected, this is a good way to delete a |
| 2864 | breakpoint where your program just stopped. |
| 2865 | |
| 2866 | @item clear @var{function} |
| 2867 | @itemx clear @var{filename}:@var{function} |
| 2868 | Delete any breakpoints set at entry to the function @var{function}. |
| 2869 | |
| 2870 | @item clear @var{linenum} |
| 2871 | @itemx clear @var{filename}:@var{linenum} |
| 2872 | Delete any breakpoints set at or within the code of the specified line. |
| 2873 | |
| 2874 | @cindex delete breakpoints |
| 2875 | @kindex delete |
| 2876 | @kindex d @r{(@code{delete})} |
| 2877 | @item delete @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
| 2878 | Delete the breakpoints, watchpoints, or catchpoints of the breakpoint |
| 2879 | ranges specified as arguments. If no argument is specified, delete all |
| 2880 | breakpoints (@value{GDBN} asks confirmation, unless you have @code{set |
| 2881 | confirm off}). You can abbreviate this command as @code{d}. |
| 2882 | @end table |
| 2883 | |
| 2884 | @node Disabling |
| 2885 | @subsection Disabling breakpoints |
| 2886 | |
| 2887 | @kindex disable breakpoints |
| 2888 | @kindex enable breakpoints |
| 2889 | Rather than deleting a breakpoint, watchpoint, or catchpoint, you might |
| 2890 | prefer to @dfn{disable} it. This makes the breakpoint inoperative as if |
| 2891 | it had been deleted, but remembers the information on the breakpoint so |
| 2892 | that you can @dfn{enable} it again later. |
| 2893 | |
| 2894 | You disable and enable breakpoints, watchpoints, and catchpoints with |
| 2895 | the @code{enable} and @code{disable} commands, optionally specifying one |
| 2896 | or more breakpoint numbers as arguments. Use @code{info break} or |
| 2897 | @code{info watch} to print a list of breakpoints, watchpoints, and |
| 2898 | catchpoints if you do not know which numbers to use. |
| 2899 | |
| 2900 | A breakpoint, watchpoint, or catchpoint can have any of four different |
| 2901 | states of enablement: |
| 2902 | |
| 2903 | @itemize @bullet |
| 2904 | @item |
| 2905 | Enabled. The breakpoint stops your program. A breakpoint set |
| 2906 | with the @code{break} command starts out in this state. |
| 2907 | @item |
| 2908 | Disabled. The breakpoint has no effect on your program. |
| 2909 | @item |
| 2910 | Enabled once. The breakpoint stops your program, but then becomes |
| 2911 | disabled. |
| 2912 | @item |
| 2913 | Enabled for deletion. The breakpoint stops your program, but |
| 2914 | immediately after it does so it is deleted permanently. A breakpoint |
| 2915 | set with the @code{tbreak} command starts out in this state. |
| 2916 | @end itemize |
| 2917 | |
| 2918 | You can use the following commands to enable or disable breakpoints, |
| 2919 | watchpoints, and catchpoints: |
| 2920 | |
| 2921 | @table @code |
| 2922 | @kindex disable breakpoints |
| 2923 | @kindex disable |
| 2924 | @kindex dis @r{(@code{disable})} |
| 2925 | @item disable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
| 2926 | Disable the specified breakpoints---or all breakpoints, if none are |
| 2927 | listed. A disabled breakpoint has no effect but is not forgotten. All |
| 2928 | options such as ignore-counts, conditions and commands are remembered in |
| 2929 | case the breakpoint is enabled again later. You may abbreviate |
| 2930 | @code{disable} as @code{dis}. |
| 2931 | |
| 2932 | @kindex enable breakpoints |
| 2933 | @kindex enable |
| 2934 | @item enable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
| 2935 | Enable the specified breakpoints (or all defined breakpoints). They |
| 2936 | become effective once again in stopping your program. |
| 2937 | |
| 2938 | @item enable @r{[}breakpoints@r{]} once @var{range}@dots{} |
| 2939 | Enable the specified breakpoints temporarily. @value{GDBN} disables any |
| 2940 | of these breakpoints immediately after stopping your program. |
| 2941 | |
| 2942 | @item enable @r{[}breakpoints@r{]} delete @var{range}@dots{} |
| 2943 | Enable the specified breakpoints to work once, then die. @value{GDBN} |
| 2944 | deletes any of these breakpoints as soon as your program stops there. |
| 2945 | @end table |
| 2946 | |
| 2947 | @c FIXME: I think the following ``Except for [...] @code{tbreak}'' is |
| 2948 | @c confusing: tbreak is also initially enabled. |
| 2949 | Except for a breakpoint set with @code{tbreak} (@pxref{Set Breaks, |
| 2950 | ,Setting breakpoints}), breakpoints that you set are initially enabled; |
| 2951 | subsequently, they become disabled or enabled only when you use one of |
| 2952 | the commands above. (The command @code{until} can set and delete a |
| 2953 | breakpoint of its own, but it does not change the state of your other |
| 2954 | breakpoints; see @ref{Continuing and Stepping, ,Continuing and |
| 2955 | stepping}.) |
| 2956 | |
| 2957 | @node Conditions |
| 2958 | @subsection Break conditions |
| 2959 | @cindex conditional breakpoints |
| 2960 | @cindex breakpoint conditions |
| 2961 | |
| 2962 | @c FIXME what is scope of break condition expr? Context where wanted? |
| 2963 | @c in particular for a watchpoint? |
| 2964 | The simplest sort of breakpoint breaks every time your program reaches a |
| 2965 | specified place. You can also specify a @dfn{condition} for a |
| 2966 | breakpoint. A condition is just a Boolean expression in your |
| 2967 | programming language (@pxref{Expressions, ,Expressions}). A breakpoint with |
| 2968 | a condition evaluates the expression each time your program reaches it, |
| 2969 | and your program stops only if the condition is @emph{true}. |
| 2970 | |
| 2971 | This is the converse of using assertions for program validation; in that |
| 2972 | situation, you want to stop when the assertion is violated---that is, |
| 2973 | when the condition is false. In C, if you want to test an assertion expressed |
| 2974 | by the condition @var{assert}, you should set the condition |
| 2975 | @samp{! @var{assert}} on the appropriate breakpoint. |
| 2976 | |
| 2977 | Conditions are also accepted for watchpoints; you may not need them, |
| 2978 | since a watchpoint is inspecting the value of an expression anyhow---but |
| 2979 | it might be simpler, say, to just set a watchpoint on a variable name, |
| 2980 | and specify a condition that tests whether the new value is an interesting |
| 2981 | one. |
| 2982 | |
| 2983 | Break conditions can have side effects, and may even call functions in |
| 2984 | your program. This can be useful, for example, to activate functions |
| 2985 | that log program progress, or to use your own print functions to |
| 2986 | format special data structures. The effects are completely predictable |
| 2987 | unless there is another enabled breakpoint at the same address. (In |
| 2988 | that case, @value{GDBN} might see the other breakpoint first and stop your |
| 2989 | program without checking the condition of this one.) Note that |
| 2990 | breakpoint commands are usually more convenient and flexible than break |
| 2991 | conditions for the |
| 2992 | purpose of performing side effects when a breakpoint is reached |
| 2993 | (@pxref{Break Commands, ,Breakpoint command lists}). |
| 2994 | |
| 2995 | Break conditions can be specified when a breakpoint is set, by using |
| 2996 | @samp{if} in the arguments to the @code{break} command. @xref{Set |
| 2997 | Breaks, ,Setting breakpoints}. They can also be changed at any time |
| 2998 | with the @code{condition} command. |
| 2999 | |
| 3000 | You can also use the @code{if} keyword with the @code{watch} command. |
| 3001 | The @code{catch} command does not recognize the @code{if} keyword; |
| 3002 | @code{condition} is the only way to impose a further condition on a |
| 3003 | catchpoint. |
| 3004 | |
| 3005 | @table @code |
| 3006 | @kindex condition |
| 3007 | @item condition @var{bnum} @var{expression} |
| 3008 | Specify @var{expression} as the break condition for breakpoint, |
| 3009 | watchpoint, or catchpoint number @var{bnum}. After you set a condition, |
| 3010 | breakpoint @var{bnum} stops your program only if the value of |
| 3011 | @var{expression} is true (nonzero, in C). When you use |
| 3012 | @code{condition}, @value{GDBN} checks @var{expression} immediately for |
| 3013 | syntactic correctness, and to determine whether symbols in it have |
| 3014 | referents in the context of your breakpoint. If @var{expression} uses |
| 3015 | symbols not referenced in the context of the breakpoint, @value{GDBN} |
| 3016 | prints an error message: |
| 3017 | |
| 3018 | @example |
| 3019 | No symbol "foo" in current context. |
| 3020 | @end example |
| 3021 | |
| 3022 | @noindent |
| 3023 | @value{GDBN} does |
| 3024 | not actually evaluate @var{expression} at the time the @code{condition} |
| 3025 | command (or a command that sets a breakpoint with a condition, like |
| 3026 | @code{break if @dots{}}) is given, however. @xref{Expressions, ,Expressions}. |
| 3027 | |
| 3028 | @item condition @var{bnum} |
| 3029 | Remove the condition from breakpoint number @var{bnum}. It becomes |
| 3030 | an ordinary unconditional breakpoint. |
| 3031 | @end table |
| 3032 | |
| 3033 | @cindex ignore count (of breakpoint) |
| 3034 | A special case of a breakpoint condition is to stop only when the |
| 3035 | breakpoint has been reached a certain number of times. This is so |
| 3036 | useful that there is a special way to do it, using the @dfn{ignore |
| 3037 | count} of the breakpoint. Every breakpoint has an ignore count, which |
| 3038 | is an integer. Most of the time, the ignore count is zero, and |
| 3039 | therefore has no effect. But if your program reaches a breakpoint whose |
| 3040 | ignore count is positive, then instead of stopping, it just decrements |
| 3041 | the ignore count by one and continues. As a result, if the ignore count |
| 3042 | value is @var{n}, the breakpoint does not stop the next @var{n} times |
| 3043 | your program reaches it. |
| 3044 | |
| 3045 | @table @code |
| 3046 | @kindex ignore |
| 3047 | @item ignore @var{bnum} @var{count} |
| 3048 | Set the ignore count of breakpoint number @var{bnum} to @var{count}. |
| 3049 | The next @var{count} times the breakpoint is reached, your program's |
| 3050 | execution does not stop; other than to decrement the ignore count, @value{GDBN} |
| 3051 | takes no action. |
| 3052 | |
| 3053 | To make the breakpoint stop the next time it is reached, specify |
| 3054 | a count of zero. |
| 3055 | |
| 3056 | When you use @code{continue} to resume execution of your program from a |
| 3057 | breakpoint, you can specify an ignore count directly as an argument to |
| 3058 | @code{continue}, rather than using @code{ignore}. @xref{Continuing and |
| 3059 | Stepping,,Continuing and stepping}. |
| 3060 | |
| 3061 | If a breakpoint has a positive ignore count and a condition, the |
| 3062 | condition is not checked. Once the ignore count reaches zero, |
| 3063 | @value{GDBN} resumes checking the condition. |
| 3064 | |
| 3065 | You could achieve the effect of the ignore count with a condition such |
| 3066 | as @w{@samp{$foo-- <= 0}} using a debugger convenience variable that |
| 3067 | is decremented each time. @xref{Convenience Vars, ,Convenience |
| 3068 | variables}. |
| 3069 | @end table |
| 3070 | |
| 3071 | Ignore counts apply to breakpoints, watchpoints, and catchpoints. |
| 3072 | |
| 3073 | |
| 3074 | @node Break Commands |
| 3075 | @subsection Breakpoint command lists |
| 3076 | |
| 3077 | @cindex breakpoint commands |
| 3078 | You can give any breakpoint (or watchpoint or catchpoint) a series of |
| 3079 | commands to execute when your program stops due to that breakpoint. For |
| 3080 | example, you might want to print the values of certain expressions, or |
| 3081 | enable other breakpoints. |
| 3082 | |
| 3083 | @table @code |
| 3084 | @kindex commands |
| 3085 | @kindex end |
| 3086 | @item commands @r{[}@var{bnum}@r{]} |
| 3087 | @itemx @dots{} @var{command-list} @dots{} |
| 3088 | @itemx end |
| 3089 | Specify a list of commands for breakpoint number @var{bnum}. The commands |
| 3090 | themselves appear on the following lines. Type a line containing just |
| 3091 | @code{end} to terminate the commands. |
| 3092 | |
| 3093 | To remove all commands from a breakpoint, type @code{commands} and |
| 3094 | follow it immediately with @code{end}; that is, give no commands. |
| 3095 | |
| 3096 | With no @var{bnum} argument, @code{commands} refers to the last |
| 3097 | breakpoint, watchpoint, or catchpoint set (not to the breakpoint most |
| 3098 | recently encountered). |
| 3099 | @end table |
| 3100 | |
| 3101 | Pressing @key{RET} as a means of repeating the last @value{GDBN} command is |
| 3102 | disabled within a @var{command-list}. |
| 3103 | |
| 3104 | You can use breakpoint commands to start your program up again. Simply |
| 3105 | use the @code{continue} command, or @code{step}, or any other command |
| 3106 | that resumes execution. |
| 3107 | |
| 3108 | Any other commands in the command list, after a command that resumes |
| 3109 | execution, are ignored. This is because any time you resume execution |
| 3110 | (even with a simple @code{next} or @code{step}), you may encounter |
| 3111 | another breakpoint---which could have its own command list, leading to |
| 3112 | ambiguities about which list to execute. |
| 3113 | |
| 3114 | @kindex silent |
| 3115 | If the first command you specify in a command list is @code{silent}, the |
| 3116 | usual message about stopping at a breakpoint is not printed. This may |
| 3117 | be desirable for breakpoints that are to print a specific message and |
| 3118 | then continue. If none of the remaining commands print anything, you |
| 3119 | see no sign that the breakpoint was reached. @code{silent} is |
| 3120 | meaningful only at the beginning of a breakpoint command list. |
| 3121 | |
| 3122 | The commands @code{echo}, @code{output}, and @code{printf} allow you to |
| 3123 | print precisely controlled output, and are often useful in silent |
| 3124 | breakpoints. @xref{Output, ,Commands for controlled output}. |
| 3125 | |
| 3126 | For example, here is how you could use breakpoint commands to print the |
| 3127 | value of @code{x} at entry to @code{foo} whenever @code{x} is positive. |
| 3128 | |
| 3129 | @example |
| 3130 | break foo if x>0 |
| 3131 | commands |
| 3132 | silent |
| 3133 | printf "x is %d\n",x |
| 3134 | cont |
| 3135 | end |
| 3136 | @end example |
| 3137 | |
| 3138 | One application for breakpoint commands is to compensate for one bug so |
| 3139 | you can test for another. Put a breakpoint just after the erroneous line |
| 3140 | of code, give it a condition to detect the case in which something |
| 3141 | erroneous has been done, and give it commands to assign correct values |
| 3142 | to any variables that need them. End with the @code{continue} command |
| 3143 | so that your program does not stop, and start with the @code{silent} |
| 3144 | command so that no output is produced. Here is an example: |
| 3145 | |
| 3146 | @example |
| 3147 | break 403 |
| 3148 | commands |
| 3149 | silent |
| 3150 | set x = y + 4 |
| 3151 | cont |
| 3152 | end |
| 3153 | @end example |
| 3154 | |
| 3155 | @node Breakpoint Menus |
| 3156 | @subsection Breakpoint menus |
| 3157 | @cindex overloading |
| 3158 | @cindex symbol overloading |
| 3159 | |
| 3160 | Some programming languages (notably C@t{++}) permit a single function name |
| 3161 | to be defined several times, for application in different contexts. |
| 3162 | This is called @dfn{overloading}. When a function name is overloaded, |
| 3163 | @samp{break @var{function}} is not enough to tell @value{GDBN} where you want |
| 3164 | a breakpoint. If you realize this is a problem, you can use |
| 3165 | something like @samp{break @var{function}(@var{types})} to specify which |
| 3166 | particular version of the function you want. Otherwise, @value{GDBN} offers |
| 3167 | you a menu of numbered choices for different possible breakpoints, and |
| 3168 | waits for your selection with the prompt @samp{>}. The first two |
| 3169 | options are always @samp{[0] cancel} and @samp{[1] all}. Typing @kbd{1} |
| 3170 | sets a breakpoint at each definition of @var{function}, and typing |
| 3171 | @kbd{0} aborts the @code{break} command without setting any new |
| 3172 | breakpoints. |
| 3173 | |
| 3174 | For example, the following session excerpt shows an attempt to set a |
| 3175 | breakpoint at the overloaded symbol @code{String::after}. |
| 3176 | We choose three particular definitions of that function name: |
| 3177 | |
| 3178 | @c FIXME! This is likely to change to show arg type lists, at least |
| 3179 | @smallexample |
| 3180 | @group |
| 3181 | (@value{GDBP}) b String::after |
| 3182 | [0] cancel |
| 3183 | [1] all |
| 3184 | [2] file:String.cc; line number:867 |
| 3185 | [3] file:String.cc; line number:860 |
| 3186 | [4] file:String.cc; line number:875 |
| 3187 | [5] file:String.cc; line number:853 |
| 3188 | [6] file:String.cc; line number:846 |
| 3189 | [7] file:String.cc; line number:735 |
| 3190 | > 2 4 6 |
| 3191 | Breakpoint 1 at 0xb26c: file String.cc, line 867. |
| 3192 | Breakpoint 2 at 0xb344: file String.cc, line 875. |
| 3193 | Breakpoint 3 at 0xafcc: file String.cc, line 846. |
| 3194 | Multiple breakpoints were set. |
| 3195 | Use the "delete" command to delete unwanted |
| 3196 | breakpoints. |
| 3197 | (@value{GDBP}) |
| 3198 | @end group |
| 3199 | @end smallexample |
| 3200 | |
| 3201 | @c @ifclear BARETARGET |
| 3202 | @node Error in Breakpoints |
| 3203 | @subsection ``Cannot insert breakpoints'' |
| 3204 | @c |
| 3205 | @c FIXME!! 14/6/95 Is there a real example of this? Let's use it. |
| 3206 | @c |
| 3207 | Under some operating systems, breakpoints cannot be used in a program if |
| 3208 | any other process is running that program. In this situation, |
| 3209 | attempting to run or continue a program with a breakpoint causes |
| 3210 | @value{GDBN} to print an error message: |
| 3211 | |
| 3212 | @example |
| 3213 | Cannot insert breakpoints. |
| 3214 | The same program may be running in another process. |
| 3215 | @end example |
| 3216 | |
| 3217 | When this happens, you have three ways to proceed: |
| 3218 | |
| 3219 | @enumerate |
| 3220 | @item |
| 3221 | Remove or disable the breakpoints, then continue. |
| 3222 | |
| 3223 | @item |
| 3224 | Suspend @value{GDBN}, and copy the file containing your program to a new |
| 3225 | name. Resume @value{GDBN} and use the @code{exec-file} command to specify |
| 3226 | that @value{GDBN} should run your program under that name. |
| 3227 | Then start your program again. |
| 3228 | |
| 3229 | @item |
| 3230 | Relink your program so that the text segment is nonsharable, using the |
| 3231 | linker option @samp{-N}. The operating system limitation may not apply |
| 3232 | to nonsharable executables. |
| 3233 | @end enumerate |
| 3234 | @c @end ifclear |
| 3235 | |
| 3236 | A similar message can be printed if you request too many active |
| 3237 | hardware-assisted breakpoints and watchpoints: |
| 3238 | |
| 3239 | @c FIXME: the precise wording of this message may change; the relevant |
| 3240 | @c source change is not committed yet (Sep 3, 1999). |
| 3241 | @smallexample |
| 3242 | Stopped; cannot insert breakpoints. |
| 3243 | You may have requested too many hardware breakpoints and watchpoints. |
| 3244 | @end smallexample |
| 3245 | |
| 3246 | @noindent |
| 3247 | This message is printed when you attempt to resume the program, since |
| 3248 | only then @value{GDBN} knows exactly how many hardware breakpoints and |
| 3249 | watchpoints it needs to insert. |
| 3250 | |
| 3251 | When this message is printed, you need to disable or remove some of the |
| 3252 | hardware-assisted breakpoints and watchpoints, and then continue. |
| 3253 | |
| 3254 | |
| 3255 | @node Continuing and Stepping |
| 3256 | @section Continuing and stepping |
| 3257 | |
| 3258 | @cindex stepping |
| 3259 | @cindex continuing |
| 3260 | @cindex resuming execution |
| 3261 | @dfn{Continuing} means resuming program execution until your program |
| 3262 | completes normally. In contrast, @dfn{stepping} means executing just |
| 3263 | one more ``step'' of your program, where ``step'' may mean either one |
| 3264 | line of source code, or one machine instruction (depending on what |
| 3265 | particular command you use). Either when continuing or when stepping, |
| 3266 | your program may stop even sooner, due to a breakpoint or a signal. (If |
| 3267 | it stops due to a signal, you may want to use @code{handle}, or use |
| 3268 | @samp{signal 0} to resume execution. @xref{Signals, ,Signals}.) |
| 3269 | |
| 3270 | @table @code |
| 3271 | @kindex continue |
| 3272 | @kindex c @r{(@code{continue})} |
| 3273 | @kindex fg @r{(resume foreground execution)} |
| 3274 | @item continue @r{[}@var{ignore-count}@r{]} |
| 3275 | @itemx c @r{[}@var{ignore-count}@r{]} |
| 3276 | @itemx fg @r{[}@var{ignore-count}@r{]} |
| 3277 | Resume program execution, at the address where your program last stopped; |
| 3278 | any breakpoints set at that address are bypassed. The optional argument |
| 3279 | @var{ignore-count} allows you to specify a further number of times to |
| 3280 | ignore a breakpoint at this location; its effect is like that of |
| 3281 | @code{ignore} (@pxref{Conditions, ,Break conditions}). |
| 3282 | |
| 3283 | The argument @var{ignore-count} is meaningful only when your program |
| 3284 | stopped due to a breakpoint. At other times, the argument to |
| 3285 | @code{continue} is ignored. |
| 3286 | |
| 3287 | The synonyms @code{c} and @code{fg} (for @dfn{foreground}, as the |
| 3288 | debugged program is deemed to be the foreground program) are provided |
| 3289 | purely for convenience, and have exactly the same behavior as |
| 3290 | @code{continue}. |
| 3291 | @end table |
| 3292 | |
| 3293 | To resume execution at a different place, you can use @code{return} |
| 3294 | (@pxref{Returning, ,Returning from a function}) to go back to the |
| 3295 | calling function; or @code{jump} (@pxref{Jumping, ,Continuing at a |
| 3296 | different address}) to go to an arbitrary location in your program. |
| 3297 | |
| 3298 | A typical technique for using stepping is to set a breakpoint |
| 3299 | (@pxref{Breakpoints, ,Breakpoints; watchpoints; and catchpoints}) at the |
| 3300 | beginning of the function or the section of your program where a problem |
| 3301 | is believed to lie, run your program until it stops at that breakpoint, |
| 3302 | and then step through the suspect area, examining the variables that are |
| 3303 | interesting, until you see the problem happen. |
| 3304 | |
| 3305 | @table @code |
| 3306 | @kindex step |
| 3307 | @kindex s @r{(@code{step})} |
| 3308 | @item step |
| 3309 | Continue running your program until control reaches a different source |
| 3310 | line, then stop it and return control to @value{GDBN}. This command is |
| 3311 | abbreviated @code{s}. |
| 3312 | |
| 3313 | @quotation |
| 3314 | @c "without debugging information" is imprecise; actually "without line |
| 3315 | @c numbers in the debugging information". (gcc -g1 has debugging info but |
| 3316 | @c not line numbers). But it seems complex to try to make that |
| 3317 | @c distinction here. |
| 3318 | @emph{Warning:} If you use the @code{step} command while control is |
| 3319 | within a function that was compiled without debugging information, |
| 3320 | execution proceeds until control reaches a function that does have |
| 3321 | debugging information. Likewise, it will not step into a function which |
| 3322 | is compiled without debugging information. To step through functions |
| 3323 | without debugging information, use the @code{stepi} command, described |
| 3324 | below. |
| 3325 | @end quotation |
| 3326 | |
| 3327 | The @code{step} command only stops at the first instruction of a source |
| 3328 | line. This prevents the multiple stops that could otherwise occur in |
| 3329 | @code{switch} statements, @code{for} loops, etc. @code{step} continues |
| 3330 | to stop if a function that has debugging information is called within |
| 3331 | the line. In other words, @code{step} @emph{steps inside} any functions |
| 3332 | called within the line. |
| 3333 | |
| 3334 | Also, the @code{step} command only enters a function if there is line |
| 3335 | number information for the function. Otherwise it acts like the |
| 3336 | @code{next} command. This avoids problems when using @code{cc -gl} |
| 3337 | on MIPS machines. Previously, @code{step} entered subroutines if there |
| 3338 | was any debugging information about the routine. |
| 3339 | |
| 3340 | @item step @var{count} |
| 3341 | Continue running as in @code{step}, but do so @var{count} times. If a |
| 3342 | breakpoint is reached, or a signal not related to stepping occurs before |
| 3343 | @var{count} steps, stepping stops right away. |
| 3344 | |
| 3345 | @kindex next |
| 3346 | @kindex n @r{(@code{next})} |
| 3347 | @item next @r{[}@var{count}@r{]} |
| 3348 | Continue to the next source line in the current (innermost) stack frame. |
| 3349 | This is similar to @code{step}, but function calls that appear within |
| 3350 | the line of code are executed without stopping. Execution stops when |
| 3351 | control reaches a different line of code at the original stack level |
| 3352 | that was executing when you gave the @code{next} command. This command |
| 3353 | is abbreviated @code{n}. |
| 3354 | |
| 3355 | An argument @var{count} is a repeat count, as for @code{step}. |
| 3356 | |
| 3357 | |
| 3358 | @c FIX ME!! Do we delete this, or is there a way it fits in with |
| 3359 | @c the following paragraph? --- Vctoria |
| 3360 | @c |
| 3361 | @c @code{next} within a function that lacks debugging information acts like |
| 3362 | @c @code{step}, but any function calls appearing within the code of the |
| 3363 | @c function are executed without stopping. |
| 3364 | |
| 3365 | The @code{next} command only stops at the first instruction of a |
| 3366 | source line. This prevents multiple stops that could otherwise occur in |
| 3367 | @code{switch} statements, @code{for} loops, etc. |
| 3368 | |
| 3369 | @kindex set step-mode |
| 3370 | @item set step-mode |
| 3371 | @cindex functions without line info, and stepping |
| 3372 | @cindex stepping into functions with no line info |
| 3373 | @itemx set step-mode on |
| 3374 | The @code{set step-mode on} command causes the @code{step} command to |
| 3375 | stop at the first instruction of a function which contains no debug line |
| 3376 | information rather than stepping over it. |
| 3377 | |
| 3378 | This is useful in cases where you may be interested in inspecting the |
| 3379 | machine instructions of a function which has no symbolic info and do not |
| 3380 | want @value{GDBN} to automatically skip over this function. |
| 3381 | |
| 3382 | @item set step-mode off |
| 3383 | Causes the @code{step} command to step over any functions which contains no |
| 3384 | debug information. This is the default. |
| 3385 | |
| 3386 | @kindex finish |
| 3387 | @item finish |
| 3388 | Continue running until just after function in the selected stack frame |
| 3389 | returns. Print the returned value (if any). |
| 3390 | |
| 3391 | Contrast this with the @code{return} command (@pxref{Returning, |
| 3392 | ,Returning from a function}). |
| 3393 | |
| 3394 | @kindex until |
| 3395 | @kindex u @r{(@code{until})} |
| 3396 | @item until |
| 3397 | @itemx u |
| 3398 | Continue running until a source line past the current line, in the |
| 3399 | current stack frame, is reached. This command is used to avoid single |
| 3400 | stepping through a loop more than once. It is like the @code{next} |
| 3401 | command, except that when @code{until} encounters a jump, it |
| 3402 | automatically continues execution until the program counter is greater |
| 3403 | than the address of the jump. |
| 3404 | |
| 3405 | This means that when you reach the end of a loop after single stepping |
| 3406 | though it, @code{until} makes your program continue execution until it |
| 3407 | exits the loop. In contrast, a @code{next} command at the end of a loop |
| 3408 | simply steps back to the beginning of the loop, which forces you to step |
| 3409 | through the next iteration. |
| 3410 | |
| 3411 | @code{until} always stops your program if it attempts to exit the current |
| 3412 | stack frame. |
| 3413 | |
| 3414 | @code{until} may produce somewhat counterintuitive results if the order |
| 3415 | of machine code does not match the order of the source lines. For |
| 3416 | example, in the following excerpt from a debugging session, the @code{f} |
| 3417 | (@code{frame}) command shows that execution is stopped at line |
| 3418 | @code{206}; yet when we use @code{until}, we get to line @code{195}: |
| 3419 | |
| 3420 | @example |
| 3421 | (@value{GDBP}) f |
| 3422 | #0 main (argc=4, argv=0xf7fffae8) at m4.c:206 |
| 3423 | 206 expand_input(); |
| 3424 | (@value{GDBP}) until |
| 3425 | 195 for ( ; argc > 0; NEXTARG) @{ |
| 3426 | @end example |
| 3427 | |
| 3428 | This happened because, for execution efficiency, the compiler had |
| 3429 | generated code for the loop closure test at the end, rather than the |
| 3430 | start, of the loop---even though the test in a C @code{for}-loop is |
| 3431 | written before the body of the loop. The @code{until} command appeared |
| 3432 | to step back to the beginning of the loop when it advanced to this |
| 3433 | expression; however, it has not really gone to an earlier |
| 3434 | statement---not in terms of the actual machine code. |
| 3435 | |
| 3436 | @code{until} with no argument works by means of single |
| 3437 | instruction stepping, and hence is slower than @code{until} with an |
| 3438 | argument. |
| 3439 | |
| 3440 | @item until @var{location} |
| 3441 | @itemx u @var{location} |
| 3442 | Continue running your program until either the specified location is |
| 3443 | reached, or the current stack frame returns. @var{location} is any of |
| 3444 | the forms of argument acceptable to @code{break} (@pxref{Set Breaks, |
| 3445 | ,Setting breakpoints}). This form of the command uses breakpoints, |
| 3446 | and hence is quicker than @code{until} without an argument. |
| 3447 | |
| 3448 | @kindex stepi |
| 3449 | @kindex si @r{(@code{stepi})} |
| 3450 | @item stepi |
| 3451 | @itemx stepi @var{arg} |
| 3452 | @itemx si |
| 3453 | Execute one machine instruction, then stop and return to the debugger. |
| 3454 | |
| 3455 | It is often useful to do @samp{display/i $pc} when stepping by machine |
| 3456 | instructions. This makes @value{GDBN} automatically display the next |
| 3457 | instruction to be executed, each time your program stops. @xref{Auto |
| 3458 | Display,, Automatic display}. |
| 3459 | |
| 3460 | An argument is a repeat count, as in @code{step}. |
| 3461 | |
| 3462 | @need 750 |
| 3463 | @kindex nexti |
| 3464 | @kindex ni @r{(@code{nexti})} |
| 3465 | @item nexti |
| 3466 | @itemx nexti @var{arg} |
| 3467 | @itemx ni |
| 3468 | Execute one machine instruction, but if it is a function call, |
| 3469 | proceed until the function returns. |
| 3470 | |
| 3471 | An argument is a repeat count, as in @code{next}. |
| 3472 | @end table |
| 3473 | |
| 3474 | @node Signals |
| 3475 | @section Signals |
| 3476 | @cindex signals |
| 3477 | |
| 3478 | A signal is an asynchronous event that can happen in a program. The |
| 3479 | operating system defines the possible kinds of signals, and gives each |
| 3480 | kind a name and a number. For example, in Unix @code{SIGINT} is the |
| 3481 | signal a program gets when you type an interrupt character (often @kbd{C-c}); |
| 3482 | @code{SIGSEGV} is the signal a program gets from referencing a place in |
| 3483 | memory far away from all the areas in use; @code{SIGALRM} occurs when |
| 3484 | the alarm clock timer goes off (which happens only if your program has |
| 3485 | requested an alarm). |
| 3486 | |
| 3487 | @cindex fatal signals |
| 3488 | Some signals, including @code{SIGALRM}, are a normal part of the |
| 3489 | functioning of your program. Others, such as @code{SIGSEGV}, indicate |
| 3490 | errors; these signals are @dfn{fatal} (they kill your program immediately) if the |
| 3491 | program has not specified in advance some other way to handle the signal. |
| 3492 | @code{SIGINT} does not indicate an error in your program, but it is normally |
| 3493 | fatal so it can carry out the purpose of the interrupt: to kill the program. |
| 3494 | |
| 3495 | @value{GDBN} has the ability to detect any occurrence of a signal in your |
| 3496 | program. You can tell @value{GDBN} in advance what to do for each kind of |
| 3497 | signal. |
| 3498 | |
| 3499 | @cindex handling signals |
| 3500 | Normally, @value{GDBN} is set up to let the non-erroneous signals like |
| 3501 | @code{SIGALRM} be silently passed to your program |
| 3502 | (so as not to interfere with their role in the program's functioning) |
| 3503 | but to stop your program immediately whenever an error signal happens. |
| 3504 | You can change these settings with the @code{handle} command. |
| 3505 | |
| 3506 | @table @code |
| 3507 | @kindex info signals |
| 3508 | @item info signals |
| 3509 | @itemx info handle |
| 3510 | Print a table of all the kinds of signals and how @value{GDBN} has been told to |
| 3511 | handle each one. You can use this to see the signal numbers of all |
| 3512 | the defined types of signals. |
| 3513 | |
| 3514 | @code{info handle} is an alias for @code{info signals}. |
| 3515 | |
| 3516 | @kindex handle |
| 3517 | @item handle @var{signal} @var{keywords}@dots{} |
| 3518 | Change the way @value{GDBN} handles signal @var{signal}. @var{signal} |
| 3519 | can be the number of a signal or its name (with or without the |
| 3520 | @samp{SIG} at the beginning); a list of signal numbers of the form |
| 3521 | @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the |
| 3522 | known signals. The @var{keywords} say what change to make. |
| 3523 | @end table |
| 3524 | |
| 3525 | @c @group |
| 3526 | The keywords allowed by the @code{handle} command can be abbreviated. |
| 3527 | Their full names are: |
| 3528 | |
| 3529 | @table @code |
| 3530 | @item nostop |
| 3531 | @value{GDBN} should not stop your program when this signal happens. It may |
| 3532 | still print a message telling you that the signal has come in. |
| 3533 | |
| 3534 | @item stop |
| 3535 | @value{GDBN} should stop your program when this signal happens. This implies |
| 3536 | the @code{print} keyword as well. |
| 3537 | |
| 3538 | @item print |
| 3539 | @value{GDBN} should print a message when this signal happens. |
| 3540 | |
| 3541 | @item noprint |
| 3542 | @value{GDBN} should not mention the occurrence of the signal at all. This |
| 3543 | implies the @code{nostop} keyword as well. |
| 3544 | |
| 3545 | @item pass |
| 3546 | @itemx noignore |
| 3547 | @value{GDBN} should allow your program to see this signal; your program |
| 3548 | can handle the signal, or else it may terminate if the signal is fatal |
| 3549 | and not handled. @code{pass} and @code{noignore} are synonyms. |
| 3550 | |
| 3551 | @item nopass |
| 3552 | @itemx ignore |
| 3553 | @value{GDBN} should not allow your program to see this signal. |
| 3554 | @code{nopass} and @code{ignore} are synonyms. |
| 3555 | @end table |
| 3556 | @c @end group |
| 3557 | |
| 3558 | When a signal stops your program, the signal is not visible to the |
| 3559 | program until you |
| 3560 | continue. Your program sees the signal then, if @code{pass} is in |
| 3561 | effect for the signal in question @emph{at that time}. In other words, |
| 3562 | after @value{GDBN} reports a signal, you can use the @code{handle} |
| 3563 | command with @code{pass} or @code{nopass} to control whether your |
| 3564 | program sees that signal when you continue. |
| 3565 | |
| 3566 | The default is set to @code{nostop}, @code{noprint}, @code{pass} for |
| 3567 | non-erroneous signals such as @code{SIGALRM}, @code{SIGWINCH} and |
| 3568 | @code{SIGCHLD}, and to @code{stop}, @code{print}, @code{pass} for the |
| 3569 | erroneous signals. |
| 3570 | |
| 3571 | You can also use the @code{signal} command to prevent your program from |
| 3572 | seeing a signal, or cause it to see a signal it normally would not see, |
| 3573 | or to give it any signal at any time. For example, if your program stopped |
| 3574 | due to some sort of memory reference error, you might store correct |
| 3575 | values into the erroneous variables and continue, hoping to see more |
| 3576 | execution; but your program would probably terminate immediately as |
| 3577 | a result of the fatal signal once it saw the signal. To prevent this, |
| 3578 | you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your |
| 3579 | program a signal}. |
| 3580 | |
| 3581 | @node Thread Stops |
| 3582 | @section Stopping and starting multi-thread programs |
| 3583 | |
| 3584 | When your program has multiple threads (@pxref{Threads,, Debugging |
| 3585 | programs with multiple threads}), you can choose whether to set |
| 3586 | breakpoints on all threads, or on a particular thread. |
| 3587 | |
| 3588 | @table @code |
| 3589 | @cindex breakpoints and threads |
| 3590 | @cindex thread breakpoints |
| 3591 | @kindex break @dots{} thread @var{threadno} |
| 3592 | @item break @var{linespec} thread @var{threadno} |
| 3593 | @itemx break @var{linespec} thread @var{threadno} if @dots{} |
| 3594 | @var{linespec} specifies source lines; there are several ways of |
| 3595 | writing them, but the effect is always to specify some source line. |
| 3596 | |
| 3597 | Use the qualifier @samp{thread @var{threadno}} with a breakpoint command |
| 3598 | to specify that you only want @value{GDBN} to stop the program when a |
| 3599 | particular thread reaches this breakpoint. @var{threadno} is one of the |
| 3600 | numeric thread identifiers assigned by @value{GDBN}, shown in the first |
| 3601 | column of the @samp{info threads} display. |
| 3602 | |
| 3603 | If you do not specify @samp{thread @var{threadno}} when you set a |
| 3604 | breakpoint, the breakpoint applies to @emph{all} threads of your |
| 3605 | program. |
| 3606 | |
| 3607 | You can use the @code{thread} qualifier on conditional breakpoints as |
| 3608 | well; in this case, place @samp{thread @var{threadno}} before the |
| 3609 | breakpoint condition, like this: |
| 3610 | |
| 3611 | @smallexample |
| 3612 | (@value{GDBP}) break frik.c:13 thread 28 if bartab > lim |
| 3613 | @end smallexample |
| 3614 | |
| 3615 | @end table |
| 3616 | |
| 3617 | @cindex stopped threads |
| 3618 | @cindex threads, stopped |
| 3619 | Whenever your program stops under @value{GDBN} for any reason, |
| 3620 | @emph{all} threads of execution stop, not just the current thread. This |
| 3621 | allows you to examine the overall state of the program, including |
| 3622 | switching between threads, without worrying that things may change |
| 3623 | underfoot. |
| 3624 | |
| 3625 | @cindex continuing threads |
| 3626 | @cindex threads, continuing |
| 3627 | Conversely, whenever you restart the program, @emph{all} threads start |
| 3628 | executing. @emph{This is true even when single-stepping} with commands |
| 3629 | like @code{step} or @code{next}. |
| 3630 | |
| 3631 | In particular, @value{GDBN} cannot single-step all threads in lockstep. |
| 3632 | Since thread scheduling is up to your debugging target's operating |
| 3633 | system (not controlled by @value{GDBN}), other threads may |
| 3634 | execute more than one statement while the current thread completes a |
| 3635 | single step. Moreover, in general other threads stop in the middle of a |
| 3636 | statement, rather than at a clean statement boundary, when the program |
| 3637 | stops. |
| 3638 | |
| 3639 | You might even find your program stopped in another thread after |
| 3640 | continuing or even single-stepping. This happens whenever some other |
| 3641 | thread runs into a breakpoint, a signal, or an exception before the |
| 3642 | first thread completes whatever you requested. |
| 3643 | |
| 3644 | On some OSes, you can lock the OS scheduler and thus allow only a single |
| 3645 | thread to run. |
| 3646 | |
| 3647 | @table @code |
| 3648 | @item set scheduler-locking @var{mode} |
| 3649 | Set the scheduler locking mode. If it is @code{off}, then there is no |
| 3650 | locking and any thread may run at any time. If @code{on}, then only the |
| 3651 | current thread may run when the inferior is resumed. The @code{step} |
| 3652 | mode optimizes for single-stepping. It stops other threads from |
| 3653 | ``seizing the prompt'' by preempting the current thread while you are |
| 3654 | stepping. Other threads will only rarely (or never) get a chance to run |
| 3655 | when you step. They are more likely to run when you @samp{next} over a |
| 3656 | function call, and they are completely free to run when you use commands |
| 3657 | like @samp{continue}, @samp{until}, or @samp{finish}. However, unless another |
| 3658 | thread hits a breakpoint during its timeslice, they will never steal the |
| 3659 | @value{GDBN} prompt away from the thread that you are debugging. |
| 3660 | |
| 3661 | @item show scheduler-locking |
| 3662 | Display the current scheduler locking mode. |
| 3663 | @end table |
| 3664 | |
| 3665 | |
| 3666 | @node Stack |
| 3667 | @chapter Examining the Stack |
| 3668 | |
| 3669 | When your program has stopped, the first thing you need to know is where it |
| 3670 | stopped and how it got there. |
| 3671 | |
| 3672 | @cindex call stack |
| 3673 | Each time your program performs a function call, information about the call |
| 3674 | is generated. |
| 3675 | That information includes the location of the call in your program, |
| 3676 | the arguments of the call, |
| 3677 | and the local variables of the function being called. |
| 3678 | The information is saved in a block of data called a @dfn{stack frame}. |
| 3679 | The stack frames are allocated in a region of memory called the @dfn{call |
| 3680 | stack}. |
| 3681 | |
| 3682 | When your program stops, the @value{GDBN} commands for examining the |
| 3683 | stack allow you to see all of this information. |
| 3684 | |
| 3685 | @cindex selected frame |
| 3686 | One of the stack frames is @dfn{selected} by @value{GDBN} and many |
| 3687 | @value{GDBN} commands refer implicitly to the selected frame. In |
| 3688 | particular, whenever you ask @value{GDBN} for the value of a variable in |
| 3689 | your program, the value is found in the selected frame. There are |
| 3690 | special @value{GDBN} commands to select whichever frame you are |
| 3691 | interested in. @xref{Selection, ,Selecting a frame}. |
| 3692 | |
| 3693 | When your program stops, @value{GDBN} automatically selects the |
| 3694 | currently executing frame and describes it briefly, similar to the |
| 3695 | @code{frame} command (@pxref{Frame Info, ,Information about a frame}). |
| 3696 | |
| 3697 | @menu |
| 3698 | * Frames:: Stack frames |
| 3699 | * Backtrace:: Backtraces |
| 3700 | * Selection:: Selecting a frame |
| 3701 | * Frame Info:: Information on a frame |
| 3702 | |
| 3703 | @end menu |
| 3704 | |
| 3705 | @node Frames |
| 3706 | @section Stack frames |
| 3707 | |
| 3708 | @cindex frame, definition |
| 3709 | @cindex stack frame |
| 3710 | The call stack is divided up into contiguous pieces called @dfn{stack |
| 3711 | frames}, or @dfn{frames} for short; each frame is the data associated |
| 3712 | with one call to one function. The frame contains the arguments given |
| 3713 | to the function, the function's local variables, and the address at |
| 3714 | which the function is executing. |
| 3715 | |
| 3716 | @cindex initial frame |
| 3717 | @cindex outermost frame |
| 3718 | @cindex innermost frame |
| 3719 | When your program is started, the stack has only one frame, that of the |
| 3720 | function @code{main}. This is called the @dfn{initial} frame or the |
| 3721 | @dfn{outermost} frame. Each time a function is called, a new frame is |
| 3722 | made. Each time a function returns, the frame for that function invocation |
| 3723 | is eliminated. If a function is recursive, there can be many frames for |
| 3724 | the same function. The frame for the function in which execution is |
| 3725 | actually occurring is called the @dfn{innermost} frame. This is the most |
| 3726 | recently created of all the stack frames that still exist. |
| 3727 | |
| 3728 | @cindex frame pointer |
| 3729 | Inside your program, stack frames are identified by their addresses. A |
| 3730 | stack frame consists of many bytes, each of which has its own address; each |
| 3731 | kind of computer has a convention for choosing one byte whose |
| 3732 | address serves as the address of the frame. Usually this address is kept |
| 3733 | in a register called the @dfn{frame pointer register} while execution is |
| 3734 | going on in that frame. |
| 3735 | |
| 3736 | @cindex frame number |
| 3737 | @value{GDBN} assigns numbers to all existing stack frames, starting with |
| 3738 | zero for the innermost frame, one for the frame that called it, |
| 3739 | and so on upward. These numbers do not really exist in your program; |
| 3740 | they are assigned by @value{GDBN} to give you a way of designating stack |
| 3741 | frames in @value{GDBN} commands. |
| 3742 | |
| 3743 | @c The -fomit-frame-pointer below perennially causes hbox overflow |
| 3744 | @c underflow problems. |
| 3745 | @cindex frameless execution |
| 3746 | Some compilers provide a way to compile functions so that they operate |
| 3747 | without stack frames. (For example, the @value{GCC} option |
| 3748 | @example |
| 3749 | @samp{-fomit-frame-pointer} |
| 3750 | @end example |
| 3751 | generates functions without a frame.) |
| 3752 | This is occasionally done with heavily used library functions to save |
| 3753 | the frame setup time. @value{GDBN} has limited facilities for dealing |
| 3754 | with these function invocations. If the innermost function invocation |
| 3755 | has no stack frame, @value{GDBN} nevertheless regards it as though |
| 3756 | it had a separate frame, which is numbered zero as usual, allowing |
| 3757 | correct tracing of the function call chain. However, @value{GDBN} has |
| 3758 | no provision for frameless functions elsewhere in the stack. |
| 3759 | |
| 3760 | @table @code |
| 3761 | @kindex frame@r{, command} |
| 3762 | @cindex current stack frame |
| 3763 | @item frame @var{args} |
| 3764 | The @code{frame} command allows you to move from one stack frame to another, |
| 3765 | and to print the stack frame you select. @var{args} may be either the |
| 3766 | address of the frame or the stack frame number. Without an argument, |
| 3767 | @code{frame} prints the current stack frame. |
| 3768 | |
| 3769 | @kindex select-frame |
| 3770 | @cindex selecting frame silently |
| 3771 | @item select-frame |
| 3772 | The @code{select-frame} command allows you to move from one stack frame |
| 3773 | to another without printing the frame. This is the silent version of |
| 3774 | @code{frame}. |
| 3775 | @end table |
| 3776 | |
| 3777 | @node Backtrace |
| 3778 | @section Backtraces |
| 3779 | |
| 3780 | @cindex backtraces |
| 3781 | @cindex tracebacks |
| 3782 | @cindex stack traces |
| 3783 | A backtrace is a summary of how your program got where it is. It shows one |
| 3784 | line per frame, for many frames, starting with the currently executing |
| 3785 | frame (frame zero), followed by its caller (frame one), and on up the |
| 3786 | stack. |
| 3787 | |
| 3788 | @table @code |
| 3789 | @kindex backtrace |
| 3790 | @kindex bt @r{(@code{backtrace})} |
| 3791 | @item backtrace |
| 3792 | @itemx bt |
| 3793 | Print a backtrace of the entire stack: one line per frame for all |
| 3794 | frames in the stack. |
| 3795 | |
| 3796 | You can stop the backtrace at any time by typing the system interrupt |
| 3797 | character, normally @kbd{C-c}. |
| 3798 | |
| 3799 | @item backtrace @var{n} |
| 3800 | @itemx bt @var{n} |
| 3801 | Similar, but print only the innermost @var{n} frames. |
| 3802 | |
| 3803 | @item backtrace -@var{n} |
| 3804 | @itemx bt -@var{n} |
| 3805 | Similar, but print only the outermost @var{n} frames. |
| 3806 | @end table |
| 3807 | |
| 3808 | @kindex where |
| 3809 | @kindex info stack |
| 3810 | @kindex info s @r{(@code{info stack})} |
| 3811 | The names @code{where} and @code{info stack} (abbreviated @code{info s}) |
| 3812 | are additional aliases for @code{backtrace}. |
| 3813 | |
| 3814 | Each line in the backtrace shows the frame number and the function name. |
| 3815 | The program counter value is also shown---unless you use @code{set |
| 3816 | print address off}. The backtrace also shows the source file name and |
| 3817 | line number, as well as the arguments to the function. The program |
| 3818 | counter value is omitted if it is at the beginning of the code for that |
| 3819 | line number. |
| 3820 | |
| 3821 | Here is an example of a backtrace. It was made with the command |
| 3822 | @samp{bt 3}, so it shows the innermost three frames. |
| 3823 | |
| 3824 | @smallexample |
| 3825 | @group |
| 3826 | #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) |
| 3827 | at builtin.c:993 |
| 3828 | #1 0x6e38 in expand_macro (sym=0x2b600) at macro.c:242 |
| 3829 | #2 0x6840 in expand_token (obs=0x0, t=177664, td=0xf7fffb08) |
| 3830 | at macro.c:71 |
| 3831 | (More stack frames follow...) |
| 3832 | @end group |
| 3833 | @end smallexample |
| 3834 | |
| 3835 | @noindent |
| 3836 | The display for frame zero does not begin with a program counter |
| 3837 | value, indicating that your program has stopped at the beginning of the |
| 3838 | code for line @code{993} of @code{builtin.c}. |
| 3839 | |
| 3840 | @node Selection |
| 3841 | @section Selecting a frame |
| 3842 | |
| 3843 | Most commands for examining the stack and other data in your program work on |
| 3844 | whichever stack frame is selected at the moment. Here are the commands for |
| 3845 | selecting a stack frame; all of them finish by printing a brief description |
| 3846 | of the stack frame just selected. |
| 3847 | |
| 3848 | @table @code |
| 3849 | @kindex frame@r{, selecting} |
| 3850 | @kindex f @r{(@code{frame})} |
| 3851 | @item frame @var{n} |
| 3852 | @itemx f @var{n} |
| 3853 | Select frame number @var{n}. Recall that frame zero is the innermost |
| 3854 | (currently executing) frame, frame one is the frame that called the |
| 3855 | innermost one, and so on. The highest-numbered frame is the one for |
| 3856 | @code{main}. |
| 3857 | |
| 3858 | @item frame @var{addr} |
| 3859 | @itemx f @var{addr} |
| 3860 | Select the frame at address @var{addr}. This is useful mainly if the |
| 3861 | chaining of stack frames has been damaged by a bug, making it |
| 3862 | impossible for @value{GDBN} to assign numbers properly to all frames. In |
| 3863 | addition, this can be useful when your program has multiple stacks and |
| 3864 | switches between them. |
| 3865 | |
| 3866 | On the SPARC architecture, @code{frame} needs two addresses to |
| 3867 | select an arbitrary frame: a frame pointer and a stack pointer. |
| 3868 | |
| 3869 | On the MIPS and Alpha architecture, it needs two addresses: a stack |
| 3870 | pointer and a program counter. |
| 3871 | |
| 3872 | On the 29k architecture, it needs three addresses: a register stack |
| 3873 | pointer, a program counter, and a memory stack pointer. |
| 3874 | @c note to future updaters: this is conditioned on a flag |
| 3875 | @c SETUP_ARBITRARY_FRAME in the tm-*.h files. The above is up to date |
| 3876 | @c as of 27 Jan 1994. |
| 3877 | |
| 3878 | @kindex up |
| 3879 | @item up @var{n} |
| 3880 | Move @var{n} frames up the stack. For positive numbers @var{n}, this |
| 3881 | advances toward the outermost frame, to higher frame numbers, to frames |
| 3882 | that have existed longer. @var{n} defaults to one. |
| 3883 | |
| 3884 | @kindex down |
| 3885 | @kindex do @r{(@code{down})} |
| 3886 | @item down @var{n} |
| 3887 | Move @var{n} frames down the stack. For positive numbers @var{n}, this |
| 3888 | advances toward the innermost frame, to lower frame numbers, to frames |
| 3889 | that were created more recently. @var{n} defaults to one. You may |
| 3890 | abbreviate @code{down} as @code{do}. |
| 3891 | @end table |
| 3892 | |
| 3893 | All of these commands end by printing two lines of output describing the |
| 3894 | frame. The first line shows the frame number, the function name, the |
| 3895 | arguments, and the source file and line number of execution in that |
| 3896 | frame. The second line shows the text of that source line. |
| 3897 | |
| 3898 | @need 1000 |
| 3899 | For example: |
| 3900 | |
| 3901 | @smallexample |
| 3902 | @group |
| 3903 | (@value{GDBP}) up |
| 3904 | #1 0x22f0 in main (argc=1, argv=0xf7fffbf4, env=0xf7fffbfc) |
| 3905 | at env.c:10 |
| 3906 | 10 read_input_file (argv[i]); |
| 3907 | @end group |
| 3908 | @end smallexample |
| 3909 | |
| 3910 | After such a printout, the @code{list} command with no arguments |
| 3911 | prints ten lines centered on the point of execution in the frame. |
| 3912 | @xref{List, ,Printing source lines}. |
| 3913 | |
| 3914 | @table @code |
| 3915 | @kindex down-silently |
| 3916 | @kindex up-silently |
| 3917 | @item up-silently @var{n} |
| 3918 | @itemx down-silently @var{n} |
| 3919 | These two commands are variants of @code{up} and @code{down}, |
| 3920 | respectively; they differ in that they do their work silently, without |
| 3921 | causing display of the new frame. They are intended primarily for use |
| 3922 | in @value{GDBN} command scripts, where the output might be unnecessary and |
| 3923 | distracting. |
| 3924 | @end table |
| 3925 | |
| 3926 | @node Frame Info |
| 3927 | @section Information about a frame |
| 3928 | |
| 3929 | There are several other commands to print information about the selected |
| 3930 | stack frame. |
| 3931 | |
| 3932 | @table @code |
| 3933 | @item frame |
| 3934 | @itemx f |
| 3935 | When used without any argument, this command does not change which |
| 3936 | frame is selected, but prints a brief description of the currently |
| 3937 | selected stack frame. It can be abbreviated @code{f}. With an |
| 3938 | argument, this command is used to select a stack frame. |
| 3939 | @xref{Selection, ,Selecting a frame}. |
| 3940 | |
| 3941 | @kindex info frame |
| 3942 | @kindex info f @r{(@code{info frame})} |
| 3943 | @item info frame |
| 3944 | @itemx info f |
| 3945 | This command prints a verbose description of the selected stack frame, |
| 3946 | including: |
| 3947 | |
| 3948 | @itemize @bullet |
| 3949 | @item |
| 3950 | the address of the frame |
| 3951 | @item |
| 3952 | the address of the next frame down (called by this frame) |
| 3953 | @item |
| 3954 | the address of the next frame up (caller of this frame) |
| 3955 | @item |
| 3956 | the language in which the source code corresponding to this frame is written |
| 3957 | @item |
| 3958 | the address of the frame's arguments |
| 3959 | @item |
| 3960 | the address of the frame's local variables |
| 3961 | @item |
| 3962 | the program counter saved in it (the address of execution in the caller frame) |
| 3963 | @item |
| 3964 | which registers were saved in the frame |
| 3965 | @end itemize |
| 3966 | |
| 3967 | @noindent The verbose description is useful when |
| 3968 | something has gone wrong that has made the stack format fail to fit |
| 3969 | the usual conventions. |
| 3970 | |
| 3971 | @item info frame @var{addr} |
| 3972 | @itemx info f @var{addr} |
| 3973 | Print a verbose description of the frame at address @var{addr}, without |
| 3974 | selecting that frame. The selected frame remains unchanged by this |
| 3975 | command. This requires the same kind of address (more than one for some |
| 3976 | architectures) that you specify in the @code{frame} command. |
| 3977 | @xref{Selection, ,Selecting a frame}. |
| 3978 | |
| 3979 | @kindex info args |
| 3980 | @item info args |
| 3981 | Print the arguments of the selected frame, each on a separate line. |
| 3982 | |
| 3983 | @item info locals |
| 3984 | @kindex info locals |
| 3985 | Print the local variables of the selected frame, each on a separate |
| 3986 | line. These are all variables (declared either static or automatic) |
| 3987 | accessible at the point of execution of the selected frame. |
| 3988 | |
| 3989 | @kindex info catch |
| 3990 | @cindex catch exceptions, list active handlers |
| 3991 | @cindex exception handlers, how to list |
| 3992 | @item info catch |
| 3993 | Print a list of all the exception handlers that are active in the |
| 3994 | current stack frame at the current point of execution. To see other |
| 3995 | exception handlers, visit the associated frame (using the @code{up}, |
| 3996 | @code{down}, or @code{frame} commands); then type @code{info catch}. |
| 3997 | @xref{Set Catchpoints, , Setting catchpoints}. |
| 3998 | |
| 3999 | @end table |
| 4000 | |
| 4001 | |
| 4002 | @node Source |
| 4003 | @chapter Examining Source Files |
| 4004 | |
| 4005 | @value{GDBN} can print parts of your program's source, since the debugging |
| 4006 | information recorded in the program tells @value{GDBN} what source files were |
| 4007 | used to build it. When your program stops, @value{GDBN} spontaneously prints |
| 4008 | the line where it stopped. Likewise, when you select a stack frame |
| 4009 | (@pxref{Selection, ,Selecting a frame}), @value{GDBN} prints the line where |
| 4010 | execution in that frame has stopped. You can print other portions of |
| 4011 | source files by explicit command. |
| 4012 | |
| 4013 | If you use @value{GDBN} through its @sc{gnu} Emacs interface, you may |
| 4014 | prefer to use Emacs facilities to view source; see @ref{Emacs, ,Using |
| 4015 | @value{GDBN} under @sc{gnu} Emacs}. |
| 4016 | |
| 4017 | @menu |
| 4018 | * List:: Printing source lines |
| 4019 | * Search:: Searching source files |
| 4020 | * Source Path:: Specifying source directories |
| 4021 | * Machine Code:: Source and machine code |
| 4022 | @end menu |
| 4023 | |
| 4024 | @node List |
| 4025 | @section Printing source lines |
| 4026 | |
| 4027 | @kindex list |
| 4028 | @kindex l @r{(@code{list})} |
| 4029 | To print lines from a source file, use the @code{list} command |
| 4030 | (abbreviated @code{l}). By default, ten lines are printed. |
| 4031 | There are several ways to specify what part of the file you want to print. |
| 4032 | |
| 4033 | Here are the forms of the @code{list} command most commonly used: |
| 4034 | |
| 4035 | @table @code |
| 4036 | @item list @var{linenum} |
| 4037 | Print lines centered around line number @var{linenum} in the |
| 4038 | current source file. |
| 4039 | |
| 4040 | @item list @var{function} |
| 4041 | Print lines centered around the beginning of function |
| 4042 | @var{function}. |
| 4043 | |
| 4044 | @item list |
| 4045 | Print more lines. If the last lines printed were printed with a |
| 4046 | @code{list} command, this prints lines following the last lines |
| 4047 | printed; however, if the last line printed was a solitary line printed |
| 4048 | as part of displaying a stack frame (@pxref{Stack, ,Examining the |
| 4049 | Stack}), this prints lines centered around that line. |
| 4050 | |
| 4051 | @item list - |
| 4052 | Print lines just before the lines last printed. |
| 4053 | @end table |
| 4054 | |
| 4055 | By default, @value{GDBN} prints ten source lines with any of these forms of |
| 4056 | the @code{list} command. You can change this using @code{set listsize}: |
| 4057 | |
| 4058 | @table @code |
| 4059 | @kindex set listsize |
| 4060 | @item set listsize @var{count} |
| 4061 | Make the @code{list} command display @var{count} source lines (unless |
| 4062 | the @code{list} argument explicitly specifies some other number). |
| 4063 | |
| 4064 | @kindex show listsize |
| 4065 | @item show listsize |
| 4066 | Display the number of lines that @code{list} prints. |
| 4067 | @end table |
| 4068 | |
| 4069 | Repeating a @code{list} command with @key{RET} discards the argument, |
| 4070 | so it is equivalent to typing just @code{list}. This is more useful |
| 4071 | than listing the same lines again. An exception is made for an |
| 4072 | argument of @samp{-}; that argument is preserved in repetition so that |
| 4073 | each repetition moves up in the source file. |
| 4074 | |
| 4075 | @cindex linespec |
| 4076 | In general, the @code{list} command expects you to supply zero, one or two |
| 4077 | @dfn{linespecs}. Linespecs specify source lines; there are several ways |
| 4078 | of writing them, but the effect is always to specify some source line. |
| 4079 | Here is a complete description of the possible arguments for @code{list}: |
| 4080 | |
| 4081 | @table @code |
| 4082 | @item list @var{linespec} |
| 4083 | Print lines centered around the line specified by @var{linespec}. |
| 4084 | |
| 4085 | @item list @var{first},@var{last} |
| 4086 | Print lines from @var{first} to @var{last}. Both arguments are |
| 4087 | linespecs. |
| 4088 | |
| 4089 | @item list ,@var{last} |
| 4090 | Print lines ending with @var{last}. |
| 4091 | |
| 4092 | @item list @var{first}, |
| 4093 | Print lines starting with @var{first}. |
| 4094 | |
| 4095 | @item list + |
| 4096 | Print lines just after the lines last printed. |
| 4097 | |
| 4098 | @item list - |
| 4099 | Print lines just before the lines last printed. |
| 4100 | |
| 4101 | @item list |
| 4102 | As described in the preceding table. |
| 4103 | @end table |
| 4104 | |
| 4105 | Here are the ways of specifying a single source line---all the |
| 4106 | kinds of linespec. |
| 4107 | |
| 4108 | @table @code |
| 4109 | @item @var{number} |
| 4110 | Specifies line @var{number} of the current source file. |
| 4111 | When a @code{list} command has two linespecs, this refers to |
| 4112 | the same source file as the first linespec. |
| 4113 | |
| 4114 | @item +@var{offset} |
| 4115 | Specifies the line @var{offset} lines after the last line printed. |
| 4116 | When used as the second linespec in a @code{list} command that has |
| 4117 | two, this specifies the line @var{offset} lines down from the |
| 4118 | first linespec. |
| 4119 | |
| 4120 | @item -@var{offset} |
| 4121 | Specifies the line @var{offset} lines before the last line printed. |
| 4122 | |
| 4123 | @item @var{filename}:@var{number} |
| 4124 | Specifies line @var{number} in the source file @var{filename}. |
| 4125 | |
| 4126 | @item @var{function} |
| 4127 | Specifies the line that begins the body of the function @var{function}. |
| 4128 | For example: in C, this is the line with the open brace. |
| 4129 | |
| 4130 | @item @var{filename}:@var{function} |
| 4131 | Specifies the line of the open-brace that begins the body of the |
| 4132 | function @var{function} in the file @var{filename}. You only need the |
| 4133 | file name with a function name to avoid ambiguity when there are |
| 4134 | identically named functions in different source files. |
| 4135 | |
| 4136 | @item *@var{address} |
| 4137 | Specifies the line containing the program address @var{address}. |
| 4138 | @var{address} may be any expression. |
| 4139 | @end table |
| 4140 | |
| 4141 | @node Search |
| 4142 | @section Searching source files |
| 4143 | @cindex searching |
| 4144 | @kindex reverse-search |
| 4145 | |
| 4146 | There are two commands for searching through the current source file for a |
| 4147 | regular expression. |
| 4148 | |
| 4149 | @table @code |
| 4150 | @kindex search |
| 4151 | @kindex forward-search |
| 4152 | @item forward-search @var{regexp} |
| 4153 | @itemx search @var{regexp} |
| 4154 | The command @samp{forward-search @var{regexp}} checks each line, |
| 4155 | starting with the one following the last line listed, for a match for |
| 4156 | @var{regexp}. It lists the line that is found. You can use the |
| 4157 | synonym @samp{search @var{regexp}} or abbreviate the command name as |
| 4158 | @code{fo}. |
| 4159 | |
| 4160 | @item reverse-search @var{regexp} |
| 4161 | The command @samp{reverse-search @var{regexp}} checks each line, starting |
| 4162 | with the one before the last line listed and going backward, for a match |
| 4163 | for @var{regexp}. It lists the line that is found. You can abbreviate |
| 4164 | this command as @code{rev}. |
| 4165 | @end table |
| 4166 | |
| 4167 | @node Source Path |
| 4168 | @section Specifying source directories |
| 4169 | |
| 4170 | @cindex source path |
| 4171 | @cindex directories for source files |
| 4172 | Executable programs sometimes do not record the directories of the source |
| 4173 | files from which they were compiled, just the names. Even when they do, |
| 4174 | the directories could be moved between the compilation and your debugging |
| 4175 | session. @value{GDBN} has a list of directories to search for source files; |
| 4176 | this is called the @dfn{source path}. Each time @value{GDBN} wants a source file, |
| 4177 | it tries all the directories in the list, in the order they are present |
| 4178 | in the list, until it finds a file with the desired name. Note that |
| 4179 | the executable search path is @emph{not} used for this purpose. Neither is |
| 4180 | the current working directory, unless it happens to be in the source |
| 4181 | path. |
| 4182 | |
| 4183 | If @value{GDBN} cannot find a source file in the source path, and the |
| 4184 | object program records a directory, @value{GDBN} tries that directory |
| 4185 | too. If the source path is empty, and there is no record of the |
| 4186 | compilation directory, @value{GDBN} looks in the current directory as a |
| 4187 | last resort. |
| 4188 | |
| 4189 | Whenever you reset or rearrange the source path, @value{GDBN} clears out |
| 4190 | any information it has cached about where source files are found and where |
| 4191 | each line is in the file. |
| 4192 | |
| 4193 | @kindex directory |
| 4194 | @kindex dir |
| 4195 | When you start @value{GDBN}, its source path includes only @samp{cdir} |
| 4196 | and @samp{cwd}, in that order. |
| 4197 | To add other directories, use the @code{directory} command. |
| 4198 | |
| 4199 | @table @code |
| 4200 | @item directory @var{dirname} @dots{} |
| 4201 | @item dir @var{dirname} @dots{} |
| 4202 | Add directory @var{dirname} to the front of the source path. Several |
| 4203 | directory names may be given to this command, separated by @samp{:} |
| 4204 | (@samp{;} on MS-DOS and MS-Windows, where @samp{:} usually appears as |
| 4205 | part of absolute file names) or |
| 4206 | whitespace. You may specify a directory that is already in the source |
| 4207 | path; this moves it forward, so @value{GDBN} searches it sooner. |
| 4208 | |
| 4209 | @kindex cdir |
| 4210 | @kindex cwd |
| 4211 | @vindex $cdir@r{, convenience variable} |
| 4212 | @vindex $cwdr@r{, convenience variable} |
| 4213 | @cindex compilation directory |
| 4214 | @cindex current directory |
| 4215 | @cindex working directory |
| 4216 | @cindex directory, current |
| 4217 | @cindex directory, compilation |
| 4218 | You can use the string @samp{$cdir} to refer to the compilation |
| 4219 | directory (if one is recorded), and @samp{$cwd} to refer to the current |
| 4220 | working directory. @samp{$cwd} is not the same as @samp{.}---the former |
| 4221 | tracks the current working directory as it changes during your @value{GDBN} |
| 4222 | session, while the latter is immediately expanded to the current |
| 4223 | directory at the time you add an entry to the source path. |
| 4224 | |
| 4225 | @item directory |
| 4226 | Reset the source path to empty again. This requires confirmation. |
| 4227 | |
| 4228 | @c RET-repeat for @code{directory} is explicitly disabled, but since |
| 4229 | @c repeating it would be a no-op we do not say that. (thanks to RMS) |
| 4230 | |
| 4231 | @item show directories |
| 4232 | @kindex show directories |
| 4233 | Print the source path: show which directories it contains. |
| 4234 | @end table |
| 4235 | |
| 4236 | If your source path is cluttered with directories that are no longer of |
| 4237 | interest, @value{GDBN} may sometimes cause confusion by finding the wrong |
| 4238 | versions of source. You can correct the situation as follows: |
| 4239 | |
| 4240 | @enumerate |
| 4241 | @item |
| 4242 | Use @code{directory} with no argument to reset the source path to empty. |
| 4243 | |
| 4244 | @item |
| 4245 | Use @code{directory} with suitable arguments to reinstall the |
| 4246 | directories you want in the source path. You can add all the |
| 4247 | directories in one command. |
| 4248 | @end enumerate |
| 4249 | |
| 4250 | @node Machine Code |
| 4251 | @section Source and machine code |
| 4252 | |
| 4253 | You can use the command @code{info line} to map source lines to program |
| 4254 | addresses (and vice versa), and the command @code{disassemble} to display |
| 4255 | a range of addresses as machine instructions. When run under @sc{gnu} Emacs |
| 4256 | mode, the @code{info line} command causes the arrow to point to the |
| 4257 | line specified. Also, @code{info line} prints addresses in symbolic form as |
| 4258 | well as hex. |
| 4259 | |
| 4260 | @table @code |
| 4261 | @kindex info line |
| 4262 | @item info line @var{linespec} |
| 4263 | Print the starting and ending addresses of the compiled code for |
| 4264 | source line @var{linespec}. You can specify source lines in any of |
| 4265 | the ways understood by the @code{list} command (@pxref{List, ,Printing |
| 4266 | source lines}). |
| 4267 | @end table |
| 4268 | |
| 4269 | For example, we can use @code{info line} to discover the location of |
| 4270 | the object code for the first line of function |
| 4271 | @code{m4_changequote}: |
| 4272 | |
| 4273 | @c FIXME: I think this example should also show the addresses in |
| 4274 | @c symbolic form, as they usually would be displayed. |
| 4275 | @smallexample |
| 4276 | (@value{GDBP}) info line m4_changequote |
| 4277 | Line 895 of "builtin.c" starts at pc 0x634c and ends at 0x6350. |
| 4278 | @end smallexample |
| 4279 | |
| 4280 | @noindent |
| 4281 | We can also inquire (using @code{*@var{addr}} as the form for |
| 4282 | @var{linespec}) what source line covers a particular address: |
| 4283 | @smallexample |
| 4284 | (@value{GDBP}) info line *0x63ff |
| 4285 | Line 926 of "builtin.c" starts at pc 0x63e4 and ends at 0x6404. |
| 4286 | @end smallexample |
| 4287 | |
| 4288 | @cindex @code{$_} and @code{info line} |
| 4289 | @kindex x@r{(examine), and} info line |
| 4290 | After @code{info line}, the default address for the @code{x} command |
| 4291 | is changed to the starting address of the line, so that @samp{x/i} is |
| 4292 | sufficient to begin examining the machine code (@pxref{Memory, |
| 4293 | ,Examining memory}). Also, this address is saved as the value of the |
| 4294 | convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience |
| 4295 | variables}). |
| 4296 | |
| 4297 | @table @code |
| 4298 | @kindex disassemble |
| 4299 | @cindex assembly instructions |
| 4300 | @cindex instructions, assembly |
| 4301 | @cindex machine instructions |
| 4302 | @cindex listing machine instructions |
| 4303 | @item disassemble |
| 4304 | This specialized command dumps a range of memory as machine |
| 4305 | instructions. The default memory range is the function surrounding the |
| 4306 | program counter of the selected frame. A single argument to this |
| 4307 | command is a program counter value; @value{GDBN} dumps the function |
| 4308 | surrounding this value. Two arguments specify a range of addresses |
| 4309 | (first inclusive, second exclusive) to dump. |
| 4310 | @end table |
| 4311 | |
| 4312 | The following example shows the disassembly of a range of addresses of |
| 4313 | HP PA-RISC 2.0 code: |
| 4314 | |
| 4315 | @smallexample |
| 4316 | (@value{GDBP}) disas 0x32c4 0x32e4 |
| 4317 | Dump of assembler code from 0x32c4 to 0x32e4: |
| 4318 | 0x32c4 <main+204>: addil 0,dp |
| 4319 | 0x32c8 <main+208>: ldw 0x22c(sr0,r1),r26 |
| 4320 | 0x32cc <main+212>: ldil 0x3000,r31 |
| 4321 | 0x32d0 <main+216>: ble 0x3f8(sr4,r31) |
| 4322 | 0x32d4 <main+220>: ldo 0(r31),rp |
| 4323 | 0x32d8 <main+224>: addil -0x800,dp |
| 4324 | 0x32dc <main+228>: ldo 0x588(r1),r26 |
| 4325 | 0x32e0 <main+232>: ldil 0x3000,r31 |
| 4326 | End of assembler dump. |
| 4327 | @end smallexample |
| 4328 | |
| 4329 | Some architectures have more than one commonly-used set of instruction |
| 4330 | mnemonics or other syntax. |
| 4331 | |
| 4332 | @table @code |
| 4333 | @kindex set disassembly-flavor |
| 4334 | @cindex assembly instructions |
| 4335 | @cindex instructions, assembly |
| 4336 | @cindex machine instructions |
| 4337 | @cindex listing machine instructions |
| 4338 | @cindex Intel disassembly flavor |
| 4339 | @cindex AT&T disassembly flavor |
| 4340 | @item set disassembly-flavor @var{instruction-set} |
| 4341 | Select the instruction set to use when disassembling the |
| 4342 | program via the @code{disassemble} or @code{x/i} commands. |
| 4343 | |
| 4344 | Currently this command is only defined for the Intel x86 family. You |
| 4345 | can set @var{instruction-set} to either @code{intel} or @code{att}. |
| 4346 | The default is @code{att}, the AT&T flavor used by default by Unix |
| 4347 | assemblers for x86-based targets. |
| 4348 | @end table |
| 4349 | |
| 4350 | |
| 4351 | @node Data |
| 4352 | @chapter Examining Data |
| 4353 | |
| 4354 | @cindex printing data |
| 4355 | @cindex examining data |
| 4356 | @kindex print |
| 4357 | @kindex inspect |
| 4358 | @c "inspect" is not quite a synonym if you are using Epoch, which we do not |
| 4359 | @c document because it is nonstandard... Under Epoch it displays in a |
| 4360 | @c different window or something like that. |
| 4361 | The usual way to examine data in your program is with the @code{print} |
| 4362 | command (abbreviated @code{p}), or its synonym @code{inspect}. It |
| 4363 | evaluates and prints the value of an expression of the language your |
| 4364 | program is written in (@pxref{Languages, ,Using @value{GDBN} with |
| 4365 | Different Languages}). |
| 4366 | |
| 4367 | @table @code |
| 4368 | @item print @var{expr} |
| 4369 | @itemx print /@var{f} @var{expr} |
| 4370 | @var{expr} is an expression (in the source language). By default the |
| 4371 | value of @var{expr} is printed in a format appropriate to its data type; |
| 4372 | you can choose a different format by specifying @samp{/@var{f}}, where |
| 4373 | @var{f} is a letter specifying the format; see @ref{Output Formats,,Output |
| 4374 | formats}. |
| 4375 | |
| 4376 | @item print |
| 4377 | @itemx print /@var{f} |
| 4378 | If you omit @var{expr}, @value{GDBN} displays the last value again (from the |
| 4379 | @dfn{value history}; @pxref{Value History, ,Value history}). This allows you to |
| 4380 | conveniently inspect the same value in an alternative format. |
| 4381 | @end table |
| 4382 | |
| 4383 | A more low-level way of examining data is with the @code{x} command. |
| 4384 | It examines data in memory at a specified address and prints it in a |
| 4385 | specified format. @xref{Memory, ,Examining memory}. |
| 4386 | |
| 4387 | If you are interested in information about types, or about how the |
| 4388 | fields of a struct or a class are declared, use the @code{ptype @var{exp}} |
| 4389 | command rather than @code{print}. @xref{Symbols, ,Examining the Symbol |
| 4390 | Table}. |
| 4391 | |
| 4392 | @menu |
| 4393 | * Expressions:: Expressions |
| 4394 | * Variables:: Program variables |
| 4395 | * Arrays:: Artificial arrays |
| 4396 | * Output Formats:: Output formats |
| 4397 | * Memory:: Examining memory |
| 4398 | * Auto Display:: Automatic display |
| 4399 | * Print Settings:: Print settings |
| 4400 | * Value History:: Value history |
| 4401 | * Convenience Vars:: Convenience variables |
| 4402 | * Registers:: Registers |
| 4403 | * Floating Point Hardware:: Floating point hardware |
| 4404 | * Memory Region Attributes:: Memory region attributes |
| 4405 | @end menu |
| 4406 | |
| 4407 | @node Expressions |
| 4408 | @section Expressions |
| 4409 | |
| 4410 | @cindex expressions |
| 4411 | @code{print} and many other @value{GDBN} commands accept an expression and |
| 4412 | compute its value. Any kind of constant, variable or operator defined |
| 4413 | by the programming language you are using is valid in an expression in |
| 4414 | @value{GDBN}. This includes conditional expressions, function calls, casts |
| 4415 | and string constants. It unfortunately does not include symbols defined |
| 4416 | by preprocessor @code{#define} commands. |
| 4417 | |
| 4418 | @value{GDBN} supports array constants in expressions input by |
| 4419 | the user. The syntax is @{@var{element}, @var{element}@dots{}@}. For example, |
| 4420 | you can use the command @code{print @{1, 2, 3@}} to build up an array in |
| 4421 | memory that is @code{malloc}ed in the target program. |
| 4422 | |
| 4423 | Because C is so widespread, most of the expressions shown in examples in |
| 4424 | this manual are in C. @xref{Languages, , Using @value{GDBN} with Different |
| 4425 | Languages}, for information on how to use expressions in other |
| 4426 | languages. |
| 4427 | |
| 4428 | In this section, we discuss operators that you can use in @value{GDBN} |
| 4429 | expressions regardless of your programming language. |
| 4430 | |
| 4431 | Casts are supported in all languages, not just in C, because it is so |
| 4432 | useful to cast a number into a pointer in order to examine a structure |
| 4433 | at that address in memory. |
| 4434 | @c FIXME: casts supported---Mod2 true? |
| 4435 | |
| 4436 | @value{GDBN} supports these operators, in addition to those common |
| 4437 | to programming languages: |
| 4438 | |
| 4439 | @table @code |
| 4440 | @item @@ |
| 4441 | @samp{@@} is a binary operator for treating parts of memory as arrays. |
| 4442 | @xref{Arrays, ,Artificial arrays}, for more information. |
| 4443 | |
| 4444 | @item :: |
| 4445 | @samp{::} allows you to specify a variable in terms of the file or |
| 4446 | function where it is defined. @xref{Variables, ,Program variables}. |
| 4447 | |
| 4448 | @cindex @{@var{type}@} |
| 4449 | @cindex type casting memory |
| 4450 | @cindex memory, viewing as typed object |
| 4451 | @cindex casts, to view memory |
| 4452 | @item @{@var{type}@} @var{addr} |
| 4453 | Refers to an object of type @var{type} stored at address @var{addr} in |
| 4454 | memory. @var{addr} may be any expression whose value is an integer or |
| 4455 | pointer (but parentheses are required around binary operators, just as in |
| 4456 | a cast). This construct is allowed regardless of what kind of data is |
| 4457 | normally supposed to reside at @var{addr}. |
| 4458 | @end table |
| 4459 | |
| 4460 | @node Variables |
| 4461 | @section Program variables |
| 4462 | |
| 4463 | The most common kind of expression to use is the name of a variable |
| 4464 | in your program. |
| 4465 | |
| 4466 | Variables in expressions are understood in the selected stack frame |
| 4467 | (@pxref{Selection, ,Selecting a frame}); they must be either: |
| 4468 | |
| 4469 | @itemize @bullet |
| 4470 | @item |
| 4471 | global (or file-static) |
| 4472 | @end itemize |
| 4473 | |
| 4474 | @noindent or |
| 4475 | |
| 4476 | @itemize @bullet |
| 4477 | @item |
| 4478 | visible according to the scope rules of the |
| 4479 | programming language from the point of execution in that frame |
| 4480 | @end itemize |
| 4481 | |
| 4482 | @noindent This means that in the function |
| 4483 | |
| 4484 | @example |
| 4485 | foo (a) |
| 4486 | int a; |
| 4487 | @{ |
| 4488 | bar (a); |
| 4489 | @{ |
| 4490 | int b = test (); |
| 4491 | bar (b); |
| 4492 | @} |
| 4493 | @} |
| 4494 | @end example |
| 4495 | |
| 4496 | @noindent |
| 4497 | you can examine and use the variable @code{a} whenever your program is |
| 4498 | executing within the function @code{foo}, but you can only use or |
| 4499 | examine the variable @code{b} while your program is executing inside |
| 4500 | the block where @code{b} is declared. |
| 4501 | |
| 4502 | @cindex variable name conflict |
| 4503 | There is an exception: you can refer to a variable or function whose |
| 4504 | scope is a single source file even if the current execution point is not |
| 4505 | in this file. But it is possible to have more than one such variable or |
| 4506 | function with the same name (in different source files). If that |
| 4507 | happens, referring to that name has unpredictable effects. If you wish, |
| 4508 | you can specify a static variable in a particular function or file, |
| 4509 | using the colon-colon notation: |
| 4510 | |
| 4511 | @cindex colon-colon, context for variables/functions |
| 4512 | @iftex |
| 4513 | @c info cannot cope with a :: index entry, but why deprive hard copy readers? |
| 4514 | @cindex @code{::}, context for variables/functions |
| 4515 | @end iftex |
| 4516 | @example |
| 4517 | @var{file}::@var{variable} |
| 4518 | @var{function}::@var{variable} |
| 4519 | @end example |
| 4520 | |
| 4521 | @noindent |
| 4522 | Here @var{file} or @var{function} is the name of the context for the |
| 4523 | static @var{variable}. In the case of file names, you can use quotes to |
| 4524 | make sure @value{GDBN} parses the file name as a single word---for example, |
| 4525 | to print a global value of @code{x} defined in @file{f2.c}: |
| 4526 | |
| 4527 | @example |
| 4528 | (@value{GDBP}) p 'f2.c'::x |
| 4529 | @end example |
| 4530 | |
| 4531 | @cindex C@t{++} scope resolution |
| 4532 | This use of @samp{::} is very rarely in conflict with the very similar |
| 4533 | use of the same notation in C@t{++}. @value{GDBN} also supports use of the C@t{++} |
| 4534 | scope resolution operator in @value{GDBN} expressions. |
| 4535 | @c FIXME: Um, so what happens in one of those rare cases where it's in |
| 4536 | @c conflict?? --mew |
| 4537 | |
| 4538 | @cindex wrong values |
| 4539 | @cindex variable values, wrong |
| 4540 | @quotation |
| 4541 | @emph{Warning:} Occasionally, a local variable may appear to have the |
| 4542 | wrong value at certain points in a function---just after entry to a new |
| 4543 | scope, and just before exit. |
| 4544 | @end quotation |
| 4545 | You may see this problem when you are stepping by machine instructions. |
| 4546 | This is because, on most machines, it takes more than one instruction to |
| 4547 | set up a stack frame (including local variable definitions); if you are |
| 4548 | stepping by machine instructions, variables may appear to have the wrong |
| 4549 | values until the stack frame is completely built. On exit, it usually |
| 4550 | also takes more than one machine instruction to destroy a stack frame; |
| 4551 | after you begin stepping through that group of instructions, local |
| 4552 | variable definitions may be gone. |
| 4553 | |
| 4554 | This may also happen when the compiler does significant optimizations. |
| 4555 | To be sure of always seeing accurate values, turn off all optimization |
| 4556 | when compiling. |
| 4557 | |
| 4558 | @cindex ``No symbol "foo" in current context'' |
| 4559 | Another possible effect of compiler optimizations is to optimize |
| 4560 | unused variables out of existence, or assign variables to registers (as |
| 4561 | opposed to memory addresses). Depending on the support for such cases |
| 4562 | offered by the debug info format used by the compiler, @value{GDBN} |
| 4563 | might not be able to display values for such local variables. If that |
| 4564 | happens, @value{GDBN} will print a message like this: |
| 4565 | |
| 4566 | @example |
| 4567 | No symbol "foo" in current context. |
| 4568 | @end example |
| 4569 | |
| 4570 | To solve such problems, either recompile without optimizations, or use a |
| 4571 | different debug info format, if the compiler supports several such |
| 4572 | formats. For example, @value{NGCC}, the @sc{gnu} C/C@t{++} compiler usually |
| 4573 | supports the @samp{-gstabs} option. @samp{-gstabs} produces debug info |
| 4574 | in a format that is superior to formats such as COFF. You may be able |
| 4575 | to use DWARF2 (@samp{-gdwarf-2}), which is also an effective form for |
| 4576 | debug info. See @ref{Debugging Options,,Options for Debugging Your |
| 4577 | Program or @sc{gnu} CC, gcc.info, Using @sc{gnu} CC}, for more |
| 4578 | information. |
| 4579 | |
| 4580 | |
| 4581 | @node Arrays |
| 4582 | @section Artificial arrays |
| 4583 | |
| 4584 | @cindex artificial array |
| 4585 | @kindex @@@r{, referencing memory as an array} |
| 4586 | It is often useful to print out several successive objects of the |
| 4587 | same type in memory; a section of an array, or an array of |
| 4588 | dynamically determined size for which only a pointer exists in the |
| 4589 | program. |
| 4590 | |
| 4591 | You can do this by referring to a contiguous span of memory as an |
| 4592 | @dfn{artificial array}, using the binary operator @samp{@@}. The left |
| 4593 | operand of @samp{@@} should be the first element of the desired array |
| 4594 | and be an individual object. The right operand should be the desired length |
| 4595 | of the array. The result is an array value whose elements are all of |
| 4596 | the type of the left argument. The first element is actually the left |
| 4597 | argument; the second element comes from bytes of memory immediately |
| 4598 | following those that hold the first element, and so on. Here is an |
| 4599 | example. If a program says |
| 4600 | |
| 4601 | @example |
| 4602 | int *array = (int *) malloc (len * sizeof (int)); |
| 4603 | @end example |
| 4604 | |
| 4605 | @noindent |
| 4606 | you can print the contents of @code{array} with |
| 4607 | |
| 4608 | @example |
| 4609 | p *array@@len |
| 4610 | @end example |
| 4611 | |
| 4612 | The left operand of @samp{@@} must reside in memory. Array values made |
| 4613 | with @samp{@@} in this way behave just like other arrays in terms of |
| 4614 | subscripting, and are coerced to pointers when used in expressions. |
| 4615 | Artificial arrays most often appear in expressions via the value history |
| 4616 | (@pxref{Value History, ,Value history}), after printing one out. |
| 4617 | |
| 4618 | Another way to create an artificial array is to use a cast. |
| 4619 | This re-interprets a value as if it were an array. |
| 4620 | The value need not be in memory: |
| 4621 | @example |
| 4622 | (@value{GDBP}) p/x (short[2])0x12345678 |
| 4623 | $1 = @{0x1234, 0x5678@} |
| 4624 | @end example |
| 4625 | |
| 4626 | As a convenience, if you leave the array length out (as in |
| 4627 | @samp{(@var{type}[])@var{value}}) @value{GDBN} calculates the size to fill |
| 4628 | the value (as @samp{sizeof(@var{value})/sizeof(@var{type})}: |
| 4629 | @example |
| 4630 | (@value{GDBP}) p/x (short[])0x12345678 |
| 4631 | $2 = @{0x1234, 0x5678@} |
| 4632 | @end example |
| 4633 | |
| 4634 | Sometimes the artificial array mechanism is not quite enough; in |
| 4635 | moderately complex data structures, the elements of interest may not |
| 4636 | actually be adjacent---for example, if you are interested in the values |
| 4637 | of pointers in an array. One useful work-around in this situation is |
| 4638 | to use a convenience variable (@pxref{Convenience Vars, ,Convenience |
| 4639 | variables}) as a counter in an expression that prints the first |
| 4640 | interesting value, and then repeat that expression via @key{RET}. For |
| 4641 | instance, suppose you have an array @code{dtab} of pointers to |
| 4642 | structures, and you are interested in the values of a field @code{fv} |
| 4643 | in each structure. Here is an example of what you might type: |
| 4644 | |
| 4645 | @example |
| 4646 | set $i = 0 |
| 4647 | p dtab[$i++]->fv |
| 4648 | @key{RET} |
| 4649 | @key{RET} |
| 4650 | @dots{} |
| 4651 | @end example |
| 4652 | |
| 4653 | @node Output Formats |
| 4654 | @section Output formats |
| 4655 | |
| 4656 | @cindex formatted output |
| 4657 | @cindex output formats |
| 4658 | By default, @value{GDBN} prints a value according to its data type. Sometimes |
| 4659 | this is not what you want. For example, you might want to print a number |
| 4660 | in hex, or a pointer in decimal. Or you might want to view data in memory |
| 4661 | at a certain address as a character string or as an instruction. To do |
| 4662 | these things, specify an @dfn{output format} when you print a value. |
| 4663 | |
| 4664 | The simplest use of output formats is to say how to print a value |
| 4665 | already computed. This is done by starting the arguments of the |
| 4666 | @code{print} command with a slash and a format letter. The format |
| 4667 | letters supported are: |
| 4668 | |
| 4669 | @table @code |
| 4670 | @item x |
| 4671 | Regard the bits of the value as an integer, and print the integer in |
| 4672 | hexadecimal. |
| 4673 | |
| 4674 | @item d |
| 4675 | Print as integer in signed decimal. |
| 4676 | |
| 4677 | @item u |
| 4678 | Print as integer in unsigned decimal. |
| 4679 | |
| 4680 | @item o |
| 4681 | Print as integer in octal. |
| 4682 | |
| 4683 | @item t |
| 4684 | Print as integer in binary. The letter @samp{t} stands for ``two''. |
| 4685 | @footnote{@samp{b} cannot be used because these format letters are also |
| 4686 | used with the @code{x} command, where @samp{b} stands for ``byte''; |
| 4687 | see @ref{Memory,,Examining memory}.} |
| 4688 | |
| 4689 | @item a |
| 4690 | @cindex unknown address, locating |
| 4691 | @cindex locate address |
| 4692 | Print as an address, both absolute in hexadecimal and as an offset from |
| 4693 | the nearest preceding symbol. You can use this format used to discover |
| 4694 | where (in what function) an unknown address is located: |
| 4695 | |
| 4696 | @example |
| 4697 | (@value{GDBP}) p/a 0x54320 |
| 4698 | $3 = 0x54320 <_initialize_vx+396> |
| 4699 | @end example |
| 4700 | |
| 4701 | @noindent |
| 4702 | The command @code{info symbol 0x54320} yields similar results. |
| 4703 | @xref{Symbols, info symbol}. |
| 4704 | |
| 4705 | @item c |
| 4706 | Regard as an integer and print it as a character constant. |
| 4707 | |
| 4708 | @item f |
| 4709 | Regard the bits of the value as a floating point number and print |
| 4710 | using typical floating point syntax. |
| 4711 | @end table |
| 4712 | |
| 4713 | For example, to print the program counter in hex (@pxref{Registers}), type |
| 4714 | |
| 4715 | @example |
| 4716 | p/x $pc |
| 4717 | @end example |
| 4718 | |
| 4719 | @noindent |
| 4720 | Note that no space is required before the slash; this is because command |
| 4721 | names in @value{GDBN} cannot contain a slash. |
| 4722 | |
| 4723 | To reprint the last value in the value history with a different format, |
| 4724 | you can use the @code{print} command with just a format and no |
| 4725 | expression. For example, @samp{p/x} reprints the last value in hex. |
| 4726 | |
| 4727 | @node Memory |
| 4728 | @section Examining memory |
| 4729 | |
| 4730 | You can use the command @code{x} (for ``examine'') to examine memory in |
| 4731 | any of several formats, independently of your program's data types. |
| 4732 | |
| 4733 | @cindex examining memory |
| 4734 | @table @code |
| 4735 | @kindex x @r{(examine memory)} |
| 4736 | @item x/@var{nfu} @var{addr} |
| 4737 | @itemx x @var{addr} |
| 4738 | @itemx x |
| 4739 | Use the @code{x} command to examine memory. |
| 4740 | @end table |
| 4741 | |
| 4742 | @var{n}, @var{f}, and @var{u} are all optional parameters that specify how |
| 4743 | much memory to display and how to format it; @var{addr} is an |
| 4744 | expression giving the address where you want to start displaying memory. |
| 4745 | If you use defaults for @var{nfu}, you need not type the slash @samp{/}. |
| 4746 | Several commands set convenient defaults for @var{addr}. |
| 4747 | |
| 4748 | @table @r |
| 4749 | @item @var{n}, the repeat count |
| 4750 | The repeat count is a decimal integer; the default is 1. It specifies |
| 4751 | how much memory (counting by units @var{u}) to display. |
| 4752 | @c This really is **decimal**; unaffected by 'set radix' as of GDB |
| 4753 | @c 4.1.2. |
| 4754 | |
| 4755 | @item @var{f}, the display format |
| 4756 | The display format is one of the formats used by @code{print}, |
| 4757 | @samp{s} (null-terminated string), or @samp{i} (machine instruction). |
| 4758 | The default is @samp{x} (hexadecimal) initially. |
| 4759 | The default changes each time you use either @code{x} or @code{print}. |
| 4760 | |
| 4761 | @item @var{u}, the unit size |
| 4762 | The unit size is any of |
| 4763 | |
| 4764 | @table @code |
| 4765 | @item b |
| 4766 | Bytes. |
| 4767 | @item h |
| 4768 | Halfwords (two bytes). |
| 4769 | @item w |
| 4770 | Words (four bytes). This is the initial default. |
| 4771 | @item g |
| 4772 | Giant words (eight bytes). |
| 4773 | @end table |
| 4774 | |
| 4775 | Each time you specify a unit size with @code{x}, that size becomes the |
| 4776 | default unit the next time you use @code{x}. (For the @samp{s} and |
| 4777 | @samp{i} formats, the unit size is ignored and is normally not written.) |
| 4778 | |
| 4779 | @item @var{addr}, starting display address |
| 4780 | @var{addr} is the address where you want @value{GDBN} to begin displaying |
| 4781 | memory. The expression need not have a pointer value (though it may); |
| 4782 | it is always interpreted as an integer address of a byte of memory. |
| 4783 | @xref{Expressions, ,Expressions}, for more information on expressions. The default for |
| 4784 | @var{addr} is usually just after the last address examined---but several |
| 4785 | other commands also set the default address: @code{info breakpoints} (to |
| 4786 | the address of the last breakpoint listed), @code{info line} (to the |
| 4787 | starting address of a line), and @code{print} (if you use it to display |
| 4788 | a value from memory). |
| 4789 | @end table |
| 4790 | |
| 4791 | For example, @samp{x/3uh 0x54320} is a request to display three halfwords |
| 4792 | (@code{h}) of memory, formatted as unsigned decimal integers (@samp{u}), |
| 4793 | starting at address @code{0x54320}. @samp{x/4xw $sp} prints the four |
| 4794 | words (@samp{w}) of memory above the stack pointer (here, @samp{$sp}; |
| 4795 | @pxref{Registers, ,Registers}) in hexadecimal (@samp{x}). |
| 4796 | |
| 4797 | Since the letters indicating unit sizes are all distinct from the |
| 4798 | letters specifying output formats, you do not have to remember whether |
| 4799 | unit size or format comes first; either order works. The output |
| 4800 | specifications @samp{4xw} and @samp{4wx} mean exactly the same thing. |
| 4801 | (However, the count @var{n} must come first; @samp{wx4} does not work.) |
| 4802 | |
| 4803 | Even though the unit size @var{u} is ignored for the formats @samp{s} |
| 4804 | and @samp{i}, you might still want to use a count @var{n}; for example, |
| 4805 | @samp{3i} specifies that you want to see three machine instructions, |
| 4806 | including any operands. The command @code{disassemble} gives an |
| 4807 | alternative way of inspecting machine instructions; see @ref{Machine |
| 4808 | Code,,Source and machine code}. |
| 4809 | |
| 4810 | All the defaults for the arguments to @code{x} are designed to make it |
| 4811 | easy to continue scanning memory with minimal specifications each time |
| 4812 | you use @code{x}. For example, after you have inspected three machine |
| 4813 | instructions with @samp{x/3i @var{addr}}, you can inspect the next seven |
| 4814 | with just @samp{x/7}. If you use @key{RET} to repeat the @code{x} command, |
| 4815 | the repeat count @var{n} is used again; the other arguments default as |
| 4816 | for successive uses of @code{x}. |
| 4817 | |
| 4818 | @cindex @code{$_}, @code{$__}, and value history |
| 4819 | The addresses and contents printed by the @code{x} command are not saved |
| 4820 | in the value history because there is often too much of them and they |
| 4821 | would get in the way. Instead, @value{GDBN} makes these values available for |
| 4822 | subsequent use in expressions as values of the convenience variables |
| 4823 | @code{$_} and @code{$__}. After an @code{x} command, the last address |
| 4824 | examined is available for use in expressions in the convenience variable |
| 4825 | @code{$_}. The contents of that address, as examined, are available in |
| 4826 | the convenience variable @code{$__}. |
| 4827 | |
| 4828 | If the @code{x} command has a repeat count, the address and contents saved |
| 4829 | are from the last memory unit printed; this is not the same as the last |
| 4830 | address printed if several units were printed on the last line of output. |
| 4831 | |
| 4832 | @node Auto Display |
| 4833 | @section Automatic display |
| 4834 | @cindex automatic display |
| 4835 | @cindex display of expressions |
| 4836 | |
| 4837 | If you find that you want to print the value of an expression frequently |
| 4838 | (to see how it changes), you might want to add it to the @dfn{automatic |
| 4839 | display list} so that @value{GDBN} prints its value each time your program stops. |
| 4840 | Each expression added to the list is given a number to identify it; |
| 4841 | to remove an expression from the list, you specify that number. |
| 4842 | The automatic display looks like this: |
| 4843 | |
| 4844 | @example |
| 4845 | 2: foo = 38 |
| 4846 | 3: bar[5] = (struct hack *) 0x3804 |
| 4847 | @end example |
| 4848 | |
| 4849 | @noindent |
| 4850 | This display shows item numbers, expressions and their current values. As with |
| 4851 | displays you request manually using @code{x} or @code{print}, you can |
| 4852 | specify the output format you prefer; in fact, @code{display} decides |
| 4853 | whether to use @code{print} or @code{x} depending on how elaborate your |
| 4854 | format specification is---it uses @code{x} if you specify a unit size, |
| 4855 | or one of the two formats (@samp{i} and @samp{s}) that are only |
| 4856 | supported by @code{x}; otherwise it uses @code{print}. |
| 4857 | |
| 4858 | @table @code |
| 4859 | @kindex display |
| 4860 | @item display @var{expr} |
| 4861 | Add the expression @var{expr} to the list of expressions to display |
| 4862 | each time your program stops. @xref{Expressions, ,Expressions}. |
| 4863 | |
| 4864 | @code{display} does not repeat if you press @key{RET} again after using it. |
| 4865 | |
| 4866 | @item display/@var{fmt} @var{expr} |
| 4867 | For @var{fmt} specifying only a display format and not a size or |
| 4868 | count, add the expression @var{expr} to the auto-display list but |
| 4869 | arrange to display it each time in the specified format @var{fmt}. |
| 4870 | @xref{Output Formats,,Output formats}. |
| 4871 | |
| 4872 | @item display/@var{fmt} @var{addr} |
| 4873 | For @var{fmt} @samp{i} or @samp{s}, or including a unit-size or a |
| 4874 | number of units, add the expression @var{addr} as a memory address to |
| 4875 | be examined each time your program stops. Examining means in effect |
| 4876 | doing @samp{x/@var{fmt} @var{addr}}. @xref{Memory, ,Examining memory}. |
| 4877 | @end table |
| 4878 | |
| 4879 | For example, @samp{display/i $pc} can be helpful, to see the machine |
| 4880 | instruction about to be executed each time execution stops (@samp{$pc} |
| 4881 | is a common name for the program counter; @pxref{Registers, ,Registers}). |
| 4882 | |
| 4883 | @table @code |
| 4884 | @kindex delete display |
| 4885 | @kindex undisplay |
| 4886 | @item undisplay @var{dnums}@dots{} |
| 4887 | @itemx delete display @var{dnums}@dots{} |
| 4888 | Remove item numbers @var{dnums} from the list of expressions to display. |
| 4889 | |
| 4890 | @code{undisplay} does not repeat if you press @key{RET} after using it. |
| 4891 | (Otherwise you would just get the error @samp{No display number @dots{}}.) |
| 4892 | |
| 4893 | @kindex disable display |
| 4894 | @item disable display @var{dnums}@dots{} |
| 4895 | Disable the display of item numbers @var{dnums}. A disabled display |
| 4896 | item is not printed automatically, but is not forgotten. It may be |
| 4897 | enabled again later. |
| 4898 | |
| 4899 | @kindex enable display |
| 4900 | @item enable display @var{dnums}@dots{} |
| 4901 | Enable display of item numbers @var{dnums}. It becomes effective once |
| 4902 | again in auto display of its expression, until you specify otherwise. |
| 4903 | |
| 4904 | @item display |
| 4905 | Display the current values of the expressions on the list, just as is |
| 4906 | done when your program stops. |
| 4907 | |
| 4908 | @kindex info display |
| 4909 | @item info display |
| 4910 | Print the list of expressions previously set up to display |
| 4911 | automatically, each one with its item number, but without showing the |
| 4912 | values. This includes disabled expressions, which are marked as such. |
| 4913 | It also includes expressions which would not be displayed right now |
| 4914 | because they refer to automatic variables not currently available. |
| 4915 | @end table |
| 4916 | |
| 4917 | If a display expression refers to local variables, then it does not make |
| 4918 | sense outside the lexical context for which it was set up. Such an |
| 4919 | expression is disabled when execution enters a context where one of its |
| 4920 | variables is not defined. For example, if you give the command |
| 4921 | @code{display last_char} while inside a function with an argument |
| 4922 | @code{last_char}, @value{GDBN} displays this argument while your program |
| 4923 | continues to stop inside that function. When it stops elsewhere---where |
| 4924 | there is no variable @code{last_char}---the display is disabled |
| 4925 | automatically. The next time your program stops where @code{last_char} |
| 4926 | is meaningful, you can enable the display expression once again. |
| 4927 | |
| 4928 | @node Print Settings |
| 4929 | @section Print settings |
| 4930 | |
| 4931 | @cindex format options |
| 4932 | @cindex print settings |
| 4933 | @value{GDBN} provides the following ways to control how arrays, structures, |
| 4934 | and symbols are printed. |
| 4935 | |
| 4936 | @noindent |
| 4937 | These settings are useful for debugging programs in any language: |
| 4938 | |
| 4939 | @table @code |
| 4940 | @kindex set print address |
| 4941 | @item set print address |
| 4942 | @itemx set print address on |
| 4943 | @value{GDBN} prints memory addresses showing the location of stack |
| 4944 | traces, structure values, pointer values, breakpoints, and so forth, |
| 4945 | even when it also displays the contents of those addresses. The default |
| 4946 | is @code{on}. For example, this is what a stack frame display looks like with |
| 4947 | @code{set print address on}: |
| 4948 | |
| 4949 | @smallexample |
| 4950 | @group |
| 4951 | (@value{GDBP}) f |
| 4952 | #0 set_quotes (lq=0x34c78 "<<", rq=0x34c88 ">>") |
| 4953 | at input.c:530 |
| 4954 | 530 if (lquote != def_lquote) |
| 4955 | @end group |
| 4956 | @end smallexample |
| 4957 | |
| 4958 | @item set print address off |
| 4959 | Do not print addresses when displaying their contents. For example, |
| 4960 | this is the same stack frame displayed with @code{set print address off}: |
| 4961 | |
| 4962 | @smallexample |
| 4963 | @group |
| 4964 | (@value{GDBP}) set print addr off |
| 4965 | (@value{GDBP}) f |
| 4966 | #0 set_quotes (lq="<<", rq=">>") at input.c:530 |
| 4967 | 530 if (lquote != def_lquote) |
| 4968 | @end group |
| 4969 | @end smallexample |
| 4970 | |
| 4971 | You can use @samp{set print address off} to eliminate all machine |
| 4972 | dependent displays from the @value{GDBN} interface. For example, with |
| 4973 | @code{print address off}, you should get the same text for backtraces on |
| 4974 | all machines---whether or not they involve pointer arguments. |
| 4975 | |
| 4976 | @kindex show print address |
| 4977 | @item show print address |
| 4978 | Show whether or not addresses are to be printed. |
| 4979 | @end table |
| 4980 | |
| 4981 | When @value{GDBN} prints a symbolic address, it normally prints the |
| 4982 | closest earlier symbol plus an offset. If that symbol does not uniquely |
| 4983 | identify the address (for example, it is a name whose scope is a single |
| 4984 | source file), you may need to clarify. One way to do this is with |
| 4985 | @code{info line}, for example @samp{info line *0x4537}. Alternately, |
| 4986 | you can set @value{GDBN} to print the source file and line number when |
| 4987 | it prints a symbolic address: |
| 4988 | |
| 4989 | @table @code |
| 4990 | @kindex set print symbol-filename |
| 4991 | @item set print symbol-filename on |
| 4992 | Tell @value{GDBN} to print the source file name and line number of a |
| 4993 | symbol in the symbolic form of an address. |
| 4994 | |
| 4995 | @item set print symbol-filename off |
| 4996 | Do not print source file name and line number of a symbol. This is the |
| 4997 | default. |
| 4998 | |
| 4999 | @kindex show print symbol-filename |
| 5000 | @item show print symbol-filename |
| 5001 | Show whether or not @value{GDBN} will print the source file name and |
| 5002 | line number of a symbol in the symbolic form of an address. |
| 5003 | @end table |
| 5004 | |
| 5005 | Another situation where it is helpful to show symbol filenames and line |
| 5006 | numbers is when disassembling code; @value{GDBN} shows you the line |
| 5007 | number and source file that corresponds to each instruction. |
| 5008 | |
| 5009 | Also, you may wish to see the symbolic form only if the address being |
| 5010 | printed is reasonably close to the closest earlier symbol: |
| 5011 | |
| 5012 | @table @code |
| 5013 | @kindex set print max-symbolic-offset |
| 5014 | @item set print max-symbolic-offset @var{max-offset} |
| 5015 | Tell @value{GDBN} to only display the symbolic form of an address if the |
| 5016 | offset between the closest earlier symbol and the address is less than |
| 5017 | @var{max-offset}. The default is 0, which tells @value{GDBN} |
| 5018 | to always print the symbolic form of an address if any symbol precedes it. |
| 5019 | |
| 5020 | @kindex show print max-symbolic-offset |
| 5021 | @item show print max-symbolic-offset |
| 5022 | Ask how large the maximum offset is that @value{GDBN} prints in a |
| 5023 | symbolic address. |
| 5024 | @end table |
| 5025 | |
| 5026 | @cindex wild pointer, interpreting |
| 5027 | @cindex pointer, finding referent |
| 5028 | If you have a pointer and you are not sure where it points, try |
| 5029 | @samp{set print symbol-filename on}. Then you can determine the name |
| 5030 | and source file location of the variable where it points, using |
| 5031 | @samp{p/a @var{pointer}}. This interprets the address in symbolic form. |
| 5032 | For example, here @value{GDBN} shows that a variable @code{ptt} points |
| 5033 | at another variable @code{t}, defined in @file{hi2.c}: |
| 5034 | |
| 5035 | @example |
| 5036 | (@value{GDBP}) set print symbol-filename on |
| 5037 | (@value{GDBP}) p/a ptt |
| 5038 | $4 = 0xe008 <t in hi2.c> |
| 5039 | @end example |
| 5040 | |
| 5041 | @quotation |
| 5042 | @emph{Warning:} For pointers that point to a local variable, @samp{p/a} |
| 5043 | does not show the symbol name and filename of the referent, even with |
| 5044 | the appropriate @code{set print} options turned on. |
| 5045 | @end quotation |
| 5046 | |
| 5047 | Other settings control how different kinds of objects are printed: |
| 5048 | |
| 5049 | @table @code |
| 5050 | @kindex set print array |
| 5051 | @item set print array |
| 5052 | @itemx set print array on |
| 5053 | Pretty print arrays. This format is more convenient to read, |
| 5054 | but uses more space. The default is off. |
| 5055 | |
| 5056 | @item set print array off |
| 5057 | Return to compressed format for arrays. |
| 5058 | |
| 5059 | @kindex show print array |
| 5060 | @item show print array |
| 5061 | Show whether compressed or pretty format is selected for displaying |
| 5062 | arrays. |
| 5063 | |
| 5064 | @kindex set print elements |
| 5065 | @item set print elements @var{number-of-elements} |
| 5066 | Set a limit on how many elements of an array @value{GDBN} will print. |
| 5067 | If @value{GDBN} is printing a large array, it stops printing after it has |
| 5068 | printed the number of elements set by the @code{set print elements} command. |
| 5069 | This limit also applies to the display of strings. |
| 5070 | When @value{GDBN} starts, this limit is set to 200. |
| 5071 | Setting @var{number-of-elements} to zero means that the printing is unlimited. |
| 5072 | |
| 5073 | @kindex show print elements |
| 5074 | @item show print elements |
| 5075 | Display the number of elements of a large array that @value{GDBN} will print. |
| 5076 | If the number is 0, then the printing is unlimited. |
| 5077 | |
| 5078 | @kindex set print null-stop |
| 5079 | @item set print null-stop |
| 5080 | Cause @value{GDBN} to stop printing the characters of an array when the first |
| 5081 | @sc{null} is encountered. This is useful when large arrays actually |
| 5082 | contain only short strings. |
| 5083 | The default is off. |
| 5084 | |
| 5085 | @kindex set print pretty |
| 5086 | @item set print pretty on |
| 5087 | Cause @value{GDBN} to print structures in an indented format with one member |
| 5088 | per line, like this: |
| 5089 | |
| 5090 | @smallexample |
| 5091 | @group |
| 5092 | $1 = @{ |
| 5093 | next = 0x0, |
| 5094 | flags = @{ |
| 5095 | sweet = 1, |
| 5096 | sour = 1 |
| 5097 | @}, |
| 5098 | meat = 0x54 "Pork" |
| 5099 | @} |
| 5100 | @end group |
| 5101 | @end smallexample |
| 5102 | |
| 5103 | @item set print pretty off |
| 5104 | Cause @value{GDBN} to print structures in a compact format, like this: |
| 5105 | |
| 5106 | @smallexample |
| 5107 | @group |
| 5108 | $1 = @{next = 0x0, flags = @{sweet = 1, sour = 1@}, \ |
| 5109 | meat = 0x54 "Pork"@} |
| 5110 | @end group |
| 5111 | @end smallexample |
| 5112 | |
| 5113 | @noindent |
| 5114 | This is the default format. |
| 5115 | |
| 5116 | @kindex show print pretty |
| 5117 | @item show print pretty |
| 5118 | Show which format @value{GDBN} is using to print structures. |
| 5119 | |
| 5120 | @kindex set print sevenbit-strings |
| 5121 | @item set print sevenbit-strings on |
| 5122 | Print using only seven-bit characters; if this option is set, |
| 5123 | @value{GDBN} displays any eight-bit characters (in strings or |
| 5124 | character values) using the notation @code{\}@var{nnn}. This setting is |
| 5125 | best if you are working in English (@sc{ascii}) and you use the |
| 5126 | high-order bit of characters as a marker or ``meta'' bit. |
| 5127 | |
| 5128 | @item set print sevenbit-strings off |
| 5129 | Print full eight-bit characters. This allows the use of more |
| 5130 | international character sets, and is the default. |
| 5131 | |
| 5132 | @kindex show print sevenbit-strings |
| 5133 | @item show print sevenbit-strings |
| 5134 | Show whether or not @value{GDBN} is printing only seven-bit characters. |
| 5135 | |
| 5136 | @kindex set print union |
| 5137 | @item set print union on |
| 5138 | Tell @value{GDBN} to print unions which are contained in structures. This |
| 5139 | is the default setting. |
| 5140 | |
| 5141 | @item set print union off |
| 5142 | Tell @value{GDBN} not to print unions which are contained in structures. |
| 5143 | |
| 5144 | @kindex show print union |
| 5145 | @item show print union |
| 5146 | Ask @value{GDBN} whether or not it will print unions which are contained in |
| 5147 | structures. |
| 5148 | |
| 5149 | For example, given the declarations |
| 5150 | |
| 5151 | @smallexample |
| 5152 | typedef enum @{Tree, Bug@} Species; |
| 5153 | typedef enum @{Big_tree, Acorn, Seedling@} Tree_forms; |
| 5154 | typedef enum @{Caterpillar, Cocoon, Butterfly@} |
| 5155 | Bug_forms; |
| 5156 | |
| 5157 | struct thing @{ |
| 5158 | Species it; |
| 5159 | union @{ |
| 5160 | Tree_forms tree; |
| 5161 | Bug_forms bug; |
| 5162 | @} form; |
| 5163 | @}; |
| 5164 | |
| 5165 | struct thing foo = @{Tree, @{Acorn@}@}; |
| 5166 | @end smallexample |
| 5167 | |
| 5168 | @noindent |
| 5169 | with @code{set print union on} in effect @samp{p foo} would print |
| 5170 | |
| 5171 | @smallexample |
| 5172 | $1 = @{it = Tree, form = @{tree = Acorn, bug = Cocoon@}@} |
| 5173 | @end smallexample |
| 5174 | |
| 5175 | @noindent |
| 5176 | and with @code{set print union off} in effect it would print |
| 5177 | |
| 5178 | @smallexample |
| 5179 | $1 = @{it = Tree, form = @{...@}@} |
| 5180 | @end smallexample |
| 5181 | @end table |
| 5182 | |
| 5183 | @need 1000 |
| 5184 | @noindent |
| 5185 | These settings are of interest when debugging C@t{++} programs: |
| 5186 | |
| 5187 | @table @code |
| 5188 | @cindex demangling |
| 5189 | @kindex set print demangle |
| 5190 | @item set print demangle |
| 5191 | @itemx set print demangle on |
| 5192 | Print C@t{++} names in their source form rather than in the encoded |
| 5193 | (``mangled'') form passed to the assembler and linker for type-safe |
| 5194 | linkage. The default is on. |
| 5195 | |
| 5196 | @kindex show print demangle |
| 5197 | @item show print demangle |
| 5198 | Show whether C@t{++} names are printed in mangled or demangled form. |
| 5199 | |
| 5200 | @kindex set print asm-demangle |
| 5201 | @item set print asm-demangle |
| 5202 | @itemx set print asm-demangle on |
| 5203 | Print C@t{++} names in their source form rather than their mangled form, even |
| 5204 | in assembler code printouts such as instruction disassemblies. |
| 5205 | The default is off. |
| 5206 | |
| 5207 | @kindex show print asm-demangle |
| 5208 | @item show print asm-demangle |
| 5209 | Show whether C@t{++} names in assembly listings are printed in mangled |
| 5210 | or demangled form. |
| 5211 | |
| 5212 | @kindex set demangle-style |
| 5213 | @cindex C@t{++} symbol decoding style |
| 5214 | @cindex symbol decoding style, C@t{++} |
| 5215 | @item set demangle-style @var{style} |
| 5216 | Choose among several encoding schemes used by different compilers to |
| 5217 | represent C@t{++} names. The choices for @var{style} are currently: |
| 5218 | |
| 5219 | @table @code |
| 5220 | @item auto |
| 5221 | Allow @value{GDBN} to choose a decoding style by inspecting your program. |
| 5222 | |
| 5223 | @item gnu |
| 5224 | Decode based on the @sc{gnu} C@t{++} compiler (@code{g++}) encoding algorithm. |
| 5225 | This is the default. |
| 5226 | |
| 5227 | @item hp |
| 5228 | Decode based on the HP ANSI C@t{++} (@code{aCC}) encoding algorithm. |
| 5229 | |
| 5230 | @item lucid |
| 5231 | Decode based on the Lucid C@t{++} compiler (@code{lcc}) encoding algorithm. |
| 5232 | |
| 5233 | @item arm |
| 5234 | Decode using the algorithm in the @cite{C@t{++} Annotated Reference Manual}. |
| 5235 | @strong{Warning:} this setting alone is not sufficient to allow |
| 5236 | debugging @code{cfront}-generated executables. @value{GDBN} would |
| 5237 | require further enhancement to permit that. |
| 5238 | |
| 5239 | @end table |
| 5240 | If you omit @var{style}, you will see a list of possible formats. |
| 5241 | |
| 5242 | @kindex show demangle-style |
| 5243 | @item show demangle-style |
| 5244 | Display the encoding style currently in use for decoding C@t{++} symbols. |
| 5245 | |
| 5246 | @kindex set print object |
| 5247 | @item set print object |
| 5248 | @itemx set print object on |
| 5249 | When displaying a pointer to an object, identify the @emph{actual} |
| 5250 | (derived) type of the object rather than the @emph{declared} type, using |
| 5251 | the virtual function table. |
| 5252 | |
| 5253 | @item set print object off |
| 5254 | Display only the declared type of objects, without reference to the |
| 5255 | virtual function table. This is the default setting. |
| 5256 | |
| 5257 | @kindex show print object |
| 5258 | @item show print object |
| 5259 | Show whether actual, or declared, object types are displayed. |
| 5260 | |
| 5261 | @kindex set print static-members |
| 5262 | @item set print static-members |
| 5263 | @itemx set print static-members on |
| 5264 | Print static members when displaying a C@t{++} object. The default is on. |
| 5265 | |
| 5266 | @item set print static-members off |
| 5267 | Do not print static members when displaying a C@t{++} object. |
| 5268 | |
| 5269 | @kindex show print static-members |
| 5270 | @item show print static-members |
| 5271 | Show whether C@t{++} static members are printed, or not. |
| 5272 | |
| 5273 | @c These don't work with HP ANSI C++ yet. |
| 5274 | @kindex set print vtbl |
| 5275 | @item set print vtbl |
| 5276 | @itemx set print vtbl on |
| 5277 | Pretty print C@t{++} virtual function tables. The default is off. |
| 5278 | (The @code{vtbl} commands do not work on programs compiled with the HP |
| 5279 | ANSI C@t{++} compiler (@code{aCC}).) |
| 5280 | |
| 5281 | @item set print vtbl off |
| 5282 | Do not pretty print C@t{++} virtual function tables. |
| 5283 | |
| 5284 | @kindex show print vtbl |
| 5285 | @item show print vtbl |
| 5286 | Show whether C@t{++} virtual function tables are pretty printed, or not. |
| 5287 | @end table |
| 5288 | |
| 5289 | @node Value History |
| 5290 | @section Value history |
| 5291 | |
| 5292 | @cindex value history |
| 5293 | Values printed by the @code{print} command are saved in the @value{GDBN} |
| 5294 | @dfn{value history}. This allows you to refer to them in other expressions. |
| 5295 | Values are kept until the symbol table is re-read or discarded |
| 5296 | (for example with the @code{file} or @code{symbol-file} commands). |
| 5297 | When the symbol table changes, the value history is discarded, |
| 5298 | since the values may contain pointers back to the types defined in the |
| 5299 | symbol table. |
| 5300 | |
| 5301 | @cindex @code{$} |
| 5302 | @cindex @code{$$} |
| 5303 | @cindex history number |
| 5304 | The values printed are given @dfn{history numbers} by which you can |
| 5305 | refer to them. These are successive integers starting with one. |
| 5306 | @code{print} shows you the history number assigned to a value by |
| 5307 | printing @samp{$@var{num} = } before the value; here @var{num} is the |
| 5308 | history number. |
| 5309 | |
| 5310 | To refer to any previous value, use @samp{$} followed by the value's |
| 5311 | history number. The way @code{print} labels its output is designed to |
| 5312 | remind you of this. Just @code{$} refers to the most recent value in |
| 5313 | the history, and @code{$$} refers to the value before that. |
| 5314 | @code{$$@var{n}} refers to the @var{n}th value from the end; @code{$$2} |
| 5315 | is the value just prior to @code{$$}, @code{$$1} is equivalent to |
| 5316 | @code{$$}, and @code{$$0} is equivalent to @code{$}. |
| 5317 | |
| 5318 | For example, suppose you have just printed a pointer to a structure and |
| 5319 | want to see the contents of the structure. It suffices to type |
| 5320 | |
| 5321 | @example |
| 5322 | p *$ |
| 5323 | @end example |
| 5324 | |
| 5325 | If you have a chain of structures where the component @code{next} points |
| 5326 | to the next one, you can print the contents of the next one with this: |
| 5327 | |
| 5328 | @example |
| 5329 | p *$.next |
| 5330 | @end example |
| 5331 | |
| 5332 | @noindent |
| 5333 | You can print successive links in the chain by repeating this |
| 5334 | command---which you can do by just typing @key{RET}. |
| 5335 | |
| 5336 | Note that the history records values, not expressions. If the value of |
| 5337 | @code{x} is 4 and you type these commands: |
| 5338 | |
| 5339 | @example |
| 5340 | print x |
| 5341 | set x=5 |
| 5342 | @end example |
| 5343 | |
| 5344 | @noindent |
| 5345 | then the value recorded in the value history by the @code{print} command |
| 5346 | remains 4 even though the value of @code{x} has changed. |
| 5347 | |
| 5348 | @table @code |
| 5349 | @kindex show values |
| 5350 | @item show values |
| 5351 | Print the last ten values in the value history, with their item numbers. |
| 5352 | This is like @samp{p@ $$9} repeated ten times, except that @code{show |
| 5353 | values} does not change the history. |
| 5354 | |
| 5355 | @item show values @var{n} |
| 5356 | Print ten history values centered on history item number @var{n}. |
| 5357 | |
| 5358 | @item show values + |
| 5359 | Print ten history values just after the values last printed. If no more |
| 5360 | values are available, @code{show values +} produces no display. |
| 5361 | @end table |
| 5362 | |
| 5363 | Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the |
| 5364 | same effect as @samp{show values +}. |
| 5365 | |
| 5366 | @node Convenience Vars |
| 5367 | @section Convenience variables |
| 5368 | |
| 5369 | @cindex convenience variables |
| 5370 | @value{GDBN} provides @dfn{convenience variables} that you can use within |
| 5371 | @value{GDBN} to hold on to a value and refer to it later. These variables |
| 5372 | exist entirely within @value{GDBN}; they are not part of your program, and |
| 5373 | setting a convenience variable has no direct effect on further execution |
| 5374 | of your program. That is why you can use them freely. |
| 5375 | |
| 5376 | Convenience variables are prefixed with @samp{$}. Any name preceded by |
| 5377 | @samp{$} can be used for a convenience variable, unless it is one of |
| 5378 | the predefined machine-specific register names (@pxref{Registers, ,Registers}). |
| 5379 | (Value history references, in contrast, are @emph{numbers} preceded |
| 5380 | by @samp{$}. @xref{Value History, ,Value history}.) |
| 5381 | |
| 5382 | You can save a value in a convenience variable with an assignment |
| 5383 | expression, just as you would set a variable in your program. |
| 5384 | For example: |
| 5385 | |
| 5386 | @example |
| 5387 | set $foo = *object_ptr |
| 5388 | @end example |
| 5389 | |
| 5390 | @noindent |
| 5391 | would save in @code{$foo} the value contained in the object pointed to by |
| 5392 | @code{object_ptr}. |
| 5393 | |
| 5394 | Using a convenience variable for the first time creates it, but its |
| 5395 | value is @code{void} until you assign a new value. You can alter the |
| 5396 | value with another assignment at any time. |
| 5397 | |
| 5398 | Convenience variables have no fixed types. You can assign a convenience |
| 5399 | variable any type of value, including structures and arrays, even if |
| 5400 | that variable already has a value of a different type. The convenience |
| 5401 | variable, when used as an expression, has the type of its current value. |
| 5402 | |
| 5403 | @table @code |
| 5404 | @kindex show convenience |
| 5405 | @item show convenience |
| 5406 | Print a list of convenience variables used so far, and their values. |
| 5407 | Abbreviated @code{show conv}. |
| 5408 | @end table |
| 5409 | |
| 5410 | One of the ways to use a convenience variable is as a counter to be |
| 5411 | incremented or a pointer to be advanced. For example, to print |
| 5412 | a field from successive elements of an array of structures: |
| 5413 | |
| 5414 | @example |
| 5415 | set $i = 0 |
| 5416 | print bar[$i++]->contents |
| 5417 | @end example |
| 5418 | |
| 5419 | @noindent |
| 5420 | Repeat that command by typing @key{RET}. |
| 5421 | |
| 5422 | Some convenience variables are created automatically by @value{GDBN} and given |
| 5423 | values likely to be useful. |
| 5424 | |
| 5425 | @table @code |
| 5426 | @vindex $_@r{, convenience variable} |
| 5427 | @item $_ |
| 5428 | The variable @code{$_} is automatically set by the @code{x} command to |
| 5429 | the last address examined (@pxref{Memory, ,Examining memory}). Other |
| 5430 | commands which provide a default address for @code{x} to examine also |
| 5431 | set @code{$_} to that address; these commands include @code{info line} |
| 5432 | and @code{info breakpoint}. The type of @code{$_} is @code{void *} |
| 5433 | except when set by the @code{x} command, in which case it is a pointer |
| 5434 | to the type of @code{$__}. |
| 5435 | |
| 5436 | @vindex $__@r{, convenience variable} |
| 5437 | @item $__ |
| 5438 | The variable @code{$__} is automatically set by the @code{x} command |
| 5439 | to the value found in the last address examined. Its type is chosen |
| 5440 | to match the format in which the data was printed. |
| 5441 | |
| 5442 | @item $_exitcode |
| 5443 | @vindex $_exitcode@r{, convenience variable} |
| 5444 | The variable @code{$_exitcode} is automatically set to the exit code when |
| 5445 | the program being debugged terminates. |
| 5446 | @end table |
| 5447 | |
| 5448 | On HP-UX systems, if you refer to a function or variable name that |
| 5449 | begins with a dollar sign, @value{GDBN} searches for a user or system |
| 5450 | name first, before it searches for a convenience variable. |
| 5451 | |
| 5452 | @node Registers |
| 5453 | @section Registers |
| 5454 | |
| 5455 | @cindex registers |
| 5456 | You can refer to machine register contents, in expressions, as variables |
| 5457 | with names starting with @samp{$}. The names of registers are different |
| 5458 | for each machine; use @code{info registers} to see the names used on |
| 5459 | your machine. |
| 5460 | |
| 5461 | @table @code |
| 5462 | @kindex info registers |
| 5463 | @item info registers |
| 5464 | Print the names and values of all registers except floating-point |
| 5465 | registers (in the selected stack frame). |
| 5466 | |
| 5467 | @kindex info all-registers |
| 5468 | @cindex floating point registers |
| 5469 | @item info all-registers |
| 5470 | Print the names and values of all registers, including floating-point |
| 5471 | registers. |
| 5472 | |
| 5473 | @item info registers @var{regname} @dots{} |
| 5474 | Print the @dfn{relativized} value of each specified register @var{regname}. |
| 5475 | As discussed in detail below, register values are normally relative to |
| 5476 | the selected stack frame. @var{regname} may be any register name valid on |
| 5477 | the machine you are using, with or without the initial @samp{$}. |
| 5478 | @end table |
| 5479 | |
| 5480 | @value{GDBN} has four ``standard'' register names that are available (in |
| 5481 | expressions) on most machines---whenever they do not conflict with an |
| 5482 | architecture's canonical mnemonics for registers. The register names |
| 5483 | @code{$pc} and @code{$sp} are used for the program counter register and |
| 5484 | the stack pointer. @code{$fp} is used for a register that contains a |
| 5485 | pointer to the current stack frame, and @code{$ps} is used for a |
| 5486 | register that contains the processor status. For example, |
| 5487 | you could print the program counter in hex with |
| 5488 | |
| 5489 | @example |
| 5490 | p/x $pc |
| 5491 | @end example |
| 5492 | |
| 5493 | @noindent |
| 5494 | or print the instruction to be executed next with |
| 5495 | |
| 5496 | @example |
| 5497 | x/i $pc |
| 5498 | @end example |
| 5499 | |
| 5500 | @noindent |
| 5501 | or add four to the stack pointer@footnote{This is a way of removing |
| 5502 | one word from the stack, on machines where stacks grow downward in |
| 5503 | memory (most machines, nowadays). This assumes that the innermost |
| 5504 | stack frame is selected; setting @code{$sp} is not allowed when other |
| 5505 | stack frames are selected. To pop entire frames off the stack, |
| 5506 | regardless of machine architecture, use @code{return}; |
| 5507 | see @ref{Returning, ,Returning from a function}.} with |
| 5508 | |
| 5509 | @example |
| 5510 | set $sp += 4 |
| 5511 | @end example |
| 5512 | |
| 5513 | Whenever possible, these four standard register names are available on |
| 5514 | your machine even though the machine has different canonical mnemonics, |
| 5515 | so long as there is no conflict. The @code{info registers} command |
| 5516 | shows the canonical names. For example, on the SPARC, @code{info |
| 5517 | registers} displays the processor status register as @code{$psr} but you |
| 5518 | can also refer to it as @code{$ps}; and on x86-based machines @code{$ps} |
| 5519 | is an alias for the @sc{eflags} register. |
| 5520 | |
| 5521 | @value{GDBN} always considers the contents of an ordinary register as an |
| 5522 | integer when the register is examined in this way. Some machines have |
| 5523 | special registers which can hold nothing but floating point; these |
| 5524 | registers are considered to have floating point values. There is no way |
| 5525 | to refer to the contents of an ordinary register as floating point value |
| 5526 | (although you can @emph{print} it as a floating point value with |
| 5527 | @samp{print/f $@var{regname}}). |
| 5528 | |
| 5529 | Some registers have distinct ``raw'' and ``virtual'' data formats. This |
| 5530 | means that the data format in which the register contents are saved by |
| 5531 | the operating system is not the same one that your program normally |
| 5532 | sees. For example, the registers of the 68881 floating point |
| 5533 | coprocessor are always saved in ``extended'' (raw) format, but all C |
| 5534 | programs expect to work with ``double'' (virtual) format. In such |
| 5535 | cases, @value{GDBN} normally works with the virtual format only (the format |
| 5536 | that makes sense for your program), but the @code{info registers} command |
| 5537 | prints the data in both formats. |
| 5538 | |
| 5539 | Normally, register values are relative to the selected stack frame |
| 5540 | (@pxref{Selection, ,Selecting a frame}). This means that you get the |
| 5541 | value that the register would contain if all stack frames farther in |
| 5542 | were exited and their saved registers restored. In order to see the |
| 5543 | true contents of hardware registers, you must select the innermost |
| 5544 | frame (with @samp{frame 0}). |
| 5545 | |
| 5546 | However, @value{GDBN} must deduce where registers are saved, from the machine |
| 5547 | code generated by your compiler. If some registers are not saved, or if |
| 5548 | @value{GDBN} is unable to locate the saved registers, the selected stack |
| 5549 | frame makes no difference. |
| 5550 | |
| 5551 | @node Floating Point Hardware |
| 5552 | @section Floating point hardware |
| 5553 | @cindex floating point |
| 5554 | |
| 5555 | Depending on the configuration, @value{GDBN} may be able to give |
| 5556 | you more information about the status of the floating point hardware. |
| 5557 | |
| 5558 | @table @code |
| 5559 | @kindex info float |
| 5560 | @item info float |
| 5561 | Display hardware-dependent information about the floating |
| 5562 | point unit. The exact contents and layout vary depending on the |
| 5563 | floating point chip. Currently, @samp{info float} is supported on |
| 5564 | the ARM and x86 machines. |
| 5565 | @end table |
| 5566 | |
| 5567 | @node Memory Region Attributes |
| 5568 | @section Memory Region Attributes |
| 5569 | @cindex memory region attributes |
| 5570 | |
| 5571 | @dfn{Memory region attributes} allow you to describe special handling |
| 5572 | required by regions of your target's memory. @value{GDBN} uses attributes |
| 5573 | to determine whether to allow certain types of memory accesses; whether to |
| 5574 | use specific width accesses; and whether to cache target memory. |
| 5575 | |
| 5576 | Defined memory regions can be individually enabled and disabled. When a |
| 5577 | memory region is disabled, @value{GDBN} uses the default attributes when |
| 5578 | accessing memory in that region. Similarly, if no memory regions have |
| 5579 | been defined, @value{GDBN} uses the default attributes when accessing |
| 5580 | all memory. |
| 5581 | |
| 5582 | When a memory region is defined, it is given a number to identify it; |
| 5583 | to enable, disable, or remove a memory region, you specify that number. |
| 5584 | |
| 5585 | @table @code |
| 5586 | @kindex mem |
| 5587 | @item mem @var{address1} @var{address2} @var{attributes}@dots{} |
| 5588 | Define memory region bounded by @var{address1} and @var{address2} |
| 5589 | with attributes @var{attributes}@dots{}. |
| 5590 | |
| 5591 | @kindex delete mem |
| 5592 | @item delete mem @var{nums}@dots{} |
| 5593 | Remove memory regions @var{nums}@dots{}. |
| 5594 | |
| 5595 | @kindex disable mem |
| 5596 | @item disable mem @var{nums}@dots{} |
| 5597 | Disable memory regions @var{nums}@dots{}. |
| 5598 | A disabled memory region is not forgotten. |
| 5599 | It may be enabled again later. |
| 5600 | |
| 5601 | @kindex enable mem |
| 5602 | @item enable mem @var{nums}@dots{} |
| 5603 | Enable memory regions @var{nums}@dots{}. |
| 5604 | |
| 5605 | @kindex info mem |
| 5606 | @item info mem |
| 5607 | Print a table of all defined memory regions, with the following columns |
| 5608 | for each region. |
| 5609 | |
| 5610 | @table @emph |
| 5611 | @item Memory Region Number |
| 5612 | @item Enabled or Disabled. |
| 5613 | Enabled memory regions are marked with @samp{y}. |
| 5614 | Disabled memory regions are marked with @samp{n}. |
| 5615 | |
| 5616 | @item Lo Address |
| 5617 | The address defining the inclusive lower bound of the memory region. |
| 5618 | |
| 5619 | @item Hi Address |
| 5620 | The address defining the exclusive upper bound of the memory region. |
| 5621 | |
| 5622 | @item Attributes |
| 5623 | The list of attributes set for this memory region. |
| 5624 | @end table |
| 5625 | @end table |
| 5626 | |
| 5627 | |
| 5628 | @subsection Attributes |
| 5629 | |
| 5630 | @subsubsection Memory Access Mode |
| 5631 | The access mode attributes set whether @value{GDBN} may make read or |
| 5632 | write accesses to a memory region. |
| 5633 | |
| 5634 | While these attributes prevent @value{GDBN} from performing invalid |
| 5635 | memory accesses, they do nothing to prevent the target system, I/O DMA, |
| 5636 | etc. from accessing memory. |
| 5637 | |
| 5638 | @table @code |
| 5639 | @item ro |
| 5640 | Memory is read only. |
| 5641 | @item wo |
| 5642 | Memory is write only. |
| 5643 | @item rw |
| 5644 | Memory is read/write. This is the default. |
| 5645 | @end table |
| 5646 | |
| 5647 | @subsubsection Memory Access Size |
| 5648 | The acccess size attributes tells @value{GDBN} to use specific sized |
| 5649 | accesses in the memory region. Often memory mapped device registers |
| 5650 | require specific sized accesses. If no access size attribute is |
| 5651 | specified, @value{GDBN} may use accesses of any size. |
| 5652 | |
| 5653 | @table @code |
| 5654 | @item 8 |
| 5655 | Use 8 bit memory accesses. |
| 5656 | @item 16 |
| 5657 | Use 16 bit memory accesses. |
| 5658 | @item 32 |
| 5659 | Use 32 bit memory accesses. |
| 5660 | @item 64 |
| 5661 | Use 64 bit memory accesses. |
| 5662 | @end table |
| 5663 | |
| 5664 | @c @subsubsection Hardware/Software Breakpoints |
| 5665 | @c The hardware/software breakpoint attributes set whether @value{GDBN} |
| 5666 | @c will use hardware or software breakpoints for the internal breakpoints |
| 5667 | @c used by the step, next, finish, until, etc. commands. |
| 5668 | @c |
| 5669 | @c @table @code |
| 5670 | @c @item hwbreak |
| 5671 | @c Always use hardware breakpoints |
| 5672 | @c @item swbreak (default) |
| 5673 | @c @end table |
| 5674 | |
| 5675 | @subsubsection Data Cache |
| 5676 | The data cache attributes set whether @value{GDBN} will cache target |
| 5677 | memory. While this generally improves performance by reducing debug |
| 5678 | protocol overhead, it can lead to incorrect results because @value{GDBN} |
| 5679 | does not know about volatile variables or memory mapped device |
| 5680 | registers. |
| 5681 | |
| 5682 | @table @code |
| 5683 | @item cache |
| 5684 | Enable @value{GDBN} to cache target memory. |
| 5685 | @item nocache |
| 5686 | Disable @value{GDBN} from caching target memory. This is the default. |
| 5687 | @end table |
| 5688 | |
| 5689 | @c @subsubsection Memory Write Verification |
| 5690 | @c The memory write verification attributes set whether @value{GDBN} |
| 5691 | @c will re-reads data after each write to verify the write was successful. |
| 5692 | @c |
| 5693 | @c @table @code |
| 5694 | @c @item verify |
| 5695 | @c @item noverify (default) |
| 5696 | @c @end table |
| 5697 | |
| 5698 | @node Tracepoints |
| 5699 | @chapter Tracepoints |
| 5700 | @c This chapter is based on the documentation written by Michael |
| 5701 | @c Snyder, David Taylor, Jim Blandy, and Elena Zannoni. |
| 5702 | |
| 5703 | @cindex tracepoints |
| 5704 | In some applications, it is not feasible for the debugger to interrupt |
| 5705 | the program's execution long enough for the developer to learn |
| 5706 | anything helpful about its behavior. If the program's correctness |
| 5707 | depends on its real-time behavior, delays introduced by a debugger |
| 5708 | might cause the program to change its behavior drastically, or perhaps |
| 5709 | fail, even when the code itself is correct. It is useful to be able |
| 5710 | to observe the program's behavior without interrupting it. |
| 5711 | |
| 5712 | Using @value{GDBN}'s @code{trace} and @code{collect} commands, you can |
| 5713 | specify locations in the program, called @dfn{tracepoints}, and |
| 5714 | arbitrary expressions to evaluate when those tracepoints are reached. |
| 5715 | Later, using the @code{tfind} command, you can examine the values |
| 5716 | those expressions had when the program hit the tracepoints. The |
| 5717 | expressions may also denote objects in memory---structures or arrays, |
| 5718 | for example---whose values @value{GDBN} should record; while visiting |
| 5719 | a particular tracepoint, you may inspect those objects as if they were |
| 5720 | in memory at that moment. However, because @value{GDBN} records these |
| 5721 | values without interacting with you, it can do so quickly and |
| 5722 | unobtrusively, hopefully not disturbing the program's behavior. |
| 5723 | |
| 5724 | The tracepoint facility is currently available only for remote |
| 5725 | targets. @xref{Targets}. In addition, your remote target must know how |
| 5726 | to collect trace data. This functionality is implemented in the remote |
| 5727 | stub; however, none of the stubs distributed with @value{GDBN} support |
| 5728 | tracepoints as of this writing. |
| 5729 | |
| 5730 | This chapter describes the tracepoint commands and features. |
| 5731 | |
| 5732 | @menu |
| 5733 | * Set Tracepoints:: |
| 5734 | * Analyze Collected Data:: |
| 5735 | * Tracepoint Variables:: |
| 5736 | @end menu |
| 5737 | |
| 5738 | @node Set Tracepoints |
| 5739 | @section Commands to Set Tracepoints |
| 5740 | |
| 5741 | Before running such a @dfn{trace experiment}, an arbitrary number of |
| 5742 | tracepoints can be set. Like a breakpoint (@pxref{Set Breaks}), a |
| 5743 | tracepoint has a number assigned to it by @value{GDBN}. Like with |
| 5744 | breakpoints, tracepoint numbers are successive integers starting from |
| 5745 | one. Many of the commands associated with tracepoints take the |
| 5746 | tracepoint number as their argument, to identify which tracepoint to |
| 5747 | work on. |
| 5748 | |
| 5749 | For each tracepoint, you can specify, in advance, some arbitrary set |
| 5750 | of data that you want the target to collect in the trace buffer when |
| 5751 | it hits that tracepoint. The collected data can include registers, |
| 5752 | local variables, or global data. Later, you can use @value{GDBN} |
| 5753 | commands to examine the values these data had at the time the |
| 5754 | tracepoint was hit. |
| 5755 | |
| 5756 | This section describes commands to set tracepoints and associated |
| 5757 | conditions and actions. |
| 5758 | |
| 5759 | @menu |
| 5760 | * Create and Delete Tracepoints:: |
| 5761 | * Enable and Disable Tracepoints:: |
| 5762 | * Tracepoint Passcounts:: |
| 5763 | * Tracepoint Actions:: |
| 5764 | * Listing Tracepoints:: |
| 5765 | * Starting and Stopping Trace Experiment:: |
| 5766 | @end menu |
| 5767 | |
| 5768 | @node Create and Delete Tracepoints |
| 5769 | @subsection Create and Delete Tracepoints |
| 5770 | |
| 5771 | @table @code |
| 5772 | @cindex set tracepoint |
| 5773 | @kindex trace |
| 5774 | @item trace |
| 5775 | The @code{trace} command is very similar to the @code{break} command. |
| 5776 | Its argument can be a source line, a function name, or an address in |
| 5777 | the target program. @xref{Set Breaks}. The @code{trace} command |
| 5778 | defines a tracepoint, which is a point in the target program where the |
| 5779 | debugger will briefly stop, collect some data, and then allow the |
| 5780 | program to continue. Setting a tracepoint or changing its commands |
| 5781 | doesn't take effect until the next @code{tstart} command; thus, you |
| 5782 | cannot change the tracepoint attributes once a trace experiment is |
| 5783 | running. |
| 5784 | |
| 5785 | Here are some examples of using the @code{trace} command: |
| 5786 | |
| 5787 | @smallexample |
| 5788 | (@value{GDBP}) @b{trace foo.c:121} // a source file and line number |
| 5789 | |
| 5790 | (@value{GDBP}) @b{trace +2} // 2 lines forward |
| 5791 | |
| 5792 | (@value{GDBP}) @b{trace my_function} // first source line of function |
| 5793 | |
| 5794 | (@value{GDBP}) @b{trace *my_function} // EXACT start address of function |
| 5795 | |
| 5796 | (@value{GDBP}) @b{trace *0x2117c4} // an address |
| 5797 | @end smallexample |
| 5798 | |
| 5799 | @noindent |
| 5800 | You can abbreviate @code{trace} as @code{tr}. |
| 5801 | |
| 5802 | @vindex $tpnum |
| 5803 | @cindex last tracepoint number |
| 5804 | @cindex recent tracepoint number |
| 5805 | @cindex tracepoint number |
| 5806 | The convenience variable @code{$tpnum} records the tracepoint number |
| 5807 | of the most recently set tracepoint. |
| 5808 | |
| 5809 | @kindex delete tracepoint |
| 5810 | @cindex tracepoint deletion |
| 5811 | @item delete tracepoint @r{[}@var{num}@r{]} |
| 5812 | Permanently delete one or more tracepoints. With no argument, the |
| 5813 | default is to delete all tracepoints. |
| 5814 | |
| 5815 | Examples: |
| 5816 | |
| 5817 | @smallexample |
| 5818 | (@value{GDBP}) @b{delete trace 1 2 3} // remove three tracepoints |
| 5819 | |
| 5820 | (@value{GDBP}) @b{delete trace} // remove all tracepoints |
| 5821 | @end smallexample |
| 5822 | |
| 5823 | @noindent |
| 5824 | You can abbreviate this command as @code{del tr}. |
| 5825 | @end table |
| 5826 | |
| 5827 | @node Enable and Disable Tracepoints |
| 5828 | @subsection Enable and Disable Tracepoints |
| 5829 | |
| 5830 | @table @code |
| 5831 | @kindex disable tracepoint |
| 5832 | @item disable tracepoint @r{[}@var{num}@r{]} |
| 5833 | Disable tracepoint @var{num}, or all tracepoints if no argument |
| 5834 | @var{num} is given. A disabled tracepoint will have no effect during |
| 5835 | the next trace experiment, but it is not forgotten. You can re-enable |
| 5836 | a disabled tracepoint using the @code{enable tracepoint} command. |
| 5837 | |
| 5838 | @kindex enable tracepoint |
| 5839 | @item enable tracepoint @r{[}@var{num}@r{]} |
| 5840 | Enable tracepoint @var{num}, or all tracepoints. The enabled |
| 5841 | tracepoints will become effective the next time a trace experiment is |
| 5842 | run. |
| 5843 | @end table |
| 5844 | |
| 5845 | @node Tracepoint Passcounts |
| 5846 | @subsection Tracepoint Passcounts |
| 5847 | |
| 5848 | @table @code |
| 5849 | @kindex passcount |
| 5850 | @cindex tracepoint pass count |
| 5851 | @item passcount @r{[}@var{n} @r{[}@var{num}@r{]]} |
| 5852 | Set the @dfn{passcount} of a tracepoint. The passcount is a way to |
| 5853 | automatically stop a trace experiment. If a tracepoint's passcount is |
| 5854 | @var{n}, then the trace experiment will be automatically stopped on |
| 5855 | the @var{n}'th time that tracepoint is hit. If the tracepoint number |
| 5856 | @var{num} is not specified, the @code{passcount} command sets the |
| 5857 | passcount of the most recently defined tracepoint. If no passcount is |
| 5858 | given, the trace experiment will run until stopped explicitly by the |
| 5859 | user. |
| 5860 | |
| 5861 | Examples: |
| 5862 | |
| 5863 | @smallexample |
| 5864 | (@value{GDBP}) @b{passcount 5 2} // Stop on the 5th execution of |
| 5865 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// tracepoint 2} |
| 5866 | |
| 5867 | (@value{GDBP}) @b{passcount 12} // Stop on the 12th execution of the |
| 5868 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// most recently defined tracepoint.} |
| 5869 | (@value{GDBP}) @b{trace foo} |
| 5870 | (@value{GDBP}) @b{pass 3} |
| 5871 | (@value{GDBP}) @b{trace bar} |
| 5872 | (@value{GDBP}) @b{pass 2} |
| 5873 | (@value{GDBP}) @b{trace baz} |
| 5874 | (@value{GDBP}) @b{pass 1} // Stop tracing when foo has been |
| 5875 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// executed 3 times OR when bar has} |
| 5876 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// been executed 2 times} |
| 5877 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// OR when baz has been executed 1 time.} |
| 5878 | @end smallexample |
| 5879 | @end table |
| 5880 | |
| 5881 | @node Tracepoint Actions |
| 5882 | @subsection Tracepoint Action Lists |
| 5883 | |
| 5884 | @table @code |
| 5885 | @kindex actions |
| 5886 | @cindex tracepoint actions |
| 5887 | @item actions @r{[}@var{num}@r{]} |
| 5888 | This command will prompt for a list of actions to be taken when the |
| 5889 | tracepoint is hit. If the tracepoint number @var{num} is not |
| 5890 | specified, this command sets the actions for the one that was most |
| 5891 | recently defined (so that you can define a tracepoint and then say |
| 5892 | @code{actions} without bothering about its number). You specify the |
| 5893 | actions themselves on the following lines, one action at a time, and |
| 5894 | terminate the actions list with a line containing just @code{end}. So |
| 5895 | far, the only defined actions are @code{collect} and |
| 5896 | @code{while-stepping}. |
| 5897 | |
| 5898 | @cindex remove actions from a tracepoint |
| 5899 | To remove all actions from a tracepoint, type @samp{actions @var{num}} |
| 5900 | and follow it immediately with @samp{end}. |
| 5901 | |
| 5902 | @smallexample |
| 5903 | (@value{GDBP}) @b{collect @var{data}} // collect some data |
| 5904 | |
| 5905 | (@value{GDBP}) @b{while-stepping 5} // single-step 5 times, collect data |
| 5906 | |
| 5907 | (@value{GDBP}) @b{end} // signals the end of actions. |
| 5908 | @end smallexample |
| 5909 | |
| 5910 | In the following example, the action list begins with @code{collect} |
| 5911 | commands indicating the things to be collected when the tracepoint is |
| 5912 | hit. Then, in order to single-step and collect additional data |
| 5913 | following the tracepoint, a @code{while-stepping} command is used, |
| 5914 | followed by the list of things to be collected while stepping. The |
| 5915 | @code{while-stepping} command is terminated by its own separate |
| 5916 | @code{end} command. Lastly, the action list is terminated by an |
| 5917 | @code{end} command. |
| 5918 | |
| 5919 | @smallexample |
| 5920 | (@value{GDBP}) @b{trace foo} |
| 5921 | (@value{GDBP}) @b{actions} |
| 5922 | Enter actions for tracepoint 1, one per line: |
| 5923 | > collect bar,baz |
| 5924 | > collect $regs |
| 5925 | > while-stepping 12 |
| 5926 | > collect $fp, $sp |
| 5927 | > end |
| 5928 | end |
| 5929 | @end smallexample |
| 5930 | |
| 5931 | @kindex collect @r{(tracepoints)} |
| 5932 | @item collect @var{expr1}, @var{expr2}, @dots{} |
| 5933 | Collect values of the given expressions when the tracepoint is hit. |
| 5934 | This command accepts a comma-separated list of any valid expressions. |
| 5935 | In addition to global, static, or local variables, the following |
| 5936 | special arguments are supported: |
| 5937 | |
| 5938 | @table @code |
| 5939 | @item $regs |
| 5940 | collect all registers |
| 5941 | |
| 5942 | @item $args |
| 5943 | collect all function arguments |
| 5944 | |
| 5945 | @item $locals |
| 5946 | collect all local variables. |
| 5947 | @end table |
| 5948 | |
| 5949 | You can give several consecutive @code{collect} commands, each one |
| 5950 | with a single argument, or one @code{collect} command with several |
| 5951 | arguments separated by commas: the effect is the same. |
| 5952 | |
| 5953 | The command @code{info scope} (@pxref{Symbols, info scope}) is |
| 5954 | particularly useful for figuring out what data to collect. |
| 5955 | |
| 5956 | @kindex while-stepping @r{(tracepoints)} |
| 5957 | @item while-stepping @var{n} |
| 5958 | Perform @var{n} single-step traces after the tracepoint, collecting |
| 5959 | new data at each step. The @code{while-stepping} command is |
| 5960 | followed by the list of what to collect while stepping (followed by |
| 5961 | its own @code{end} command): |
| 5962 | |
| 5963 | @smallexample |
| 5964 | > while-stepping 12 |
| 5965 | > collect $regs, myglobal |
| 5966 | > end |
| 5967 | > |
| 5968 | @end smallexample |
| 5969 | |
| 5970 | @noindent |
| 5971 | You may abbreviate @code{while-stepping} as @code{ws} or |
| 5972 | @code{stepping}. |
| 5973 | @end table |
| 5974 | |
| 5975 | @node Listing Tracepoints |
| 5976 | @subsection Listing Tracepoints |
| 5977 | |
| 5978 | @table @code |
| 5979 | @kindex info tracepoints |
| 5980 | @cindex information about tracepoints |
| 5981 | @item info tracepoints @r{[}@var{num}@r{]} |
| 5982 | Display information about the tracepoint @var{num}. If you don't specify |
| 5983 | a tracepoint number, displays information about all the tracepoints |
| 5984 | defined so far. For each tracepoint, the following information is |
| 5985 | shown: |
| 5986 | |
| 5987 | @itemize @bullet |
| 5988 | @item |
| 5989 | its number |
| 5990 | @item |
| 5991 | whether it is enabled or disabled |
| 5992 | @item |
| 5993 | its address |
| 5994 | @item |
| 5995 | its passcount as given by the @code{passcount @var{n}} command |
| 5996 | @item |
| 5997 | its step count as given by the @code{while-stepping @var{n}} command |
| 5998 | @item |
| 5999 | where in the source files is the tracepoint set |
| 6000 | @item |
| 6001 | its action list as given by the @code{actions} command |
| 6002 | @end itemize |
| 6003 | |
| 6004 | @smallexample |
| 6005 | (@value{GDBP}) @b{info trace} |
| 6006 | Num Enb Address PassC StepC What |
| 6007 | 1 y 0x002117c4 0 0 <gdb_asm> |
| 6008 | 2 y 0x0020dc64 0 0 in g_test at g_test.c:1375 |
| 6009 | 3 y 0x0020b1f4 0 0 in get_data at ../foo.c:41 |
| 6010 | (@value{GDBP}) |
| 6011 | @end smallexample |
| 6012 | |
| 6013 | @noindent |
| 6014 | This command can be abbreviated @code{info tp}. |
| 6015 | @end table |
| 6016 | |
| 6017 | @node Starting and Stopping Trace Experiment |
| 6018 | @subsection Starting and Stopping Trace Experiment |
| 6019 | |
| 6020 | @table @code |
| 6021 | @kindex tstart |
| 6022 | @cindex start a new trace experiment |
| 6023 | @cindex collected data discarded |
| 6024 | @item tstart |
| 6025 | This command takes no arguments. It starts the trace experiment, and |
| 6026 | begins collecting data. This has the side effect of discarding all |
| 6027 | the data collected in the trace buffer during the previous trace |
| 6028 | experiment. |
| 6029 | |
| 6030 | @kindex tstop |
| 6031 | @cindex stop a running trace experiment |
| 6032 | @item tstop |
| 6033 | This command takes no arguments. It ends the trace experiment, and |
| 6034 | stops collecting data. |
| 6035 | |
| 6036 | @strong{Note:} a trace experiment and data collection may stop |
| 6037 | automatically if any tracepoint's passcount is reached |
| 6038 | (@pxref{Tracepoint Passcounts}), or if the trace buffer becomes full. |
| 6039 | |
| 6040 | @kindex tstatus |
| 6041 | @cindex status of trace data collection |
| 6042 | @cindex trace experiment, status of |
| 6043 | @item tstatus |
| 6044 | This command displays the status of the current trace data |
| 6045 | collection. |
| 6046 | @end table |
| 6047 | |
| 6048 | Here is an example of the commands we described so far: |
| 6049 | |
| 6050 | @smallexample |
| 6051 | (@value{GDBP}) @b{trace gdb_c_test} |
| 6052 | (@value{GDBP}) @b{actions} |
| 6053 | Enter actions for tracepoint #1, one per line. |
| 6054 | > collect $regs,$locals,$args |
| 6055 | > while-stepping 11 |
| 6056 | > collect $regs |
| 6057 | > end |
| 6058 | > end |
| 6059 | (@value{GDBP}) @b{tstart} |
| 6060 | [time passes @dots{}] |
| 6061 | (@value{GDBP}) @b{tstop} |
| 6062 | @end smallexample |
| 6063 | |
| 6064 | |
| 6065 | @node Analyze Collected Data |
| 6066 | @section Using the collected data |
| 6067 | |
| 6068 | After the tracepoint experiment ends, you use @value{GDBN} commands |
| 6069 | for examining the trace data. The basic idea is that each tracepoint |
| 6070 | collects a trace @dfn{snapshot} every time it is hit and another |
| 6071 | snapshot every time it single-steps. All these snapshots are |
| 6072 | consecutively numbered from zero and go into a buffer, and you can |
| 6073 | examine them later. The way you examine them is to @dfn{focus} on a |
| 6074 | specific trace snapshot. When the remote stub is focused on a trace |
| 6075 | snapshot, it will respond to all @value{GDBN} requests for memory and |
| 6076 | registers by reading from the buffer which belongs to that snapshot, |
| 6077 | rather than from @emph{real} memory or registers of the program being |
| 6078 | debugged. This means that @strong{all} @value{GDBN} commands |
| 6079 | (@code{print}, @code{info registers}, @code{backtrace}, etc.) will |
| 6080 | behave as if we were currently debugging the program state as it was |
| 6081 | when the tracepoint occurred. Any requests for data that are not in |
| 6082 | the buffer will fail. |
| 6083 | |
| 6084 | @menu |
| 6085 | * tfind:: How to select a trace snapshot |
| 6086 | * tdump:: How to display all data for a snapshot |
| 6087 | * save-tracepoints:: How to save tracepoints for a future run |
| 6088 | @end menu |
| 6089 | |
| 6090 | @node tfind |
| 6091 | @subsection @code{tfind @var{n}} |
| 6092 | |
| 6093 | @kindex tfind |
| 6094 | @cindex select trace snapshot |
| 6095 | @cindex find trace snapshot |
| 6096 | The basic command for selecting a trace snapshot from the buffer is |
| 6097 | @code{tfind @var{n}}, which finds trace snapshot number @var{n}, |
| 6098 | counting from zero. If no argument @var{n} is given, the next |
| 6099 | snapshot is selected. |
| 6100 | |
| 6101 | Here are the various forms of using the @code{tfind} command. |
| 6102 | |
| 6103 | @table @code |
| 6104 | @item tfind start |
| 6105 | Find the first snapshot in the buffer. This is a synonym for |
| 6106 | @code{tfind 0} (since 0 is the number of the first snapshot). |
| 6107 | |
| 6108 | @item tfind none |
| 6109 | Stop debugging trace snapshots, resume @emph{live} debugging. |
| 6110 | |
| 6111 | @item tfind end |
| 6112 | Same as @samp{tfind none}. |
| 6113 | |
| 6114 | @item tfind |
| 6115 | No argument means find the next trace snapshot. |
| 6116 | |
| 6117 | @item tfind - |
| 6118 | Find the previous trace snapshot before the current one. This permits |
| 6119 | retracing earlier steps. |
| 6120 | |
| 6121 | @item tfind tracepoint @var{num} |
| 6122 | Find the next snapshot associated with tracepoint @var{num}. Search |
| 6123 | proceeds forward from the last examined trace snapshot. If no |
| 6124 | argument @var{num} is given, it means find the next snapshot collected |
| 6125 | for the same tracepoint as the current snapshot. |
| 6126 | |
| 6127 | @item tfind pc @var{addr} |
| 6128 | Find the next snapshot associated with the value @var{addr} of the |
| 6129 | program counter. Search proceeds forward from the last examined trace |
| 6130 | snapshot. If no argument @var{addr} is given, it means find the next |
| 6131 | snapshot with the same value of PC as the current snapshot. |
| 6132 | |
| 6133 | @item tfind outside @var{addr1}, @var{addr2} |
| 6134 | Find the next snapshot whose PC is outside the given range of |
| 6135 | addresses. |
| 6136 | |
| 6137 | @item tfind range @var{addr1}, @var{addr2} |
| 6138 | Find the next snapshot whose PC is between @var{addr1} and |
| 6139 | @var{addr2}. @c FIXME: Is the range inclusive or exclusive? |
| 6140 | |
| 6141 | @item tfind line @r{[}@var{file}:@r{]}@var{n} |
| 6142 | Find the next snapshot associated with the source line @var{n}. If |
| 6143 | the optional argument @var{file} is given, refer to line @var{n} in |
| 6144 | that source file. Search proceeds forward from the last examined |
| 6145 | trace snapshot. If no argument @var{n} is given, it means find the |
| 6146 | next line other than the one currently being examined; thus saying |
| 6147 | @code{tfind line} repeatedly can appear to have the same effect as |
| 6148 | stepping from line to line in a @emph{live} debugging session. |
| 6149 | @end table |
| 6150 | |
| 6151 | The default arguments for the @code{tfind} commands are specifically |
| 6152 | designed to make it easy to scan through the trace buffer. For |
| 6153 | instance, @code{tfind} with no argument selects the next trace |
| 6154 | snapshot, and @code{tfind -} with no argument selects the previous |
| 6155 | trace snapshot. So, by giving one @code{tfind} command, and then |
| 6156 | simply hitting @key{RET} repeatedly you can examine all the trace |
| 6157 | snapshots in order. Or, by saying @code{tfind -} and then hitting |
| 6158 | @key{RET} repeatedly you can examine the snapshots in reverse order. |
| 6159 | The @code{tfind line} command with no argument selects the snapshot |
| 6160 | for the next source line executed. The @code{tfind pc} command with |
| 6161 | no argument selects the next snapshot with the same program counter |
| 6162 | (PC) as the current frame. The @code{tfind tracepoint} command with |
| 6163 | no argument selects the next trace snapshot collected by the same |
| 6164 | tracepoint as the current one. |
| 6165 | |
| 6166 | In addition to letting you scan through the trace buffer manually, |
| 6167 | these commands make it easy to construct @value{GDBN} scripts that |
| 6168 | scan through the trace buffer and print out whatever collected data |
| 6169 | you are interested in. Thus, if we want to examine the PC, FP, and SP |
| 6170 | registers from each trace frame in the buffer, we can say this: |
| 6171 | |
| 6172 | @smallexample |
| 6173 | (@value{GDBP}) @b{tfind start} |
| 6174 | (@value{GDBP}) @b{while ($trace_frame != -1)} |
| 6175 | > printf "Frame %d, PC = %08X, SP = %08X, FP = %08X\n", \ |
| 6176 | $trace_frame, $pc, $sp, $fp |
| 6177 | > tfind |
| 6178 | > end |
| 6179 | |
| 6180 | Frame 0, PC = 0020DC64, SP = 0030BF3C, FP = 0030BF44 |
| 6181 | Frame 1, PC = 0020DC6C, SP = 0030BF38, FP = 0030BF44 |
| 6182 | Frame 2, PC = 0020DC70, SP = 0030BF34, FP = 0030BF44 |
| 6183 | Frame 3, PC = 0020DC74, SP = 0030BF30, FP = 0030BF44 |
| 6184 | Frame 4, PC = 0020DC78, SP = 0030BF2C, FP = 0030BF44 |
| 6185 | Frame 5, PC = 0020DC7C, SP = 0030BF28, FP = 0030BF44 |
| 6186 | Frame 6, PC = 0020DC80, SP = 0030BF24, FP = 0030BF44 |
| 6187 | Frame 7, PC = 0020DC84, SP = 0030BF20, FP = 0030BF44 |
| 6188 | Frame 8, PC = 0020DC88, SP = 0030BF1C, FP = 0030BF44 |
| 6189 | Frame 9, PC = 0020DC8E, SP = 0030BF18, FP = 0030BF44 |
| 6190 | Frame 10, PC = 00203F6C, SP = 0030BE3C, FP = 0030BF14 |
| 6191 | @end smallexample |
| 6192 | |
| 6193 | Or, if we want to examine the variable @code{X} at each source line in |
| 6194 | the buffer: |
| 6195 | |
| 6196 | @smallexample |
| 6197 | (@value{GDBP}) @b{tfind start} |
| 6198 | (@value{GDBP}) @b{while ($trace_frame != -1)} |
| 6199 | > printf "Frame %d, X == %d\n", $trace_frame, X |
| 6200 | > tfind line |
| 6201 | > end |
| 6202 | |
| 6203 | Frame 0, X = 1 |
| 6204 | Frame 7, X = 2 |
| 6205 | Frame 13, X = 255 |
| 6206 | @end smallexample |
| 6207 | |
| 6208 | @node tdump |
| 6209 | @subsection @code{tdump} |
| 6210 | @kindex tdump |
| 6211 | @cindex dump all data collected at tracepoint |
| 6212 | @cindex tracepoint data, display |
| 6213 | |
| 6214 | This command takes no arguments. It prints all the data collected at |
| 6215 | the current trace snapshot. |
| 6216 | |
| 6217 | @smallexample |
| 6218 | (@value{GDBP}) @b{trace 444} |
| 6219 | (@value{GDBP}) @b{actions} |
| 6220 | Enter actions for tracepoint #2, one per line: |
| 6221 | > collect $regs, $locals, $args, gdb_long_test |
| 6222 | > end |
| 6223 | |
| 6224 | (@value{GDBP}) @b{tstart} |
| 6225 | |
| 6226 | (@value{GDBP}) @b{tfind line 444} |
| 6227 | #0 gdb_test (p1=0x11, p2=0x22, p3=0x33, p4=0x44, p5=0x55, p6=0x66) |
| 6228 | at gdb_test.c:444 |
| 6229 | 444 printp( "%s: arguments = 0x%X 0x%X 0x%X 0x%X 0x%X 0x%X\n", ) |
| 6230 | |
| 6231 | (@value{GDBP}) @b{tdump} |
| 6232 | Data collected at tracepoint 2, trace frame 1: |
| 6233 | d0 0xc4aa0085 -995491707 |
| 6234 | d1 0x18 24 |
| 6235 | d2 0x80 128 |
| 6236 | d3 0x33 51 |
| 6237 | d4 0x71aea3d 119204413 |
| 6238 | d5 0x22 34 |
| 6239 | d6 0xe0 224 |
| 6240 | d7 0x380035 3670069 |
| 6241 | a0 0x19e24a 1696330 |
| 6242 | a1 0x3000668 50333288 |
| 6243 | a2 0x100 256 |
| 6244 | a3 0x322000 3284992 |
| 6245 | a4 0x3000698 50333336 |
| 6246 | a5 0x1ad3cc 1758156 |
| 6247 | fp 0x30bf3c 0x30bf3c |
| 6248 | sp 0x30bf34 0x30bf34 |
| 6249 | ps 0x0 0 |
| 6250 | pc 0x20b2c8 0x20b2c8 |
| 6251 | fpcontrol 0x0 0 |
| 6252 | fpstatus 0x0 0 |
| 6253 | fpiaddr 0x0 0 |
| 6254 | p = 0x20e5b4 "gdb-test" |
| 6255 | p1 = (void *) 0x11 |
| 6256 | p2 = (void *) 0x22 |
| 6257 | p3 = (void *) 0x33 |
| 6258 | p4 = (void *) 0x44 |
| 6259 | p5 = (void *) 0x55 |
| 6260 | p6 = (void *) 0x66 |
| 6261 | gdb_long_test = 17 '\021' |
| 6262 | |
| 6263 | (@value{GDBP}) |
| 6264 | @end smallexample |
| 6265 | |
| 6266 | @node save-tracepoints |
| 6267 | @subsection @code{save-tracepoints @var{filename}} |
| 6268 | @kindex save-tracepoints |
| 6269 | @cindex save tracepoints for future sessions |
| 6270 | |
| 6271 | This command saves all current tracepoint definitions together with |
| 6272 | their actions and passcounts, into a file @file{@var{filename}} |
| 6273 | suitable for use in a later debugging session. To read the saved |
| 6274 | tracepoint definitions, use the @code{source} command (@pxref{Command |
| 6275 | Files}). |
| 6276 | |
| 6277 | @node Tracepoint Variables |
| 6278 | @section Convenience Variables for Tracepoints |
| 6279 | @cindex tracepoint variables |
| 6280 | @cindex convenience variables for tracepoints |
| 6281 | |
| 6282 | @table @code |
| 6283 | @vindex $trace_frame |
| 6284 | @item (int) $trace_frame |
| 6285 | The current trace snapshot (a.k.a.@: @dfn{frame}) number, or -1 if no |
| 6286 | snapshot is selected. |
| 6287 | |
| 6288 | @vindex $tracepoint |
| 6289 | @item (int) $tracepoint |
| 6290 | The tracepoint for the current trace snapshot. |
| 6291 | |
| 6292 | @vindex $trace_line |
| 6293 | @item (int) $trace_line |
| 6294 | The line number for the current trace snapshot. |
| 6295 | |
| 6296 | @vindex $trace_file |
| 6297 | @item (char []) $trace_file |
| 6298 | The source file for the current trace snapshot. |
| 6299 | |
| 6300 | @vindex $trace_func |
| 6301 | @item (char []) $trace_func |
| 6302 | The name of the function containing @code{$tracepoint}. |
| 6303 | @end table |
| 6304 | |
| 6305 | Note: @code{$trace_file} is not suitable for use in @code{printf}, |
| 6306 | use @code{output} instead. |
| 6307 | |
| 6308 | Here's a simple example of using these convenience variables for |
| 6309 | stepping through all the trace snapshots and printing some of their |
| 6310 | data. |
| 6311 | |
| 6312 | @smallexample |
| 6313 | (@value{GDBP}) @b{tfind start} |
| 6314 | |
| 6315 | (@value{GDBP}) @b{while $trace_frame != -1} |
| 6316 | > output $trace_file |
| 6317 | > printf ", line %d (tracepoint #%d)\n", $trace_line, $tracepoint |
| 6318 | > tfind |
| 6319 | > end |
| 6320 | @end smallexample |
| 6321 | |
| 6322 | @node Overlays |
| 6323 | @chapter Debugging Programs That Use Overlays |
| 6324 | @cindex overlays |
| 6325 | |
| 6326 | If your program is too large to fit completely in your target system's |
| 6327 | memory, you can sometimes use @dfn{overlays} to work around this |
| 6328 | problem. @value{GDBN} provides some support for debugging programs that |
| 6329 | use overlays. |
| 6330 | |
| 6331 | @menu |
| 6332 | * How Overlays Work:: A general explanation of overlays. |
| 6333 | * Overlay Commands:: Managing overlays in @value{GDBN}. |
| 6334 | * Automatic Overlay Debugging:: @value{GDBN} can find out which overlays are |
| 6335 | mapped by asking the inferior. |
| 6336 | * Overlay Sample Program:: A sample program using overlays. |
| 6337 | @end menu |
| 6338 | |
| 6339 | @node How Overlays Work |
| 6340 | @section How Overlays Work |
| 6341 | @cindex mapped overlays |
| 6342 | @cindex unmapped overlays |
| 6343 | @cindex load address, overlay's |
| 6344 | @cindex mapped address |
| 6345 | @cindex overlay area |
| 6346 | |
| 6347 | Suppose you have a computer whose instruction address space is only 64 |
| 6348 | kilobytes long, but which has much more memory which can be accessed by |
| 6349 | other means: special instructions, segment registers, or memory |
| 6350 | management hardware, for example. Suppose further that you want to |
| 6351 | adapt a program which is larger than 64 kilobytes to run on this system. |
| 6352 | |
| 6353 | One solution is to identify modules of your program which are relatively |
| 6354 | independent, and need not call each other directly; call these modules |
| 6355 | @dfn{overlays}. Separate the overlays from the main program, and place |
| 6356 | their machine code in the larger memory. Place your main program in |
| 6357 | instruction memory, but leave at least enough space there to hold the |
| 6358 | largest overlay as well. |
| 6359 | |
| 6360 | Now, to call a function located in an overlay, you must first copy that |
| 6361 | overlay's machine code from the large memory into the space set aside |
| 6362 | for it in the instruction memory, and then jump to its entry point |
| 6363 | there. |
| 6364 | |
| 6365 | @c NB: In the below the mapped area's size is greater or equal to the |
| 6366 | @c size of all overlays. This is intentional to remind the developer |
| 6367 | @c that overlays don't necessarily need to be the same size. |
| 6368 | |
| 6369 | @example |
| 6370 | @group |
| 6371 | Data Instruction Larger |
| 6372 | Address Space Address Space Address Space |
| 6373 | +-----------+ +-----------+ +-----------+ |
| 6374 | | | | | | | |
| 6375 | +-----------+ +-----------+ +-----------+<-- overlay 1 |
| 6376 | | program | | main | .----| overlay 1 | load address |
| 6377 | | variables | | program | | +-----------+ |
| 6378 | | and heap | | | | | | |
| 6379 | +-----------+ | | | +-----------+<-- overlay 2 |
| 6380 | | | +-----------+ | | | load address |
| 6381 | +-----------+ | | | .-| overlay 2 | |
| 6382 | | | | | | | |
| 6383 | mapped --->+-----------+ | | +-----------+ |
| 6384 | address | | | | | | |
| 6385 | | overlay | <-' | | | |
| 6386 | | area | <---' +-----------+<-- overlay 3 |
| 6387 | | | <---. | | load address |
| 6388 | +-----------+ `--| overlay 3 | |
| 6389 | | | | | |
| 6390 | +-----------+ | | |
| 6391 | +-----------+ |
| 6392 | | | |
| 6393 | +-----------+ |
| 6394 | |
| 6395 | @anchor{A code overlay}A code overlay |
| 6396 | @end group |
| 6397 | @end example |
| 6398 | |
| 6399 | The diagram (@pxref{A code overlay}) shows a system with separate data |
| 6400 | and instruction address spaces. To map an overlay, the program copies |
| 6401 | its code from the larger address space to the instruction address space. |
| 6402 | Since the overlays shown here all use the same mapped address, only one |
| 6403 | may be mapped at a time. For a system with a single address space for |
| 6404 | data and instructions, the diagram would be similar, except that the |
| 6405 | program variables and heap would share an address space with the main |
| 6406 | program and the overlay area. |
| 6407 | |
| 6408 | An overlay loaded into instruction memory and ready for use is called a |
| 6409 | @dfn{mapped} overlay; its @dfn{mapped address} is its address in the |
| 6410 | instruction memory. An overlay not present (or only partially present) |
| 6411 | in instruction memory is called @dfn{unmapped}; its @dfn{load address} |
| 6412 | is its address in the larger memory. The mapped address is also called |
| 6413 | the @dfn{virtual memory address}, or @dfn{VMA}; the load address is also |
| 6414 | called the @dfn{load memory address}, or @dfn{LMA}. |
| 6415 | |
| 6416 | Unfortunately, overlays are not a completely transparent way to adapt a |
| 6417 | program to limited instruction memory. They introduce a new set of |
| 6418 | global constraints you must keep in mind as you design your program: |
| 6419 | |
| 6420 | @itemize @bullet |
| 6421 | |
| 6422 | @item |
| 6423 | Before calling or returning to a function in an overlay, your program |
| 6424 | must make sure that overlay is actually mapped. Otherwise, the call or |
| 6425 | return will transfer control to the right address, but in the wrong |
| 6426 | overlay, and your program will probably crash. |
| 6427 | |
| 6428 | @item |
| 6429 | If the process of mapping an overlay is expensive on your system, you |
| 6430 | will need to choose your overlays carefully to minimize their effect on |
| 6431 | your program's performance. |
| 6432 | |
| 6433 | @item |
| 6434 | The executable file you load onto your system must contain each |
| 6435 | overlay's instructions, appearing at the overlay's load address, not its |
| 6436 | mapped address. However, each overlay's instructions must be relocated |
| 6437 | and its symbols defined as if the overlay were at its mapped address. |
| 6438 | You can use GNU linker scripts to specify different load and relocation |
| 6439 | addresses for pieces of your program; see @ref{Overlay Description,,, |
| 6440 | ld.info, Using ld: the GNU linker}. |
| 6441 | |
| 6442 | @item |
| 6443 | The procedure for loading executable files onto your system must be able |
| 6444 | to load their contents into the larger address space as well as the |
| 6445 | instruction and data spaces. |
| 6446 | |
| 6447 | @end itemize |
| 6448 | |
| 6449 | The overlay system described above is rather simple, and could be |
| 6450 | improved in many ways: |
| 6451 | |
| 6452 | @itemize @bullet |
| 6453 | |
| 6454 | @item |
| 6455 | If your system has suitable bank switch registers or memory management |
| 6456 | hardware, you could use those facilities to make an overlay's load area |
| 6457 | contents simply appear at their mapped address in instruction space. |
| 6458 | This would probably be faster than copying the overlay to its mapped |
| 6459 | area in the usual way. |
| 6460 | |
| 6461 | @item |
| 6462 | If your overlays are small enough, you could set aside more than one |
| 6463 | overlay area, and have more than one overlay mapped at a time. |
| 6464 | |
| 6465 | @item |
| 6466 | You can use overlays to manage data, as well as instructions. In |
| 6467 | general, data overlays are even less transparent to your design than |
| 6468 | code overlays: whereas code overlays only require care when you call or |
| 6469 | return to functions, data overlays require care every time you access |
| 6470 | the data. Also, if you change the contents of a data overlay, you |
| 6471 | must copy its contents back out to its load address before you can copy a |
| 6472 | different data overlay into the same mapped area. |
| 6473 | |
| 6474 | @end itemize |
| 6475 | |
| 6476 | |
| 6477 | @node Overlay Commands |
| 6478 | @section Overlay Commands |
| 6479 | |
| 6480 | To use @value{GDBN}'s overlay support, each overlay in your program must |
| 6481 | correspond to a separate section of the executable file. The section's |
| 6482 | virtual memory address and load memory address must be the overlay's |
| 6483 | mapped and load addresses. Identifying overlays with sections allows |
| 6484 | @value{GDBN} to determine the appropriate address of a function or |
| 6485 | variable, depending on whether the overlay is mapped or not. |
| 6486 | |
| 6487 | @value{GDBN}'s overlay commands all start with the word @code{overlay}; |
| 6488 | you can abbreviate this as @code{ov} or @code{ovly}. The commands are: |
| 6489 | |
| 6490 | @table @code |
| 6491 | @item overlay off |
| 6492 | @kindex overlay off |
| 6493 | Disable @value{GDBN}'s overlay support. When overlay support is |
| 6494 | disabled, @value{GDBN} assumes that all functions and variables are |
| 6495 | always present at their mapped addresses. By default, @value{GDBN}'s |
| 6496 | overlay support is disabled. |
| 6497 | |
| 6498 | @item overlay manual |
| 6499 | @kindex overlay manual |
| 6500 | @cindex manual overlay debugging |
| 6501 | Enable @dfn{manual} overlay debugging. In this mode, @value{GDBN} |
| 6502 | relies on you to tell it which overlays are mapped, and which are not, |
| 6503 | using the @code{overlay map-overlay} and @code{overlay unmap-overlay} |
| 6504 | commands described below. |
| 6505 | |
| 6506 | @item overlay map-overlay @var{overlay} |
| 6507 | @itemx overlay map @var{overlay} |
| 6508 | @kindex overlay map-overlay |
| 6509 | @cindex map an overlay |
| 6510 | Tell @value{GDBN} that @var{overlay} is now mapped; @var{overlay} must |
| 6511 | be the name of the object file section containing the overlay. When an |
| 6512 | overlay is mapped, @value{GDBN} assumes it can find the overlay's |
| 6513 | functions and variables at their mapped addresses. @value{GDBN} assumes |
| 6514 | that any other overlays whose mapped ranges overlap that of |
| 6515 | @var{overlay} are now unmapped. |
| 6516 | |
| 6517 | @item overlay unmap-overlay @var{overlay} |
| 6518 | @itemx overlay unmap @var{overlay} |
| 6519 | @kindex overlay unmap-overlay |
| 6520 | @cindex unmap an overlay |
| 6521 | Tell @value{GDBN} that @var{overlay} is no longer mapped; @var{overlay} |
| 6522 | must be the name of the object file section containing the overlay. |
| 6523 | When an overlay is unmapped, @value{GDBN} assumes it can find the |
| 6524 | overlay's functions and variables at their load addresses. |
| 6525 | |
| 6526 | @item overlay auto |
| 6527 | @kindex overlay auto |
| 6528 | Enable @dfn{automatic} overlay debugging. In this mode, @value{GDBN} |
| 6529 | consults a data structure the overlay manager maintains in the inferior |
| 6530 | to see which overlays are mapped. For details, see @ref{Automatic |
| 6531 | Overlay Debugging}. |
| 6532 | |
| 6533 | @item overlay load-target |
| 6534 | @itemx overlay load |
| 6535 | @kindex overlay load-target |
| 6536 | @cindex reloading the overlay table |
| 6537 | Re-read the overlay table from the inferior. Normally, @value{GDBN} |
| 6538 | re-reads the table @value{GDBN} automatically each time the inferior |
| 6539 | stops, so this command should only be necessary if you have changed the |
| 6540 | overlay mapping yourself using @value{GDBN}. This command is only |
| 6541 | useful when using automatic overlay debugging. |
| 6542 | |
| 6543 | @item overlay list-overlays |
| 6544 | @itemx overlay list |
| 6545 | @cindex listing mapped overlays |
| 6546 | Display a list of the overlays currently mapped, along with their mapped |
| 6547 | addresses, load addresses, and sizes. |
| 6548 | |
| 6549 | @end table |
| 6550 | |
| 6551 | Normally, when @value{GDBN} prints a code address, it includes the name |
| 6552 | of the function the address falls in: |
| 6553 | |
| 6554 | @example |
| 6555 | (gdb) print main |
| 6556 | $3 = @{int ()@} 0x11a0 <main> |
| 6557 | @end example |
| 6558 | @noindent |
| 6559 | When overlay debugging is enabled, @value{GDBN} recognizes code in |
| 6560 | unmapped overlays, and prints the names of unmapped functions with |
| 6561 | asterisks around them. For example, if @code{foo} is a function in an |
| 6562 | unmapped overlay, @value{GDBN} prints it this way: |
| 6563 | |
| 6564 | @example |
| 6565 | (gdb) overlay list |
| 6566 | No sections are mapped. |
| 6567 | (gdb) print foo |
| 6568 | $5 = @{int (int)@} 0x100000 <*foo*> |
| 6569 | @end example |
| 6570 | @noindent |
| 6571 | When @code{foo}'s overlay is mapped, @value{GDBN} prints the function's |
| 6572 | name normally: |
| 6573 | |
| 6574 | @example |
| 6575 | (gdb) overlay list |
| 6576 | Section .ov.foo.text, loaded at 0x100000 - 0x100034, |
| 6577 | mapped at 0x1016 - 0x104a |
| 6578 | (gdb) print foo |
| 6579 | $6 = @{int (int)@} 0x1016 <foo> |
| 6580 | @end example |
| 6581 | |
| 6582 | When overlay debugging is enabled, @value{GDBN} can find the correct |
| 6583 | address for functions and variables in an overlay, whether or not the |
| 6584 | overlay is mapped. This allows most @value{GDBN} commands, like |
| 6585 | @code{break} and @code{disassemble}, to work normally, even on unmapped |
| 6586 | code. However, @value{GDBN}'s breakpoint support has some limitations: |
| 6587 | |
| 6588 | @itemize @bullet |
| 6589 | @item |
| 6590 | @cindex breakpoints in overlays |
| 6591 | @cindex overlays, setting breakpoints in |
| 6592 | You can set breakpoints in functions in unmapped overlays, as long as |
| 6593 | @value{GDBN} can write to the overlay at its load address. |
| 6594 | @item |
| 6595 | @value{GDBN} can not set hardware or simulator-based breakpoints in |
| 6596 | unmapped overlays. However, if you set a breakpoint at the end of your |
| 6597 | overlay manager (and tell @value{GDBN} which overlays are now mapped, if |
| 6598 | you are using manual overlay management), @value{GDBN} will re-set its |
| 6599 | breakpoints properly. |
| 6600 | @end itemize |
| 6601 | |
| 6602 | |
| 6603 | @node Automatic Overlay Debugging |
| 6604 | @section Automatic Overlay Debugging |
| 6605 | @cindex automatic overlay debugging |
| 6606 | |
| 6607 | @value{GDBN} can automatically track which overlays are mapped and which |
| 6608 | are not, given some simple co-operation from the overlay manager in the |
| 6609 | inferior. If you enable automatic overlay debugging with the |
| 6610 | @code{overlay auto} command (@pxref{Overlay Commands}), @value{GDBN} |
| 6611 | looks in the inferior's memory for certain variables describing the |
| 6612 | current state of the overlays. |
| 6613 | |
| 6614 | Here are the variables your overlay manager must define to support |
| 6615 | @value{GDBN}'s automatic overlay debugging: |
| 6616 | |
| 6617 | @table @asis |
| 6618 | |
| 6619 | @item @code{_ovly_table}: |
| 6620 | This variable must be an array of the following structures: |
| 6621 | |
| 6622 | @example |
| 6623 | struct |
| 6624 | @{ |
| 6625 | /* The overlay's mapped address. */ |
| 6626 | unsigned long vma; |
| 6627 | |
| 6628 | /* The size of the overlay, in bytes. */ |
| 6629 | unsigned long size; |
| 6630 | |
| 6631 | /* The overlay's load address. */ |
| 6632 | unsigned long lma; |
| 6633 | |
| 6634 | /* Non-zero if the overlay is currently mapped; |
| 6635 | zero otherwise. */ |
| 6636 | unsigned long mapped; |
| 6637 | @} |
| 6638 | @end example |
| 6639 | |
| 6640 | @item @code{_novlys}: |
| 6641 | This variable must be a four-byte signed integer, holding the total |
| 6642 | number of elements in @code{_ovly_table}. |
| 6643 | |
| 6644 | @end table |
| 6645 | |
| 6646 | To decide whether a particular overlay is mapped or not, @value{GDBN} |
| 6647 | looks for an entry in @w{@code{_ovly_table}} whose @code{vma} and |
| 6648 | @code{lma} members equal the VMA and LMA of the overlay's section in the |
| 6649 | executable file. When @value{GDBN} finds a matching entry, it consults |
| 6650 | the entry's @code{mapped} member to determine whether the overlay is |
| 6651 | currently mapped. |
| 6652 | |
| 6653 | In addition, your overlay manager may define a function called |
| 6654 | @code{_ovly_debug_event}. If this function is defined, @value{GDBN} |
| 6655 | will silently set a breakpoint there. If the overlay manager then |
| 6656 | calls this function whenever it has changed the overlay table, this |
| 6657 | will enable @value{GDBN} to accurately keep track of which overlays |
| 6658 | are in program memory, and update any breakpoints that may be set |
| 6659 | in overlays. This will allow breakpoints to work even if the |
| 6660 | overlays are kept in ROM or other non-writable memory while they |
| 6661 | are not being executed. |
| 6662 | |
| 6663 | @node Overlay Sample Program |
| 6664 | @section Overlay Sample Program |
| 6665 | @cindex overlay example program |
| 6666 | |
| 6667 | When linking a program which uses overlays, you must place the overlays |
| 6668 | at their load addresses, while relocating them to run at their mapped |
| 6669 | addresses. To do this, you must write a linker script (@pxref{Overlay |
| 6670 | Description,,, ld.info, Using ld: the GNU linker}). Unfortunately, |
| 6671 | since linker scripts are specific to a particular host system, target |
| 6672 | architecture, and target memory layout, this manual cannot provide |
| 6673 | portable sample code demonstrating @value{GDBN}'s overlay support. |
| 6674 | |
| 6675 | However, the @value{GDBN} source distribution does contain an overlaid |
| 6676 | program, with linker scripts for a few systems, as part of its test |
| 6677 | suite. The program consists of the following files from |
| 6678 | @file{gdb/testsuite/gdb.base}: |
| 6679 | |
| 6680 | @table @file |
| 6681 | @item overlays.c |
| 6682 | The main program file. |
| 6683 | @item ovlymgr.c |
| 6684 | A simple overlay manager, used by @file{overlays.c}. |
| 6685 | @item foo.c |
| 6686 | @itemx bar.c |
| 6687 | @itemx baz.c |
| 6688 | @itemx grbx.c |
| 6689 | Overlay modules, loaded and used by @file{overlays.c}. |
| 6690 | @item d10v.ld |
| 6691 | @itemx m32r.ld |
| 6692 | Linker scripts for linking the test program on the @code{d10v-elf} |
| 6693 | and @code{m32r-elf} targets. |
| 6694 | @end table |
| 6695 | |
| 6696 | You can build the test program using the @code{d10v-elf} GCC |
| 6697 | cross-compiler like this: |
| 6698 | |
| 6699 | @example |
| 6700 | $ d10v-elf-gcc -g -c overlays.c |
| 6701 | $ d10v-elf-gcc -g -c ovlymgr.c |
| 6702 | $ d10v-elf-gcc -g -c foo.c |
| 6703 | $ d10v-elf-gcc -g -c bar.c |
| 6704 | $ d10v-elf-gcc -g -c baz.c |
| 6705 | $ d10v-elf-gcc -g -c grbx.c |
| 6706 | $ d10v-elf-gcc -g overlays.o ovlymgr.o foo.o bar.o \ |
| 6707 | baz.o grbx.o -Wl,-Td10v.ld -o overlays |
| 6708 | @end example |
| 6709 | |
| 6710 | The build process is identical for any other architecture, except that |
| 6711 | you must substitute the appropriate compiler and linker script for the |
| 6712 | target system for @code{d10v-elf-gcc} and @code{d10v.ld}. |
| 6713 | |
| 6714 | |
| 6715 | @node Languages |
| 6716 | @chapter Using @value{GDBN} with Different Languages |
| 6717 | @cindex languages |
| 6718 | |
| 6719 | Although programming languages generally have common aspects, they are |
| 6720 | rarely expressed in the same manner. For instance, in ANSI C, |
| 6721 | dereferencing a pointer @code{p} is accomplished by @code{*p}, but in |
| 6722 | Modula-2, it is accomplished by @code{p^}. Values can also be |
| 6723 | represented (and displayed) differently. Hex numbers in C appear as |
| 6724 | @samp{0x1ae}, while in Modula-2 they appear as @samp{1AEH}. |
| 6725 | |
| 6726 | @cindex working language |
| 6727 | Language-specific information is built into @value{GDBN} for some languages, |
| 6728 | allowing you to express operations like the above in your program's |
| 6729 | native language, and allowing @value{GDBN} to output values in a manner |
| 6730 | consistent with the syntax of your program's native language. The |
| 6731 | language you use to build expressions is called the @dfn{working |
| 6732 | language}. |
| 6733 | |
| 6734 | @menu |
| 6735 | * Setting:: Switching between source languages |
| 6736 | * Show:: Displaying the language |
| 6737 | * Checks:: Type and range checks |
| 6738 | * Support:: Supported languages |
| 6739 | @end menu |
| 6740 | |
| 6741 | @node Setting |
| 6742 | @section Switching between source languages |
| 6743 | |
| 6744 | There are two ways to control the working language---either have @value{GDBN} |
| 6745 | set it automatically, or select it manually yourself. You can use the |
| 6746 | @code{set language} command for either purpose. On startup, @value{GDBN} |
| 6747 | defaults to setting the language automatically. The working language is |
| 6748 | used to determine how expressions you type are interpreted, how values |
| 6749 | are printed, etc. |
| 6750 | |
| 6751 | In addition to the working language, every source file that |
| 6752 | @value{GDBN} knows about has its own working language. For some object |
| 6753 | file formats, the compiler might indicate which language a particular |
| 6754 | source file is in. However, most of the time @value{GDBN} infers the |
| 6755 | language from the name of the file. The language of a source file |
| 6756 | controls whether C@t{++} names are demangled---this way @code{backtrace} can |
| 6757 | show each frame appropriately for its own language. There is no way to |
| 6758 | set the language of a source file from within @value{GDBN}, but you can |
| 6759 | set the language associated with a filename extension. @xref{Show, , |
| 6760 | Displaying the language}. |
| 6761 | |
| 6762 | This is most commonly a problem when you use a program, such |
| 6763 | as @code{cfront} or @code{f2c}, that generates C but is written in |
| 6764 | another language. In that case, make the |
| 6765 | program use @code{#line} directives in its C output; that way |
| 6766 | @value{GDBN} will know the correct language of the source code of the original |
| 6767 | program, and will display that source code, not the generated C code. |
| 6768 | |
| 6769 | @menu |
| 6770 | * Filenames:: Filename extensions and languages. |
| 6771 | * Manually:: Setting the working language manually |
| 6772 | * Automatically:: Having @value{GDBN} infer the source language |
| 6773 | @end menu |
| 6774 | |
| 6775 | @node Filenames |
| 6776 | @subsection List of filename extensions and languages |
| 6777 | |
| 6778 | If a source file name ends in one of the following extensions, then |
| 6779 | @value{GDBN} infers that its language is the one indicated. |
| 6780 | |
| 6781 | @table @file |
| 6782 | |
| 6783 | @item .c |
| 6784 | C source file |
| 6785 | |
| 6786 | @item .C |
| 6787 | @itemx .cc |
| 6788 | @itemx .cp |
| 6789 | @itemx .cpp |
| 6790 | @itemx .cxx |
| 6791 | @itemx .c++ |
| 6792 | C@t{++} source file |
| 6793 | |
| 6794 | @item .f |
| 6795 | @itemx .F |
| 6796 | Fortran source file |
| 6797 | |
| 6798 | @item .ch |
| 6799 | @itemx .c186 |
| 6800 | @itemx .c286 |
| 6801 | CHILL source file |
| 6802 | |
| 6803 | @item .mod |
| 6804 | Modula-2 source file |
| 6805 | |
| 6806 | @item .s |
| 6807 | @itemx .S |
| 6808 | Assembler source file. This actually behaves almost like C, but |
| 6809 | @value{GDBN} does not skip over function prologues when stepping. |
| 6810 | @end table |
| 6811 | |
| 6812 | In addition, you may set the language associated with a filename |
| 6813 | extension. @xref{Show, , Displaying the language}. |
| 6814 | |
| 6815 | @node Manually |
| 6816 | @subsection Setting the working language |
| 6817 | |
| 6818 | If you allow @value{GDBN} to set the language automatically, |
| 6819 | expressions are interpreted the same way in your debugging session and |
| 6820 | your program. |
| 6821 | |
| 6822 | @kindex set language |
| 6823 | If you wish, you may set the language manually. To do this, issue the |
| 6824 | command @samp{set language @var{lang}}, where @var{lang} is the name of |
| 6825 | a language, such as |
| 6826 | @code{c} or @code{modula-2}. |
| 6827 | For a list of the supported languages, type @samp{set language}. |
| 6828 | |
| 6829 | Setting the language manually prevents @value{GDBN} from updating the working |
| 6830 | language automatically. This can lead to confusion if you try |
| 6831 | to debug a program when the working language is not the same as the |
| 6832 | source language, when an expression is acceptable to both |
| 6833 | languages---but means different things. For instance, if the current |
| 6834 | source file were written in C, and @value{GDBN} was parsing Modula-2, a |
| 6835 | command such as: |
| 6836 | |
| 6837 | @example |
| 6838 | print a = b + c |
| 6839 | @end example |
| 6840 | |
| 6841 | @noindent |
| 6842 | might not have the effect you intended. In C, this means to add |
| 6843 | @code{b} and @code{c} and place the result in @code{a}. The result |
| 6844 | printed would be the value of @code{a}. In Modula-2, this means to compare |
| 6845 | @code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value. |
| 6846 | |
| 6847 | @node Automatically |
| 6848 | @subsection Having @value{GDBN} infer the source language |
| 6849 | |
| 6850 | To have @value{GDBN} set the working language automatically, use |
| 6851 | @samp{set language local} or @samp{set language auto}. @value{GDBN} |
| 6852 | then infers the working language. That is, when your program stops in a |
| 6853 | frame (usually by encountering a breakpoint), @value{GDBN} sets the |
| 6854 | working language to the language recorded for the function in that |
| 6855 | frame. If the language for a frame is unknown (that is, if the function |
| 6856 | or block corresponding to the frame was defined in a source file that |
| 6857 | does not have a recognized extension), the current working language is |
| 6858 | not changed, and @value{GDBN} issues a warning. |
| 6859 | |
| 6860 | This may not seem necessary for most programs, which are written |
| 6861 | entirely in one source language. However, program modules and libraries |
| 6862 | written in one source language can be used by a main program written in |
| 6863 | a different source language. Using @samp{set language auto} in this |
| 6864 | case frees you from having to set the working language manually. |
| 6865 | |
| 6866 | @node Show |
| 6867 | @section Displaying the language |
| 6868 | |
| 6869 | The following commands help you find out which language is the |
| 6870 | working language, and also what language source files were written in. |
| 6871 | |
| 6872 | @kindex show language |
| 6873 | @kindex info frame@r{, show the source language} |
| 6874 | @kindex info source@r{, show the source language} |
| 6875 | @table @code |
| 6876 | @item show language |
| 6877 | Display the current working language. This is the |
| 6878 | language you can use with commands such as @code{print} to |
| 6879 | build and compute expressions that may involve variables in your program. |
| 6880 | |
| 6881 | @item info frame |
| 6882 | Display the source language for this frame. This language becomes the |
| 6883 | working language if you use an identifier from this frame. |
| 6884 | @xref{Frame Info, ,Information about a frame}, to identify the other |
| 6885 | information listed here. |
| 6886 | |
| 6887 | @item info source |
| 6888 | Display the source language of this source file. |
| 6889 | @xref{Symbols, ,Examining the Symbol Table}, to identify the other |
| 6890 | information listed here. |
| 6891 | @end table |
| 6892 | |
| 6893 | In unusual circumstances, you may have source files with extensions |
| 6894 | not in the standard list. You can then set the extension associated |
| 6895 | with a language explicitly: |
| 6896 | |
| 6897 | @kindex set extension-language |
| 6898 | @kindex info extensions |
| 6899 | @table @code |
| 6900 | @item set extension-language @var{.ext} @var{language} |
| 6901 | Set source files with extension @var{.ext} to be assumed to be in |
| 6902 | the source language @var{language}. |
| 6903 | |
| 6904 | @item info extensions |
| 6905 | List all the filename extensions and the associated languages. |
| 6906 | @end table |
| 6907 | |
| 6908 | @node Checks |
| 6909 | @section Type and range checking |
| 6910 | |
| 6911 | @quotation |
| 6912 | @emph{Warning:} In this release, the @value{GDBN} commands for type and range |
| 6913 | checking are included, but they do not yet have any effect. This |
| 6914 | section documents the intended facilities. |
| 6915 | @end quotation |
| 6916 | @c FIXME remove warning when type/range code added |
| 6917 | |
| 6918 | Some languages are designed to guard you against making seemingly common |
| 6919 | errors through a series of compile- and run-time checks. These include |
| 6920 | checking the type of arguments to functions and operators, and making |
| 6921 | sure mathematical overflows are caught at run time. Checks such as |
| 6922 | these help to ensure a program's correctness once it has been compiled |
| 6923 | by eliminating type mismatches, and providing active checks for range |
| 6924 | errors when your program is running. |
| 6925 | |
| 6926 | @value{GDBN} can check for conditions like the above if you wish. |
| 6927 | Although @value{GDBN} does not check the statements in your program, it |
| 6928 | can check expressions entered directly into @value{GDBN} for evaluation via |
| 6929 | the @code{print} command, for example. As with the working language, |
| 6930 | @value{GDBN} can also decide whether or not to check automatically based on |
| 6931 | your program's source language. @xref{Support, ,Supported languages}, |
| 6932 | for the default settings of supported languages. |
| 6933 | |
| 6934 | @menu |
| 6935 | * Type Checking:: An overview of type checking |
| 6936 | * Range Checking:: An overview of range checking |
| 6937 | @end menu |
| 6938 | |
| 6939 | @cindex type checking |
| 6940 | @cindex checks, type |
| 6941 | @node Type Checking |
| 6942 | @subsection An overview of type checking |
| 6943 | |
| 6944 | Some languages, such as Modula-2, are strongly typed, meaning that the |
| 6945 | arguments to operators and functions have to be of the correct type, |
| 6946 | otherwise an error occurs. These checks prevent type mismatch |
| 6947 | errors from ever causing any run-time problems. For example, |
| 6948 | |
| 6949 | @smallexample |
| 6950 | 1 + 2 @result{} 3 |
| 6951 | @exdent but |
| 6952 | @error{} 1 + 2.3 |
| 6953 | @end smallexample |
| 6954 | |
| 6955 | The second example fails because the @code{CARDINAL} 1 is not |
| 6956 | type-compatible with the @code{REAL} 2.3. |
| 6957 | |
| 6958 | For the expressions you use in @value{GDBN} commands, you can tell the |
| 6959 | @value{GDBN} type checker to skip checking; |
| 6960 | to treat any mismatches as errors and abandon the expression; |
| 6961 | or to only issue warnings when type mismatches occur, |
| 6962 | but evaluate the expression anyway. When you choose the last of |
| 6963 | these, @value{GDBN} evaluates expressions like the second example above, but |
| 6964 | also issues a warning. |
| 6965 | |
| 6966 | Even if you turn type checking off, there may be other reasons |
| 6967 | related to type that prevent @value{GDBN} from evaluating an expression. |
| 6968 | For instance, @value{GDBN} does not know how to add an @code{int} and |
| 6969 | a @code{struct foo}. These particular type errors have nothing to do |
| 6970 | with the language in use, and usually arise from expressions, such as |
| 6971 | the one described above, which make little sense to evaluate anyway. |
| 6972 | |
| 6973 | Each language defines to what degree it is strict about type. For |
| 6974 | instance, both Modula-2 and C require the arguments to arithmetical |
| 6975 | operators to be numbers. In C, enumerated types and pointers can be |
| 6976 | represented as numbers, so that they are valid arguments to mathematical |
| 6977 | operators. @xref{Support, ,Supported languages}, for further |
| 6978 | details on specific languages. |
| 6979 | |
| 6980 | @value{GDBN} provides some additional commands for controlling the type checker: |
| 6981 | |
| 6982 | @kindex set check@r{, type} |
| 6983 | @kindex set check type |
| 6984 | @kindex show check type |
| 6985 | @table @code |
| 6986 | @item set check type auto |
| 6987 | Set type checking on or off based on the current working language. |
| 6988 | @xref{Support, ,Supported languages}, for the default settings for |
| 6989 | each language. |
| 6990 | |
| 6991 | @item set check type on |
| 6992 | @itemx set check type off |
| 6993 | Set type checking on or off, overriding the default setting for the |
| 6994 | current working language. Issue a warning if the setting does not |
| 6995 | match the language default. If any type mismatches occur in |
| 6996 | evaluating an expression while type checking is on, @value{GDBN} prints a |
| 6997 | message and aborts evaluation of the expression. |
| 6998 | |
| 6999 | @item set check type warn |
| 7000 | Cause the type checker to issue warnings, but to always attempt to |
| 7001 | evaluate the expression. Evaluating the expression may still |
| 7002 | be impossible for other reasons. For example, @value{GDBN} cannot add |
| 7003 | numbers and structures. |
| 7004 | |
| 7005 | @item show type |
| 7006 | Show the current setting of the type checker, and whether or not @value{GDBN} |
| 7007 | is setting it automatically. |
| 7008 | @end table |
| 7009 | |
| 7010 | @cindex range checking |
| 7011 | @cindex checks, range |
| 7012 | @node Range Checking |
| 7013 | @subsection An overview of range checking |
| 7014 | |
| 7015 | In some languages (such as Modula-2), it is an error to exceed the |
| 7016 | bounds of a type; this is enforced with run-time checks. Such range |
| 7017 | checking is meant to ensure program correctness by making sure |
| 7018 | computations do not overflow, or indices on an array element access do |
| 7019 | not exceed the bounds of the array. |
| 7020 | |
| 7021 | For expressions you use in @value{GDBN} commands, you can tell |
| 7022 | @value{GDBN} to treat range errors in one of three ways: ignore them, |
| 7023 | always treat them as errors and abandon the expression, or issue |
| 7024 | warnings but evaluate the expression anyway. |
| 7025 | |
| 7026 | A range error can result from numerical overflow, from exceeding an |
| 7027 | array index bound, or when you type a constant that is not a member |
| 7028 | of any type. Some languages, however, do not treat overflows as an |
| 7029 | error. In many implementations of C, mathematical overflow causes the |
| 7030 | result to ``wrap around'' to lower values---for example, if @var{m} is |
| 7031 | the largest integer value, and @var{s} is the smallest, then |
| 7032 | |
| 7033 | @example |
| 7034 | @var{m} + 1 @result{} @var{s} |
| 7035 | @end example |
| 7036 | |
| 7037 | This, too, is specific to individual languages, and in some cases |
| 7038 | specific to individual compilers or machines. @xref{Support, , |
| 7039 | Supported languages}, for further details on specific languages. |
| 7040 | |
| 7041 | @value{GDBN} provides some additional commands for controlling the range checker: |
| 7042 | |
| 7043 | @kindex set check@r{, range} |
| 7044 | @kindex set check range |
| 7045 | @kindex show check range |
| 7046 | @table @code |
| 7047 | @item set check range auto |
| 7048 | Set range checking on or off based on the current working language. |
| 7049 | @xref{Support, ,Supported languages}, for the default settings for |
| 7050 | each language. |
| 7051 | |
| 7052 | @item set check range on |
| 7053 | @itemx set check range off |
| 7054 | Set range checking on or off, overriding the default setting for the |
| 7055 | current working language. A warning is issued if the setting does not |
| 7056 | match the language default. If a range error occurs and range checking is on, |
| 7057 | then a message is printed and evaluation of the expression is aborted. |
| 7058 | |
| 7059 | @item set check range warn |
| 7060 | Output messages when the @value{GDBN} range checker detects a range error, |
| 7061 | but attempt to evaluate the expression anyway. Evaluating the |
| 7062 | expression may still be impossible for other reasons, such as accessing |
| 7063 | memory that the process does not own (a typical example from many Unix |
| 7064 | systems). |
| 7065 | |
| 7066 | @item show range |
| 7067 | Show the current setting of the range checker, and whether or not it is |
| 7068 | being set automatically by @value{GDBN}. |
| 7069 | @end table |
| 7070 | |
| 7071 | @node Support |
| 7072 | @section Supported languages |
| 7073 | |
| 7074 | @value{GDBN} supports C, C@t{++}, Fortran, Java, Chill, assembly, and Modula-2. |
| 7075 | @c This is false ... |
| 7076 | Some @value{GDBN} features may be used in expressions regardless of the |
| 7077 | language you use: the @value{GDBN} @code{@@} and @code{::} operators, |
| 7078 | and the @samp{@{type@}addr} construct (@pxref{Expressions, |
| 7079 | ,Expressions}) can be used with the constructs of any supported |
| 7080 | language. |
| 7081 | |
| 7082 | The following sections detail to what degree each source language is |
| 7083 | supported by @value{GDBN}. These sections are not meant to be language |
| 7084 | tutorials or references, but serve only as a reference guide to what the |
| 7085 | @value{GDBN} expression parser accepts, and what input and output |
| 7086 | formats should look like for different languages. There are many good |
| 7087 | books written on each of these languages; please look to these for a |
| 7088 | language reference or tutorial. |
| 7089 | |
| 7090 | @menu |
| 7091 | * C:: C and C@t{++} |
| 7092 | * Modula-2:: Modula-2 |
| 7093 | * Chill:: Chill |
| 7094 | @end menu |
| 7095 | |
| 7096 | @node C |
| 7097 | @subsection C and C@t{++} |
| 7098 | |
| 7099 | @cindex C and C@t{++} |
| 7100 | @cindex expressions in C or C@t{++} |
| 7101 | |
| 7102 | Since C and C@t{++} are so closely related, many features of @value{GDBN} apply |
| 7103 | to both languages. Whenever this is the case, we discuss those languages |
| 7104 | together. |
| 7105 | |
| 7106 | @cindex C@t{++} |
| 7107 | @cindex @code{g++}, @sc{gnu} C@t{++} compiler |
| 7108 | @cindex @sc{gnu} C@t{++} |
| 7109 | The C@t{++} debugging facilities are jointly implemented by the C@t{++} |
| 7110 | compiler and @value{GDBN}. Therefore, to debug your C@t{++} code |
| 7111 | effectively, you must compile your C@t{++} programs with a supported |
| 7112 | C@t{++} compiler, such as @sc{gnu} @code{g++}, or the HP ANSI C@t{++} |
| 7113 | compiler (@code{aCC}). |
| 7114 | |
| 7115 | For best results when using @sc{gnu} C@t{++}, use the stabs debugging |
| 7116 | format. You can select that format explicitly with the @code{g++} |
| 7117 | command-line options @samp{-gstabs} or @samp{-gstabs+}. See |
| 7118 | @ref{Debugging Options,,Options for Debugging Your Program or @sc{gnu} |
| 7119 | CC, gcc.info, Using @sc{gnu} CC}, for more information. |
| 7120 | |
| 7121 | @menu |
| 7122 | * C Operators:: C and C@t{++} operators |
| 7123 | * C Constants:: C and C@t{++} constants |
| 7124 | * C plus plus expressions:: C@t{++} expressions |
| 7125 | * C Defaults:: Default settings for C and C@t{++} |
| 7126 | * C Checks:: C and C@t{++} type and range checks |
| 7127 | * Debugging C:: @value{GDBN} and C |
| 7128 | * Debugging C plus plus:: @value{GDBN} features for C@t{++} |
| 7129 | @end menu |
| 7130 | |
| 7131 | @node C Operators |
| 7132 | @subsubsection C and C@t{++} operators |
| 7133 | |
| 7134 | @cindex C and C@t{++} operators |
| 7135 | |
| 7136 | Operators must be defined on values of specific types. For instance, |
| 7137 | @code{+} is defined on numbers, but not on structures. Operators are |
| 7138 | often defined on groups of types. |
| 7139 | |
| 7140 | For the purposes of C and C@t{++}, the following definitions hold: |
| 7141 | |
| 7142 | @itemize @bullet |
| 7143 | |
| 7144 | @item |
| 7145 | @emph{Integral types} include @code{int} with any of its storage-class |
| 7146 | specifiers; @code{char}; @code{enum}; and, for C@t{++}, @code{bool}. |
| 7147 | |
| 7148 | @item |
| 7149 | @emph{Floating-point types} include @code{float}, @code{double}, and |
| 7150 | @code{long double} (if supported by the target platform). |
| 7151 | |
| 7152 | @item |
| 7153 | @emph{Pointer types} include all types defined as @code{(@var{type} *)}. |
| 7154 | |
| 7155 | @item |
| 7156 | @emph{Scalar types} include all of the above. |
| 7157 | |
| 7158 | @end itemize |
| 7159 | |
| 7160 | @noindent |
| 7161 | The following operators are supported. They are listed here |
| 7162 | in order of increasing precedence: |
| 7163 | |
| 7164 | @table @code |
| 7165 | @item , |
| 7166 | The comma or sequencing operator. Expressions in a comma-separated list |
| 7167 | are evaluated from left to right, with the result of the entire |
| 7168 | expression being the last expression evaluated. |
| 7169 | |
| 7170 | @item = |
| 7171 | Assignment. The value of an assignment expression is the value |
| 7172 | assigned. Defined on scalar types. |
| 7173 | |
| 7174 | @item @var{op}= |
| 7175 | Used in an expression of the form @w{@code{@var{a} @var{op}= @var{b}}}, |
| 7176 | and translated to @w{@code{@var{a} = @var{a op b}}}. |
| 7177 | @w{@code{@var{op}=}} and @code{=} have the same precedence. |
| 7178 | @var{op} is any one of the operators @code{|}, @code{^}, @code{&}, |
| 7179 | @code{<<}, @code{>>}, @code{+}, @code{-}, @code{*}, @code{/}, @code{%}. |
| 7180 | |
| 7181 | @item ?: |
| 7182 | The ternary operator. @code{@var{a} ? @var{b} : @var{c}} can be thought |
| 7183 | of as: if @var{a} then @var{b} else @var{c}. @var{a} should be of an |
| 7184 | integral type. |
| 7185 | |
| 7186 | @item || |
| 7187 | Logical @sc{or}. Defined on integral types. |
| 7188 | |
| 7189 | @item && |
| 7190 | Logical @sc{and}. Defined on integral types. |
| 7191 | |
| 7192 | @item | |
| 7193 | Bitwise @sc{or}. Defined on integral types. |
| 7194 | |
| 7195 | @item ^ |
| 7196 | Bitwise exclusive-@sc{or}. Defined on integral types. |
| 7197 | |
| 7198 | @item & |
| 7199 | Bitwise @sc{and}. Defined on integral types. |
| 7200 | |
| 7201 | @item ==@r{, }!= |
| 7202 | Equality and inequality. Defined on scalar types. The value of these |
| 7203 | expressions is 0 for false and non-zero for true. |
| 7204 | |
| 7205 | @item <@r{, }>@r{, }<=@r{, }>= |
| 7206 | Less than, greater than, less than or equal, greater than or equal. |
| 7207 | Defined on scalar types. The value of these expressions is 0 for false |
| 7208 | and non-zero for true. |
| 7209 | |
| 7210 | @item <<@r{, }>> |
| 7211 | left shift, and right shift. Defined on integral types. |
| 7212 | |
| 7213 | @item @@ |
| 7214 | The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}). |
| 7215 | |
| 7216 | @item +@r{, }- |
| 7217 | Addition and subtraction. Defined on integral types, floating-point types and |
| 7218 | pointer types. |
| 7219 | |
| 7220 | @item *@r{, }/@r{, }% |
| 7221 | Multiplication, division, and modulus. Multiplication and division are |
| 7222 | defined on integral and floating-point types. Modulus is defined on |
| 7223 | integral types. |
| 7224 | |
| 7225 | @item ++@r{, }-- |
| 7226 | Increment and decrement. When appearing before a variable, the |
| 7227 | operation is performed before the variable is used in an expression; |
| 7228 | when appearing after it, the variable's value is used before the |
| 7229 | operation takes place. |
| 7230 | |
| 7231 | @item * |
| 7232 | Pointer dereferencing. Defined on pointer types. Same precedence as |
| 7233 | @code{++}. |
| 7234 | |
| 7235 | @item & |
| 7236 | Address operator. Defined on variables. Same precedence as @code{++}. |
| 7237 | |
| 7238 | For debugging C@t{++}, @value{GDBN} implements a use of @samp{&} beyond what is |
| 7239 | allowed in the C@t{++} language itself: you can use @samp{&(&@var{ref})} |
| 7240 | (or, if you prefer, simply @samp{&&@var{ref}}) to examine the address |
| 7241 | where a C@t{++} reference variable (declared with @samp{&@var{ref}}) is |
| 7242 | stored. |
| 7243 | |
| 7244 | @item - |
| 7245 | Negative. Defined on integral and floating-point types. Same |
| 7246 | precedence as @code{++}. |
| 7247 | |
| 7248 | @item ! |
| 7249 | Logical negation. Defined on integral types. Same precedence as |
| 7250 | @code{++}. |
| 7251 | |
| 7252 | @item ~ |
| 7253 | Bitwise complement operator. Defined on integral types. Same precedence as |
| 7254 | @code{++}. |
| 7255 | |
| 7256 | |
| 7257 | @item .@r{, }-> |
| 7258 | Structure member, and pointer-to-structure member. For convenience, |
| 7259 | @value{GDBN} regards the two as equivalent, choosing whether to dereference a |
| 7260 | pointer based on the stored type information. |
| 7261 | Defined on @code{struct} and @code{union} data. |
| 7262 | |
| 7263 | @item .*@r{, }->* |
| 7264 | Dereferences of pointers to members. |
| 7265 | |
| 7266 | @item [] |
| 7267 | Array indexing. @code{@var{a}[@var{i}]} is defined as |
| 7268 | @code{*(@var{a}+@var{i})}. Same precedence as @code{->}. |
| 7269 | |
| 7270 | @item () |
| 7271 | Function parameter list. Same precedence as @code{->}. |
| 7272 | |
| 7273 | @item :: |
| 7274 | C@t{++} scope resolution operator. Defined on @code{struct}, @code{union}, |
| 7275 | and @code{class} types. |
| 7276 | |
| 7277 | @item :: |
| 7278 | Doubled colons also represent the @value{GDBN} scope operator |
| 7279 | (@pxref{Expressions, ,Expressions}). Same precedence as @code{::}, |
| 7280 | above. |
| 7281 | @end table |
| 7282 | |
| 7283 | If an operator is redefined in the user code, @value{GDBN} usually |
| 7284 | attempts to invoke the redefined version instead of using the operator's |
| 7285 | predefined meaning. |
| 7286 | |
| 7287 | @menu |
| 7288 | * C Constants:: |
| 7289 | @end menu |
| 7290 | |
| 7291 | @node C Constants |
| 7292 | @subsubsection C and C@t{++} constants |
| 7293 | |
| 7294 | @cindex C and C@t{++} constants |
| 7295 | |
| 7296 | @value{GDBN} allows you to express the constants of C and C@t{++} in the |
| 7297 | following ways: |
| 7298 | |
| 7299 | @itemize @bullet |
| 7300 | @item |
| 7301 | Integer constants are a sequence of digits. Octal constants are |
| 7302 | specified by a leading @samp{0} (i.e.@: zero), and hexadecimal constants |
| 7303 | by a leading @samp{0x} or @samp{0X}. Constants may also end with a letter |
| 7304 | @samp{l}, specifying that the constant should be treated as a |
| 7305 | @code{long} value. |
| 7306 | |
| 7307 | @item |
| 7308 | Floating point constants are a sequence of digits, followed by a decimal |
| 7309 | point, followed by a sequence of digits, and optionally followed by an |
| 7310 | exponent. An exponent is of the form: |
| 7311 | @samp{@w{e@r{[[}+@r{]|}-@r{]}@var{nnn}}}, where @var{nnn} is another |
| 7312 | sequence of digits. The @samp{+} is optional for positive exponents. |
| 7313 | A floating-point constant may also end with a letter @samp{f} or |
| 7314 | @samp{F}, specifying that the constant should be treated as being of |
| 7315 | the @code{float} (as opposed to the default @code{double}) type; or with |
| 7316 | a letter @samp{l} or @samp{L}, which specifies a @code{long double} |
| 7317 | constant. |
| 7318 | |
| 7319 | @item |
| 7320 | Enumerated constants consist of enumerated identifiers, or their |
| 7321 | integral equivalents. |
| 7322 | |
| 7323 | @item |
| 7324 | Character constants are a single character surrounded by single quotes |
| 7325 | (@code{'}), or a number---the ordinal value of the corresponding character |
| 7326 | (usually its @sc{ascii} value). Within quotes, the single character may |
| 7327 | be represented by a letter or by @dfn{escape sequences}, which are of |
| 7328 | the form @samp{\@var{nnn}}, where @var{nnn} is the octal representation |
| 7329 | of the character's ordinal value; or of the form @samp{\@var{x}}, where |
| 7330 | @samp{@var{x}} is a predefined special character---for example, |
| 7331 | @samp{\n} for newline. |
| 7332 | |
| 7333 | @item |
| 7334 | String constants are a sequence of character constants surrounded by |
| 7335 | double quotes (@code{"}). Any valid character constant (as described |
| 7336 | above) may appear. Double quotes within the string must be preceded by |
| 7337 | a backslash, so for instance @samp{"a\"b'c"} is a string of five |
| 7338 | characters. |
| 7339 | |
| 7340 | @item |
| 7341 | Pointer constants are an integral value. You can also write pointers |
| 7342 | to constants using the C operator @samp{&}. |
| 7343 | |
| 7344 | @item |
| 7345 | Array constants are comma-separated lists surrounded by braces @samp{@{} |
| 7346 | and @samp{@}}; for example, @samp{@{1,2,3@}} is a three-element array of |
| 7347 | integers, @samp{@{@{1,2@}, @{3,4@}, @{5,6@}@}} is a three-by-two array, |
| 7348 | and @samp{@{&"hi", &"there", &"fred"@}} is a three-element array of pointers. |
| 7349 | @end itemize |
| 7350 | |
| 7351 | @menu |
| 7352 | * C plus plus expressions:: |
| 7353 | * C Defaults:: |
| 7354 | * C Checks:: |
| 7355 | |
| 7356 | * Debugging C:: |
| 7357 | @end menu |
| 7358 | |
| 7359 | @node C plus plus expressions |
| 7360 | @subsubsection C@t{++} expressions |
| 7361 | |
| 7362 | @cindex expressions in C@t{++} |
| 7363 | @value{GDBN} expression handling can interpret most C@t{++} expressions. |
| 7364 | |
| 7365 | @cindex C@t{++} support, not in @sc{coff} |
| 7366 | @cindex @sc{coff} versus C@t{++} |
| 7367 | @cindex C@t{++} and object formats |
| 7368 | @cindex object formats and C@t{++} |
| 7369 | @cindex a.out and C@t{++} |
| 7370 | @cindex @sc{ecoff} and C@t{++} |
| 7371 | @cindex @sc{xcoff} and C@t{++} |
| 7372 | @cindex @sc{elf}/stabs and C@t{++} |
| 7373 | @cindex @sc{elf}/@sc{dwarf} and C@t{++} |
| 7374 | @c FIXME!! GDB may eventually be able to debug C++ using DWARF; check |
| 7375 | @c periodically whether this has happened... |
| 7376 | @quotation |
| 7377 | @emph{Warning:} @value{GDBN} can only debug C@t{++} code if you use the |
| 7378 | proper compiler. Typically, C@t{++} debugging depends on the use of |
| 7379 | additional debugging information in the symbol table, and thus requires |
| 7380 | special support. In particular, if your compiler generates a.out, MIPS |
| 7381 | @sc{ecoff}, RS/6000 @sc{xcoff}, or @sc{elf} with stabs extensions to the |
| 7382 | symbol table, these facilities are all available. (With @sc{gnu} CC, |
| 7383 | you can use the @samp{-gstabs} option to request stabs debugging |
| 7384 | extensions explicitly.) Where the object code format is standard |
| 7385 | @sc{coff} or @sc{dwarf} in @sc{elf}, on the other hand, most of the C@t{++} |
| 7386 | support in @value{GDBN} does @emph{not} work. |
| 7387 | @end quotation |
| 7388 | |
| 7389 | @enumerate |
| 7390 | |
| 7391 | @cindex member functions |
| 7392 | @item |
| 7393 | Member function calls are allowed; you can use expressions like |
| 7394 | |
| 7395 | @example |
| 7396 | count = aml->GetOriginal(x, y) |
| 7397 | @end example |
| 7398 | |
| 7399 | @vindex this@r{, inside C@t{++} member functions} |
| 7400 | @cindex namespace in C@t{++} |
| 7401 | @item |
| 7402 | While a member function is active (in the selected stack frame), your |
| 7403 | expressions have the same namespace available as the member function; |
| 7404 | that is, @value{GDBN} allows implicit references to the class instance |
| 7405 | pointer @code{this} following the same rules as C@t{++}. |
| 7406 | |
| 7407 | @cindex call overloaded functions |
| 7408 | @cindex overloaded functions, calling |
| 7409 | @cindex type conversions in C@t{++} |
| 7410 | @item |
| 7411 | You can call overloaded functions; @value{GDBN} resolves the function |
| 7412 | call to the right definition, with some restrictions. @value{GDBN} does not |
| 7413 | perform overload resolution involving user-defined type conversions, |
| 7414 | calls to constructors, or instantiations of templates that do not exist |
| 7415 | in the program. It also cannot handle ellipsis argument lists or |
| 7416 | default arguments. |
| 7417 | |
| 7418 | It does perform integral conversions and promotions, floating-point |
| 7419 | promotions, arithmetic conversions, pointer conversions, conversions of |
| 7420 | class objects to base classes, and standard conversions such as those of |
| 7421 | functions or arrays to pointers; it requires an exact match on the |
| 7422 | number of function arguments. |
| 7423 | |
| 7424 | Overload resolution is always performed, unless you have specified |
| 7425 | @code{set overload-resolution off}. @xref{Debugging C plus plus, |
| 7426 | ,@value{GDBN} features for C@t{++}}. |
| 7427 | |
| 7428 | You must specify @code{set overload-resolution off} in order to use an |
| 7429 | explicit function signature to call an overloaded function, as in |
| 7430 | @smallexample |
| 7431 | p 'foo(char,int)'('x', 13) |
| 7432 | @end smallexample |
| 7433 | |
| 7434 | The @value{GDBN} command-completion facility can simplify this; |
| 7435 | see @ref{Completion, ,Command completion}. |
| 7436 | |
| 7437 | @cindex reference declarations |
| 7438 | @item |
| 7439 | @value{GDBN} understands variables declared as C@t{++} references; you can use |
| 7440 | them in expressions just as you do in C@t{++} source---they are automatically |
| 7441 | dereferenced. |
| 7442 | |
| 7443 | In the parameter list shown when @value{GDBN} displays a frame, the values of |
| 7444 | reference variables are not displayed (unlike other variables); this |
| 7445 | avoids clutter, since references are often used for large structures. |
| 7446 | The @emph{address} of a reference variable is always shown, unless |
| 7447 | you have specified @samp{set print address off}. |
| 7448 | |
| 7449 | @item |
| 7450 | @value{GDBN} supports the C@t{++} name resolution operator @code{::}---your |
| 7451 | expressions can use it just as expressions in your program do. Since |
| 7452 | one scope may be defined in another, you can use @code{::} repeatedly if |
| 7453 | necessary, for example in an expression like |
| 7454 | @samp{@var{scope1}::@var{scope2}::@var{name}}. @value{GDBN} also allows |
| 7455 | resolving name scope by reference to source files, in both C and C@t{++} |
| 7456 | debugging (@pxref{Variables, ,Program variables}). |
| 7457 | @end enumerate |
| 7458 | |
| 7459 | In addition, when used with HP's C@t{++} compiler, @value{GDBN} supports |
| 7460 | calling virtual functions correctly, printing out virtual bases of |
| 7461 | objects, calling functions in a base subobject, casting objects, and |
| 7462 | invoking user-defined operators. |
| 7463 | |
| 7464 | @node C Defaults |
| 7465 | @subsubsection C and C@t{++} defaults |
| 7466 | |
| 7467 | @cindex C and C@t{++} defaults |
| 7468 | |
| 7469 | If you allow @value{GDBN} to set type and range checking automatically, they |
| 7470 | both default to @code{off} whenever the working language changes to |
| 7471 | C or C@t{++}. This happens regardless of whether you or @value{GDBN} |
| 7472 | selects the working language. |
| 7473 | |
| 7474 | If you allow @value{GDBN} to set the language automatically, it |
| 7475 | recognizes source files whose names end with @file{.c}, @file{.C}, or |
| 7476 | @file{.cc}, etc, and when @value{GDBN} enters code compiled from one of |
| 7477 | these files, it sets the working language to C or C@t{++}. |
| 7478 | @xref{Automatically, ,Having @value{GDBN} infer the source language}, |
| 7479 | for further details. |
| 7480 | |
| 7481 | @c Type checking is (a) primarily motivated by Modula-2, and (b) |
| 7482 | @c unimplemented. If (b) changes, it might make sense to let this node |
| 7483 | @c appear even if Mod-2 does not, but meanwhile ignore it. roland 16jul93. |
| 7484 | |
| 7485 | @node C Checks |
| 7486 | @subsubsection C and C@t{++} type and range checks |
| 7487 | |
| 7488 | @cindex C and C@t{++} checks |
| 7489 | |
| 7490 | By default, when @value{GDBN} parses C or C@t{++} expressions, type checking |
| 7491 | is not used. However, if you turn type checking on, @value{GDBN} |
| 7492 | considers two variables type equivalent if: |
| 7493 | |
| 7494 | @itemize @bullet |
| 7495 | @item |
| 7496 | The two variables are structured and have the same structure, union, or |
| 7497 | enumerated tag. |
| 7498 | |
| 7499 | @item |
| 7500 | The two variables have the same type name, or types that have been |
| 7501 | declared equivalent through @code{typedef}. |
| 7502 | |
| 7503 | @ignore |
| 7504 | @c leaving this out because neither J Gilmore nor R Pesch understand it. |
| 7505 | @c FIXME--beers? |
| 7506 | @item |
| 7507 | The two @code{struct}, @code{union}, or @code{enum} variables are |
| 7508 | declared in the same declaration. (Note: this may not be true for all C |
| 7509 | compilers.) |
| 7510 | @end ignore |
| 7511 | @end itemize |
| 7512 | |
| 7513 | Range checking, if turned on, is done on mathematical operations. Array |
| 7514 | indices are not checked, since they are often used to index a pointer |
| 7515 | that is not itself an array. |
| 7516 | |
| 7517 | @node Debugging C |
| 7518 | @subsubsection @value{GDBN} and C |
| 7519 | |
| 7520 | The @code{set print union} and @code{show print union} commands apply to |
| 7521 | the @code{union} type. When set to @samp{on}, any @code{union} that is |
| 7522 | inside a @code{struct} or @code{class} is also printed. Otherwise, it |
| 7523 | appears as @samp{@{...@}}. |
| 7524 | |
| 7525 | The @code{@@} operator aids in the debugging of dynamic arrays, formed |
| 7526 | with pointers and a memory allocation function. @xref{Expressions, |
| 7527 | ,Expressions}. |
| 7528 | |
| 7529 | @menu |
| 7530 | * Debugging C plus plus:: |
| 7531 | @end menu |
| 7532 | |
| 7533 | @node Debugging C plus plus |
| 7534 | @subsubsection @value{GDBN} features for C@t{++} |
| 7535 | |
| 7536 | @cindex commands for C@t{++} |
| 7537 | |
| 7538 | Some @value{GDBN} commands are particularly useful with C@t{++}, and some are |
| 7539 | designed specifically for use with C@t{++}. Here is a summary: |
| 7540 | |
| 7541 | @table @code |
| 7542 | @cindex break in overloaded functions |
| 7543 | @item @r{breakpoint menus} |
| 7544 | When you want a breakpoint in a function whose name is overloaded, |
| 7545 | @value{GDBN} breakpoint menus help you specify which function definition |
| 7546 | you want. @xref{Breakpoint Menus,,Breakpoint menus}. |
| 7547 | |
| 7548 | @cindex overloading in C@t{++} |
| 7549 | @item rbreak @var{regex} |
| 7550 | Setting breakpoints using regular expressions is helpful for setting |
| 7551 | breakpoints on overloaded functions that are not members of any special |
| 7552 | classes. |
| 7553 | @xref{Set Breaks, ,Setting breakpoints}. |
| 7554 | |
| 7555 | @cindex C@t{++} exception handling |
| 7556 | @item catch throw |
| 7557 | @itemx catch catch |
| 7558 | Debug C@t{++} exception handling using these commands. @xref{Set |
| 7559 | Catchpoints, , Setting catchpoints}. |
| 7560 | |
| 7561 | @cindex inheritance |
| 7562 | @item ptype @var{typename} |
| 7563 | Print inheritance relationships as well as other information for type |
| 7564 | @var{typename}. |
| 7565 | @xref{Symbols, ,Examining the Symbol Table}. |
| 7566 | |
| 7567 | @cindex C@t{++} symbol display |
| 7568 | @item set print demangle |
| 7569 | @itemx show print demangle |
| 7570 | @itemx set print asm-demangle |
| 7571 | @itemx show print asm-demangle |
| 7572 | Control whether C@t{++} symbols display in their source form, both when |
| 7573 | displaying code as C@t{++} source and when displaying disassemblies. |
| 7574 | @xref{Print Settings, ,Print settings}. |
| 7575 | |
| 7576 | @item set print object |
| 7577 | @itemx show print object |
| 7578 | Choose whether to print derived (actual) or declared types of objects. |
| 7579 | @xref{Print Settings, ,Print settings}. |
| 7580 | |
| 7581 | @item set print vtbl |
| 7582 | @itemx show print vtbl |
| 7583 | Control the format for printing virtual function tables. |
| 7584 | @xref{Print Settings, ,Print settings}. |
| 7585 | (The @code{vtbl} commands do not work on programs compiled with the HP |
| 7586 | ANSI C@t{++} compiler (@code{aCC}).) |
| 7587 | |
| 7588 | @kindex set overload-resolution |
| 7589 | @cindex overloaded functions, overload resolution |
| 7590 | @item set overload-resolution on |
| 7591 | Enable overload resolution for C@t{++} expression evaluation. The default |
| 7592 | is on. For overloaded functions, @value{GDBN} evaluates the arguments |
| 7593 | and searches for a function whose signature matches the argument types, |
| 7594 | using the standard C@t{++} conversion rules (see @ref{C plus plus expressions, ,C@t{++} |
| 7595 | expressions}, for details). If it cannot find a match, it emits a |
| 7596 | message. |
| 7597 | |
| 7598 | @item set overload-resolution off |
| 7599 | Disable overload resolution for C@t{++} expression evaluation. For |
| 7600 | overloaded functions that are not class member functions, @value{GDBN} |
| 7601 | chooses the first function of the specified name that it finds in the |
| 7602 | symbol table, whether or not its arguments are of the correct type. For |
| 7603 | overloaded functions that are class member functions, @value{GDBN} |
| 7604 | searches for a function whose signature @emph{exactly} matches the |
| 7605 | argument types. |
| 7606 | |
| 7607 | @item @r{Overloaded symbol names} |
| 7608 | You can specify a particular definition of an overloaded symbol, using |
| 7609 | the same notation that is used to declare such symbols in C@t{++}: type |
| 7610 | @code{@var{symbol}(@var{types})} rather than just @var{symbol}. You can |
| 7611 | also use the @value{GDBN} command-line word completion facilities to list the |
| 7612 | available choices, or to finish the type list for you. |
| 7613 | @xref{Completion,, Command completion}, for details on how to do this. |
| 7614 | @end table |
| 7615 | |
| 7616 | @node Modula-2 |
| 7617 | @subsection Modula-2 |
| 7618 | |
| 7619 | @cindex Modula-2, @value{GDBN} support |
| 7620 | |
| 7621 | The extensions made to @value{GDBN} to support Modula-2 only support |
| 7622 | output from the @sc{gnu} Modula-2 compiler (which is currently being |
| 7623 | developed). Other Modula-2 compilers are not currently supported, and |
| 7624 | attempting to debug executables produced by them is most likely |
| 7625 | to give an error as @value{GDBN} reads in the executable's symbol |
| 7626 | table. |
| 7627 | |
| 7628 | @cindex expressions in Modula-2 |
| 7629 | @menu |
| 7630 | * M2 Operators:: Built-in operators |
| 7631 | * Built-In Func/Proc:: Built-in functions and procedures |
| 7632 | * M2 Constants:: Modula-2 constants |
| 7633 | * M2 Defaults:: Default settings for Modula-2 |
| 7634 | * Deviations:: Deviations from standard Modula-2 |
| 7635 | * M2 Checks:: Modula-2 type and range checks |
| 7636 | * M2 Scope:: The scope operators @code{::} and @code{.} |
| 7637 | * GDB/M2:: @value{GDBN} and Modula-2 |
| 7638 | @end menu |
| 7639 | |
| 7640 | @node M2 Operators |
| 7641 | @subsubsection Operators |
| 7642 | @cindex Modula-2 operators |
| 7643 | |
| 7644 | Operators must be defined on values of specific types. For instance, |
| 7645 | @code{+} is defined on numbers, but not on structures. Operators are |
| 7646 | often defined on groups of types. For the purposes of Modula-2, the |
| 7647 | following definitions hold: |
| 7648 | |
| 7649 | @itemize @bullet |
| 7650 | |
| 7651 | @item |
| 7652 | @emph{Integral types} consist of @code{INTEGER}, @code{CARDINAL}, and |
| 7653 | their subranges. |
| 7654 | |
| 7655 | @item |
| 7656 | @emph{Character types} consist of @code{CHAR} and its subranges. |
| 7657 | |
| 7658 | @item |
| 7659 | @emph{Floating-point types} consist of @code{REAL}. |
| 7660 | |
| 7661 | @item |
| 7662 | @emph{Pointer types} consist of anything declared as @code{POINTER TO |
| 7663 | @var{type}}. |
| 7664 | |
| 7665 | @item |
| 7666 | @emph{Scalar types} consist of all of the above. |
| 7667 | |
| 7668 | @item |
| 7669 | @emph{Set types} consist of @code{SET} and @code{BITSET} types. |
| 7670 | |
| 7671 | @item |
| 7672 | @emph{Boolean types} consist of @code{BOOLEAN}. |
| 7673 | @end itemize |
| 7674 | |
| 7675 | @noindent |
| 7676 | The following operators are supported, and appear in order of |
| 7677 | increasing precedence: |
| 7678 | |
| 7679 | @table @code |
| 7680 | @item , |
| 7681 | Function argument or array index separator. |
| 7682 | |
| 7683 | @item := |
| 7684 | Assignment. The value of @var{var} @code{:=} @var{value} is |
| 7685 | @var{value}. |
| 7686 | |
| 7687 | @item <@r{, }> |
| 7688 | Less than, greater than on integral, floating-point, or enumerated |
| 7689 | types. |
| 7690 | |
| 7691 | @item <=@r{, }>= |
| 7692 | Less than or equal to, greater than or equal to |
| 7693 | on integral, floating-point and enumerated types, or set inclusion on |
| 7694 | set types. Same precedence as @code{<}. |
| 7695 | |
| 7696 | @item =@r{, }<>@r{, }# |
| 7697 | Equality and two ways of expressing inequality, valid on scalar types. |
| 7698 | Same precedence as @code{<}. In @value{GDBN} scripts, only @code{<>} is |
| 7699 | available for inequality, since @code{#} conflicts with the script |
| 7700 | comment character. |
| 7701 | |
| 7702 | @item IN |
| 7703 | Set membership. Defined on set types and the types of their members. |
| 7704 | Same precedence as @code{<}. |
| 7705 | |
| 7706 | @item OR |
| 7707 | Boolean disjunction. Defined on boolean types. |
| 7708 | |
| 7709 | @item AND@r{, }& |
| 7710 | Boolean conjunction. Defined on boolean types. |
| 7711 | |
| 7712 | @item @@ |
| 7713 | The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}). |
| 7714 | |
| 7715 | @item +@r{, }- |
| 7716 | Addition and subtraction on integral and floating-point types, or union |
| 7717 | and difference on set types. |
| 7718 | |
| 7719 | @item * |
| 7720 | Multiplication on integral and floating-point types, or set intersection |
| 7721 | on set types. |
| 7722 | |
| 7723 | @item / |
| 7724 | Division on floating-point types, or symmetric set difference on set |
| 7725 | types. Same precedence as @code{*}. |
| 7726 | |
| 7727 | @item DIV@r{, }MOD |
| 7728 | Integer division and remainder. Defined on integral types. Same |
| 7729 | precedence as @code{*}. |
| 7730 | |
| 7731 | @item - |
| 7732 | Negative. Defined on @code{INTEGER} and @code{REAL} data. |
| 7733 | |
| 7734 | @item ^ |
| 7735 | Pointer dereferencing. Defined on pointer types. |
| 7736 | |
| 7737 | @item NOT |
| 7738 | Boolean negation. Defined on boolean types. Same precedence as |
| 7739 | @code{^}. |
| 7740 | |
| 7741 | @item . |
| 7742 | @code{RECORD} field selector. Defined on @code{RECORD} data. Same |
| 7743 | precedence as @code{^}. |
| 7744 | |
| 7745 | @item [] |
| 7746 | Array indexing. Defined on @code{ARRAY} data. Same precedence as @code{^}. |
| 7747 | |
| 7748 | @item () |
| 7749 | Procedure argument list. Defined on @code{PROCEDURE} objects. Same precedence |
| 7750 | as @code{^}. |
| 7751 | |
| 7752 | @item ::@r{, }. |
| 7753 | @value{GDBN} and Modula-2 scope operators. |
| 7754 | @end table |
| 7755 | |
| 7756 | @quotation |
| 7757 | @emph{Warning:} Sets and their operations are not yet supported, so @value{GDBN} |
| 7758 | treats the use of the operator @code{IN}, or the use of operators |
| 7759 | @code{+}, @code{-}, @code{*}, @code{/}, @code{=}, , @code{<>}, @code{#}, |
| 7760 | @code{<=}, and @code{>=} on sets as an error. |
| 7761 | @end quotation |
| 7762 | |
| 7763 | |
| 7764 | @node Built-In Func/Proc |
| 7765 | @subsubsection Built-in functions and procedures |
| 7766 | @cindex Modula-2 built-ins |
| 7767 | |
| 7768 | Modula-2 also makes available several built-in procedures and functions. |
| 7769 | In describing these, the following metavariables are used: |
| 7770 | |
| 7771 | @table @var |
| 7772 | |
| 7773 | @item a |
| 7774 | represents an @code{ARRAY} variable. |
| 7775 | |
| 7776 | @item c |
| 7777 | represents a @code{CHAR} constant or variable. |
| 7778 | |
| 7779 | @item i |
| 7780 | represents a variable or constant of integral type. |
| 7781 | |
| 7782 | @item m |
| 7783 | represents an identifier that belongs to a set. Generally used in the |
| 7784 | same function with the metavariable @var{s}. The type of @var{s} should |
| 7785 | be @code{SET OF @var{mtype}} (where @var{mtype} is the type of @var{m}). |
| 7786 | |
| 7787 | @item n |
| 7788 | represents a variable or constant of integral or floating-point type. |
| 7789 | |
| 7790 | @item r |
| 7791 | represents a variable or constant of floating-point type. |
| 7792 | |
| 7793 | @item t |
| 7794 | represents a type. |
| 7795 | |
| 7796 | @item v |
| 7797 | represents a variable. |
| 7798 | |
| 7799 | @item x |
| 7800 | represents a variable or constant of one of many types. See the |
| 7801 | explanation of the function for details. |
| 7802 | @end table |
| 7803 | |
| 7804 | All Modula-2 built-in procedures also return a result, described below. |
| 7805 | |
| 7806 | @table @code |
| 7807 | @item ABS(@var{n}) |
| 7808 | Returns the absolute value of @var{n}. |
| 7809 | |
| 7810 | @item CAP(@var{c}) |
| 7811 | If @var{c} is a lower case letter, it returns its upper case |
| 7812 | equivalent, otherwise it returns its argument. |
| 7813 | |
| 7814 | @item CHR(@var{i}) |
| 7815 | Returns the character whose ordinal value is @var{i}. |
| 7816 | |
| 7817 | @item DEC(@var{v}) |
| 7818 | Decrements the value in the variable @var{v} by one. Returns the new value. |
| 7819 | |
| 7820 | @item DEC(@var{v},@var{i}) |
| 7821 | Decrements the value in the variable @var{v} by @var{i}. Returns the |
| 7822 | new value. |
| 7823 | |
| 7824 | @item EXCL(@var{m},@var{s}) |
| 7825 | Removes the element @var{m} from the set @var{s}. Returns the new |
| 7826 | set. |
| 7827 | |
| 7828 | @item FLOAT(@var{i}) |
| 7829 | Returns the floating point equivalent of the integer @var{i}. |
| 7830 | |
| 7831 | @item HIGH(@var{a}) |
| 7832 | Returns the index of the last member of @var{a}. |
| 7833 | |
| 7834 | @item INC(@var{v}) |
| 7835 | Increments the value in the variable @var{v} by one. Returns the new value. |
| 7836 | |
| 7837 | @item INC(@var{v},@var{i}) |
| 7838 | Increments the value in the variable @var{v} by @var{i}. Returns the |
| 7839 | new value. |
| 7840 | |
| 7841 | @item INCL(@var{m},@var{s}) |
| 7842 | Adds the element @var{m} to the set @var{s} if it is not already |
| 7843 | there. Returns the new set. |
| 7844 | |
| 7845 | @item MAX(@var{t}) |
| 7846 | Returns the maximum value of the type @var{t}. |
| 7847 | |
| 7848 | @item MIN(@var{t}) |
| 7849 | Returns the minimum value of the type @var{t}. |
| 7850 | |
| 7851 | @item ODD(@var{i}) |
| 7852 | Returns boolean TRUE if @var{i} is an odd number. |
| 7853 | |
| 7854 | @item ORD(@var{x}) |
| 7855 | Returns the ordinal value of its argument. For example, the ordinal |
| 7856 | value of a character is its @sc{ascii} value (on machines supporting the |
| 7857 | @sc{ascii} character set). @var{x} must be of an ordered type, which include |
| 7858 | integral, character and enumerated types. |
| 7859 | |
| 7860 | @item SIZE(@var{x}) |
| 7861 | Returns the size of its argument. @var{x} can be a variable or a type. |
| 7862 | |
| 7863 | @item TRUNC(@var{r}) |
| 7864 | Returns the integral part of @var{r}. |
| 7865 | |
| 7866 | @item VAL(@var{t},@var{i}) |
| 7867 | Returns the member of the type @var{t} whose ordinal value is @var{i}. |
| 7868 | @end table |
| 7869 | |
| 7870 | @quotation |
| 7871 | @emph{Warning:} Sets and their operations are not yet supported, so |
| 7872 | @value{GDBN} treats the use of procedures @code{INCL} and @code{EXCL} as |
| 7873 | an error. |
| 7874 | @end quotation |
| 7875 | |
| 7876 | @cindex Modula-2 constants |
| 7877 | @node M2 Constants |
| 7878 | @subsubsection Constants |
| 7879 | |
| 7880 | @value{GDBN} allows you to express the constants of Modula-2 in the following |
| 7881 | ways: |
| 7882 | |
| 7883 | @itemize @bullet |
| 7884 | |
| 7885 | @item |
| 7886 | Integer constants are simply a sequence of digits. When used in an |
| 7887 | expression, a constant is interpreted to be type-compatible with the |
| 7888 | rest of the expression. Hexadecimal integers are specified by a |
| 7889 | trailing @samp{H}, and octal integers by a trailing @samp{B}. |
| 7890 | |
| 7891 | @item |
| 7892 | Floating point constants appear as a sequence of digits, followed by a |
| 7893 | decimal point and another sequence of digits. An optional exponent can |
| 7894 | then be specified, in the form @samp{E@r{[}+@r{|}-@r{]}@var{nnn}}, where |
| 7895 | @samp{@r{[}+@r{|}-@r{]}@var{nnn}} is the desired exponent. All of the |
| 7896 | digits of the floating point constant must be valid decimal (base 10) |
| 7897 | digits. |
| 7898 | |
| 7899 | @item |
| 7900 | Character constants consist of a single character enclosed by a pair of |
| 7901 | like quotes, either single (@code{'}) or double (@code{"}). They may |
| 7902 | also be expressed by their ordinal value (their @sc{ascii} value, usually) |
| 7903 | followed by a @samp{C}. |
| 7904 | |
| 7905 | @item |
| 7906 | String constants consist of a sequence of characters enclosed by a |
| 7907 | pair of like quotes, either single (@code{'}) or double (@code{"}). |
| 7908 | Escape sequences in the style of C are also allowed. @xref{C |
| 7909 | Constants, ,C and C@t{++} constants}, for a brief explanation of escape |
| 7910 | sequences. |
| 7911 | |
| 7912 | @item |
| 7913 | Enumerated constants consist of an enumerated identifier. |
| 7914 | |
| 7915 | @item |
| 7916 | Boolean constants consist of the identifiers @code{TRUE} and |
| 7917 | @code{FALSE}. |
| 7918 | |
| 7919 | @item |
| 7920 | Pointer constants consist of integral values only. |
| 7921 | |
| 7922 | @item |
| 7923 | Set constants are not yet supported. |
| 7924 | @end itemize |
| 7925 | |
| 7926 | @node M2 Defaults |
| 7927 | @subsubsection Modula-2 defaults |
| 7928 | @cindex Modula-2 defaults |
| 7929 | |
| 7930 | If type and range checking are set automatically by @value{GDBN}, they |
| 7931 | both default to @code{on} whenever the working language changes to |
| 7932 | Modula-2. This happens regardless of whether you or @value{GDBN} |
| 7933 | selected the working language. |
| 7934 | |
| 7935 | If you allow @value{GDBN} to set the language automatically, then entering |
| 7936 | code compiled from a file whose name ends with @file{.mod} sets the |
| 7937 | working language to Modula-2. @xref{Automatically, ,Having @value{GDBN} set |
| 7938 | the language automatically}, for further details. |
| 7939 | |
| 7940 | @node Deviations |
| 7941 | @subsubsection Deviations from standard Modula-2 |
| 7942 | @cindex Modula-2, deviations from |
| 7943 | |
| 7944 | A few changes have been made to make Modula-2 programs easier to debug. |
| 7945 | This is done primarily via loosening its type strictness: |
| 7946 | |
| 7947 | @itemize @bullet |
| 7948 | @item |
| 7949 | Unlike in standard Modula-2, pointer constants can be formed by |
| 7950 | integers. This allows you to modify pointer variables during |
| 7951 | debugging. (In standard Modula-2, the actual address contained in a |
| 7952 | pointer variable is hidden from you; it can only be modified |
| 7953 | through direct assignment to another pointer variable or expression that |
| 7954 | returned a pointer.) |
| 7955 | |
| 7956 | @item |
| 7957 | C escape sequences can be used in strings and characters to represent |
| 7958 | non-printable characters. @value{GDBN} prints out strings with these |
| 7959 | escape sequences embedded. Single non-printable characters are |
| 7960 | printed using the @samp{CHR(@var{nnn})} format. |
| 7961 | |
| 7962 | @item |
| 7963 | The assignment operator (@code{:=}) returns the value of its right-hand |
| 7964 | argument. |
| 7965 | |
| 7966 | @item |
| 7967 | All built-in procedures both modify @emph{and} return their argument. |
| 7968 | @end itemize |
| 7969 | |
| 7970 | @node M2 Checks |
| 7971 | @subsubsection Modula-2 type and range checks |
| 7972 | @cindex Modula-2 checks |
| 7973 | |
| 7974 | @quotation |
| 7975 | @emph{Warning:} in this release, @value{GDBN} does not yet perform type or |
| 7976 | range checking. |
| 7977 | @end quotation |
| 7978 | @c FIXME remove warning when type/range checks added |
| 7979 | |
| 7980 | @value{GDBN} considers two Modula-2 variables type equivalent if: |
| 7981 | |
| 7982 | @itemize @bullet |
| 7983 | @item |
| 7984 | They are of types that have been declared equivalent via a @code{TYPE |
| 7985 | @var{t1} = @var{t2}} statement |
| 7986 | |
| 7987 | @item |
| 7988 | They have been declared on the same line. (Note: This is true of the |
| 7989 | @sc{gnu} Modula-2 compiler, but it may not be true of other compilers.) |
| 7990 | @end itemize |
| 7991 | |
| 7992 | As long as type checking is enabled, any attempt to combine variables |
| 7993 | whose types are not equivalent is an error. |
| 7994 | |
| 7995 | Range checking is done on all mathematical operations, assignment, array |
| 7996 | index bounds, and all built-in functions and procedures. |
| 7997 | |
| 7998 | @node M2 Scope |
| 7999 | @subsubsection The scope operators @code{::} and @code{.} |
| 8000 | @cindex scope |
| 8001 | @cindex @code{.}, Modula-2 scope operator |
| 8002 | @cindex colon, doubled as scope operator |
| 8003 | @ifinfo |
| 8004 | @vindex colon-colon@r{, in Modula-2} |
| 8005 | @c Info cannot handle :: but TeX can. |
| 8006 | @end ifinfo |
| 8007 | @iftex |
| 8008 | @vindex ::@r{, in Modula-2} |
| 8009 | @end iftex |
| 8010 | |
| 8011 | There are a few subtle differences between the Modula-2 scope operator |
| 8012 | (@code{.}) and the @value{GDBN} scope operator (@code{::}). The two have |
| 8013 | similar syntax: |
| 8014 | |
| 8015 | @example |
| 8016 | |
| 8017 | @var{module} . @var{id} |
| 8018 | @var{scope} :: @var{id} |
| 8019 | @end example |
| 8020 | |
| 8021 | @noindent |
| 8022 | where @var{scope} is the name of a module or a procedure, |
| 8023 | @var{module} the name of a module, and @var{id} is any declared |
| 8024 | identifier within your program, except another module. |
| 8025 | |
| 8026 | Using the @code{::} operator makes @value{GDBN} search the scope |
| 8027 | specified by @var{scope} for the identifier @var{id}. If it is not |
| 8028 | found in the specified scope, then @value{GDBN} searches all scopes |
| 8029 | enclosing the one specified by @var{scope}. |
| 8030 | |
| 8031 | Using the @code{.} operator makes @value{GDBN} search the current scope for |
| 8032 | the identifier specified by @var{id} that was imported from the |
| 8033 | definition module specified by @var{module}. With this operator, it is |
| 8034 | an error if the identifier @var{id} was not imported from definition |
| 8035 | module @var{module}, or if @var{id} is not an identifier in |
| 8036 | @var{module}. |
| 8037 | |
| 8038 | @node GDB/M2 |
| 8039 | @subsubsection @value{GDBN} and Modula-2 |
| 8040 | |
| 8041 | Some @value{GDBN} commands have little use when debugging Modula-2 programs. |
| 8042 | Five subcommands of @code{set print} and @code{show print} apply |
| 8043 | specifically to C and C@t{++}: @samp{vtbl}, @samp{demangle}, |
| 8044 | @samp{asm-demangle}, @samp{object}, and @samp{union}. The first four |
| 8045 | apply to C@t{++}, and the last to the C @code{union} type, which has no direct |
| 8046 | analogue in Modula-2. |
| 8047 | |
| 8048 | The @code{@@} operator (@pxref{Expressions, ,Expressions}), while available |
| 8049 | with any language, is not useful with Modula-2. Its |
| 8050 | intent is to aid the debugging of @dfn{dynamic arrays}, which cannot be |
| 8051 | created in Modula-2 as they can in C or C@t{++}. However, because an |
| 8052 | address can be specified by an integral constant, the construct |
| 8053 | @samp{@{@var{type}@}@var{adrexp}} is still useful. |
| 8054 | |
| 8055 | @cindex @code{#} in Modula-2 |
| 8056 | In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is |
| 8057 | interpreted as the beginning of a comment. Use @code{<>} instead. |
| 8058 | |
| 8059 | @node Chill |
| 8060 | @subsection Chill |
| 8061 | |
| 8062 | The extensions made to @value{GDBN} to support Chill only support output |
| 8063 | from the @sc{gnu} Chill compiler. Other Chill compilers are not currently |
| 8064 | supported, and attempting to debug executables produced by them is most |
| 8065 | likely to give an error as @value{GDBN} reads in the executable's symbol |
| 8066 | table. |
| 8067 | |
| 8068 | @c This used to say "... following Chill related topics ...", but since |
| 8069 | @c menus are not shown in the printed manual, it would look awkward. |
| 8070 | This section covers the Chill related topics and the features |
| 8071 | of @value{GDBN} which support these topics. |
| 8072 | |
| 8073 | @menu |
| 8074 | * How modes are displayed:: How modes are displayed |
| 8075 | * Locations:: Locations and their accesses |
| 8076 | * Values and their Operations:: Values and their Operations |
| 8077 | * Chill type and range checks:: |
| 8078 | * Chill defaults:: |
| 8079 | @end menu |
| 8080 | |
| 8081 | @node How modes are displayed |
| 8082 | @subsubsection How modes are displayed |
| 8083 | |
| 8084 | The Chill Datatype- (Mode) support of @value{GDBN} is directly related |
| 8085 | with the functionality of the @sc{gnu} Chill compiler, and therefore deviates |
| 8086 | slightly from the standard specification of the Chill language. The |
| 8087 | provided modes are: |
| 8088 | |
| 8089 | @c FIXME: this @table's contents effectively disable @code by using @r |
| 8090 | @c on every @item. So why does it need @code? |
| 8091 | @table @code |
| 8092 | @item @r{@emph{Discrete modes:}} |
| 8093 | @itemize @bullet |
| 8094 | @item |
| 8095 | @emph{Integer Modes} which are predefined by @code{BYTE, UBYTE, INT, |
| 8096 | UINT, LONG, ULONG}, |
| 8097 | @item |
| 8098 | @emph{Boolean Mode} which is predefined by @code{BOOL}, |
| 8099 | @item |
| 8100 | @emph{Character Mode} which is predefined by @code{CHAR}, |
| 8101 | @item |
| 8102 | @emph{Set Mode} which is displayed by the keyword @code{SET}. |
| 8103 | @smallexample |
| 8104 | (@value{GDBP}) ptype x |
| 8105 | type = SET (karli = 10, susi = 20, fritzi = 100) |
| 8106 | @end smallexample |
| 8107 | If the type is an unnumbered set the set element values are omitted. |
| 8108 | @item |
| 8109 | @emph{Range Mode} which is displayed by |
| 8110 | @smallexample |
| 8111 | @code{type = <basemode>(<lower bound> : <upper bound>)} |
| 8112 | @end smallexample |
| 8113 | where @code{<lower bound>, <upper bound>} can be of any discrete literal |
| 8114 | expression (e.g. set element names). |
| 8115 | @end itemize |
| 8116 | |
| 8117 | @item @r{@emph{Powerset Mode:}} |
| 8118 | A Powerset Mode is displayed by the keyword @code{POWERSET} followed by |
| 8119 | the member mode of the powerset. The member mode can be any discrete mode. |
| 8120 | @smallexample |
| 8121 | (@value{GDBP}) ptype x |
| 8122 | type = POWERSET SET (egon, hugo, otto) |
| 8123 | @end smallexample |
| 8124 | |
| 8125 | @item @r{@emph{Reference Modes:}} |
| 8126 | @itemize @bullet |
| 8127 | @item |
| 8128 | @emph{Bound Reference Mode} which is displayed by the keyword @code{REF} |
| 8129 | followed by the mode name to which the reference is bound. |
| 8130 | @item |
| 8131 | @emph{Free Reference Mode} which is displayed by the keyword @code{PTR}. |
| 8132 | @end itemize |
| 8133 | |
| 8134 | @item @r{@emph{Procedure mode}} |
| 8135 | The procedure mode is displayed by @code{type = PROC(<parameter list>) |
| 8136 | <return mode> EXCEPTIONS (<exception list>)}. The @code{<parameter |
| 8137 | list>} is a list of the parameter modes. @code{<return mode>} indicates |
| 8138 | the mode of the result of the procedure if any. The exceptionlist lists |
| 8139 | all possible exceptions which can be raised by the procedure. |
| 8140 | |
| 8141 | @ignore |
| 8142 | @item @r{@emph{Instance mode}} |
| 8143 | The instance mode is represented by a structure, which has a static |
| 8144 | type, and is therefore not really of interest. |
| 8145 | @end ignore |
| 8146 | |
| 8147 | @item @r{@emph{Synchronization Modes:}} |
| 8148 | @itemize @bullet |
| 8149 | @item |
| 8150 | @emph{Event Mode} which is displayed by |
| 8151 | @smallexample |
| 8152 | @code{EVENT (<event length>)} |
| 8153 | @end smallexample |
| 8154 | where @code{(<event length>)} is optional. |
| 8155 | @item |
| 8156 | @emph{Buffer Mode} which is displayed by |
| 8157 | @smallexample |
| 8158 | @code{BUFFER (<buffer length>)<buffer element mode>} |
| 8159 | @end smallexample |
| 8160 | where @code{(<buffer length>)} is optional. |
| 8161 | @end itemize |
| 8162 | |
| 8163 | @item @r{@emph{Timing Modes:}} |
| 8164 | @itemize @bullet |
| 8165 | @item |
| 8166 | @emph{Duration Mode} which is predefined by @code{DURATION} |
| 8167 | @item |
| 8168 | @emph{Absolute Time Mode} which is predefined by @code{TIME} |
| 8169 | @end itemize |
| 8170 | |
| 8171 | @item @r{@emph{Real Modes:}} |
| 8172 | Real Modes are predefined with @code{REAL} and @code{LONG_REAL}. |
| 8173 | |
| 8174 | @item @r{@emph{String Modes:}} |
| 8175 | @itemize @bullet |
| 8176 | @item |
| 8177 | @emph{Character String Mode} which is displayed by |
| 8178 | @smallexample |
| 8179 | @code{CHARS(<string length>)} |
| 8180 | @end smallexample |
| 8181 | followed by the keyword @code{VARYING} if the String Mode is a varying |
| 8182 | mode |
| 8183 | @item |
| 8184 | @emph{Bit String Mode} which is displayed by |
| 8185 | @smallexample |
| 8186 | @code{BOOLS(<string |
| 8187 | length>)} |
| 8188 | @end smallexample |
| 8189 | @end itemize |
| 8190 | |
| 8191 | @item @r{@emph{Array Mode:}} |
| 8192 | The Array Mode is displayed by the keyword @code{ARRAY(<range>)} |
| 8193 | followed by the element mode (which may in turn be an array mode). |
| 8194 | @smallexample |
| 8195 | (@value{GDBP}) ptype x |
| 8196 | type = ARRAY (1:42) |
| 8197 | ARRAY (1:20) |
| 8198 | SET (karli = 10, susi = 20, fritzi = 100) |
| 8199 | @end smallexample |
| 8200 | |
| 8201 | @item @r{@emph{Structure Mode}} |
| 8202 | The Structure mode is displayed by the keyword @code{STRUCT(<field |
| 8203 | list>)}. The @code{<field list>} consists of names and modes of fields |
| 8204 | of the structure. Variant structures have the keyword @code{CASE <field> |
| 8205 | OF <variant fields> ESAC} in their field list. Since the current version |
| 8206 | of the GNU Chill compiler doesn't implement tag processing (no runtime |
| 8207 | checks of variant fields, and therefore no debugging info), the output |
| 8208 | always displays all variant fields. |
| 8209 | @smallexample |
| 8210 | (@value{GDBP}) ptype str |
| 8211 | type = STRUCT ( |
| 8212 | as x, |
| 8213 | bs x, |
| 8214 | CASE bs OF |
| 8215 | (karli): |
| 8216 | cs a |
| 8217 | (ott): |
| 8218 | ds x |
| 8219 | ESAC |
| 8220 | ) |
| 8221 | @end smallexample |
| 8222 | @end table |
| 8223 | |
| 8224 | @node Locations |
| 8225 | @subsubsection Locations and their accesses |
| 8226 | |
| 8227 | A location in Chill is an object which can contain values. |
| 8228 | |
| 8229 | A value of a location is generally accessed by the (declared) name of |
| 8230 | the location. The output conforms to the specification of values in |
| 8231 | Chill programs. How values are specified |
| 8232 | is the topic of the next section, @ref{Values and their Operations}. |
| 8233 | |
| 8234 | The pseudo-location @code{RESULT} (or @code{result}) can be used to |
| 8235 | display or change the result of a currently-active procedure: |
| 8236 | |
| 8237 | @smallexample |
| 8238 | set result := EXPR |
| 8239 | @end smallexample |
| 8240 | |
| 8241 | @noindent |
| 8242 | This does the same as the Chill action @code{RESULT EXPR} (which |
| 8243 | is not available in @value{GDBN}). |
| 8244 | |
| 8245 | Values of reference mode locations are printed by @code{PTR(<hex |
| 8246 | value>)} in case of a free reference mode, and by @code{(REF <reference |
| 8247 | mode>) (<hex-value>)} in case of a bound reference. @code{<hex value>} |
| 8248 | represents the address where the reference points to. To access the |
| 8249 | value of the location referenced by the pointer, use the dereference |
| 8250 | operator @samp{->}. |
| 8251 | |
| 8252 | Values of procedure mode locations are displayed by |
| 8253 | @smallexample |
| 8254 | @code{@{ PROC |
| 8255 | (<argument modes> ) <return mode> @} <address> <name of procedure |
| 8256 | location>} |
| 8257 | @end smallexample |
| 8258 | @code{<argument modes>} is a list of modes according to the parameter |
| 8259 | specification of the procedure and @code{<address>} shows the address of |
| 8260 | the entry point. |
| 8261 | |
| 8262 | @ignore |
| 8263 | Locations of instance modes are displayed just like a structure with two |
| 8264 | fields specifying the @emph{process type} and the @emph{copy number} of |
| 8265 | the investigated instance location@footnote{This comes from the current |
| 8266 | implementation of instances. They are implemented as a structure (no |
| 8267 | na). The output should be something like @code{[<name of the process>; |
| 8268 | <instance number>]}.}. The field names are @code{__proc_type} and |
| 8269 | @code{__proc_copy}. |
| 8270 | |
| 8271 | Locations of synchronization modes are displayed like a structure with |
| 8272 | the field name @code{__event_data} in case of a event mode location, and |
| 8273 | like a structure with the field @code{__buffer_data} in case of a buffer |
| 8274 | mode location (refer to previous paragraph). |
| 8275 | |
| 8276 | Structure Mode locations are printed by @code{[.<field name>: <value>, |
| 8277 | ...]}. The @code{<field name>} corresponds to the structure mode |
| 8278 | definition and the layout of @code{<value>} varies depending of the mode |
| 8279 | of the field. If the investigated structure mode location is of variant |
| 8280 | structure mode, the variant parts of the structure are enclosed in curled |
| 8281 | braces (@samp{@{@}}). Fields enclosed by @samp{@{,@}} are residing |
| 8282 | on the same memory location and represent the current values of the |
| 8283 | memory location in their specific modes. Since no tag processing is done |
| 8284 | all variants are displayed. A variant field is printed by |
| 8285 | @code{(<variant name>) = .<field name>: <value>}. (who implements the |
| 8286 | stuff ???) |
| 8287 | @smallexample |
| 8288 | (@value{GDBP}) print str1 $4 = [.as: 0, .bs: karli, .<TAG>: { (karli) = |
| 8289 | [.cs: []], (susi) = [.ds: susi]}] |
| 8290 | @end smallexample |
| 8291 | @end ignore |
| 8292 | |
| 8293 | Substructures of string mode-, array mode- or structure mode-values |
| 8294 | (e.g. array slices, fields of structure locations) are accessed using |
| 8295 | certain operations which are described in the next section, @ref{Values |
| 8296 | and their Operations}. |
| 8297 | |
| 8298 | A location value may be interpreted as having a different mode using the |
| 8299 | location conversion. This mode conversion is written as @code{<mode |
| 8300 | name>(<location>)}. The user has to consider that the sizes of the modes |
| 8301 | have to be equal otherwise an error occurs. Furthermore, no range |
| 8302 | checking of the location against the destination mode is performed, and |
| 8303 | therefore the result can be quite confusing. |
| 8304 | |
| 8305 | @smallexample |
| 8306 | (@value{GDBP}) print int (s(3 up 4)) XXX TO be filled in !! XXX |
| 8307 | @end smallexample |
| 8308 | |
| 8309 | @node Values and their Operations |
| 8310 | @subsubsection Values and their Operations |
| 8311 | |
| 8312 | Values are used to alter locations, to investigate complex structures in |
| 8313 | more detail or to filter relevant information out of a large amount of |
| 8314 | data. There are several (mode dependent) operations defined which enable |
| 8315 | such investigations. These operations are not only applicable to |
| 8316 | constant values but also to locations, which can become quite useful |
| 8317 | when debugging complex structures. During parsing the command line |
| 8318 | (e.g. evaluating an expression) @value{GDBN} treats location names as |
| 8319 | the values behind these locations. |
| 8320 | |
| 8321 | This section describes how values have to be specified and which |
| 8322 | operations are legal to be used with such values. |
| 8323 | |
| 8324 | @table @code |
| 8325 | @item Literal Values |
| 8326 | Literal values are specified in the same manner as in @sc{gnu} Chill programs. |
| 8327 | For detailed specification refer to the @sc{gnu} Chill implementation Manual |
| 8328 | chapter 1.5. |
| 8329 | @c FIXME: if the Chill Manual is a Texinfo documents, the above should |
| 8330 | @c be converted to a @ref. |
| 8331 | |
| 8332 | @ignore |
| 8333 | @itemize @bullet |
| 8334 | @item |
| 8335 | @emph{Integer Literals} are specified in the same manner as in Chill |
| 8336 | programs (refer to the Chill Standard z200/88 chpt 5.2.4.2) |
| 8337 | @item |
| 8338 | @emph{Boolean Literals} are defined by @code{TRUE} and @code{FALSE}. |
| 8339 | @item |
| 8340 | @emph{Character Literals} are defined by @code{'<character>'}. (e.g. |
| 8341 | @code{'M'}) |
| 8342 | @item |
| 8343 | @emph{Set Literals} are defined by a name which was specified in a set |
| 8344 | mode. The value delivered by a Set Literal is the set value. This is |
| 8345 | comparable to an enumeration in C/C@t{++} language. |
| 8346 | @item |
| 8347 | @emph{Emptiness Literal} is predefined by @code{NULL}. The value of the |
| 8348 | emptiness literal delivers either the empty reference value, the empty |
| 8349 | procedure value or the empty instance value. |
| 8350 | |
| 8351 | @item |
| 8352 | @emph{Character String Literals} are defined by a sequence of characters |
| 8353 | enclosed in single- or double quotes. If a single- or double quote has |
| 8354 | to be part of the string literal it has to be stuffed (specified twice). |
| 8355 | @item |
| 8356 | @emph{Bitstring Literals} are specified in the same manner as in Chill |
| 8357 | programs (refer z200/88 chpt 5.2.4.8). |
| 8358 | @item |
| 8359 | @emph{Floating point literals} are specified in the same manner as in |
| 8360 | (gnu-)Chill programs (refer @sc{gnu} Chill implementation Manual chapter 1.5). |
| 8361 | @end itemize |
| 8362 | @end ignore |
| 8363 | |
| 8364 | @item Tuple Values |
| 8365 | A tuple is specified by @code{<mode name>[<tuple>]}, where @code{<mode |
| 8366 | name>} can be omitted if the mode of the tuple is unambiguous. This |
| 8367 | unambiguity is derived from the context of a evaluated expression. |
| 8368 | @code{<tuple>} can be one of the following: |
| 8369 | |
| 8370 | @itemize @bullet |
| 8371 | @item @emph{Powerset Tuple} |
| 8372 | @item @emph{Array Tuple} |
| 8373 | @item @emph{Structure Tuple} |
| 8374 | Powerset tuples, array tuples and structure tuples are specified in the |
| 8375 | same manner as in Chill programs refer to z200/88 chpt 5.2.5. |
| 8376 | @end itemize |
| 8377 | |
| 8378 | @item String Element Value |
| 8379 | A string element value is specified by |
| 8380 | @smallexample |
| 8381 | @code{<string value>(<index>)} |
| 8382 | @end smallexample |
| 8383 | where @code{<index>} is a integer expression. It delivers a character |
| 8384 | value which is equivalent to the character indexed by @code{<index>} in |
| 8385 | the string. |
| 8386 | |
| 8387 | @item String Slice Value |
| 8388 | A string slice value is specified by @code{<string value>(<slice |
| 8389 | spec>)}, where @code{<slice spec>} can be either a range of integer |
| 8390 | expressions or specified by @code{<start expr> up <size>}. |
| 8391 | @code{<size>} denotes the number of elements which the slice contains. |
| 8392 | The delivered value is a string value, which is part of the specified |
| 8393 | string. |
| 8394 | |
| 8395 | @item Array Element Values |
| 8396 | An array element value is specified by @code{<array value>(<expr>)} and |
| 8397 | delivers a array element value of the mode of the specified array. |
| 8398 | |
| 8399 | @item Array Slice Values |
| 8400 | An array slice is specified by @code{<array value>(<slice spec>)}, where |
| 8401 | @code{<slice spec>} can be either a range specified by expressions or by |
| 8402 | @code{<start expr> up <size>}. @code{<size>} denotes the number of |
| 8403 | arrayelements the slice contains. The delivered value is an array value |
| 8404 | which is part of the specified array. |
| 8405 | |
| 8406 | @item Structure Field Values |
| 8407 | A structure field value is derived by @code{<structure value>.<field |
| 8408 | name>}, where @code{<field name>} indicates the name of a field specified |
| 8409 | in the mode definition of the structure. The mode of the delivered value |
| 8410 | corresponds to this mode definition in the structure definition. |
| 8411 | |
| 8412 | @item Procedure Call Value |
| 8413 | The procedure call value is derived from the return value of the |
| 8414 | procedure@footnote{If a procedure call is used for instance in an |
| 8415 | expression, then this procedure is called with all its side |
| 8416 | effects. This can lead to confusing results if used carelessly.}. |
| 8417 | |
| 8418 | Values of duration mode locations are represented by @code{ULONG} literals. |
| 8419 | |
| 8420 | Values of time mode locations appear as |
| 8421 | @smallexample |
| 8422 | @code{TIME(<secs>:<nsecs>)} |
| 8423 | @end smallexample |
| 8424 | |
| 8425 | |
| 8426 | @ignore |
| 8427 | This is not implemented yet: |
| 8428 | @item Built-in Value |
| 8429 | @noindent |
| 8430 | The following built in functions are provided: |
| 8431 | |
| 8432 | @table @code |
| 8433 | @item @code{ADDR()} |
| 8434 | @item @code{NUM()} |
| 8435 | @item @code{PRED()} |
| 8436 | @item @code{SUCC()} |
| 8437 | @item @code{ABS()} |
| 8438 | @item @code{CARD()} |
| 8439 | @item @code{MAX()} |
| 8440 | @item @code{MIN()} |
| 8441 | @item @code{SIZE()} |
| 8442 | @item @code{UPPER()} |
| 8443 | @item @code{LOWER()} |
| 8444 | @item @code{LENGTH()} |
| 8445 | @item @code{SIN()} |
| 8446 | @item @code{COS()} |
| 8447 | @item @code{TAN()} |
| 8448 | @item @code{ARCSIN()} |
| 8449 | @item @code{ARCCOS()} |
| 8450 | @item @code{ARCTAN()} |
| 8451 | @item @code{EXP()} |
| 8452 | @item @code{LN()} |
| 8453 | @item @code{LOG()} |
| 8454 | @item @code{SQRT()} |
| 8455 | @end table |
| 8456 | |
| 8457 | For a detailed description refer to the GNU Chill implementation manual |
| 8458 | chapter 1.6. |
| 8459 | @end ignore |
| 8460 | |
| 8461 | @item Zero-adic Operator Value |
| 8462 | The zero-adic operator value is derived from the instance value for the |
| 8463 | current active process. |
| 8464 | |
| 8465 | @item Expression Values |
| 8466 | The value delivered by an expression is the result of the evaluation of |
| 8467 | the specified expression. If there are error conditions (mode |
| 8468 | incompatibility, etc.) the evaluation of expressions is aborted with a |
| 8469 | corresponding error message. Expressions may be parenthesised which |
| 8470 | causes the evaluation of this expression before any other expression |
| 8471 | which uses the result of the parenthesised expression. The following |
| 8472 | operators are supported by @value{GDBN}: |
| 8473 | |
| 8474 | @table @code |
| 8475 | @item @code{OR, ORIF, XOR} |
| 8476 | @itemx @code{AND, ANDIF} |
| 8477 | @itemx @code{NOT} |
| 8478 | Logical operators defined over operands of boolean mode. |
| 8479 | |
| 8480 | @item @code{=, /=} |
| 8481 | Equality and inequality operators defined over all modes. |
| 8482 | |
| 8483 | @item @code{>, >=} |
| 8484 | @itemx @code{<, <=} |
| 8485 | Relational operators defined over predefined modes. |
| 8486 | |
| 8487 | @item @code{+, -} |
| 8488 | @itemx @code{*, /, MOD, REM} |
| 8489 | Arithmetic operators defined over predefined modes. |
| 8490 | |
| 8491 | @item @code{-} |
| 8492 | Change sign operator. |
| 8493 | |
| 8494 | @item @code{//} |
| 8495 | String concatenation operator. |
| 8496 | |
| 8497 | @item @code{()} |
| 8498 | String repetition operator. |
| 8499 | |
| 8500 | @item @code{->} |
| 8501 | Referenced location operator which can be used either to take the |
| 8502 | address of a location (@code{->loc}), or to dereference a reference |
| 8503 | location (@code{loc->}). |
| 8504 | |
| 8505 | @item @code{OR, XOR} |
| 8506 | @itemx @code{AND} |
| 8507 | @itemx @code{NOT} |
| 8508 | Powerset and bitstring operators. |
| 8509 | |
| 8510 | @item @code{>, >=} |
| 8511 | @itemx @code{<, <=} |
| 8512 | Powerset inclusion operators. |
| 8513 | |
| 8514 | @item @code{IN} |
| 8515 | Membership operator. |
| 8516 | @end table |
| 8517 | @end table |
| 8518 | |
| 8519 | @node Chill type and range checks |
| 8520 | @subsubsection Chill type and range checks |
| 8521 | |
| 8522 | @value{GDBN} considers two Chill variables mode equivalent if the sizes |
| 8523 | of the two modes are equal. This rule applies recursively to more |
| 8524 | complex datatypes which means that complex modes are treated |
| 8525 | equivalent if all element modes (which also can be complex modes like |
| 8526 | structures, arrays, etc.) have the same size. |
| 8527 | |
| 8528 | Range checking is done on all mathematical operations, assignment, array |
| 8529 | index bounds and all built in procedures. |
| 8530 | |
| 8531 | Strong type checks are forced using the @value{GDBN} command @code{set |
| 8532 | check strong}. This enforces strong type and range checks on all |
| 8533 | operations where Chill constructs are used (expressions, built in |
| 8534 | functions, etc.) in respect to the semantics as defined in the z.200 |
| 8535 | language specification. |
| 8536 | |
| 8537 | All checks can be disabled by the @value{GDBN} command @code{set check |
| 8538 | off}. |
| 8539 | |
| 8540 | @ignore |
| 8541 | @c Deviations from the Chill Standard Z200/88 |
| 8542 | see last paragraph ? |
| 8543 | @end ignore |
| 8544 | |
| 8545 | @node Chill defaults |
| 8546 | @subsubsection Chill defaults |
| 8547 | |
| 8548 | If type and range checking are set automatically by @value{GDBN}, they |
| 8549 | both default to @code{on} whenever the working language changes to |
| 8550 | Chill. This happens regardless of whether you or @value{GDBN} |
| 8551 | selected the working language. |
| 8552 | |
| 8553 | If you allow @value{GDBN} to set the language automatically, then entering |
| 8554 | code compiled from a file whose name ends with @file{.ch} sets the |
| 8555 | working language to Chill. @xref{Automatically, ,Having @value{GDBN} set |
| 8556 | the language automatically}, for further details. |
| 8557 | |
| 8558 | @node Symbols |
| 8559 | @chapter Examining the Symbol Table |
| 8560 | |
| 8561 | The commands described in this chapter allow you to inquire about the |
| 8562 | symbols (names of variables, functions and types) defined in your |
| 8563 | program. This information is inherent in the text of your program and |
| 8564 | does not change as your program executes. @value{GDBN} finds it in your |
| 8565 | program's symbol table, in the file indicated when you started @value{GDBN} |
| 8566 | (@pxref{File Options, ,Choosing files}), or by one of the |
| 8567 | file-management commands (@pxref{Files, ,Commands to specify files}). |
| 8568 | |
| 8569 | @cindex symbol names |
| 8570 | @cindex names of symbols |
| 8571 | @cindex quoting names |
| 8572 | Occasionally, you may need to refer to symbols that contain unusual |
| 8573 | characters, which @value{GDBN} ordinarily treats as word delimiters. The |
| 8574 | most frequent case is in referring to static variables in other |
| 8575 | source files (@pxref{Variables,,Program variables}). File names |
| 8576 | are recorded in object files as debugging symbols, but @value{GDBN} would |
| 8577 | ordinarily parse a typical file name, like @file{foo.c}, as the three words |
| 8578 | @samp{foo} @samp{.} @samp{c}. To allow @value{GDBN} to recognize |
| 8579 | @samp{foo.c} as a single symbol, enclose it in single quotes; for example, |
| 8580 | |
| 8581 | @example |
| 8582 | p 'foo.c'::x |
| 8583 | @end example |
| 8584 | |
| 8585 | @noindent |
| 8586 | looks up the value of @code{x} in the scope of the file @file{foo.c}. |
| 8587 | |
| 8588 | @table @code |
| 8589 | @kindex info address |
| 8590 | @cindex address of a symbol |
| 8591 | @item info address @var{symbol} |
| 8592 | Describe where the data for @var{symbol} is stored. For a register |
| 8593 | variable, this says which register it is kept in. For a non-register |
| 8594 | local variable, this prints the stack-frame offset at which the variable |
| 8595 | is always stored. |
| 8596 | |
| 8597 | Note the contrast with @samp{print &@var{symbol}}, which does not work |
| 8598 | at all for a register variable, and for a stack local variable prints |
| 8599 | the exact address of the current instantiation of the variable. |
| 8600 | |
| 8601 | @kindex info symbol |
| 8602 | @cindex symbol from address |
| 8603 | @item info symbol @var{addr} |
| 8604 | Print the name of a symbol which is stored at the address @var{addr}. |
| 8605 | If no symbol is stored exactly at @var{addr}, @value{GDBN} prints the |
| 8606 | nearest symbol and an offset from it: |
| 8607 | |
| 8608 | @example |
| 8609 | (@value{GDBP}) info symbol 0x54320 |
| 8610 | _initialize_vx + 396 in section .text |
| 8611 | @end example |
| 8612 | |
| 8613 | @noindent |
| 8614 | This is the opposite of the @code{info address} command. You can use |
| 8615 | it to find out the name of a variable or a function given its address. |
| 8616 | |
| 8617 | @kindex whatis |
| 8618 | @item whatis @var{expr} |
| 8619 | Print the data type of expression @var{expr}. @var{expr} is not |
| 8620 | actually evaluated, and any side-effecting operations (such as |
| 8621 | assignments or function calls) inside it do not take place. |
| 8622 | @xref{Expressions, ,Expressions}. |
| 8623 | |
| 8624 | @item whatis |
| 8625 | Print the data type of @code{$}, the last value in the value history. |
| 8626 | |
| 8627 | @kindex ptype |
| 8628 | @item ptype @var{typename} |
| 8629 | Print a description of data type @var{typename}. @var{typename} may be |
| 8630 | the name of a type, or for C code it may have the form @samp{class |
| 8631 | @var{class-name}}, @samp{struct @var{struct-tag}}, @samp{union |
| 8632 | @var{union-tag}} or @samp{enum @var{enum-tag}}. |
| 8633 | |
| 8634 | @item ptype @var{expr} |
| 8635 | @itemx ptype |
| 8636 | Print a description of the type of expression @var{expr}. @code{ptype} |
| 8637 | differs from @code{whatis} by printing a detailed description, instead |
| 8638 | of just the name of the type. |
| 8639 | |
| 8640 | For example, for this variable declaration: |
| 8641 | |
| 8642 | @example |
| 8643 | struct complex @{double real; double imag;@} v; |
| 8644 | @end example |
| 8645 | |
| 8646 | @noindent |
| 8647 | the two commands give this output: |
| 8648 | |
| 8649 | @example |
| 8650 | @group |
| 8651 | (@value{GDBP}) whatis v |
| 8652 | type = struct complex |
| 8653 | (@value{GDBP}) ptype v |
| 8654 | type = struct complex @{ |
| 8655 | double real; |
| 8656 | double imag; |
| 8657 | @} |
| 8658 | @end group |
| 8659 | @end example |
| 8660 | |
| 8661 | @noindent |
| 8662 | As with @code{whatis}, using @code{ptype} without an argument refers to |
| 8663 | the type of @code{$}, the last value in the value history. |
| 8664 | |
| 8665 | @kindex info types |
| 8666 | @item info types @var{regexp} |
| 8667 | @itemx info types |
| 8668 | Print a brief description of all types whose names match @var{regexp} |
| 8669 | (or all types in your program, if you supply no argument). Each |
| 8670 | complete typename is matched as though it were a complete line; thus, |
| 8671 | @samp{i type value} gives information on all types in your program whose |
| 8672 | names include the string @code{value}, but @samp{i type ^value$} gives |
| 8673 | information only on types whose complete name is @code{value}. |
| 8674 | |
| 8675 | This command differs from @code{ptype} in two ways: first, like |
| 8676 | @code{whatis}, it does not print a detailed description; second, it |
| 8677 | lists all source files where a type is defined. |
| 8678 | |
| 8679 | @kindex info scope |
| 8680 | @cindex local variables |
| 8681 | @item info scope @var{addr} |
| 8682 | List all the variables local to a particular scope. This command |
| 8683 | accepts a location---a function name, a source line, or an address |
| 8684 | preceded by a @samp{*}, and prints all the variables local to the |
| 8685 | scope defined by that location. For example: |
| 8686 | |
| 8687 | @smallexample |
| 8688 | (@value{GDBP}) @b{info scope command_line_handler} |
| 8689 | Scope for command_line_handler: |
| 8690 | Symbol rl is an argument at stack/frame offset 8, length 4. |
| 8691 | Symbol linebuffer is in static storage at address 0x150a18, length 4. |
| 8692 | Symbol linelength is in static storage at address 0x150a1c, length 4. |
| 8693 | Symbol p is a local variable in register $esi, length 4. |
| 8694 | Symbol p1 is a local variable in register $ebx, length 4. |
| 8695 | Symbol nline is a local variable in register $edx, length 4. |
| 8696 | Symbol repeat is a local variable at frame offset -8, length 4. |
| 8697 | @end smallexample |
| 8698 | |
| 8699 | @noindent |
| 8700 | This command is especially useful for determining what data to collect |
| 8701 | during a @dfn{trace experiment}, see @ref{Tracepoint Actions, |
| 8702 | collect}. |
| 8703 | |
| 8704 | @kindex info source |
| 8705 | @item info source |
| 8706 | Show the name of the current source file---that is, the source file for |
| 8707 | the function containing the current point of execution---and the language |
| 8708 | it was written in. |
| 8709 | |
| 8710 | @kindex info sources |
| 8711 | @item info sources |
| 8712 | Print the names of all source files in your program for which there is |
| 8713 | debugging information, organized into two lists: files whose symbols |
| 8714 | have already been read, and files whose symbols will be read when needed. |
| 8715 | |
| 8716 | @kindex info functions |
| 8717 | @item info functions |
| 8718 | Print the names and data types of all defined functions. |
| 8719 | |
| 8720 | @item info functions @var{regexp} |
| 8721 | Print the names and data types of all defined functions |
| 8722 | whose names contain a match for regular expression @var{regexp}. |
| 8723 | Thus, @samp{info fun step} finds all functions whose names |
| 8724 | include @code{step}; @samp{info fun ^step} finds those whose names |
| 8725 | start with @code{step}. If a function name contains characters |
| 8726 | that conflict with the regular expression language (eg. |
| 8727 | @samp{operator*()}), they may be quoted with a backslash. |
| 8728 | |
| 8729 | @kindex info variables |
| 8730 | @item info variables |
| 8731 | Print the names and data types of all variables that are declared |
| 8732 | outside of functions (i.e.@: excluding local variables). |
| 8733 | |
| 8734 | @item info variables @var{regexp} |
| 8735 | Print the names and data types of all variables (except for local |
| 8736 | variables) whose names contain a match for regular expression |
| 8737 | @var{regexp}. |
| 8738 | |
| 8739 | @ignore |
| 8740 | This was never implemented. |
| 8741 | @kindex info methods |
| 8742 | @item info methods |
| 8743 | @itemx info methods @var{regexp} |
| 8744 | The @code{info methods} command permits the user to examine all defined |
| 8745 | methods within C@t{++} program, or (with the @var{regexp} argument) a |
| 8746 | specific set of methods found in the various C@t{++} classes. Many |
| 8747 | C@t{++} classes provide a large number of methods. Thus, the output |
| 8748 | from the @code{ptype} command can be overwhelming and hard to use. The |
| 8749 | @code{info-methods} command filters the methods, printing only those |
| 8750 | which match the regular-expression @var{regexp}. |
| 8751 | @end ignore |
| 8752 | |
| 8753 | @cindex reloading symbols |
| 8754 | Some systems allow individual object files that make up your program to |
| 8755 | be replaced without stopping and restarting your program. For example, |
| 8756 | in VxWorks you can simply recompile a defective object file and keep on |
| 8757 | running. If you are running on one of these systems, you can allow |
| 8758 | @value{GDBN} to reload the symbols for automatically relinked modules: |
| 8759 | |
| 8760 | @table @code |
| 8761 | @kindex set symbol-reloading |
| 8762 | @item set symbol-reloading on |
| 8763 | Replace symbol definitions for the corresponding source file when an |
| 8764 | object file with a particular name is seen again. |
| 8765 | |
| 8766 | @item set symbol-reloading off |
| 8767 | Do not replace symbol definitions when encountering object files of the |
| 8768 | same name more than once. This is the default state; if you are not |
| 8769 | running on a system that permits automatic relinking of modules, you |
| 8770 | should leave @code{symbol-reloading} off, since otherwise @value{GDBN} |
| 8771 | may discard symbols when linking large programs, that may contain |
| 8772 | several modules (from different directories or libraries) with the same |
| 8773 | name. |
| 8774 | |
| 8775 | @kindex show symbol-reloading |
| 8776 | @item show symbol-reloading |
| 8777 | Show the current @code{on} or @code{off} setting. |
| 8778 | @end table |
| 8779 | |
| 8780 | @kindex set opaque-type-resolution |
| 8781 | @item set opaque-type-resolution on |
| 8782 | Tell @value{GDBN} to resolve opaque types. An opaque type is a type |
| 8783 | declared as a pointer to a @code{struct}, @code{class}, or |
| 8784 | @code{union}---for example, @code{struct MyType *}---that is used in one |
| 8785 | source file although the full declaration of @code{struct MyType} is in |
| 8786 | another source file. The default is on. |
| 8787 | |
| 8788 | A change in the setting of this subcommand will not take effect until |
| 8789 | the next time symbols for a file are loaded. |
| 8790 | |
| 8791 | @item set opaque-type-resolution off |
| 8792 | Tell @value{GDBN} not to resolve opaque types. In this case, the type |
| 8793 | is printed as follows: |
| 8794 | @smallexample |
| 8795 | @{<no data fields>@} |
| 8796 | @end smallexample |
| 8797 | |
| 8798 | @kindex show opaque-type-resolution |
| 8799 | @item show opaque-type-resolution |
| 8800 | Show whether opaque types are resolved or not. |
| 8801 | |
| 8802 | @kindex maint print symbols |
| 8803 | @cindex symbol dump |
| 8804 | @kindex maint print psymbols |
| 8805 | @cindex partial symbol dump |
| 8806 | @item maint print symbols @var{filename} |
| 8807 | @itemx maint print psymbols @var{filename} |
| 8808 | @itemx maint print msymbols @var{filename} |
| 8809 | Write a dump of debugging symbol data into the file @var{filename}. |
| 8810 | These commands are used to debug the @value{GDBN} symbol-reading code. Only |
| 8811 | symbols with debugging data are included. If you use @samp{maint print |
| 8812 | symbols}, @value{GDBN} includes all the symbols for which it has already |
| 8813 | collected full details: that is, @var{filename} reflects symbols for |
| 8814 | only those files whose symbols @value{GDBN} has read. You can use the |
| 8815 | command @code{info sources} to find out which files these are. If you |
| 8816 | use @samp{maint print psymbols} instead, the dump shows information about |
| 8817 | symbols that @value{GDBN} only knows partially---that is, symbols defined in |
| 8818 | files that @value{GDBN} has skimmed, but not yet read completely. Finally, |
| 8819 | @samp{maint print msymbols} dumps just the minimal symbol information |
| 8820 | required for each object file from which @value{GDBN} has read some symbols. |
| 8821 | @xref{Files, ,Commands to specify files}, for a discussion of how |
| 8822 | @value{GDBN} reads symbols (in the description of @code{symbol-file}). |
| 8823 | @end table |
| 8824 | |
| 8825 | @node Altering |
| 8826 | @chapter Altering Execution |
| 8827 | |
| 8828 | Once you think you have found an error in your program, you might want to |
| 8829 | find out for certain whether correcting the apparent error would lead to |
| 8830 | correct results in the rest of the run. You can find the answer by |
| 8831 | experiment, using the @value{GDBN} features for altering execution of the |
| 8832 | program. |
| 8833 | |
| 8834 | For example, you can store new values into variables or memory |
| 8835 | locations, give your program a signal, restart it at a different |
| 8836 | address, or even return prematurely from a function. |
| 8837 | |
| 8838 | @menu |
| 8839 | * Assignment:: Assignment to variables |
| 8840 | * Jumping:: Continuing at a different address |
| 8841 | * Signaling:: Giving your program a signal |
| 8842 | * Returning:: Returning from a function |
| 8843 | * Calling:: Calling your program's functions |
| 8844 | * Patching:: Patching your program |
| 8845 | @end menu |
| 8846 | |
| 8847 | @node Assignment |
| 8848 | @section Assignment to variables |
| 8849 | |
| 8850 | @cindex assignment |
| 8851 | @cindex setting variables |
| 8852 | To alter the value of a variable, evaluate an assignment expression. |
| 8853 | @xref{Expressions, ,Expressions}. For example, |
| 8854 | |
| 8855 | @example |
| 8856 | print x=4 |
| 8857 | @end example |
| 8858 | |
| 8859 | @noindent |
| 8860 | stores the value 4 into the variable @code{x}, and then prints the |
| 8861 | value of the assignment expression (which is 4). |
| 8862 | @xref{Languages, ,Using @value{GDBN} with Different Languages}, for more |
| 8863 | information on operators in supported languages. |
| 8864 | |
| 8865 | @kindex set variable |
| 8866 | @cindex variables, setting |
| 8867 | If you are not interested in seeing the value of the assignment, use the |
| 8868 | @code{set} command instead of the @code{print} command. @code{set} is |
| 8869 | really the same as @code{print} except that the expression's value is |
| 8870 | not printed and is not put in the value history (@pxref{Value History, |
| 8871 | ,Value history}). The expression is evaluated only for its effects. |
| 8872 | |
| 8873 | If the beginning of the argument string of the @code{set} command |
| 8874 | appears identical to a @code{set} subcommand, use the @code{set |
| 8875 | variable} command instead of just @code{set}. This command is identical |
| 8876 | to @code{set} except for its lack of subcommands. For example, if your |
| 8877 | program has a variable @code{width}, you get an error if you try to set |
| 8878 | a new value with just @samp{set width=13}, because @value{GDBN} has the |
| 8879 | command @code{set width}: |
| 8880 | |
| 8881 | @example |
| 8882 | (@value{GDBP}) whatis width |
| 8883 | type = double |
| 8884 | (@value{GDBP}) p width |
| 8885 | $4 = 13 |
| 8886 | (@value{GDBP}) set width=47 |
| 8887 | Invalid syntax in expression. |
| 8888 | @end example |
| 8889 | |
| 8890 | @noindent |
| 8891 | The invalid expression, of course, is @samp{=47}. In |
| 8892 | order to actually set the program's variable @code{width}, use |
| 8893 | |
| 8894 | @example |
| 8895 | (@value{GDBP}) set var width=47 |
| 8896 | @end example |
| 8897 | |
| 8898 | Because the @code{set} command has many subcommands that can conflict |
| 8899 | with the names of program variables, it is a good idea to use the |
| 8900 | @code{set variable} command instead of just @code{set}. For example, if |
| 8901 | your program has a variable @code{g}, you run into problems if you try |
| 8902 | to set a new value with just @samp{set g=4}, because @value{GDBN} has |
| 8903 | the command @code{set gnutarget}, abbreviated @code{set g}: |
| 8904 | |
| 8905 | @example |
| 8906 | @group |
| 8907 | (@value{GDBP}) whatis g |
| 8908 | type = double |
| 8909 | (@value{GDBP}) p g |
| 8910 | $1 = 1 |
| 8911 | (@value{GDBP}) set g=4 |
| 8912 | (@value{GDBP}) p g |
| 8913 | $2 = 1 |
| 8914 | (@value{GDBP}) r |
| 8915 | The program being debugged has been started already. |
| 8916 | Start it from the beginning? (y or n) y |
| 8917 | Starting program: /home/smith/cc_progs/a.out |
| 8918 | "/home/smith/cc_progs/a.out": can't open to read symbols: |
| 8919 | Invalid bfd target. |
| 8920 | (@value{GDBP}) show g |
| 8921 | The current BFD target is "=4". |
| 8922 | @end group |
| 8923 | @end example |
| 8924 | |
| 8925 | @noindent |
| 8926 | The program variable @code{g} did not change, and you silently set the |
| 8927 | @code{gnutarget} to an invalid value. In order to set the variable |
| 8928 | @code{g}, use |
| 8929 | |
| 8930 | @example |
| 8931 | (@value{GDBP}) set var g=4 |
| 8932 | @end example |
| 8933 | |
| 8934 | @value{GDBN} allows more implicit conversions in assignments than C; you can |
| 8935 | freely store an integer value into a pointer variable or vice versa, |
| 8936 | and you can convert any structure to any other structure that is the |
| 8937 | same length or shorter. |
| 8938 | @comment FIXME: how do structs align/pad in these conversions? |
| 8939 | @comment /doc@cygnus.com 18dec1990 |
| 8940 | |
| 8941 | To store values into arbitrary places in memory, use the @samp{@{@dots{}@}} |
| 8942 | construct to generate a value of specified type at a specified address |
| 8943 | (@pxref{Expressions, ,Expressions}). For example, @code{@{int@}0x83040} refers |
| 8944 | to memory location @code{0x83040} as an integer (which implies a certain size |
| 8945 | and representation in memory), and |
| 8946 | |
| 8947 | @example |
| 8948 | set @{int@}0x83040 = 4 |
| 8949 | @end example |
| 8950 | |
| 8951 | @noindent |
| 8952 | stores the value 4 into that memory location. |
| 8953 | |
| 8954 | @node Jumping |
| 8955 | @section Continuing at a different address |
| 8956 | |
| 8957 | Ordinarily, when you continue your program, you do so at the place where |
| 8958 | it stopped, with the @code{continue} command. You can instead continue at |
| 8959 | an address of your own choosing, with the following commands: |
| 8960 | |
| 8961 | @table @code |
| 8962 | @kindex jump |
| 8963 | @item jump @var{linespec} |
| 8964 | Resume execution at line @var{linespec}. Execution stops again |
| 8965 | immediately if there is a breakpoint there. @xref{List, ,Printing |
| 8966 | source lines}, for a description of the different forms of |
| 8967 | @var{linespec}. It is common practice to use the @code{tbreak} command |
| 8968 | in conjunction with @code{jump}. @xref{Set Breaks, ,Setting |
| 8969 | breakpoints}. |
| 8970 | |
| 8971 | The @code{jump} command does not change the current stack frame, or |
| 8972 | the stack pointer, or the contents of any memory location or any |
| 8973 | register other than the program counter. If line @var{linespec} is in |
| 8974 | a different function from the one currently executing, the results may |
| 8975 | be bizarre if the two functions expect different patterns of arguments or |
| 8976 | of local variables. For this reason, the @code{jump} command requests |
| 8977 | confirmation if the specified line is not in the function currently |
| 8978 | executing. However, even bizarre results are predictable if you are |
| 8979 | well acquainted with the machine-language code of your program. |
| 8980 | |
| 8981 | @item jump *@var{address} |
| 8982 | Resume execution at the instruction at address @var{address}. |
| 8983 | @end table |
| 8984 | |
| 8985 | @c Doesn't work on HP-UX; have to set $pcoqh and $pcoqt. |
| 8986 | On many systems, you can get much the same effect as the @code{jump} |
| 8987 | command by storing a new value into the register @code{$pc}. The |
| 8988 | difference is that this does not start your program running; it only |
| 8989 | changes the address of where it @emph{will} run when you continue. For |
| 8990 | example, |
| 8991 | |
| 8992 | @example |
| 8993 | set $pc = 0x485 |
| 8994 | @end example |
| 8995 | |
| 8996 | @noindent |
| 8997 | makes the next @code{continue} command or stepping command execute at |
| 8998 | address @code{0x485}, rather than at the address where your program stopped. |
| 8999 | @xref{Continuing and Stepping, ,Continuing and stepping}. |
| 9000 | |
| 9001 | The most common occasion to use the @code{jump} command is to back |
| 9002 | up---perhaps with more breakpoints set---over a portion of a program |
| 9003 | that has already executed, in order to examine its execution in more |
| 9004 | detail. |
| 9005 | |
| 9006 | @c @group |
| 9007 | @node Signaling |
| 9008 | @section Giving your program a signal |
| 9009 | |
| 9010 | @table @code |
| 9011 | @kindex signal |
| 9012 | @item signal @var{signal} |
| 9013 | Resume execution where your program stopped, but immediately give it the |
| 9014 | signal @var{signal}. @var{signal} can be the name or the number of a |
| 9015 | signal. For example, on many systems @code{signal 2} and @code{signal |
| 9016 | SIGINT} are both ways of sending an interrupt signal. |
| 9017 | |
| 9018 | Alternatively, if @var{signal} is zero, continue execution without |
| 9019 | giving a signal. This is useful when your program stopped on account of |
| 9020 | a signal and would ordinary see the signal when resumed with the |
| 9021 | @code{continue} command; @samp{signal 0} causes it to resume without a |
| 9022 | signal. |
| 9023 | |
| 9024 | @code{signal} does not repeat when you press @key{RET} a second time |
| 9025 | after executing the command. |
| 9026 | @end table |
| 9027 | @c @end group |
| 9028 | |
| 9029 | Invoking the @code{signal} command is not the same as invoking the |
| 9030 | @code{kill} utility from the shell. Sending a signal with @code{kill} |
| 9031 | causes @value{GDBN} to decide what to do with the signal depending on |
| 9032 | the signal handling tables (@pxref{Signals}). The @code{signal} command |
| 9033 | passes the signal directly to your program. |
| 9034 | |
| 9035 | |
| 9036 | @node Returning |
| 9037 | @section Returning from a function |
| 9038 | |
| 9039 | @table @code |
| 9040 | @cindex returning from a function |
| 9041 | @kindex return |
| 9042 | @item return |
| 9043 | @itemx return @var{expression} |
| 9044 | You can cancel execution of a function call with the @code{return} |
| 9045 | command. If you give an |
| 9046 | @var{expression} argument, its value is used as the function's return |
| 9047 | value. |
| 9048 | @end table |
| 9049 | |
| 9050 | When you use @code{return}, @value{GDBN} discards the selected stack frame |
| 9051 | (and all frames within it). You can think of this as making the |
| 9052 | discarded frame return prematurely. If you wish to specify a value to |
| 9053 | be returned, give that value as the argument to @code{return}. |
| 9054 | |
| 9055 | This pops the selected stack frame (@pxref{Selection, ,Selecting a |
| 9056 | frame}), and any other frames inside of it, leaving its caller as the |
| 9057 | innermost remaining frame. That frame becomes selected. The |
| 9058 | specified value is stored in the registers used for returning values |
| 9059 | of functions. |
| 9060 | |
| 9061 | The @code{return} command does not resume execution; it leaves the |
| 9062 | program stopped in the state that would exist if the function had just |
| 9063 | returned. In contrast, the @code{finish} command (@pxref{Continuing |
| 9064 | and Stepping, ,Continuing and stepping}) resumes execution until the |
| 9065 | selected stack frame returns naturally. |
| 9066 | |
| 9067 | @node Calling |
| 9068 | @section Calling program functions |
| 9069 | |
| 9070 | @cindex calling functions |
| 9071 | @kindex call |
| 9072 | @table @code |
| 9073 | @item call @var{expr} |
| 9074 | Evaluate the expression @var{expr} without displaying @code{void} |
| 9075 | returned values. |
| 9076 | @end table |
| 9077 | |
| 9078 | You can use this variant of the @code{print} command if you want to |
| 9079 | execute a function from your program, but without cluttering the output |
| 9080 | with @code{void} returned values. If the result is not void, it |
| 9081 | is printed and saved in the value history. |
| 9082 | |
| 9083 | @c OBSOLETE For the A29K, a user-controlled variable @code{call_scratch_address}, |
| 9084 | @c OBSOLETE specifies the location of a scratch area to be used when @value{GDBN} |
| 9085 | @c OBSOLETE calls a function in the target. This is necessary because the usual |
| 9086 | @c OBSOLETE method of putting the scratch area on the stack does not work in systems |
| 9087 | @c OBSOLETE that have separate instruction and data spaces. |
| 9088 | |
| 9089 | @node Patching |
| 9090 | @section Patching programs |
| 9091 | |
| 9092 | @cindex patching binaries |
| 9093 | @cindex writing into executables |
| 9094 | @cindex writing into corefiles |
| 9095 | |
| 9096 | By default, @value{GDBN} opens the file containing your program's |
| 9097 | executable code (or the corefile) read-only. This prevents accidental |
| 9098 | alterations to machine code; but it also prevents you from intentionally |
| 9099 | patching your program's binary. |
| 9100 | |
| 9101 | If you'd like to be able to patch the binary, you can specify that |
| 9102 | explicitly with the @code{set write} command. For example, you might |
| 9103 | want to turn on internal debugging flags, or even to make emergency |
| 9104 | repairs. |
| 9105 | |
| 9106 | @table @code |
| 9107 | @kindex set write |
| 9108 | @item set write on |
| 9109 | @itemx set write off |
| 9110 | If you specify @samp{set write on}, @value{GDBN} opens executable and |
| 9111 | core files for both reading and writing; if you specify @samp{set write |
| 9112 | off} (the default), @value{GDBN} opens them read-only. |
| 9113 | |
| 9114 | If you have already loaded a file, you must load it again (using the |
| 9115 | @code{exec-file} or @code{core-file} command) after changing @code{set |
| 9116 | write}, for your new setting to take effect. |
| 9117 | |
| 9118 | @item show write |
| 9119 | @kindex show write |
| 9120 | Display whether executable files and core files are opened for writing |
| 9121 | as well as reading. |
| 9122 | @end table |
| 9123 | |
| 9124 | @node GDB Files |
| 9125 | @chapter @value{GDBN} Files |
| 9126 | |
| 9127 | @value{GDBN} needs to know the file name of the program to be debugged, |
| 9128 | both in order to read its symbol table and in order to start your |
| 9129 | program. To debug a core dump of a previous run, you must also tell |
| 9130 | @value{GDBN} the name of the core dump file. |
| 9131 | |
| 9132 | @menu |
| 9133 | * Files:: Commands to specify files |
| 9134 | * Symbol Errors:: Errors reading symbol files |
| 9135 | @end menu |
| 9136 | |
| 9137 | @node Files |
| 9138 | @section Commands to specify files |
| 9139 | |
| 9140 | @cindex symbol table |
| 9141 | @cindex core dump file |
| 9142 | |
| 9143 | You may want to specify executable and core dump file names. The usual |
| 9144 | way to do this is at start-up time, using the arguments to |
| 9145 | @value{GDBN}'s start-up commands (@pxref{Invocation, , Getting In and |
| 9146 | Out of @value{GDBN}}). |
| 9147 | |
| 9148 | Occasionally it is necessary to change to a different file during a |
| 9149 | @value{GDBN} session. Or you may run @value{GDBN} and forget to specify |
| 9150 | a file you want to use. In these situations the @value{GDBN} commands |
| 9151 | to specify new files are useful. |
| 9152 | |
| 9153 | @table @code |
| 9154 | @cindex executable file |
| 9155 | @kindex file |
| 9156 | @item file @var{filename} |
| 9157 | Use @var{filename} as the program to be debugged. It is read for its |
| 9158 | symbols and for the contents of pure memory. It is also the program |
| 9159 | executed when you use the @code{run} command. If you do not specify a |
| 9160 | directory and the file is not found in the @value{GDBN} working directory, |
| 9161 | @value{GDBN} uses the environment variable @code{PATH} as a list of |
| 9162 | directories to search, just as the shell does when looking for a program |
| 9163 | to run. You can change the value of this variable, for both @value{GDBN} |
| 9164 | and your program, using the @code{path} command. |
| 9165 | |
| 9166 | On systems with memory-mapped files, an auxiliary file named |
| 9167 | @file{@var{filename}.syms} may hold symbol table information for |
| 9168 | @var{filename}. If so, @value{GDBN} maps in the symbol table from |
| 9169 | @file{@var{filename}.syms}, starting up more quickly. See the |
| 9170 | descriptions of the file options @samp{-mapped} and @samp{-readnow} |
| 9171 | (available on the command line, and with the commands @code{file}, |
| 9172 | @code{symbol-file}, or @code{add-symbol-file}, described below), |
| 9173 | for more information. |
| 9174 | |
| 9175 | @item file |
| 9176 | @code{file} with no argument makes @value{GDBN} discard any information it |
| 9177 | has on both executable file and the symbol table. |
| 9178 | |
| 9179 | @kindex exec-file |
| 9180 | @item exec-file @r{[} @var{filename} @r{]} |
| 9181 | Specify that the program to be run (but not the symbol table) is found |
| 9182 | in @var{filename}. @value{GDBN} searches the environment variable @code{PATH} |
| 9183 | if necessary to locate your program. Omitting @var{filename} means to |
| 9184 | discard information on the executable file. |
| 9185 | |
| 9186 | @kindex symbol-file |
| 9187 | @item symbol-file @r{[} @var{filename} @r{]} |
| 9188 | Read symbol table information from file @var{filename}. @code{PATH} is |
| 9189 | searched when necessary. Use the @code{file} command to get both symbol |
| 9190 | table and program to run from the same file. |
| 9191 | |
| 9192 | @code{symbol-file} with no argument clears out @value{GDBN} information on your |
| 9193 | program's symbol table. |
| 9194 | |
| 9195 | The @code{symbol-file} command causes @value{GDBN} to forget the contents |
| 9196 | of its convenience variables, the value history, and all breakpoints and |
| 9197 | auto-display expressions. This is because they may contain pointers to |
| 9198 | the internal data recording symbols and data types, which are part of |
| 9199 | the old symbol table data being discarded inside @value{GDBN}. |
| 9200 | |
| 9201 | @code{symbol-file} does not repeat if you press @key{RET} again after |
| 9202 | executing it once. |
| 9203 | |
| 9204 | When @value{GDBN} is configured for a particular environment, it |
| 9205 | understands debugging information in whatever format is the standard |
| 9206 | generated for that environment; you may use either a @sc{gnu} compiler, or |
| 9207 | other compilers that adhere to the local conventions. |
| 9208 | Best results are usually obtained from @sc{gnu} compilers; for example, |
| 9209 | using @code{@value{GCC}} you can generate debugging information for |
| 9210 | optimized code. |
| 9211 | |
| 9212 | For most kinds of object files, with the exception of old SVR3 systems |
| 9213 | using COFF, the @code{symbol-file} command does not normally read the |
| 9214 | symbol table in full right away. Instead, it scans the symbol table |
| 9215 | quickly to find which source files and which symbols are present. The |
| 9216 | details are read later, one source file at a time, as they are needed. |
| 9217 | |
| 9218 | The purpose of this two-stage reading strategy is to make @value{GDBN} |
| 9219 | start up faster. For the most part, it is invisible except for |
| 9220 | occasional pauses while the symbol table details for a particular source |
| 9221 | file are being read. (The @code{set verbose} command can turn these |
| 9222 | pauses into messages if desired. @xref{Messages/Warnings, ,Optional |
| 9223 | warnings and messages}.) |
| 9224 | |
| 9225 | We have not implemented the two-stage strategy for COFF yet. When the |
| 9226 | symbol table is stored in COFF format, @code{symbol-file} reads the |
| 9227 | symbol table data in full right away. Note that ``stabs-in-COFF'' |
| 9228 | still does the two-stage strategy, since the debug info is actually |
| 9229 | in stabs format. |
| 9230 | |
| 9231 | @kindex readnow |
| 9232 | @cindex reading symbols immediately |
| 9233 | @cindex symbols, reading immediately |
| 9234 | @kindex mapped |
| 9235 | @cindex memory-mapped symbol file |
| 9236 | @cindex saving symbol table |
| 9237 | @item symbol-file @var{filename} @r{[} -readnow @r{]} @r{[} -mapped @r{]} |
| 9238 | @itemx file @var{filename} @r{[} -readnow @r{]} @r{[} -mapped @r{]} |
| 9239 | You can override the @value{GDBN} two-stage strategy for reading symbol |
| 9240 | tables by using the @samp{-readnow} option with any of the commands that |
| 9241 | load symbol table information, if you want to be sure @value{GDBN} has the |
| 9242 | entire symbol table available. |
| 9243 | |
| 9244 | If memory-mapped files are available on your system through the |
| 9245 | @code{mmap} system call, you can use another option, @samp{-mapped}, to |
| 9246 | cause @value{GDBN} to write the symbols for your program into a reusable |
| 9247 | file. Future @value{GDBN} debugging sessions map in symbol information |
| 9248 | from this auxiliary symbol file (if the program has not changed), rather |
| 9249 | than spending time reading the symbol table from the executable |
| 9250 | program. Using the @samp{-mapped} option has the same effect as |
| 9251 | starting @value{GDBN} with the @samp{-mapped} command-line option. |
| 9252 | |
| 9253 | You can use both options together, to make sure the auxiliary symbol |
| 9254 | file has all the symbol information for your program. |
| 9255 | |
| 9256 | The auxiliary symbol file for a program called @var{myprog} is called |
| 9257 | @samp{@var{myprog}.syms}. Once this file exists (so long as it is newer |
| 9258 | than the corresponding executable), @value{GDBN} always attempts to use |
| 9259 | it when you debug @var{myprog}; no special options or commands are |
| 9260 | needed. |
| 9261 | |
| 9262 | The @file{.syms} file is specific to the host machine where you run |
| 9263 | @value{GDBN}. It holds an exact image of the internal @value{GDBN} |
| 9264 | symbol table. It cannot be shared across multiple host platforms. |
| 9265 | |
| 9266 | @c FIXME: for now no mention of directories, since this seems to be in |
| 9267 | @c flux. 13mar1992 status is that in theory GDB would look either in |
| 9268 | @c current dir or in same dir as myprog; but issues like competing |
| 9269 | @c GDB's, or clutter in system dirs, mean that in practice right now |
| 9270 | @c only current dir is used. FFish says maybe a special GDB hierarchy |
| 9271 | @c (eg rooted in val of env var GDBSYMS) could exist for mappable symbol |
| 9272 | @c files. |
| 9273 | |
| 9274 | @kindex core |
| 9275 | @kindex core-file |
| 9276 | @item core-file @r{[} @var{filename} @r{]} |
| 9277 | Specify the whereabouts of a core dump file to be used as the ``contents |
| 9278 | of memory''. Traditionally, core files contain only some parts of the |
| 9279 | address space of the process that generated them; @value{GDBN} can access the |
| 9280 | executable file itself for other parts. |
| 9281 | |
| 9282 | @code{core-file} with no argument specifies that no core file is |
| 9283 | to be used. |
| 9284 | |
| 9285 | Note that the core file is ignored when your program is actually running |
| 9286 | under @value{GDBN}. So, if you have been running your program and you |
| 9287 | wish to debug a core file instead, you must kill the subprocess in which |
| 9288 | the program is running. To do this, use the @code{kill} command |
| 9289 | (@pxref{Kill Process, ,Killing the child process}). |
| 9290 | |
| 9291 | @kindex add-symbol-file |
| 9292 | @cindex dynamic linking |
| 9293 | @item add-symbol-file @var{filename} @var{address} |
| 9294 | @itemx add-symbol-file @var{filename} @var{address} @r{[} -readnow @r{]} @r{[} -mapped @r{]} |
| 9295 | @itemx add-symbol-file @var{filename} @r{-s}@var{section} @var{address} @dots{} |
| 9296 | The @code{add-symbol-file} command reads additional symbol table |
| 9297 | information from the file @var{filename}. You would use this command |
| 9298 | when @var{filename} has been dynamically loaded (by some other means) |
| 9299 | into the program that is running. @var{address} should be the memory |
| 9300 | address at which the file has been loaded; @value{GDBN} cannot figure |
| 9301 | this out for itself. You can additionally specify an arbitrary number |
| 9302 | of @samp{@r{-s}@var{section} @var{address}} pairs, to give an explicit |
| 9303 | section name and base address for that section. You can specify any |
| 9304 | @var{address} as an expression. |
| 9305 | |
| 9306 | The symbol table of the file @var{filename} is added to the symbol table |
| 9307 | originally read with the @code{symbol-file} command. You can use the |
| 9308 | @code{add-symbol-file} command any number of times; the new symbol data |
| 9309 | thus read keeps adding to the old. To discard all old symbol data |
| 9310 | instead, use the @code{symbol-file} command without any arguments. |
| 9311 | |
| 9312 | @cindex relocatable object files, reading symbols from |
| 9313 | @cindex object files, relocatable, reading symbols from |
| 9314 | @cindex reading symbols from relocatable object files |
| 9315 | @cindex symbols, reading from relocatable object files |
| 9316 | @cindex @file{.o} files, reading symbols from |
| 9317 | Although @var{filename} is typically a shared library file, an |
| 9318 | executable file, or some other object file which has been fully |
| 9319 | relocated for loading into a process, you can also load symbolic |
| 9320 | information from relocatable @file{.o} files, as long as: |
| 9321 | |
| 9322 | @itemize @bullet |
| 9323 | @item |
| 9324 | the file's symbolic information refers only to linker symbols defined in |
| 9325 | that file, not to symbols defined by other object files, |
| 9326 | @item |
| 9327 | every section the file's symbolic information refers to has actually |
| 9328 | been loaded into the inferior, as it appears in the file, and |
| 9329 | @item |
| 9330 | you can determine the address at which every section was loaded, and |
| 9331 | provide these to the @code{add-symbol-file} command. |
| 9332 | @end itemize |
| 9333 | |
| 9334 | @noindent |
| 9335 | Some embedded operating systems, like Sun Chorus and VxWorks, can load |
| 9336 | relocatable files into an already running program; such systems |
| 9337 | typically make the requirements above easy to meet. However, it's |
| 9338 | important to recognize that many native systems use complex link |
| 9339 | procedures (@code{.linkonce} section factoring and C++ constructor table |
| 9340 | assembly, for example) that make the requirements difficult to meet. In |
| 9341 | general, one cannot assume that using @code{add-symbol-file} to read a |
| 9342 | relocatable object file's symbolic information will have the same effect |
| 9343 | as linking the relocatable object file into the program in the normal |
| 9344 | way. |
| 9345 | |
| 9346 | @code{add-symbol-file} does not repeat if you press @key{RET} after using it. |
| 9347 | |
| 9348 | You can use the @samp{-mapped} and @samp{-readnow} options just as with |
| 9349 | the @code{symbol-file} command, to change how @value{GDBN} manages the symbol |
| 9350 | table information for @var{filename}. |
| 9351 | |
| 9352 | @kindex add-shared-symbol-file |
| 9353 | @item add-shared-symbol-file |
| 9354 | The @code{add-shared-symbol-file} command can be used only under Harris' CXUX |
| 9355 | operating system for the Motorola 88k. @value{GDBN} automatically looks for |
| 9356 | shared libraries, however if @value{GDBN} does not find yours, you can run |
| 9357 | @code{add-shared-symbol-file}. It takes no arguments. |
| 9358 | |
| 9359 | @kindex section |
| 9360 | @item section |
| 9361 | The @code{section} command changes the base address of section SECTION of |
| 9362 | the exec file to ADDR. This can be used if the exec file does not contain |
| 9363 | section addresses, (such as in the a.out format), or when the addresses |
| 9364 | specified in the file itself are wrong. Each section must be changed |
| 9365 | separately. The @code{info files} command, described below, lists all |
| 9366 | the sections and their addresses. |
| 9367 | |
| 9368 | @kindex info files |
| 9369 | @kindex info target |
| 9370 | @item info files |
| 9371 | @itemx info target |
| 9372 | @code{info files} and @code{info target} are synonymous; both print the |
| 9373 | current target (@pxref{Targets, ,Specifying a Debugging Target}), |
| 9374 | including the names of the executable and core dump files currently in |
| 9375 | use by @value{GDBN}, and the files from which symbols were loaded. The |
| 9376 | command @code{help target} lists all possible targets rather than |
| 9377 | current ones. |
| 9378 | |
| 9379 | @kindex maint info sections |
| 9380 | @item maint info sections |
| 9381 | Another command that can give you extra information about program sections |
| 9382 | is @code{maint info sections}. In addition to the section information |
| 9383 | displayed by @code{info files}, this command displays the flags and file |
| 9384 | offset of each section in the executable and core dump files. In addition, |
| 9385 | @code{maint info sections} provides the following command options (which |
| 9386 | may be arbitrarily combined): |
| 9387 | |
| 9388 | @table @code |
| 9389 | @item ALLOBJ |
| 9390 | Display sections for all loaded object files, including shared libraries. |
| 9391 | @item @var{sections} |
| 9392 | Display info only for named @var{sections}. |
| 9393 | @item @var{section-flags} |
| 9394 | Display info only for sections for which @var{section-flags} are true. |
| 9395 | The section flags that @value{GDBN} currently knows about are: |
| 9396 | @table @code |
| 9397 | @item ALLOC |
| 9398 | Section will have space allocated in the process when loaded. |
| 9399 | Set for all sections except those containing debug information. |
| 9400 | @item LOAD |
| 9401 | Section will be loaded from the file into the child process memory. |
| 9402 | Set for pre-initialized code and data, clear for @code{.bss} sections. |
| 9403 | @item RELOC |
| 9404 | Section needs to be relocated before loading. |
| 9405 | @item READONLY |
| 9406 | Section cannot be modified by the child process. |
| 9407 | @item CODE |
| 9408 | Section contains executable code only. |
| 9409 | @item DATA |
| 9410 | Section contains data only (no executable code). |
| 9411 | @item ROM |
| 9412 | Section will reside in ROM. |
| 9413 | @item CONSTRUCTOR |
| 9414 | Section contains data for constructor/destructor lists. |
| 9415 | @item HAS_CONTENTS |
| 9416 | Section is not empty. |
| 9417 | @item NEVER_LOAD |
| 9418 | An instruction to the linker to not output the section. |
| 9419 | @item COFF_SHARED_LIBRARY |
| 9420 | A notification to the linker that the section contains |
| 9421 | COFF shared library information. |
| 9422 | @item IS_COMMON |
| 9423 | Section contains common symbols. |
| 9424 | @end table |
| 9425 | @end table |
| 9426 | @kindex set trust-readonly-sections |
| 9427 | @item set trust-readonly-sections on |
| 9428 | Tell @value{GDBN} that readonly sections in your object file |
| 9429 | really are read-only (i.e.@: that their contents will not change). |
| 9430 | In that case, @value{GDBN} can fetch values from these sections |
| 9431 | out of the object file, rather than from the target program. |
| 9432 | For some targets (notably embedded ones), this can be a significant |
| 9433 | enhancement to debugging performance. |
| 9434 | |
| 9435 | The default is off. |
| 9436 | |
| 9437 | @item set trust-readonly-sections off |
| 9438 | Tell @value{GDBN} not to trust readonly sections. This means that |
| 9439 | the contents of the section might change while the program is running, |
| 9440 | and must therefore be fetched from the target when needed. |
| 9441 | @end table |
| 9442 | |
| 9443 | All file-specifying commands allow both absolute and relative file names |
| 9444 | as arguments. @value{GDBN} always converts the file name to an absolute file |
| 9445 | name and remembers it that way. |
| 9446 | |
| 9447 | @cindex shared libraries |
| 9448 | @value{GDBN} supports HP-UX, SunOS, SVr4, Irix 5, and IBM RS/6000 shared |
| 9449 | libraries. |
| 9450 | |
| 9451 | @value{GDBN} automatically loads symbol definitions from shared libraries |
| 9452 | when you use the @code{run} command, or when you examine a core file. |
| 9453 | (Before you issue the @code{run} command, @value{GDBN} does not understand |
| 9454 | references to a function in a shared library, however---unless you are |
| 9455 | debugging a core file). |
| 9456 | |
| 9457 | On HP-UX, if the program loads a library explicitly, @value{GDBN} |
| 9458 | automatically loads the symbols at the time of the @code{shl_load} call. |
| 9459 | |
| 9460 | @c FIXME: some @value{GDBN} release may permit some refs to undef |
| 9461 | @c FIXME...symbols---eg in a break cmd---assuming they are from a shared |
| 9462 | @c FIXME...lib; check this from time to time when updating manual |
| 9463 | |
| 9464 | There are times, however, when you may wish to not automatically load |
| 9465 | symbol definitions from shared libraries, such as when they are |
| 9466 | particularly large or there are many of them. |
| 9467 | |
| 9468 | To control the automatic loading of shared library symbols, use the |
| 9469 | commands: |
| 9470 | |
| 9471 | @table @code |
| 9472 | @kindex set auto-solib-add |
| 9473 | @item set auto-solib-add @var{mode} |
| 9474 | If @var{mode} is @code{on}, symbols from all shared object libraries |
| 9475 | will be loaded automatically when the inferior begins execution, you |
| 9476 | attach to an independently started inferior, or when the dynamic linker |
| 9477 | informs @value{GDBN} that a new library has been loaded. If @var{mode} |
| 9478 | is @code{off}, symbols must be loaded manually, using the |
| 9479 | @code{sharedlibrary} command. The default value is @code{on}. |
| 9480 | |
| 9481 | @kindex show auto-solib-add |
| 9482 | @item show auto-solib-add |
| 9483 | Display the current autoloading mode. |
| 9484 | @end table |
| 9485 | |
| 9486 | To explicitly load shared library symbols, use the @code{sharedlibrary} |
| 9487 | command: |
| 9488 | |
| 9489 | @table @code |
| 9490 | @kindex info sharedlibrary |
| 9491 | @kindex info share |
| 9492 | @item info share |
| 9493 | @itemx info sharedlibrary |
| 9494 | Print the names of the shared libraries which are currently loaded. |
| 9495 | |
| 9496 | @kindex sharedlibrary |
| 9497 | @kindex share |
| 9498 | @item sharedlibrary @var{regex} |
| 9499 | @itemx share @var{regex} |
| 9500 | Load shared object library symbols for files matching a |
| 9501 | Unix regular expression. |
| 9502 | As with files loaded automatically, it only loads shared libraries |
| 9503 | required by your program for a core file or after typing @code{run}. If |
| 9504 | @var{regex} is omitted all shared libraries required by your program are |
| 9505 | loaded. |
| 9506 | @end table |
| 9507 | |
| 9508 | On some systems, such as HP-UX systems, @value{GDBN} supports |
| 9509 | autoloading shared library symbols until a limiting threshold size is |
| 9510 | reached. This provides the benefit of allowing autoloading to remain on |
| 9511 | by default, but avoids autoloading excessively large shared libraries, |
| 9512 | up to a threshold that is initially set, but which you can modify if you |
| 9513 | wish. |
| 9514 | |
| 9515 | Beyond that threshold, symbols from shared libraries must be explicitly |
| 9516 | loaded. To load these symbols, use the command @code{sharedlibrary |
| 9517 | @var{filename}}. The base address of the shared library is determined |
| 9518 | automatically by @value{GDBN} and need not be specified. |
| 9519 | |
| 9520 | To display or set the threshold, use the commands: |
| 9521 | |
| 9522 | @table @code |
| 9523 | @kindex set auto-solib-limit |
| 9524 | @item set auto-solib-limit @var{threshold} |
| 9525 | Set the autoloading size threshold, in an integral number of megabytes. |
| 9526 | If @var{threshold} is nonzero and shared library autoloading is enabled, |
| 9527 | symbols from all shared object libraries will be loaded until the total |
| 9528 | size of the loaded shared library symbols exceeds this threshold. |
| 9529 | Otherwise, symbols must be loaded manually, using the |
| 9530 | @code{sharedlibrary} command. The default threshold is 100 (i.e.@: 100 |
| 9531 | Mb). |
| 9532 | |
| 9533 | @kindex show auto-solib-limit |
| 9534 | @item show auto-solib-limit |
| 9535 | Display the current autoloading size threshold, in megabytes. |
| 9536 | @end table |
| 9537 | |
| 9538 | @node Symbol Errors |
| 9539 | @section Errors reading symbol files |
| 9540 | |
| 9541 | While reading a symbol file, @value{GDBN} occasionally encounters problems, |
| 9542 | such as symbol types it does not recognize, or known bugs in compiler |
| 9543 | output. By default, @value{GDBN} does not notify you of such problems, since |
| 9544 | they are relatively common and primarily of interest to people |
| 9545 | debugging compilers. If you are interested in seeing information |
| 9546 | about ill-constructed symbol tables, you can either ask @value{GDBN} to print |
| 9547 | only one message about each such type of problem, no matter how many |
| 9548 | times the problem occurs; or you can ask @value{GDBN} to print more messages, |
| 9549 | to see how many times the problems occur, with the @code{set |
| 9550 | complaints} command (@pxref{Messages/Warnings, ,Optional warnings and |
| 9551 | messages}). |
| 9552 | |
| 9553 | The messages currently printed, and their meanings, include: |
| 9554 | |
| 9555 | @table @code |
| 9556 | @item inner block not inside outer block in @var{symbol} |
| 9557 | |
| 9558 | The symbol information shows where symbol scopes begin and end |
| 9559 | (such as at the start of a function or a block of statements). This |
| 9560 | error indicates that an inner scope block is not fully contained |
| 9561 | in its outer scope blocks. |
| 9562 | |
| 9563 | @value{GDBN} circumvents the problem by treating the inner block as if it had |
| 9564 | the same scope as the outer block. In the error message, @var{symbol} |
| 9565 | may be shown as ``@code{(don't know)}'' if the outer block is not a |
| 9566 | function. |
| 9567 | |
| 9568 | @item block at @var{address} out of order |
| 9569 | |
| 9570 | The symbol information for symbol scope blocks should occur in |
| 9571 | order of increasing addresses. This error indicates that it does not |
| 9572 | do so. |
| 9573 | |
| 9574 | @value{GDBN} does not circumvent this problem, and has trouble |
| 9575 | locating symbols in the source file whose symbols it is reading. (You |
| 9576 | can often determine what source file is affected by specifying |
| 9577 | @code{set verbose on}. @xref{Messages/Warnings, ,Optional warnings and |
| 9578 | messages}.) |
| 9579 | |
| 9580 | @item bad block start address patched |
| 9581 | |
| 9582 | The symbol information for a symbol scope block has a start address |
| 9583 | smaller than the address of the preceding source line. This is known |
| 9584 | to occur in the SunOS 4.1.1 (and earlier) C compiler. |
| 9585 | |
| 9586 | @value{GDBN} circumvents the problem by treating the symbol scope block as |
| 9587 | starting on the previous source line. |
| 9588 | |
| 9589 | @item bad string table offset in symbol @var{n} |
| 9590 | |
| 9591 | @cindex foo |
| 9592 | Symbol number @var{n} contains a pointer into the string table which is |
| 9593 | larger than the size of the string table. |
| 9594 | |
| 9595 | @value{GDBN} circumvents the problem by considering the symbol to have the |
| 9596 | name @code{foo}, which may cause other problems if many symbols end up |
| 9597 | with this name. |
| 9598 | |
| 9599 | @item unknown symbol type @code{0x@var{nn}} |
| 9600 | |
| 9601 | The symbol information contains new data types that @value{GDBN} does |
| 9602 | not yet know how to read. @code{0x@var{nn}} is the symbol type of the |
| 9603 | uncomprehended information, in hexadecimal. |
| 9604 | |
| 9605 | @value{GDBN} circumvents the error by ignoring this symbol information. |
| 9606 | This usually allows you to debug your program, though certain symbols |
| 9607 | are not accessible. If you encounter such a problem and feel like |
| 9608 | debugging it, you can debug @code{@value{GDBP}} with itself, breakpoint |
| 9609 | on @code{complain}, then go up to the function @code{read_dbx_symtab} |
| 9610 | and examine @code{*bufp} to see the symbol. |
| 9611 | |
| 9612 | @item stub type has NULL name |
| 9613 | |
| 9614 | @value{GDBN} could not find the full definition for a struct or class. |
| 9615 | |
| 9616 | @item const/volatile indicator missing (ok if using g++ v1.x), got@dots{} |
| 9617 | The symbol information for a C@t{++} member function is missing some |
| 9618 | information that recent versions of the compiler should have output for |
| 9619 | it. |
| 9620 | |
| 9621 | @item info mismatch between compiler and debugger |
| 9622 | |
| 9623 | @value{GDBN} could not parse a type specification output by the compiler. |
| 9624 | |
| 9625 | @end table |
| 9626 | |
| 9627 | @node Targets |
| 9628 | @chapter Specifying a Debugging Target |
| 9629 | |
| 9630 | @cindex debugging target |
| 9631 | @kindex target |
| 9632 | |
| 9633 | A @dfn{target} is the execution environment occupied by your program. |
| 9634 | |
| 9635 | Often, @value{GDBN} runs in the same host environment as your program; |
| 9636 | in that case, the debugging target is specified as a side effect when |
| 9637 | you use the @code{file} or @code{core} commands. When you need more |
| 9638 | flexibility---for example, running @value{GDBN} on a physically separate |
| 9639 | host, or controlling a standalone system over a serial port or a |
| 9640 | realtime system over a TCP/IP connection---you can use the @code{target} |
| 9641 | command to specify one of the target types configured for @value{GDBN} |
| 9642 | (@pxref{Target Commands, ,Commands for managing targets}). |
| 9643 | |
| 9644 | @menu |
| 9645 | * Active Targets:: Active targets |
| 9646 | * Target Commands:: Commands for managing targets |
| 9647 | * Byte Order:: Choosing target byte order |
| 9648 | * Remote:: Remote debugging |
| 9649 | * KOD:: Kernel Object Display |
| 9650 | |
| 9651 | @end menu |
| 9652 | |
| 9653 | @node Active Targets |
| 9654 | @section Active targets |
| 9655 | |
| 9656 | @cindex stacking targets |
| 9657 | @cindex active targets |
| 9658 | @cindex multiple targets |
| 9659 | |
| 9660 | There are three classes of targets: processes, core files, and |
| 9661 | executable files. @value{GDBN} can work concurrently on up to three |
| 9662 | active targets, one in each class. This allows you to (for example) |
| 9663 | start a process and inspect its activity without abandoning your work on |
| 9664 | a core file. |
| 9665 | |
| 9666 | For example, if you execute @samp{gdb a.out}, then the executable file |
| 9667 | @code{a.out} is the only active target. If you designate a core file as |
| 9668 | well---presumably from a prior run that crashed and coredumped---then |
| 9669 | @value{GDBN} has two active targets and uses them in tandem, looking |
| 9670 | first in the corefile target, then in the executable file, to satisfy |
| 9671 | requests for memory addresses. (Typically, these two classes of target |
| 9672 | are complementary, since core files contain only a program's |
| 9673 | read-write memory---variables and so on---plus machine status, while |
| 9674 | executable files contain only the program text and initialized data.) |
| 9675 | |
| 9676 | When you type @code{run}, your executable file becomes an active process |
| 9677 | target as well. When a process target is active, all @value{GDBN} |
| 9678 | commands requesting memory addresses refer to that target; addresses in |
| 9679 | an active core file or executable file target are obscured while the |
| 9680 | process target is active. |
| 9681 | |
| 9682 | Use the @code{core-file} and @code{exec-file} commands to select a new |
| 9683 | core file or executable target (@pxref{Files, ,Commands to specify |
| 9684 | files}). To specify as a target a process that is already running, use |
| 9685 | the @code{attach} command (@pxref{Attach, ,Debugging an already-running |
| 9686 | process}). |
| 9687 | |
| 9688 | @node Target Commands |
| 9689 | @section Commands for managing targets |
| 9690 | |
| 9691 | @table @code |
| 9692 | @item target @var{type} @var{parameters} |
| 9693 | Connects the @value{GDBN} host environment to a target machine or |
| 9694 | process. A target is typically a protocol for talking to debugging |
| 9695 | facilities. You use the argument @var{type} to specify the type or |
| 9696 | protocol of the target machine. |
| 9697 | |
| 9698 | Further @var{parameters} are interpreted by the target protocol, but |
| 9699 | typically include things like device names or host names to connect |
| 9700 | with, process numbers, and baud rates. |
| 9701 | |
| 9702 | The @code{target} command does not repeat if you press @key{RET} again |
| 9703 | after executing the command. |
| 9704 | |
| 9705 | @kindex help target |
| 9706 | @item help target |
| 9707 | Displays the names of all targets available. To display targets |
| 9708 | currently selected, use either @code{info target} or @code{info files} |
| 9709 | (@pxref{Files, ,Commands to specify files}). |
| 9710 | |
| 9711 | @item help target @var{name} |
| 9712 | Describe a particular target, including any parameters necessary to |
| 9713 | select it. |
| 9714 | |
| 9715 | @kindex set gnutarget |
| 9716 | @item set gnutarget @var{args} |
| 9717 | @value{GDBN} uses its own library BFD to read your files. @value{GDBN} |
| 9718 | knows whether it is reading an @dfn{executable}, |
| 9719 | a @dfn{core}, or a @dfn{.o} file; however, you can specify the file format |
| 9720 | with the @code{set gnutarget} command. Unlike most @code{target} commands, |
| 9721 | with @code{gnutarget} the @code{target} refers to a program, not a machine. |
| 9722 | |
| 9723 | @quotation |
| 9724 | @emph{Warning:} To specify a file format with @code{set gnutarget}, |
| 9725 | you must know the actual BFD name. |
| 9726 | @end quotation |
| 9727 | |
| 9728 | @noindent |
| 9729 | @xref{Files, , Commands to specify files}. |
| 9730 | |
| 9731 | @kindex show gnutarget |
| 9732 | @item show gnutarget |
| 9733 | Use the @code{show gnutarget} command to display what file format |
| 9734 | @code{gnutarget} is set to read. If you have not set @code{gnutarget}, |
| 9735 | @value{GDBN} will determine the file format for each file automatically, |
| 9736 | and @code{show gnutarget} displays @samp{The current BDF target is "auto"}. |
| 9737 | @end table |
| 9738 | |
| 9739 | Here are some common targets (available, or not, depending on the GDB |
| 9740 | configuration): |
| 9741 | |
| 9742 | @table @code |
| 9743 | @kindex target exec |
| 9744 | @item target exec @var{program} |
| 9745 | An executable file. @samp{target exec @var{program}} is the same as |
| 9746 | @samp{exec-file @var{program}}. |
| 9747 | |
| 9748 | @kindex target core |
| 9749 | @item target core @var{filename} |
| 9750 | A core dump file. @samp{target core @var{filename}} is the same as |
| 9751 | @samp{core-file @var{filename}}. |
| 9752 | |
| 9753 | @kindex target remote |
| 9754 | @item target remote @var{dev} |
| 9755 | Remote serial target in GDB-specific protocol. The argument @var{dev} |
| 9756 | specifies what serial device to use for the connection (e.g. |
| 9757 | @file{/dev/ttya}). @xref{Remote, ,Remote debugging}. @code{target remote} |
| 9758 | supports the @code{load} command. This is only useful if you have |
| 9759 | some other way of getting the stub to the target system, and you can put |
| 9760 | it somewhere in memory where it won't get clobbered by the download. |
| 9761 | |
| 9762 | @kindex target sim |
| 9763 | @item target sim |
| 9764 | Builtin CPU simulator. @value{GDBN} includes simulators for most architectures. |
| 9765 | In general, |
| 9766 | @example |
| 9767 | target sim |
| 9768 | load |
| 9769 | run |
| 9770 | @end example |
| 9771 | @noindent |
| 9772 | works; however, you cannot assume that a specific memory map, device |
| 9773 | drivers, or even basic I/O is available, although some simulators do |
| 9774 | provide these. For info about any processor-specific simulator details, |
| 9775 | see the appropriate section in @ref{Embedded Processors, ,Embedded |
| 9776 | Processors}. |
| 9777 | |
| 9778 | @end table |
| 9779 | |
| 9780 | Some configurations may include these targets as well: |
| 9781 | |
| 9782 | @table @code |
| 9783 | |
| 9784 | @kindex target nrom |
| 9785 | @item target nrom @var{dev} |
| 9786 | NetROM ROM emulator. This target only supports downloading. |
| 9787 | |
| 9788 | @end table |
| 9789 | |
| 9790 | Different targets are available on different configurations of @value{GDBN}; |
| 9791 | your configuration may have more or fewer targets. |
| 9792 | |
| 9793 | Many remote targets require you to download the executable's code |
| 9794 | once you've successfully established a connection. |
| 9795 | |
| 9796 | @table @code |
| 9797 | |
| 9798 | @kindex load @var{filename} |
| 9799 | @item load @var{filename} |
| 9800 | Depending on what remote debugging facilities are configured into |
| 9801 | @value{GDBN}, the @code{load} command may be available. Where it exists, it |
| 9802 | is meant to make @var{filename} (an executable) available for debugging |
| 9803 | on the remote system---by downloading, or dynamic linking, for example. |
| 9804 | @code{load} also records the @var{filename} symbol table in @value{GDBN}, like |
| 9805 | the @code{add-symbol-file} command. |
| 9806 | |
| 9807 | If your @value{GDBN} does not have a @code{load} command, attempting to |
| 9808 | execute it gets the error message ``@code{You can't do that when your |
| 9809 | target is @dots{}}'' |
| 9810 | |
| 9811 | The file is loaded at whatever address is specified in the executable. |
| 9812 | For some object file formats, you can specify the load address when you |
| 9813 | link the program; for other formats, like a.out, the object file format |
| 9814 | specifies a fixed address. |
| 9815 | @c FIXME! This would be a good place for an xref to the GNU linker doc. |
| 9816 | |
| 9817 | @code{load} does not repeat if you press @key{RET} again after using it. |
| 9818 | @end table |
| 9819 | |
| 9820 | @node Byte Order |
| 9821 | @section Choosing target byte order |
| 9822 | |
| 9823 | @cindex choosing target byte order |
| 9824 | @cindex target byte order |
| 9825 | |
| 9826 | Some types of processors, such as the MIPS, PowerPC, and Hitachi SH, |
| 9827 | offer the ability to run either big-endian or little-endian byte |
| 9828 | orders. Usually the executable or symbol will include a bit to |
| 9829 | designate the endian-ness, and you will not need to worry about |
| 9830 | which to use. However, you may still find it useful to adjust |
| 9831 | @value{GDBN}'s idea of processor endian-ness manually. |
| 9832 | |
| 9833 | @table @code |
| 9834 | @kindex set endian big |
| 9835 | @item set endian big |
| 9836 | Instruct @value{GDBN} to assume the target is big-endian. |
| 9837 | |
| 9838 | @kindex set endian little |
| 9839 | @item set endian little |
| 9840 | Instruct @value{GDBN} to assume the target is little-endian. |
| 9841 | |
| 9842 | @kindex set endian auto |
| 9843 | @item set endian auto |
| 9844 | Instruct @value{GDBN} to use the byte order associated with the |
| 9845 | executable. |
| 9846 | |
| 9847 | @item show endian |
| 9848 | Display @value{GDBN}'s current idea of the target byte order. |
| 9849 | |
| 9850 | @end table |
| 9851 | |
| 9852 | Note that these commands merely adjust interpretation of symbolic |
| 9853 | data on the host, and that they have absolutely no effect on the |
| 9854 | target system. |
| 9855 | |
| 9856 | @node Remote |
| 9857 | @section Remote debugging |
| 9858 | @cindex remote debugging |
| 9859 | |
| 9860 | If you are trying to debug a program running on a machine that cannot run |
| 9861 | @value{GDBN} in the usual way, it is often useful to use remote debugging. |
| 9862 | For example, you might use remote debugging on an operating system kernel, |
| 9863 | or on a small system which does not have a general purpose operating system |
| 9864 | powerful enough to run a full-featured debugger. |
| 9865 | |
| 9866 | Some configurations of @value{GDBN} have special serial or TCP/IP interfaces |
| 9867 | to make this work with particular debugging targets. In addition, |
| 9868 | @value{GDBN} comes with a generic serial protocol (specific to @value{GDBN}, |
| 9869 | but not specific to any particular target system) which you can use if you |
| 9870 | write the remote stubs---the code that runs on the remote system to |
| 9871 | communicate with @value{GDBN}. |
| 9872 | |
| 9873 | Other remote targets may be available in your |
| 9874 | configuration of @value{GDBN}; use @code{help target} to list them. |
| 9875 | |
| 9876 | @node KOD |
| 9877 | @section Kernel Object Display |
| 9878 | |
| 9879 | @cindex kernel object display |
| 9880 | @cindex kernel object |
| 9881 | @cindex KOD |
| 9882 | |
| 9883 | Some targets support kernel object display. Using this facility, |
| 9884 | @value{GDBN} communicates specially with the underlying operating system |
| 9885 | and can display information about operating system-level objects such as |
| 9886 | mutexes and other synchronization objects. Exactly which objects can be |
| 9887 | displayed is determined on a per-OS basis. |
| 9888 | |
| 9889 | Use the @code{set os} command to set the operating system. This tells |
| 9890 | @value{GDBN} which kernel object display module to initialize: |
| 9891 | |
| 9892 | @example |
| 9893 | (@value{GDBP}) set os cisco |
| 9894 | @end example |
| 9895 | |
| 9896 | If @code{set os} succeeds, @value{GDBN} will display some information |
| 9897 | about the operating system, and will create a new @code{info} command |
| 9898 | which can be used to query the target. The @code{info} command is named |
| 9899 | after the operating system: |
| 9900 | |
| 9901 | @example |
| 9902 | (@value{GDBP}) info cisco |
| 9903 | List of Cisco Kernel Objects |
| 9904 | Object Description |
| 9905 | any Any and all objects |
| 9906 | @end example |
| 9907 | |
| 9908 | Further subcommands can be used to query about particular objects known |
| 9909 | by the kernel. |
| 9910 | |
| 9911 | There is currently no way to determine whether a given operating system |
| 9912 | is supported other than to try it. |
| 9913 | |
| 9914 | |
| 9915 | @node Remote Debugging |
| 9916 | @chapter Debugging remote programs |
| 9917 | |
| 9918 | @menu |
| 9919 | * Server:: Using the gdbserver program |
| 9920 | * NetWare:: Using the gdbserve.nlm program |
| 9921 | * remote stub:: Implementing a remote stub |
| 9922 | @end menu |
| 9923 | |
| 9924 | @node Server |
| 9925 | @section Using the @code{gdbserver} program |
| 9926 | |
| 9927 | @kindex gdbserver |
| 9928 | @cindex remote connection without stubs |
| 9929 | @code{gdbserver} is a control program for Unix-like systems, which |
| 9930 | allows you to connect your program with a remote @value{GDBN} via |
| 9931 | @code{target remote}---but without linking in the usual debugging stub. |
| 9932 | |
| 9933 | @code{gdbserver} is not a complete replacement for the debugging stubs, |
| 9934 | because it requires essentially the same operating-system facilities |
| 9935 | that @value{GDBN} itself does. In fact, a system that can run |
| 9936 | @code{gdbserver} to connect to a remote @value{GDBN} could also run |
| 9937 | @value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless, |
| 9938 | because it is a much smaller program than @value{GDBN} itself. It is |
| 9939 | also easier to port than all of @value{GDBN}, so you may be able to get |
| 9940 | started more quickly on a new system by using @code{gdbserver}. |
| 9941 | Finally, if you develop code for real-time systems, you may find that |
| 9942 | the tradeoffs involved in real-time operation make it more convenient to |
| 9943 | do as much development work as possible on another system, for example |
| 9944 | by cross-compiling. You can use @code{gdbserver} to make a similar |
| 9945 | choice for debugging. |
| 9946 | |
| 9947 | @value{GDBN} and @code{gdbserver} communicate via either a serial line |
| 9948 | or a TCP connection, using the standard @value{GDBN} remote serial |
| 9949 | protocol. |
| 9950 | |
| 9951 | @table @emph |
| 9952 | @item On the target machine, |
| 9953 | you need to have a copy of the program you want to debug. |
| 9954 | @code{gdbserver} does not need your program's symbol table, so you can |
| 9955 | strip the program if necessary to save space. @value{GDBN} on the host |
| 9956 | system does all the symbol handling. |
| 9957 | |
| 9958 | To use the server, you must tell it how to communicate with @value{GDBN}; |
| 9959 | the name of your program; and the arguments for your program. The usual |
| 9960 | syntax is: |
| 9961 | |
| 9962 | @smallexample |
| 9963 | target> gdbserver @var{comm} @var{program} [ @var{args} @dots{} ] |
| 9964 | @end smallexample |
| 9965 | |
| 9966 | @var{comm} is either a device name (to use a serial line) or a TCP |
| 9967 | hostname and portnumber. For example, to debug Emacs with the argument |
| 9968 | @samp{foo.txt} and communicate with @value{GDBN} over the serial port |
| 9969 | @file{/dev/com1}: |
| 9970 | |
| 9971 | @smallexample |
| 9972 | target> gdbserver /dev/com1 emacs foo.txt |
| 9973 | @end smallexample |
| 9974 | |
| 9975 | @code{gdbserver} waits passively for the host @value{GDBN} to communicate |
| 9976 | with it. |
| 9977 | |
| 9978 | To use a TCP connection instead of a serial line: |
| 9979 | |
| 9980 | @smallexample |
| 9981 | target> gdbserver host:2345 emacs foo.txt |
| 9982 | @end smallexample |
| 9983 | |
| 9984 | The only difference from the previous example is the first argument, |
| 9985 | specifying that you are communicating with the host @value{GDBN} via |
| 9986 | TCP. The @samp{host:2345} argument means that @code{gdbserver} is to |
| 9987 | expect a TCP connection from machine @samp{host} to local TCP port 2345. |
| 9988 | (Currently, the @samp{host} part is ignored.) You can choose any number |
| 9989 | you want for the port number as long as it does not conflict with any |
| 9990 | TCP ports already in use on the target system (for example, @code{23} is |
| 9991 | reserved for @code{telnet}).@footnote{If you choose a port number that |
| 9992 | conflicts with another service, @code{gdbserver} prints an error message |
| 9993 | and exits.} You must use the same port number with the host @value{GDBN} |
| 9994 | @code{target remote} command. |
| 9995 | |
| 9996 | On some targets, @code{gdbserver} can also attach to running programs. |
| 9997 | This is accomplished via the @code{--attach} argument. The syntax is: |
| 9998 | |
| 9999 | @smallexample |
| 10000 | target> gdbserver @var{comm} --attach @var{pid} |
| 10001 | @end smallexample |
| 10002 | |
| 10003 | @var{pid} is the process ID of a currently running process. It isn't necessary |
| 10004 | to point @code{gdbserver} at a binary for the running process. |
| 10005 | |
| 10006 | @item On the @value{GDBN} host machine, |
| 10007 | you need an unstripped copy of your program, since @value{GDBN} needs |
| 10008 | symbols and debugging information. Start up @value{GDBN} as usual, |
| 10009 | using the name of the local copy of your program as the first argument. |
| 10010 | (You may also need the @w{@samp{--baud}} option if the serial line is |
| 10011 | running at anything other than 9600@dmn{bps}.) After that, use @code{target |
| 10012 | remote} to establish communications with @code{gdbserver}. Its argument |
| 10013 | is either a device name (usually a serial device, like |
| 10014 | @file{/dev/ttyb}), or a TCP port descriptor in the form |
| 10015 | @code{@var{host}:@var{PORT}}. For example: |
| 10016 | |
| 10017 | @smallexample |
| 10018 | (@value{GDBP}) target remote /dev/ttyb |
| 10019 | @end smallexample |
| 10020 | |
| 10021 | @noindent |
| 10022 | communicates with the server via serial line @file{/dev/ttyb}, and |
| 10023 | |
| 10024 | @smallexample |
| 10025 | (@value{GDBP}) target remote the-target:2345 |
| 10026 | @end smallexample |
| 10027 | |
| 10028 | @noindent |
| 10029 | communicates via a TCP connection to port 2345 on host @w{@file{the-target}}. |
| 10030 | For TCP connections, you must start up @code{gdbserver} prior to using |
| 10031 | the @code{target remote} command. Otherwise you may get an error whose |
| 10032 | text depends on the host system, but which usually looks something like |
| 10033 | @samp{Connection refused}. |
| 10034 | @end table |
| 10035 | |
| 10036 | @node NetWare |
| 10037 | @section Using the @code{gdbserve.nlm} program |
| 10038 | |
| 10039 | @kindex gdbserve.nlm |
| 10040 | @code{gdbserve.nlm} is a control program for NetWare systems, which |
| 10041 | allows you to connect your program with a remote @value{GDBN} via |
| 10042 | @code{target remote}. |
| 10043 | |
| 10044 | @value{GDBN} and @code{gdbserve.nlm} communicate via a serial line, |
| 10045 | using the standard @value{GDBN} remote serial protocol. |
| 10046 | |
| 10047 | @table @emph |
| 10048 | @item On the target machine, |
| 10049 | you need to have a copy of the program you want to debug. |
| 10050 | @code{gdbserve.nlm} does not need your program's symbol table, so you |
| 10051 | can strip the program if necessary to save space. @value{GDBN} on the |
| 10052 | host system does all the symbol handling. |
| 10053 | |
| 10054 | To use the server, you must tell it how to communicate with |
| 10055 | @value{GDBN}; the name of your program; and the arguments for your |
| 10056 | program. The syntax is: |
| 10057 | |
| 10058 | @smallexample |
| 10059 | load gdbserve [ BOARD=@var{board} ] [ PORT=@var{port} ] |
| 10060 | [ BAUD=@var{baud} ] @var{program} [ @var{args} @dots{} ] |
| 10061 | @end smallexample |
| 10062 | |
| 10063 | @var{board} and @var{port} specify the serial line; @var{baud} specifies |
| 10064 | the baud rate used by the connection. @var{port} and @var{node} default |
| 10065 | to 0, @var{baud} defaults to 9600@dmn{bps}. |
| 10066 | |
| 10067 | For example, to debug Emacs with the argument @samp{foo.txt}and |
| 10068 | communicate with @value{GDBN} over serial port number 2 or board 1 |
| 10069 | using a 19200@dmn{bps} connection: |
| 10070 | |
| 10071 | @smallexample |
| 10072 | load gdbserve BOARD=1 PORT=2 BAUD=19200 emacs foo.txt |
| 10073 | @end smallexample |
| 10074 | |
| 10075 | @item On the @value{GDBN} host machine, |
| 10076 | you need an unstripped copy of your program, since @value{GDBN} needs |
| 10077 | symbols and debugging information. Start up @value{GDBN} as usual, |
| 10078 | using the name of the local copy of your program as the first argument. |
| 10079 | (You may also need the @w{@samp{--baud}} option if the serial line is |
| 10080 | running at anything other than 9600@dmn{bps}. After that, use @code{target |
| 10081 | remote} to establish communications with @code{gdbserve.nlm}. Its |
| 10082 | argument is a device name (usually a serial device, like |
| 10083 | @file{/dev/ttyb}). For example: |
| 10084 | |
| 10085 | @smallexample |
| 10086 | (@value{GDBP}) target remote /dev/ttyb |
| 10087 | @end smallexample |
| 10088 | |
| 10089 | @noindent |
| 10090 | communications with the server via serial line @file{/dev/ttyb}. |
| 10091 | @end table |
| 10092 | |
| 10093 | @node remote stub |
| 10094 | @section Implementing a remote stub |
| 10095 | |
| 10096 | @cindex debugging stub, example |
| 10097 | @cindex remote stub, example |
| 10098 | @cindex stub example, remote debugging |
| 10099 | The stub files provided with @value{GDBN} implement the target side of the |
| 10100 | communication protocol, and the @value{GDBN} side is implemented in the |
| 10101 | @value{GDBN} source file @file{remote.c}. Normally, you can simply allow |
| 10102 | these subroutines to communicate, and ignore the details. (If you're |
| 10103 | implementing your own stub file, you can still ignore the details: start |
| 10104 | with one of the existing stub files. @file{sparc-stub.c} is the best |
| 10105 | organized, and therefore the easiest to read.) |
| 10106 | |
| 10107 | @cindex remote serial debugging, overview |
| 10108 | To debug a program running on another machine (the debugging |
| 10109 | @dfn{target} machine), you must first arrange for all the usual |
| 10110 | prerequisites for the program to run by itself. For example, for a C |
| 10111 | program, you need: |
| 10112 | |
| 10113 | @enumerate |
| 10114 | @item |
| 10115 | A startup routine to set up the C runtime environment; these usually |
| 10116 | have a name like @file{crt0}. The startup routine may be supplied by |
| 10117 | your hardware supplier, or you may have to write your own. |
| 10118 | |
| 10119 | @item |
| 10120 | A C subroutine library to support your program's |
| 10121 | subroutine calls, notably managing input and output. |
| 10122 | |
| 10123 | @item |
| 10124 | A way of getting your program to the other machine---for example, a |
| 10125 | download program. These are often supplied by the hardware |
| 10126 | manufacturer, but you may have to write your own from hardware |
| 10127 | documentation. |
| 10128 | @end enumerate |
| 10129 | |
| 10130 | The next step is to arrange for your program to use a serial port to |
| 10131 | communicate with the machine where @value{GDBN} is running (the @dfn{host} |
| 10132 | machine). In general terms, the scheme looks like this: |
| 10133 | |
| 10134 | @table @emph |
| 10135 | @item On the host, |
| 10136 | @value{GDBN} already understands how to use this protocol; when everything |
| 10137 | else is set up, you can simply use the @samp{target remote} command |
| 10138 | (@pxref{Targets,,Specifying a Debugging Target}). |
| 10139 | |
| 10140 | @item On the target, |
| 10141 | you must link with your program a few special-purpose subroutines that |
| 10142 | implement the @value{GDBN} remote serial protocol. The file containing these |
| 10143 | subroutines is called a @dfn{debugging stub}. |
| 10144 | |
| 10145 | On certain remote targets, you can use an auxiliary program |
| 10146 | @code{gdbserver} instead of linking a stub into your program. |
| 10147 | @xref{Server,,Using the @code{gdbserver} program}, for details. |
| 10148 | @end table |
| 10149 | |
| 10150 | The debugging stub is specific to the architecture of the remote |
| 10151 | machine; for example, use @file{sparc-stub.c} to debug programs on |
| 10152 | @sc{sparc} boards. |
| 10153 | |
| 10154 | @cindex remote serial stub list |
| 10155 | These working remote stubs are distributed with @value{GDBN}: |
| 10156 | |
| 10157 | @table @code |
| 10158 | |
| 10159 | @item i386-stub.c |
| 10160 | @cindex @file{i386-stub.c} |
| 10161 | @cindex Intel |
| 10162 | @cindex i386 |
| 10163 | For Intel 386 and compatible architectures. |
| 10164 | |
| 10165 | @item m68k-stub.c |
| 10166 | @cindex @file{m68k-stub.c} |
| 10167 | @cindex Motorola 680x0 |
| 10168 | @cindex m680x0 |
| 10169 | For Motorola 680x0 architectures. |
| 10170 | |
| 10171 | @item sh-stub.c |
| 10172 | @cindex @file{sh-stub.c} |
| 10173 | @cindex Hitachi |
| 10174 | @cindex SH |
| 10175 | For Hitachi SH architectures. |
| 10176 | |
| 10177 | @item sparc-stub.c |
| 10178 | @cindex @file{sparc-stub.c} |
| 10179 | @cindex Sparc |
| 10180 | For @sc{sparc} architectures. |
| 10181 | |
| 10182 | @item sparcl-stub.c |
| 10183 | @cindex @file{sparcl-stub.c} |
| 10184 | @cindex Fujitsu |
| 10185 | @cindex SparcLite |
| 10186 | For Fujitsu @sc{sparclite} architectures. |
| 10187 | |
| 10188 | @end table |
| 10189 | |
| 10190 | The @file{README} file in the @value{GDBN} distribution may list other |
| 10191 | recently added stubs. |
| 10192 | |
| 10193 | @menu |
| 10194 | * Stub Contents:: What the stub can do for you |
| 10195 | * Bootstrapping:: What you must do for the stub |
| 10196 | * Debug Session:: Putting it all together |
| 10197 | @end menu |
| 10198 | |
| 10199 | @node Stub Contents |
| 10200 | @subsection What the stub can do for you |
| 10201 | |
| 10202 | @cindex remote serial stub |
| 10203 | The debugging stub for your architecture supplies these three |
| 10204 | subroutines: |
| 10205 | |
| 10206 | @table @code |
| 10207 | @item set_debug_traps |
| 10208 | @kindex set_debug_traps |
| 10209 | @cindex remote serial stub, initialization |
| 10210 | This routine arranges for @code{handle_exception} to run when your |
| 10211 | program stops. You must call this subroutine explicitly near the |
| 10212 | beginning of your program. |
| 10213 | |
| 10214 | @item handle_exception |
| 10215 | @kindex handle_exception |
| 10216 | @cindex remote serial stub, main routine |
| 10217 | This is the central workhorse, but your program never calls it |
| 10218 | explicitly---the setup code arranges for @code{handle_exception} to |
| 10219 | run when a trap is triggered. |
| 10220 | |
| 10221 | @code{handle_exception} takes control when your program stops during |
| 10222 | execution (for example, on a breakpoint), and mediates communications |
| 10223 | with @value{GDBN} on the host machine. This is where the communications |
| 10224 | protocol is implemented; @code{handle_exception} acts as the @value{GDBN} |
| 10225 | representative on the target machine. It begins by sending summary |
| 10226 | information on the state of your program, then continues to execute, |
| 10227 | retrieving and transmitting any information @value{GDBN} needs, until you |
| 10228 | execute a @value{GDBN} command that makes your program resume; at that point, |
| 10229 | @code{handle_exception} returns control to your own code on the target |
| 10230 | machine. |
| 10231 | |
| 10232 | @item breakpoint |
| 10233 | @cindex @code{breakpoint} subroutine, remote |
| 10234 | Use this auxiliary subroutine to make your program contain a |
| 10235 | breakpoint. Depending on the particular situation, this may be the only |
| 10236 | way for @value{GDBN} to get control. For instance, if your target |
| 10237 | machine has some sort of interrupt button, you won't need to call this; |
| 10238 | pressing the interrupt button transfers control to |
| 10239 | @code{handle_exception}---in effect, to @value{GDBN}. On some machines, |
| 10240 | simply receiving characters on the serial port may also trigger a trap; |
| 10241 | again, in that situation, you don't need to call @code{breakpoint} from |
| 10242 | your own program---simply running @samp{target remote} from the host |
| 10243 | @value{GDBN} session gets control. |
| 10244 | |
| 10245 | Call @code{breakpoint} if none of these is true, or if you simply want |
| 10246 | to make certain your program stops at a predetermined point for the |
| 10247 | start of your debugging session. |
| 10248 | @end table |
| 10249 | |
| 10250 | @node Bootstrapping |
| 10251 | @subsection What you must do for the stub |
| 10252 | |
| 10253 | @cindex remote stub, support routines |
| 10254 | The debugging stubs that come with @value{GDBN} are set up for a particular |
| 10255 | chip architecture, but they have no information about the rest of your |
| 10256 | debugging target machine. |
| 10257 | |
| 10258 | First of all you need to tell the stub how to communicate with the |
| 10259 | serial port. |
| 10260 | |
| 10261 | @table @code |
| 10262 | @item int getDebugChar() |
| 10263 | @kindex getDebugChar |
| 10264 | Write this subroutine to read a single character from the serial port. |
| 10265 | It may be identical to @code{getchar} for your target system; a |
| 10266 | different name is used to allow you to distinguish the two if you wish. |
| 10267 | |
| 10268 | @item void putDebugChar(int) |
| 10269 | @kindex putDebugChar |
| 10270 | Write this subroutine to write a single character to the serial port. |
| 10271 | It may be identical to @code{putchar} for your target system; a |
| 10272 | different name is used to allow you to distinguish the two if you wish. |
| 10273 | @end table |
| 10274 | |
| 10275 | @cindex control C, and remote debugging |
| 10276 | @cindex interrupting remote targets |
| 10277 | If you want @value{GDBN} to be able to stop your program while it is |
| 10278 | running, you need to use an interrupt-driven serial driver, and arrange |
| 10279 | for it to stop when it receives a @code{^C} (@samp{\003}, the control-C |
| 10280 | character). That is the character which @value{GDBN} uses to tell the |
| 10281 | remote system to stop. |
| 10282 | |
| 10283 | Getting the debugging target to return the proper status to @value{GDBN} |
| 10284 | probably requires changes to the standard stub; one quick and dirty way |
| 10285 | is to just execute a breakpoint instruction (the ``dirty'' part is that |
| 10286 | @value{GDBN} reports a @code{SIGTRAP} instead of a @code{SIGINT}). |
| 10287 | |
| 10288 | Other routines you need to supply are: |
| 10289 | |
| 10290 | @table @code |
| 10291 | @item void exceptionHandler (int @var{exception_number}, void *@var{exception_address}) |
| 10292 | @kindex exceptionHandler |
| 10293 | Write this function to install @var{exception_address} in the exception |
| 10294 | handling tables. You need to do this because the stub does not have any |
| 10295 | way of knowing what the exception handling tables on your target system |
| 10296 | are like (for example, the processor's table might be in @sc{rom}, |
| 10297 | containing entries which point to a table in @sc{ram}). |
| 10298 | @var{exception_number} is the exception number which should be changed; |
| 10299 | its meaning is architecture-dependent (for example, different numbers |
| 10300 | might represent divide by zero, misaligned access, etc). When this |
| 10301 | exception occurs, control should be transferred directly to |
| 10302 | @var{exception_address}, and the processor state (stack, registers, |
| 10303 | and so on) should be just as it is when a processor exception occurs. So if |
| 10304 | you want to use a jump instruction to reach @var{exception_address}, it |
| 10305 | should be a simple jump, not a jump to subroutine. |
| 10306 | |
| 10307 | For the 386, @var{exception_address} should be installed as an interrupt |
| 10308 | gate so that interrupts are masked while the handler runs. The gate |
| 10309 | should be at privilege level 0 (the most privileged level). The |
| 10310 | @sc{sparc} and 68k stubs are able to mask interrupts themselves without |
| 10311 | help from @code{exceptionHandler}. |
| 10312 | |
| 10313 | @item void flush_i_cache() |
| 10314 | @kindex flush_i_cache |
| 10315 | On @sc{sparc} and @sc{sparclite} only, write this subroutine to flush the |
| 10316 | instruction cache, if any, on your target machine. If there is no |
| 10317 | instruction cache, this subroutine may be a no-op. |
| 10318 | |
| 10319 | On target machines that have instruction caches, @value{GDBN} requires this |
| 10320 | function to make certain that the state of your program is stable. |
| 10321 | @end table |
| 10322 | |
| 10323 | @noindent |
| 10324 | You must also make sure this library routine is available: |
| 10325 | |
| 10326 | @table @code |
| 10327 | @item void *memset(void *, int, int) |
| 10328 | @kindex memset |
| 10329 | This is the standard library function @code{memset} that sets an area of |
| 10330 | memory to a known value. If you have one of the free versions of |
| 10331 | @code{libc.a}, @code{memset} can be found there; otherwise, you must |
| 10332 | either obtain it from your hardware manufacturer, or write your own. |
| 10333 | @end table |
| 10334 | |
| 10335 | If you do not use the GNU C compiler, you may need other standard |
| 10336 | library subroutines as well; this varies from one stub to another, |
| 10337 | but in general the stubs are likely to use any of the common library |
| 10338 | subroutines which @code{@value{GCC}} generates as inline code. |
| 10339 | |
| 10340 | |
| 10341 | @node Debug Session |
| 10342 | @subsection Putting it all together |
| 10343 | |
| 10344 | @cindex remote serial debugging summary |
| 10345 | In summary, when your program is ready to debug, you must follow these |
| 10346 | steps. |
| 10347 | |
| 10348 | @enumerate |
| 10349 | @item |
| 10350 | Make sure you have defined the supporting low-level routines |
| 10351 | (@pxref{Bootstrapping,,What you must do for the stub}): |
| 10352 | @display |
| 10353 | @code{getDebugChar}, @code{putDebugChar}, |
| 10354 | @code{flush_i_cache}, @code{memset}, @code{exceptionHandler}. |
| 10355 | @end display |
| 10356 | |
| 10357 | @item |
| 10358 | Insert these lines near the top of your program: |
| 10359 | |
| 10360 | @example |
| 10361 | set_debug_traps(); |
| 10362 | breakpoint(); |
| 10363 | @end example |
| 10364 | |
| 10365 | @item |
| 10366 | For the 680x0 stub only, you need to provide a variable called |
| 10367 | @code{exceptionHook}. Normally you just use: |
| 10368 | |
| 10369 | @example |
| 10370 | void (*exceptionHook)() = 0; |
| 10371 | @end example |
| 10372 | |
| 10373 | @noindent |
| 10374 | but if before calling @code{set_debug_traps}, you set it to point to a |
| 10375 | function in your program, that function is called when |
| 10376 | @code{@value{GDBN}} continues after stopping on a trap (for example, bus |
| 10377 | error). The function indicated by @code{exceptionHook} is called with |
| 10378 | one parameter: an @code{int} which is the exception number. |
| 10379 | |
| 10380 | @item |
| 10381 | Compile and link together: your program, the @value{GDBN} debugging stub for |
| 10382 | your target architecture, and the supporting subroutines. |
| 10383 | |
| 10384 | @item |
| 10385 | Make sure you have a serial connection between your target machine and |
| 10386 | the @value{GDBN} host, and identify the serial port on the host. |
| 10387 | |
| 10388 | @item |
| 10389 | @c The "remote" target now provides a `load' command, so we should |
| 10390 | @c document that. FIXME. |
| 10391 | Download your program to your target machine (or get it there by |
| 10392 | whatever means the manufacturer provides), and start it. |
| 10393 | |
| 10394 | @item |
| 10395 | To start remote debugging, run @value{GDBN} on the host machine, and specify |
| 10396 | as an executable file the program that is running in the remote machine. |
| 10397 | This tells @value{GDBN} how to find your program's symbols and the contents |
| 10398 | of its pure text. |
| 10399 | |
| 10400 | @item |
| 10401 | @cindex serial line, @code{target remote} |
| 10402 | Establish communication using the @code{target remote} command. |
| 10403 | Its argument specifies how to communicate with the target |
| 10404 | machine---either via a devicename attached to a direct serial line, or a |
| 10405 | TCP port (usually to a terminal server which in turn has a serial line |
| 10406 | to the target). For example, to use a serial line connected to the |
| 10407 | device named @file{/dev/ttyb}: |
| 10408 | |
| 10409 | @example |
| 10410 | target remote /dev/ttyb |
| 10411 | @end example |
| 10412 | |
| 10413 | @cindex TCP port, @code{target remote} |
| 10414 | To use a TCP connection, use an argument of the form |
| 10415 | @code{@var{host}:port}. For example, to connect to port 2828 on a |
| 10416 | terminal server named @code{manyfarms}: |
| 10417 | |
| 10418 | @example |
| 10419 | target remote manyfarms:2828 |
| 10420 | @end example |
| 10421 | |
| 10422 | If your remote target is actually running on the same machine as |
| 10423 | your debugger session (e.g.@: a simulator of your target running on |
| 10424 | the same host), you can omit the hostname. For example, to connect |
| 10425 | to port 1234 on your local machine: |
| 10426 | |
| 10427 | @example |
| 10428 | target remote :1234 |
| 10429 | @end example |
| 10430 | @noindent |
| 10431 | |
| 10432 | Note that the colon is still required here. |
| 10433 | @end enumerate |
| 10434 | |
| 10435 | Now you can use all the usual commands to examine and change data and to |
| 10436 | step and continue the remote program. |
| 10437 | |
| 10438 | To resume the remote program and stop debugging it, use the @code{detach} |
| 10439 | command. |
| 10440 | |
| 10441 | @cindex interrupting remote programs |
| 10442 | @cindex remote programs, interrupting |
| 10443 | Whenever @value{GDBN} is waiting for the remote program, if you type the |
| 10444 | interrupt character (often @key{C-C}), @value{GDBN} attempts to stop the |
| 10445 | program. This may or may not succeed, depending in part on the hardware |
| 10446 | and the serial drivers the remote system uses. If you type the |
| 10447 | interrupt character once again, @value{GDBN} displays this prompt: |
| 10448 | |
| 10449 | @example |
| 10450 | Interrupted while waiting for the program. |
| 10451 | Give up (and stop debugging it)? (y or n) |
| 10452 | @end example |
| 10453 | |
| 10454 | If you type @kbd{y}, @value{GDBN} abandons the remote debugging session. |
| 10455 | (If you decide you want to try again later, you can use @samp{target |
| 10456 | remote} again to connect once more.) If you type @kbd{n}, @value{GDBN} |
| 10457 | goes back to waiting. |
| 10458 | |
| 10459 | |
| 10460 | @node Configurations |
| 10461 | @chapter Configuration-Specific Information |
| 10462 | |
| 10463 | While nearly all @value{GDBN} commands are available for all native and |
| 10464 | cross versions of the debugger, there are some exceptions. This chapter |
| 10465 | describes things that are only available in certain configurations. |
| 10466 | |
| 10467 | There are three major categories of configurations: native |
| 10468 | configurations, where the host and target are the same, embedded |
| 10469 | operating system configurations, which are usually the same for several |
| 10470 | different processor architectures, and bare embedded processors, which |
| 10471 | are quite different from each other. |
| 10472 | |
| 10473 | @menu |
| 10474 | * Native:: |
| 10475 | * Embedded OS:: |
| 10476 | * Embedded Processors:: |
| 10477 | * Architectures:: |
| 10478 | @end menu |
| 10479 | |
| 10480 | @node Native |
| 10481 | @section Native |
| 10482 | |
| 10483 | This section describes details specific to particular native |
| 10484 | configurations. |
| 10485 | |
| 10486 | @menu |
| 10487 | * HP-UX:: HP-UX |
| 10488 | * SVR4 Process Information:: SVR4 process information |
| 10489 | * DJGPP Native:: Features specific to the DJGPP port |
| 10490 | @end menu |
| 10491 | |
| 10492 | @node HP-UX |
| 10493 | @subsection HP-UX |
| 10494 | |
| 10495 | On HP-UX systems, if you refer to a function or variable name that |
| 10496 | begins with a dollar sign, @value{GDBN} searches for a user or system |
| 10497 | name first, before it searches for a convenience variable. |
| 10498 | |
| 10499 | @node SVR4 Process Information |
| 10500 | @subsection SVR4 process information |
| 10501 | |
| 10502 | @kindex /proc |
| 10503 | @cindex process image |
| 10504 | |
| 10505 | Many versions of SVR4 provide a facility called @samp{/proc} that can be |
| 10506 | used to examine the image of a running process using file-system |
| 10507 | subroutines. If @value{GDBN} is configured for an operating system with |
| 10508 | this facility, the command @code{info proc} is available to report on |
| 10509 | several kinds of information about the process running your program. |
| 10510 | @code{info proc} works only on SVR4 systems that include the |
| 10511 | @code{procfs} code. This includes OSF/1 (Digital Unix), Solaris, Irix, |
| 10512 | and Unixware, but not HP-UX or Linux, for example. |
| 10513 | |
| 10514 | @table @code |
| 10515 | @kindex info proc |
| 10516 | @item info proc |
| 10517 | Summarize available information about the process. |
| 10518 | |
| 10519 | @kindex info proc mappings |
| 10520 | @item info proc mappings |
| 10521 | Report on the address ranges accessible in the program, with information |
| 10522 | on whether your program may read, write, or execute each range. |
| 10523 | @ignore |
| 10524 | @comment These sub-options of 'info proc' were not included when |
| 10525 | @comment procfs.c was re-written. Keep their descriptions around |
| 10526 | @comment against the day when someone finds the time to put them back in. |
| 10527 | @kindex info proc times |
| 10528 | @item info proc times |
| 10529 | Starting time, user CPU time, and system CPU time for your program and |
| 10530 | its children. |
| 10531 | |
| 10532 | @kindex info proc id |
| 10533 | @item info proc id |
| 10534 | Report on the process IDs related to your program: its own process ID, |
| 10535 | the ID of its parent, the process group ID, and the session ID. |
| 10536 | |
| 10537 | @kindex info proc status |
| 10538 | @item info proc status |
| 10539 | General information on the state of the process. If the process is |
| 10540 | stopped, this report includes the reason for stopping, and any signal |
| 10541 | received. |
| 10542 | |
| 10543 | @item info proc all |
| 10544 | Show all the above information about the process. |
| 10545 | @end ignore |
| 10546 | @end table |
| 10547 | |
| 10548 | @node DJGPP Native |
| 10549 | @subsection Features for Debugging @sc{djgpp} Programs |
| 10550 | @cindex @sc{djgpp} debugging |
| 10551 | @cindex native @sc{djgpp} debugging |
| 10552 | @cindex MS-DOS-specific commands |
| 10553 | |
| 10554 | @sc{djgpp} is the port of @sc{gnu} development tools to MS-DOS and |
| 10555 | MS-Windows. @sc{djgpp} programs are 32-bit protected-mode programs |
| 10556 | that use the @dfn{DPMI} (DOS Protected-Mode Interface) API to run on |
| 10557 | top of real-mode DOS systems and their emulations. |
| 10558 | |
| 10559 | @value{GDBN} supports native debugging of @sc{djgpp} programs, and |
| 10560 | defines a few commands specific to the @sc{djgpp} port. This |
| 10561 | subsection describes those commands. |
| 10562 | |
| 10563 | @table @code |
| 10564 | @kindex info dos |
| 10565 | @item info dos |
| 10566 | This is a prefix of @sc{djgpp}-specific commands which print |
| 10567 | information about the target system and important OS structures. |
| 10568 | |
| 10569 | @kindex sysinfo |
| 10570 | @cindex MS-DOS system info |
| 10571 | @cindex free memory information (MS-DOS) |
| 10572 | @item info dos sysinfo |
| 10573 | This command displays assorted information about the underlying |
| 10574 | platform: the CPU type and features, the OS version and flavor, the |
| 10575 | DPMI version, and the available conventional and DPMI memory. |
| 10576 | |
| 10577 | @cindex GDT |
| 10578 | @cindex LDT |
| 10579 | @cindex IDT |
| 10580 | @cindex segment descriptor tables |
| 10581 | @cindex descriptor tables display |
| 10582 | @item info dos gdt |
| 10583 | @itemx info dos ldt |
| 10584 | @itemx info dos idt |
| 10585 | These 3 commands display entries from, respectively, Global, Local, |
| 10586 | and Interrupt Descriptor Tables (GDT, LDT, and IDT). The descriptor |
| 10587 | tables are data structures which store a descriptor for each segment |
| 10588 | that is currently in use. The segment's selector is an index into a |
| 10589 | descriptor table; the table entry for that index holds the |
| 10590 | descriptor's base address and limit, and its attributes and access |
| 10591 | rights. |
| 10592 | |
| 10593 | A typical @sc{djgpp} program uses 3 segments: a code segment, a data |
| 10594 | segment (used for both data and the stack), and a DOS segment (which |
| 10595 | allows access to DOS/BIOS data structures and absolute addresses in |
| 10596 | conventional memory). However, the DPMI host will usually define |
| 10597 | additional segments in order to support the DPMI environment. |
| 10598 | |
| 10599 | @cindex garbled pointers |
| 10600 | These commands allow to display entries from the descriptor tables. |
| 10601 | Without an argument, all entries from the specified table are |
| 10602 | displayed. An argument, which should be an integer expression, means |
| 10603 | display a single entry whose index is given by the argument. For |
| 10604 | example, here's a convenient way to display information about the |
| 10605 | debugged program's data segment: |
| 10606 | |
| 10607 | @smallexample |
| 10608 | @exdent @code{(@value{GDBP}) info dos ldt $ds} |
| 10609 | @exdent @code{0x13f: base=0x11970000 limit=0x0009ffff 32-Bit Data (Read/Write, Exp-up)} |
| 10610 | @end smallexample |
| 10611 | |
| 10612 | @noindent |
| 10613 | This comes in handy when you want to see whether a pointer is outside |
| 10614 | the data segment's limit (i.e.@: @dfn{garbled}). |
| 10615 | |
| 10616 | @cindex page tables display (MS-DOS) |
| 10617 | @item info dos pde |
| 10618 | @itemx info dos pte |
| 10619 | These two commands display entries from, respectively, the Page |
| 10620 | Directory and the Page Tables. Page Directories and Page Tables are |
| 10621 | data structures which control how virtual memory addresses are mapped |
| 10622 | into physical addresses. A Page Table includes an entry for every |
| 10623 | page of memory that is mapped into the program's address space; there |
| 10624 | may be several Page Tables, each one holding up to 4096 entries. A |
| 10625 | Page Directory has up to 4096 entries, one each for every Page Table |
| 10626 | that is currently in use. |
| 10627 | |
| 10628 | Without an argument, @kbd{info dos pde} displays the entire Page |
| 10629 | Directory, and @kbd{info dos pte} displays all the entries in all of |
| 10630 | the Page Tables. An argument, an integer expression, given to the |
| 10631 | @kbd{info dos pde} command means display only that entry from the Page |
| 10632 | Directory table. An argument given to the @kbd{info dos pte} command |
| 10633 | means display entries from a single Page Table, the one pointed to by |
| 10634 | the specified entry in the Page Directory. |
| 10635 | |
| 10636 | @cindex direct memory access (DMA) on MS-DOS |
| 10637 | These commands are useful when your program uses @dfn{DMA} (Direct |
| 10638 | Memory Access), which needs physical addresses to program the DMA |
| 10639 | controller. |
| 10640 | |
| 10641 | These commands are supported only with some DPMI servers. |
| 10642 | |
| 10643 | @cindex physical address from linear address |
| 10644 | @item info dos address-pte @var{addr} |
| 10645 | This command displays the Page Table entry for a specified linear |
| 10646 | address. The argument linear address @var{addr} should already have the |
| 10647 | appropriate segment's base address added to it, because this command |
| 10648 | accepts addresses which may belong to @emph{any} segment. For |
| 10649 | example, here's how to display the Page Table entry for the page where |
| 10650 | the variable @code{i} is stored: |
| 10651 | |
| 10652 | @smallexample |
| 10653 | @exdent @code{(@value{GDBP}) info dos address-pte __djgpp_base_address + (char *)&i} |
| 10654 | @exdent @code{Page Table entry for address 0x11a00d30:} |
| 10655 | @exdent @code{Base=0x02698000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0xd30} |
| 10656 | @end smallexample |
| 10657 | |
| 10658 | @noindent |
| 10659 | This says that @code{i} is stored at offset @code{0xd30} from the page |
| 10660 | whose physical base address is @code{0x02698000}, and prints all the |
| 10661 | attributes of that page. |
| 10662 | |
| 10663 | Note that you must cast the addresses of variables to a @code{char *}, |
| 10664 | since otherwise the value of @code{__djgpp_base_address}, the base |
| 10665 | address of all variables and functions in a @sc{djgpp} program, will |
| 10666 | be added using the rules of C pointer arithmetics: if @code{i} is |
| 10667 | declared an @code{int}, @value{GDBN} will add 4 times the value of |
| 10668 | @code{__djgpp_base_address} to the address of @code{i}. |
| 10669 | |
| 10670 | Here's another example, it displays the Page Table entry for the |
| 10671 | transfer buffer: |
| 10672 | |
| 10673 | @smallexample |
| 10674 | @exdent @code{(@value{GDBP}) info dos address-pte *((unsigned *)&_go32_info_block + 3)} |
| 10675 | @exdent @code{Page Table entry for address 0x29110:} |
| 10676 | @exdent @code{Base=0x00029000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0x110} |
| 10677 | @end smallexample |
| 10678 | |
| 10679 | @noindent |
| 10680 | (The @code{+ 3} offset is because the transfer buffer's address is the |
| 10681 | 3rd member of the @code{_go32_info_block} structure.) The output of |
| 10682 | this command clearly shows that addresses in conventional memory are |
| 10683 | mapped 1:1, i.e.@: the physical and linear addresses are identical. |
| 10684 | |
| 10685 | This command is supported only with some DPMI servers. |
| 10686 | @end table |
| 10687 | |
| 10688 | @node Embedded OS |
| 10689 | @section Embedded Operating Systems |
| 10690 | |
| 10691 | This section describes configurations involving the debugging of |
| 10692 | embedded operating systems that are available for several different |
| 10693 | architectures. |
| 10694 | |
| 10695 | @menu |
| 10696 | * VxWorks:: Using @value{GDBN} with VxWorks |
| 10697 | @end menu |
| 10698 | |
| 10699 | @value{GDBN} includes the ability to debug programs running on |
| 10700 | various real-time operating systems. |
| 10701 | |
| 10702 | @node VxWorks |
| 10703 | @subsection Using @value{GDBN} with VxWorks |
| 10704 | |
| 10705 | @cindex VxWorks |
| 10706 | |
| 10707 | @table @code |
| 10708 | |
| 10709 | @kindex target vxworks |
| 10710 | @item target vxworks @var{machinename} |
| 10711 | A VxWorks system, attached via TCP/IP. The argument @var{machinename} |
| 10712 | is the target system's machine name or IP address. |
| 10713 | |
| 10714 | @end table |
| 10715 | |
| 10716 | On VxWorks, @code{load} links @var{filename} dynamically on the |
| 10717 | current target system as well as adding its symbols in @value{GDBN}. |
| 10718 | |
| 10719 | @value{GDBN} enables developers to spawn and debug tasks running on networked |
| 10720 | VxWorks targets from a Unix host. Already-running tasks spawned from |
| 10721 | the VxWorks shell can also be debugged. @value{GDBN} uses code that runs on |
| 10722 | both the Unix host and on the VxWorks target. The program |
| 10723 | @code{@value{GDBP}} is installed and executed on the Unix host. (It may be |
| 10724 | installed with the name @code{vxgdb}, to distinguish it from a |
| 10725 | @value{GDBN} for debugging programs on the host itself.) |
| 10726 | |
| 10727 | @table @code |
| 10728 | @item VxWorks-timeout @var{args} |
| 10729 | @kindex vxworks-timeout |
| 10730 | All VxWorks-based targets now support the option @code{vxworks-timeout}. |
| 10731 | This option is set by the user, and @var{args} represents the number of |
| 10732 | seconds @value{GDBN} waits for responses to rpc's. You might use this if |
| 10733 | your VxWorks target is a slow software simulator or is on the far side |
| 10734 | of a thin network line. |
| 10735 | @end table |
| 10736 | |
| 10737 | The following information on connecting to VxWorks was current when |
| 10738 | this manual was produced; newer releases of VxWorks may use revised |
| 10739 | procedures. |
| 10740 | |
| 10741 | @kindex INCLUDE_RDB |
| 10742 | To use @value{GDBN} with VxWorks, you must rebuild your VxWorks kernel |
| 10743 | to include the remote debugging interface routines in the VxWorks |
| 10744 | library @file{rdb.a}. To do this, define @code{INCLUDE_RDB} in the |
| 10745 | VxWorks configuration file @file{configAll.h} and rebuild your VxWorks |
| 10746 | kernel. The resulting kernel contains @file{rdb.a}, and spawns the |
| 10747 | source debugging task @code{tRdbTask} when VxWorks is booted. For more |
| 10748 | information on configuring and remaking VxWorks, see the manufacturer's |
| 10749 | manual. |
| 10750 | @c VxWorks, see the @cite{VxWorks Programmer's Guide}. |
| 10751 | |
| 10752 | Once you have included @file{rdb.a} in your VxWorks system image and set |
| 10753 | your Unix execution search path to find @value{GDBN}, you are ready to |
| 10754 | run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} (or |
| 10755 | @code{vxgdb}, depending on your installation). |
| 10756 | |
| 10757 | @value{GDBN} comes up showing the prompt: |
| 10758 | |
| 10759 | @example |
| 10760 | (vxgdb) |
| 10761 | @end example |
| 10762 | |
| 10763 | @menu |
| 10764 | * VxWorks Connection:: Connecting to VxWorks |
| 10765 | * VxWorks Download:: VxWorks download |
| 10766 | * VxWorks Attach:: Running tasks |
| 10767 | @end menu |
| 10768 | |
| 10769 | @node VxWorks Connection |
| 10770 | @subsubsection Connecting to VxWorks |
| 10771 | |
| 10772 | The @value{GDBN} command @code{target} lets you connect to a VxWorks target on the |
| 10773 | network. To connect to a target whose host name is ``@code{tt}'', type: |
| 10774 | |
| 10775 | @example |
| 10776 | (vxgdb) target vxworks tt |
| 10777 | @end example |
| 10778 | |
| 10779 | @need 750 |
| 10780 | @value{GDBN} displays messages like these: |
| 10781 | |
| 10782 | @smallexample |
| 10783 | Attaching remote machine across net... |
| 10784 | Connected to tt. |
| 10785 | @end smallexample |
| 10786 | |
| 10787 | @need 1000 |
| 10788 | @value{GDBN} then attempts to read the symbol tables of any object modules |
| 10789 | loaded into the VxWorks target since it was last booted. @value{GDBN} locates |
| 10790 | these files by searching the directories listed in the command search |
| 10791 | path (@pxref{Environment, ,Your program's environment}); if it fails |
| 10792 | to find an object file, it displays a message such as: |
| 10793 | |
| 10794 | @example |
| 10795 | prog.o: No such file or directory. |
| 10796 | @end example |
| 10797 | |
| 10798 | When this happens, add the appropriate directory to the search path with |
| 10799 | the @value{GDBN} command @code{path}, and execute the @code{target} |
| 10800 | command again. |
| 10801 | |
| 10802 | @node VxWorks Download |
| 10803 | @subsubsection VxWorks download |
| 10804 | |
| 10805 | @cindex download to VxWorks |
| 10806 | If you have connected to the VxWorks target and you want to debug an |
| 10807 | object that has not yet been loaded, you can use the @value{GDBN} |
| 10808 | @code{load} command to download a file from Unix to VxWorks |
| 10809 | incrementally. The object file given as an argument to the @code{load} |
| 10810 | command is actually opened twice: first by the VxWorks target in order |
| 10811 | to download the code, then by @value{GDBN} in order to read the symbol |
| 10812 | table. This can lead to problems if the current working directories on |
| 10813 | the two systems differ. If both systems have NFS mounted the same |
| 10814 | filesystems, you can avoid these problems by using absolute paths. |
| 10815 | Otherwise, it is simplest to set the working directory on both systems |
| 10816 | to the directory in which the object file resides, and then to reference |
| 10817 | the file by its name, without any path. For instance, a program |
| 10818 | @file{prog.o} may reside in @file{@var{vxpath}/vw/demo/rdb} in VxWorks |
| 10819 | and in @file{@var{hostpath}/vw/demo/rdb} on the host. To load this |
| 10820 | program, type this on VxWorks: |
| 10821 | |
| 10822 | @example |
| 10823 | -> cd "@var{vxpath}/vw/demo/rdb" |
| 10824 | @end example |
| 10825 | |
| 10826 | @noindent |
| 10827 | Then, in @value{GDBN}, type: |
| 10828 | |
| 10829 | @example |
| 10830 | (vxgdb) cd @var{hostpath}/vw/demo/rdb |
| 10831 | (vxgdb) load prog.o |
| 10832 | @end example |
| 10833 | |
| 10834 | @value{GDBN} displays a response similar to this: |
| 10835 | |
| 10836 | @smallexample |
| 10837 | Reading symbol data from wherever/vw/demo/rdb/prog.o... done. |
| 10838 | @end smallexample |
| 10839 | |
| 10840 | You can also use the @code{load} command to reload an object module |
| 10841 | after editing and recompiling the corresponding source file. Note that |
| 10842 | this makes @value{GDBN} delete all currently-defined breakpoints, |
| 10843 | auto-displays, and convenience variables, and to clear the value |
| 10844 | history. (This is necessary in order to preserve the integrity of |
| 10845 | debugger's data structures that reference the target system's symbol |
| 10846 | table.) |
| 10847 | |
| 10848 | @node VxWorks Attach |
| 10849 | @subsubsection Running tasks |
| 10850 | |
| 10851 | @cindex running VxWorks tasks |
| 10852 | You can also attach to an existing task using the @code{attach} command as |
| 10853 | follows: |
| 10854 | |
| 10855 | @example |
| 10856 | (vxgdb) attach @var{task} |
| 10857 | @end example |
| 10858 | |
| 10859 | @noindent |
| 10860 | where @var{task} is the VxWorks hexadecimal task ID. The task can be running |
| 10861 | or suspended when you attach to it. Running tasks are suspended at |
| 10862 | the time of attachment. |
| 10863 | |
| 10864 | @node Embedded Processors |
| 10865 | @section Embedded Processors |
| 10866 | |
| 10867 | This section goes into details specific to particular embedded |
| 10868 | configurations. |
| 10869 | |
| 10870 | |
| 10871 | @c OBSOLETE * A29K Embedded:: AMD A29K Embedded |
| 10872 | @menu |
| 10873 | * ARM:: ARM |
| 10874 | * H8/300:: Hitachi H8/300 |
| 10875 | * H8/500:: Hitachi H8/500 |
| 10876 | * i960:: Intel i960 |
| 10877 | * M32R/D:: Mitsubishi M32R/D |
| 10878 | * M68K:: Motorola M68K |
| 10879 | * M88K:: Motorola M88K |
| 10880 | * MIPS Embedded:: MIPS Embedded |
| 10881 | * PA:: HP PA Embedded |
| 10882 | * PowerPC: PowerPC |
| 10883 | * SH:: Hitachi SH |
| 10884 | * Sparclet:: Tsqware Sparclet |
| 10885 | * Sparclite:: Fujitsu Sparclite |
| 10886 | * ST2000:: Tandem ST2000 |
| 10887 | * Z8000:: Zilog Z8000 |
| 10888 | @end menu |
| 10889 | |
| 10890 | @c OBSOLETE @node A29K Embedded |
| 10891 | @c OBSOLETE @subsection AMD A29K Embedded |
| 10892 | @c OBSOLETE |
| 10893 | @c OBSOLETE @menu |
| 10894 | @c OBSOLETE * A29K UDI:: |
| 10895 | @c OBSOLETE * A29K EB29K:: |
| 10896 | @c OBSOLETE * Comms (EB29K):: Communications setup |
| 10897 | @c OBSOLETE * gdb-EB29K:: EB29K cross-debugging |
| 10898 | @c OBSOLETE * Remote Log:: Remote log |
| 10899 | @c OBSOLETE @end menu |
| 10900 | @c OBSOLETE |
| 10901 | @c OBSOLETE @table @code |
| 10902 | @c OBSOLETE |
| 10903 | @c OBSOLETE @kindex target adapt |
| 10904 | @c OBSOLETE @item target adapt @var{dev} |
| 10905 | @c OBSOLETE Adapt monitor for A29K. |
| 10906 | @c OBSOLETE |
| 10907 | @c OBSOLETE @kindex target amd-eb |
| 10908 | @c OBSOLETE @item target amd-eb @var{dev} @var{speed} @var{PROG} |
| 10909 | @c OBSOLETE @cindex AMD EB29K |
| 10910 | @c OBSOLETE Remote PC-resident AMD EB29K board, attached over serial lines. |
| 10911 | @c OBSOLETE @var{dev} is the serial device, as for @code{target remote}; |
| 10912 | @c OBSOLETE @var{speed} allows you to specify the linespeed; and @var{PROG} is the |
| 10913 | @c OBSOLETE name of the program to be debugged, as it appears to DOS on the PC. |
| 10914 | @c OBSOLETE @xref{A29K EB29K, ,EBMON protocol for AMD29K}. |
| 10915 | @c OBSOLETE |
| 10916 | @c OBSOLETE @end table |
| 10917 | @c OBSOLETE |
| 10918 | @c OBSOLETE @node A29K UDI |
| 10919 | @c OBSOLETE @subsubsection A29K UDI |
| 10920 | @c OBSOLETE |
| 10921 | @c OBSOLETE @cindex UDI |
| 10922 | @c OBSOLETE @cindex AMD29K via UDI |
| 10923 | @c OBSOLETE |
| 10924 | @c OBSOLETE @value{GDBN} supports AMD's UDI (``Universal Debugger Interface'') |
| 10925 | @c OBSOLETE protocol for debugging the a29k processor family. To use this |
| 10926 | @c OBSOLETE configuration with AMD targets running the MiniMON monitor, you need the |
| 10927 | @c OBSOLETE program @code{MONTIP}, available from AMD at no charge. You can also |
| 10928 | @c OBSOLETE use @value{GDBN} with the UDI-conformant a29k simulator program |
| 10929 | @c OBSOLETE @code{ISSTIP}, also available from AMD. |
| 10930 | @c OBSOLETE |
| 10931 | @c OBSOLETE @table @code |
| 10932 | @c OBSOLETE @item target udi @var{keyword} |
| 10933 | @c OBSOLETE @kindex udi |
| 10934 | @c OBSOLETE Select the UDI interface to a remote a29k board or simulator, where |
| 10935 | @c OBSOLETE @var{keyword} is an entry in the AMD configuration file @file{udi_soc}. |
| 10936 | @c OBSOLETE This file contains keyword entries which specify parameters used to |
| 10937 | @c OBSOLETE connect to a29k targets. If the @file{udi_soc} file is not in your |
| 10938 | @c OBSOLETE working directory, you must set the environment variable @samp{UDICONF} |
| 10939 | @c OBSOLETE to its pathname. |
| 10940 | @c OBSOLETE @end table |
| 10941 | @c OBSOLETE |
| 10942 | @c OBSOLETE @node A29K EB29K |
| 10943 | @c OBSOLETE @subsubsection EBMON protocol for AMD29K |
| 10944 | @c OBSOLETE |
| 10945 | @c OBSOLETE @cindex EB29K board |
| 10946 | @c OBSOLETE @cindex running 29K programs |
| 10947 | @c OBSOLETE |
| 10948 | @c OBSOLETE AMD distributes a 29K development board meant to fit in a PC, together |
| 10949 | @c OBSOLETE with a DOS-hosted monitor program called @code{EBMON}. As a shorthand |
| 10950 | @c OBSOLETE term, this development system is called the ``EB29K''. To use |
| 10951 | @c OBSOLETE @value{GDBN} from a Unix system to run programs on the EB29K board, you |
| 10952 | @c OBSOLETE must first connect a serial cable between the PC (which hosts the EB29K |
| 10953 | @c OBSOLETE board) and a serial port on the Unix system. In the following, we |
| 10954 | @c OBSOLETE assume you've hooked the cable between the PC's @file{COM1} port and |
| 10955 | @c OBSOLETE @file{/dev/ttya} on the Unix system. |
| 10956 | @c OBSOLETE |
| 10957 | @c OBSOLETE @node Comms (EB29K) |
| 10958 | @c OBSOLETE @subsubsection Communications setup |
| 10959 | @c OBSOLETE |
| 10960 | @c OBSOLETE The next step is to set up the PC's port, by doing something like this |
| 10961 | @c OBSOLETE in DOS on the PC: |
| 10962 | @c OBSOLETE |
| 10963 | @c OBSOLETE @example |
| 10964 | @c OBSOLETE C:\> MODE com1:9600,n,8,1,none |
| 10965 | @c OBSOLETE @end example |
| 10966 | @c OBSOLETE |
| 10967 | @c OBSOLETE @noindent |
| 10968 | @c OBSOLETE This example---run on an MS DOS 4.0 system---sets the PC port to 9600 |
| 10969 | @c OBSOLETE bps, no parity, eight data bits, one stop bit, and no ``retry'' action; |
| 10970 | @c OBSOLETE you must match the communications parameters when establishing the Unix |
| 10971 | @c OBSOLETE end of the connection as well. |
| 10972 | @c OBSOLETE @c FIXME: Who knows what this "no retry action" crud from the DOS manual may |
| 10973 | @c OBSOLETE @c mean? It's optional; leave it out? ---doc@cygnus.com, 25feb91 |
| 10974 | @c OBSOLETE @c |
| 10975 | @c OBSOLETE @c It's optional, but it's unwise to omit it: who knows what is the |
| 10976 | @c OBSOLETE @c default value set when the DOS machines boots? "No retry" means that |
| 10977 | @c OBSOLETE @c the DOS serial device driver won't retry the operation if it fails; |
| 10978 | @c OBSOLETE @c I understand that this is needed because the GDB serial protocol |
| 10979 | @c OBSOLETE @c handles any errors and retransmissions itself. ---Eli Zaretskii, 3sep99 |
| 10980 | @c OBSOLETE |
| 10981 | @c OBSOLETE To give control of the PC to the Unix side of the serial line, type |
| 10982 | @c OBSOLETE the following at the DOS console: |
| 10983 | @c OBSOLETE |
| 10984 | @c OBSOLETE @example |
| 10985 | @c OBSOLETE C:\> CTTY com1 |
| 10986 | @c OBSOLETE @end example |
| 10987 | @c OBSOLETE |
| 10988 | @c OBSOLETE @noindent |
| 10989 | @c OBSOLETE (Later, if you wish to return control to the DOS console, you can use |
| 10990 | @c OBSOLETE the command @code{CTTY con}---but you must send it over the device that |
| 10991 | @c OBSOLETE had control, in our example over the @file{COM1} serial line.) |
| 10992 | @c OBSOLETE |
| 10993 | @c OBSOLETE From the Unix host, use a communications program such as @code{tip} or |
| 10994 | @c OBSOLETE @code{cu} to communicate with the PC; for example, |
| 10995 | @c OBSOLETE |
| 10996 | @c OBSOLETE @example |
| 10997 | @c OBSOLETE cu -s 9600 -l /dev/ttya |
| 10998 | @c OBSOLETE @end example |
| 10999 | @c OBSOLETE |
| 11000 | @c OBSOLETE @noindent |
| 11001 | @c OBSOLETE The @code{cu} options shown specify, respectively, the linespeed and the |
| 11002 | @c OBSOLETE serial port to use. If you use @code{tip} instead, your command line |
| 11003 | @c OBSOLETE may look something like the following: |
| 11004 | @c OBSOLETE |
| 11005 | @c OBSOLETE @example |
| 11006 | @c OBSOLETE tip -9600 /dev/ttya |
| 11007 | @c OBSOLETE @end example |
| 11008 | @c OBSOLETE |
| 11009 | @c OBSOLETE @noindent |
| 11010 | @c OBSOLETE Your system may require a different name where we show |
| 11011 | @c OBSOLETE @file{/dev/ttya} as the argument to @code{tip}. The communications |
| 11012 | @c OBSOLETE parameters, including which port to use, are associated with the |
| 11013 | @c OBSOLETE @code{tip} argument in the ``remote'' descriptions file---normally the |
| 11014 | @c OBSOLETE system table @file{/etc/remote}. |
| 11015 | @c OBSOLETE @c FIXME: What if anything needs doing to match the "n,8,1,none" part of |
| 11016 | @c OBSOLETE @c the DOS side's comms setup? cu can support -o (odd |
| 11017 | @c OBSOLETE @c parity), -e (even parity)---apparently no settings for no parity or |
| 11018 | @c OBSOLETE @c for character size. Taken from stty maybe...? John points out tip |
| 11019 | @c OBSOLETE @c can set these as internal variables, eg ~s parity=none; man stty |
| 11020 | @c OBSOLETE @c suggests that it *might* work to stty these options with stdin or |
| 11021 | @c OBSOLETE @c stdout redirected... ---doc@cygnus.com, 25feb91 |
| 11022 | @c OBSOLETE @c |
| 11023 | @c OBSOLETE @c There's nothing to be done for the "none" part of the DOS MODE |
| 11024 | @c OBSOLETE @c command. The rest of the parameters should be matched by the |
| 11025 | @c OBSOLETE @c baudrate, bits, and parity used by the Unix side. ---Eli Zaretskii, 3Sep99 |
| 11026 | @c OBSOLETE |
| 11027 | @c OBSOLETE @kindex EBMON |
| 11028 | @c OBSOLETE Using the @code{tip} or @code{cu} connection, change the DOS working |
| 11029 | @c OBSOLETE directory to the directory containing a copy of your 29K program, then |
| 11030 | @c OBSOLETE start the PC program @code{EBMON} (an EB29K control program supplied |
| 11031 | @c OBSOLETE with your board by AMD). You should see an initial display from |
| 11032 | @c OBSOLETE @code{EBMON} similar to the one that follows, ending with the |
| 11033 | @c OBSOLETE @code{EBMON} prompt @samp{#}--- |
| 11034 | @c OBSOLETE |
| 11035 | @c OBSOLETE @example |
| 11036 | @c OBSOLETE C:\> G: |
| 11037 | @c OBSOLETE |
| 11038 | @c OBSOLETE G:\> CD \usr\joe\work29k |
| 11039 | @c OBSOLETE |
| 11040 | @c OBSOLETE G:\USR\JOE\WORK29K> EBMON |
| 11041 | @c OBSOLETE Am29000 PC Coprocessor Board Monitor, version 3.0-18 |
| 11042 | @c OBSOLETE Copyright 1990 Advanced Micro Devices, Inc. |
| 11043 | @c OBSOLETE Written by Gibbons and Associates, Inc. |
| 11044 | @c OBSOLETE |
| 11045 | @c OBSOLETE Enter '?' or 'H' for help |
| 11046 | @c OBSOLETE |
| 11047 | @c OBSOLETE PC Coprocessor Type = EB29K |
| 11048 | @c OBSOLETE I/O Base = 0x208 |
| 11049 | @c OBSOLETE Memory Base = 0xd0000 |
| 11050 | @c OBSOLETE |
| 11051 | @c OBSOLETE Data Memory Size = 2048KB |
| 11052 | @c OBSOLETE Available I-RAM Range = 0x8000 to 0x1fffff |
| 11053 | @c OBSOLETE Available D-RAM Range = 0x80002000 to 0x801fffff |
| 11054 | @c OBSOLETE |
| 11055 | @c OBSOLETE PageSize = 0x400 |
| 11056 | @c OBSOLETE Register Stack Size = 0x800 |
| 11057 | @c OBSOLETE Memory Stack Size = 0x1800 |
| 11058 | @c OBSOLETE |
| 11059 | @c OBSOLETE CPU PRL = 0x3 |
| 11060 | @c OBSOLETE Am29027 Available = No |
| 11061 | @c OBSOLETE Byte Write Available = Yes |
| 11062 | @c OBSOLETE |
| 11063 | @c OBSOLETE # ~. |
| 11064 | @c OBSOLETE @end example |
| 11065 | @c OBSOLETE |
| 11066 | @c OBSOLETE Then exit the @code{cu} or @code{tip} program (done in the example by |
| 11067 | @c OBSOLETE typing @code{~.} at the @code{EBMON} prompt). @code{EBMON} keeps |
| 11068 | @c OBSOLETE running, ready for @value{GDBN} to take over. |
| 11069 | @c OBSOLETE |
| 11070 | @c OBSOLETE For this example, we've assumed what is probably the most convenient |
| 11071 | @c OBSOLETE way to make sure the same 29K program is on both the PC and the Unix |
| 11072 | @c OBSOLETE system: a PC/NFS connection that establishes ``drive @file{G:}'' on the |
| 11073 | @c OBSOLETE PC as a file system on the Unix host. If you do not have PC/NFS or |
| 11074 | @c OBSOLETE something similar connecting the two systems, you must arrange some |
| 11075 | @c OBSOLETE other way---perhaps floppy-disk transfer---of getting the 29K program |
| 11076 | @c OBSOLETE from the Unix system to the PC; @value{GDBN} does @emph{not} download it over the |
| 11077 | @c OBSOLETE serial line. |
| 11078 | @c OBSOLETE |
| 11079 | @c OBSOLETE @node gdb-EB29K |
| 11080 | @c OBSOLETE @subsubsection EB29K cross-debugging |
| 11081 | @c OBSOLETE |
| 11082 | @c OBSOLETE Finally, @code{cd} to the directory containing an image of your 29K |
| 11083 | @c OBSOLETE program on the Unix system, and start @value{GDBN}---specifying as argument the |
| 11084 | @c OBSOLETE name of your 29K program: |
| 11085 | @c OBSOLETE |
| 11086 | @c OBSOLETE @example |
| 11087 | @c OBSOLETE cd /usr/joe/work29k |
| 11088 | @c OBSOLETE @value{GDBP} myfoo |
| 11089 | @c OBSOLETE @end example |
| 11090 | @c OBSOLETE |
| 11091 | @c OBSOLETE @need 500 |
| 11092 | @c OBSOLETE Now you can use the @code{target} command: |
| 11093 | @c OBSOLETE |
| 11094 | @c OBSOLETE @example |
| 11095 | @c OBSOLETE target amd-eb /dev/ttya 9600 MYFOO |
| 11096 | @c OBSOLETE @c FIXME: test above 'target amd-eb' as spelled, with caps! caps are meant to |
| 11097 | @c OBSOLETE @c emphasize that this is the name as seen by DOS (since I think DOS is |
| 11098 | @c OBSOLETE @c single-minded about case of letters). ---doc@cygnus.com, 25feb91 |
| 11099 | @c OBSOLETE @end example |
| 11100 | @c OBSOLETE |
| 11101 | @c OBSOLETE @noindent |
| 11102 | @c OBSOLETE In this example, we've assumed your program is in a file called |
| 11103 | @c OBSOLETE @file{myfoo}. Note that the filename given as the last argument to |
| 11104 | @c OBSOLETE @code{target amd-eb} should be the name of the program as it appears to DOS. |
| 11105 | @c OBSOLETE In our example this is simply @code{MYFOO}, but in general it can include |
| 11106 | @c OBSOLETE a DOS path, and depending on your transfer mechanism may not resemble |
| 11107 | @c OBSOLETE the name on the Unix side. |
| 11108 | @c OBSOLETE |
| 11109 | @c OBSOLETE At this point, you can set any breakpoints you wish; when you are ready |
| 11110 | @c OBSOLETE to see your program run on the 29K board, use the @value{GDBN} command |
| 11111 | @c OBSOLETE @code{run}. |
| 11112 | @c OBSOLETE |
| 11113 | @c OBSOLETE To stop debugging the remote program, use the @value{GDBN} @code{detach} |
| 11114 | @c OBSOLETE command. |
| 11115 | @c OBSOLETE |
| 11116 | @c OBSOLETE To return control of the PC to its console, use @code{tip} or @code{cu} |
| 11117 | @c OBSOLETE once again, after your @value{GDBN} session has concluded, to attach to |
| 11118 | @c OBSOLETE @code{EBMON}. You can then type the command @code{q} to shut down |
| 11119 | @c OBSOLETE @code{EBMON}, returning control to the DOS command-line interpreter. |
| 11120 | @c OBSOLETE Type @kbd{CTTY con} to return command input to the main DOS console, |
| 11121 | @c OBSOLETE and type @kbd{~.} to leave @code{tip} or @code{cu}. |
| 11122 | @c OBSOLETE |
| 11123 | @c OBSOLETE @node Remote Log |
| 11124 | @c OBSOLETE @subsubsection Remote log |
| 11125 | @c OBSOLETE @cindex @file{eb.log}, a log file for EB29K |
| 11126 | @c OBSOLETE @cindex log file for EB29K |
| 11127 | @c OBSOLETE |
| 11128 | @c OBSOLETE The @code{target amd-eb} command creates a file @file{eb.log} in the |
| 11129 | @c OBSOLETE current working directory, to help debug problems with the connection. |
| 11130 | @c OBSOLETE @file{eb.log} records all the output from @code{EBMON}, including echoes |
| 11131 | @c OBSOLETE of the commands sent to it. Running @samp{tail -f} on this file in |
| 11132 | @c OBSOLETE another window often helps to understand trouble with @code{EBMON}, or |
| 11133 | @c OBSOLETE unexpected events on the PC side of the connection. |
| 11134 | |
| 11135 | @node ARM |
| 11136 | @subsection ARM |
| 11137 | |
| 11138 | @table @code |
| 11139 | |
| 11140 | @kindex target rdi |
| 11141 | @item target rdi @var{dev} |
| 11142 | ARM Angel monitor, via RDI library interface to ADP protocol. You may |
| 11143 | use this target to communicate with both boards running the Angel |
| 11144 | monitor, or with the EmbeddedICE JTAG debug device. |
| 11145 | |
| 11146 | @kindex target rdp |
| 11147 | @item target rdp @var{dev} |
| 11148 | ARM Demon monitor. |
| 11149 | |
| 11150 | @end table |
| 11151 | |
| 11152 | @node H8/300 |
| 11153 | @subsection Hitachi H8/300 |
| 11154 | |
| 11155 | @table @code |
| 11156 | |
| 11157 | @kindex target hms@r{, with H8/300} |
| 11158 | @item target hms @var{dev} |
| 11159 | A Hitachi SH, H8/300, or H8/500 board, attached via serial line to your host. |
| 11160 | Use special commands @code{device} and @code{speed} to control the serial |
| 11161 | line and the communications speed used. |
| 11162 | |
| 11163 | @kindex target e7000@r{, with H8/300} |
| 11164 | @item target e7000 @var{dev} |
| 11165 | E7000 emulator for Hitachi H8 and SH. |
| 11166 | |
| 11167 | @kindex target sh3@r{, with H8/300} |
| 11168 | @kindex target sh3e@r{, with H8/300} |
| 11169 | @item target sh3 @var{dev} |
| 11170 | @itemx target sh3e @var{dev} |
| 11171 | Hitachi SH-3 and SH-3E target systems. |
| 11172 | |
| 11173 | @end table |
| 11174 | |
| 11175 | @cindex download to H8/300 or H8/500 |
| 11176 | @cindex H8/300 or H8/500 download |
| 11177 | @cindex download to Hitachi SH |
| 11178 | @cindex Hitachi SH download |
| 11179 | When you select remote debugging to a Hitachi SH, H8/300, or H8/500 |
| 11180 | board, the @code{load} command downloads your program to the Hitachi |
| 11181 | board and also opens it as the current executable target for |
| 11182 | @value{GDBN} on your host (like the @code{file} command). |
| 11183 | |
| 11184 | @value{GDBN} needs to know these things to talk to your |
| 11185 | Hitachi SH, H8/300, or H8/500: |
| 11186 | |
| 11187 | @enumerate |
| 11188 | @item |
| 11189 | that you want to use @samp{target hms}, the remote debugging interface |
| 11190 | for Hitachi microprocessors, or @samp{target e7000}, the in-circuit |
| 11191 | emulator for the Hitachi SH and the Hitachi 300H. (@samp{target hms} is |
| 11192 | the default when @value{GDBN} is configured specifically for the Hitachi SH, |
| 11193 | H8/300, or H8/500.) |
| 11194 | |
| 11195 | @item |
| 11196 | what serial device connects your host to your Hitachi board (the first |
| 11197 | serial device available on your host is the default). |
| 11198 | |
| 11199 | @item |
| 11200 | what speed to use over the serial device. |
| 11201 | @end enumerate |
| 11202 | |
| 11203 | @menu |
| 11204 | * Hitachi Boards:: Connecting to Hitachi boards. |
| 11205 | * Hitachi ICE:: Using the E7000 In-Circuit Emulator. |
| 11206 | * Hitachi Special:: Special @value{GDBN} commands for Hitachi micros. |
| 11207 | @end menu |
| 11208 | |
| 11209 | @node Hitachi Boards |
| 11210 | @subsubsection Connecting to Hitachi boards |
| 11211 | |
| 11212 | @c only for Unix hosts |
| 11213 | @kindex device |
| 11214 | @cindex serial device, Hitachi micros |
| 11215 | Use the special @code{@value{GDBN}} command @samp{device @var{port}} if you |
| 11216 | need to explicitly set the serial device. The default @var{port} is the |
| 11217 | first available port on your host. This is only necessary on Unix |
| 11218 | hosts, where it is typically something like @file{/dev/ttya}. |
| 11219 | |
| 11220 | @kindex speed |
| 11221 | @cindex serial line speed, Hitachi micros |
| 11222 | @code{@value{GDBN}} has another special command to set the communications |
| 11223 | speed: @samp{speed @var{bps}}. This command also is only used from Unix |
| 11224 | hosts; on DOS hosts, set the line speed as usual from outside @value{GDBN} with |
| 11225 | the DOS @code{mode} command (for instance, |
| 11226 | @w{@kbd{mode com2:9600,n,8,1,p}} for a 9600@dmn{bps} connection). |
| 11227 | |
| 11228 | The @samp{device} and @samp{speed} commands are available only when you |
| 11229 | use a Unix host to debug your Hitachi microprocessor programs. If you |
| 11230 | use a DOS host, |
| 11231 | @value{GDBN} depends on an auxiliary terminate-and-stay-resident program |
| 11232 | called @code{asynctsr} to communicate with the development board |
| 11233 | through a PC serial port. You must also use the DOS @code{mode} command |
| 11234 | to set up the serial port on the DOS side. |
| 11235 | |
| 11236 | The following sample session illustrates the steps needed to start a |
| 11237 | program under @value{GDBN} control on an H8/300. The example uses a |
| 11238 | sample H8/300 program called @file{t.x}. The procedure is the same for |
| 11239 | the Hitachi SH and the H8/500. |
| 11240 | |
| 11241 | First hook up your development board. In this example, we use a |
| 11242 | board attached to serial port @code{COM2}; if you use a different serial |
| 11243 | port, substitute its name in the argument of the @code{mode} command. |
| 11244 | When you call @code{asynctsr}, the auxiliary comms program used by the |
| 11245 | debugger, you give it just the numeric part of the serial port's name; |
| 11246 | for example, @samp{asyncstr 2} below runs @code{asyncstr} on |
| 11247 | @code{COM2}. |
| 11248 | |
| 11249 | @example |
| 11250 | C:\H8300\TEST> asynctsr 2 |
| 11251 | C:\H8300\TEST> mode com2:9600,n,8,1,p |
| 11252 | |
| 11253 | Resident portion of MODE loaded |
| 11254 | |
| 11255 | COM2: 9600, n, 8, 1, p |
| 11256 | |
| 11257 | @end example |
| 11258 | |
| 11259 | @quotation |
| 11260 | @emph{Warning:} We have noticed a bug in PC-NFS that conflicts with |
| 11261 | @code{asynctsr}. If you also run PC-NFS on your DOS host, you may need to |
| 11262 | disable it, or even boot without it, to use @code{asynctsr} to control |
| 11263 | your development board. |
| 11264 | @end quotation |
| 11265 | |
| 11266 | @kindex target hms@r{, and serial protocol} |
| 11267 | Now that serial communications are set up, and the development board is |
| 11268 | connected, you can start up @value{GDBN}. Call @code{@value{GDBP}} with |
| 11269 | the name of your program as the argument. @code{@value{GDBN}} prompts |
| 11270 | you, as usual, with the prompt @samp{(@value{GDBP})}. Use two special |
| 11271 | commands to begin your debugging session: @samp{target hms} to specify |
| 11272 | cross-debugging to the Hitachi board, and the @code{load} command to |
| 11273 | download your program to the board. @code{load} displays the names of |
| 11274 | the program's sections, and a @samp{*} for each 2K of data downloaded. |
| 11275 | (If you want to refresh @value{GDBN} data on symbols or on the |
| 11276 | executable file without downloading, use the @value{GDBN} commands |
| 11277 | @code{file} or @code{symbol-file}. These commands, and @code{load} |
| 11278 | itself, are described in @ref{Files,,Commands to specify files}.) |
| 11279 | |
| 11280 | @smallexample |
| 11281 | (eg-C:\H8300\TEST) @value{GDBP} t.x |
| 11282 | @value{GDBN} is free software and you are welcome to distribute copies |
| 11283 | of it under certain conditions; type "show copying" to see |
| 11284 | the conditions. |
| 11285 | There is absolutely no warranty for @value{GDBN}; type "show warranty" |
| 11286 | for details. |
| 11287 | @value{GDBN} @value{GDBVN}, Copyright 1992 Free Software Foundation, Inc... |
| 11288 | (@value{GDBP}) target hms |
| 11289 | Connected to remote H8/300 HMS system. |
| 11290 | (@value{GDBP}) load t.x |
| 11291 | .text : 0x8000 .. 0xabde *********** |
| 11292 | .data : 0xabde .. 0xad30 * |
| 11293 | .stack : 0xf000 .. 0xf014 * |
| 11294 | @end smallexample |
| 11295 | |
| 11296 | At this point, you're ready to run or debug your program. From here on, |
| 11297 | you can use all the usual @value{GDBN} commands. The @code{break} command |
| 11298 | sets breakpoints; the @code{run} command starts your program; |
| 11299 | @code{print} or @code{x} display data; the @code{continue} command |
| 11300 | resumes execution after stopping at a breakpoint. You can use the |
| 11301 | @code{help} command at any time to find out more about @value{GDBN} commands. |
| 11302 | |
| 11303 | Remember, however, that @emph{operating system} facilities aren't |
| 11304 | available on your development board; for example, if your program hangs, |
| 11305 | you can't send an interrupt---but you can press the @sc{reset} switch! |
| 11306 | |
| 11307 | Use the @sc{reset} button on the development board |
| 11308 | @itemize @bullet |
| 11309 | @item |
| 11310 | to interrupt your program (don't use @kbd{ctl-C} on the DOS host---it has |
| 11311 | no way to pass an interrupt signal to the development board); and |
| 11312 | |
| 11313 | @item |
| 11314 | to return to the @value{GDBN} command prompt after your program finishes |
| 11315 | normally. The communications protocol provides no other way for @value{GDBN} |
| 11316 | to detect program completion. |
| 11317 | @end itemize |
| 11318 | |
| 11319 | In either case, @value{GDBN} sees the effect of a @sc{reset} on the |
| 11320 | development board as a ``normal exit'' of your program. |
| 11321 | |
| 11322 | @node Hitachi ICE |
| 11323 | @subsubsection Using the E7000 in-circuit emulator |
| 11324 | |
| 11325 | @kindex target e7000@r{, with Hitachi ICE} |
| 11326 | You can use the E7000 in-circuit emulator to develop code for either the |
| 11327 | Hitachi SH or the H8/300H. Use one of these forms of the @samp{target |
| 11328 | e7000} command to connect @value{GDBN} to your E7000: |
| 11329 | |
| 11330 | @table @code |
| 11331 | @item target e7000 @var{port} @var{speed} |
| 11332 | Use this form if your E7000 is connected to a serial port. The |
| 11333 | @var{port} argument identifies what serial port to use (for example, |
| 11334 | @samp{com2}). The third argument is the line speed in bits per second |
| 11335 | (for example, @samp{9600}). |
| 11336 | |
| 11337 | @item target e7000 @var{hostname} |
| 11338 | If your E7000 is installed as a host on a TCP/IP network, you can just |
| 11339 | specify its hostname; @value{GDBN} uses @code{telnet} to connect. |
| 11340 | @end table |
| 11341 | |
| 11342 | @node Hitachi Special |
| 11343 | @subsubsection Special @value{GDBN} commands for Hitachi micros |
| 11344 | |
| 11345 | Some @value{GDBN} commands are available only for the H8/300: |
| 11346 | |
| 11347 | @table @code |
| 11348 | |
| 11349 | @kindex set machine |
| 11350 | @kindex show machine |
| 11351 | @item set machine h8300 |
| 11352 | @itemx set machine h8300h |
| 11353 | Condition @value{GDBN} for one of the two variants of the H8/300 |
| 11354 | architecture with @samp{set machine}. You can use @samp{show machine} |
| 11355 | to check which variant is currently in effect. |
| 11356 | |
| 11357 | @end table |
| 11358 | |
| 11359 | @node H8/500 |
| 11360 | @subsection H8/500 |
| 11361 | |
| 11362 | @table @code |
| 11363 | |
| 11364 | @kindex set memory @var{mod} |
| 11365 | @cindex memory models, H8/500 |
| 11366 | @item set memory @var{mod} |
| 11367 | @itemx show memory |
| 11368 | Specify which H8/500 memory model (@var{mod}) you are using with |
| 11369 | @samp{set memory}; check which memory model is in effect with @samp{show |
| 11370 | memory}. The accepted values for @var{mod} are @code{small}, |
| 11371 | @code{big}, @code{medium}, and @code{compact}. |
| 11372 | |
| 11373 | @end table |
| 11374 | |
| 11375 | @node i960 |
| 11376 | @subsection Intel i960 |
| 11377 | |
| 11378 | @table @code |
| 11379 | |
| 11380 | @kindex target mon960 |
| 11381 | @item target mon960 @var{dev} |
| 11382 | MON960 monitor for Intel i960. |
| 11383 | |
| 11384 | @kindex target nindy |
| 11385 | @item target nindy @var{devicename} |
| 11386 | An Intel 960 board controlled by a Nindy Monitor. @var{devicename} is |
| 11387 | the name of the serial device to use for the connection, e.g. |
| 11388 | @file{/dev/ttya}. |
| 11389 | |
| 11390 | @end table |
| 11391 | |
| 11392 | @cindex Nindy |
| 11393 | @cindex i960 |
| 11394 | @dfn{Nindy} is a ROM Monitor program for Intel 960 target systems. When |
| 11395 | @value{GDBN} is configured to control a remote Intel 960 using Nindy, you can |
| 11396 | tell @value{GDBN} how to connect to the 960 in several ways: |
| 11397 | |
| 11398 | @itemize @bullet |
| 11399 | @item |
| 11400 | Through command line options specifying serial port, version of the |
| 11401 | Nindy protocol, and communications speed; |
| 11402 | |
| 11403 | @item |
| 11404 | By responding to a prompt on startup; |
| 11405 | |
| 11406 | @item |
| 11407 | By using the @code{target} command at any point during your @value{GDBN} |
| 11408 | session. @xref{Target Commands, ,Commands for managing targets}. |
| 11409 | |
| 11410 | @end itemize |
| 11411 | |
| 11412 | @cindex download to Nindy-960 |
| 11413 | With the Nindy interface to an Intel 960 board, @code{load} |
| 11414 | downloads @var{filename} to the 960 as well as adding its symbols in |
| 11415 | @value{GDBN}. |
| 11416 | |
| 11417 | @menu |
| 11418 | * Nindy Startup:: Startup with Nindy |
| 11419 | * Nindy Options:: Options for Nindy |
| 11420 | * Nindy Reset:: Nindy reset command |
| 11421 | @end menu |
| 11422 | |
| 11423 | @node Nindy Startup |
| 11424 | @subsubsection Startup with Nindy |
| 11425 | |
| 11426 | If you simply start @code{@value{GDBP}} without using any command-line |
| 11427 | options, you are prompted for what serial port to use, @emph{before} you |
| 11428 | reach the ordinary @value{GDBN} prompt: |
| 11429 | |
| 11430 | @example |
| 11431 | Attach /dev/ttyNN -- specify NN, or "quit" to quit: |
| 11432 | @end example |
| 11433 | |
| 11434 | @noindent |
| 11435 | Respond to the prompt with whatever suffix (after @samp{/dev/tty}) |
| 11436 | identifies the serial port you want to use. You can, if you choose, |
| 11437 | simply start up with no Nindy connection by responding to the prompt |
| 11438 | with an empty line. If you do this and later wish to attach to Nindy, |
| 11439 | use @code{target} (@pxref{Target Commands, ,Commands for managing targets}). |
| 11440 | |
| 11441 | @node Nindy Options |
| 11442 | @subsubsection Options for Nindy |
| 11443 | |
| 11444 | These are the startup options for beginning your @value{GDBN} session with a |
| 11445 | Nindy-960 board attached: |
| 11446 | |
| 11447 | @table @code |
| 11448 | @item -r @var{port} |
| 11449 | Specify the serial port name of a serial interface to be used to connect |
| 11450 | to the target system. This option is only available when @value{GDBN} is |
| 11451 | configured for the Intel 960 target architecture. You may specify |
| 11452 | @var{port} as any of: a full pathname (e.g. @samp{-r /dev/ttya}), a |
| 11453 | device name in @file{/dev} (e.g. @samp{-r ttya}), or simply the unique |
| 11454 | suffix for a specific @code{tty} (e.g. @samp{-r a}). |
| 11455 | |
| 11456 | @item -O |
| 11457 | (An uppercase letter ``O'', not a zero.) Specify that @value{GDBN} should use |
| 11458 | the ``old'' Nindy monitor protocol to connect to the target system. |
| 11459 | This option is only available when @value{GDBN} is configured for the Intel 960 |
| 11460 | target architecture. |
| 11461 | |
| 11462 | @quotation |
| 11463 | @emph{Warning:} if you specify @samp{-O}, but are actually trying to |
| 11464 | connect to a target system that expects the newer protocol, the connection |
| 11465 | fails, appearing to be a speed mismatch. @value{GDBN} repeatedly |
| 11466 | attempts to reconnect at several different line speeds. You can abort |
| 11467 | this process with an interrupt. |
| 11468 | @end quotation |
| 11469 | |
| 11470 | @item -brk |
| 11471 | Specify that @value{GDBN} should first send a @code{BREAK} signal to the target |
| 11472 | system, in an attempt to reset it, before connecting to a Nindy target. |
| 11473 | |
| 11474 | @quotation |
| 11475 | @emph{Warning:} Many target systems do not have the hardware that this |
| 11476 | requires; it only works with a few boards. |
| 11477 | @end quotation |
| 11478 | @end table |
| 11479 | |
| 11480 | The standard @samp{-b} option controls the line speed used on the serial |
| 11481 | port. |
| 11482 | |
| 11483 | @c @group |
| 11484 | @node Nindy Reset |
| 11485 | @subsubsection Nindy reset command |
| 11486 | |
| 11487 | @table @code |
| 11488 | @item reset |
| 11489 | @kindex reset |
| 11490 | For a Nindy target, this command sends a ``break'' to the remote target |
| 11491 | system; this is only useful if the target has been equipped with a |
| 11492 | circuit to perform a hard reset (or some other interesting action) when |
| 11493 | a break is detected. |
| 11494 | @end table |
| 11495 | @c @end group |
| 11496 | |
| 11497 | @node M32R/D |
| 11498 | @subsection Mitsubishi M32R/D |
| 11499 | |
| 11500 | @table @code |
| 11501 | |
| 11502 | @kindex target m32r |
| 11503 | @item target m32r @var{dev} |
| 11504 | Mitsubishi M32R/D ROM monitor. |
| 11505 | |
| 11506 | @end table |
| 11507 | |
| 11508 | @node M68K |
| 11509 | @subsection M68k |
| 11510 | |
| 11511 | The Motorola m68k configuration includes ColdFire support, and |
| 11512 | target command for the following ROM monitors. |
| 11513 | |
| 11514 | @table @code |
| 11515 | |
| 11516 | @kindex target abug |
| 11517 | @item target abug @var{dev} |
| 11518 | ABug ROM monitor for M68K. |
| 11519 | |
| 11520 | @kindex target cpu32bug |
| 11521 | @item target cpu32bug @var{dev} |
| 11522 | CPU32BUG monitor, running on a CPU32 (M68K) board. |
| 11523 | |
| 11524 | @kindex target dbug |
| 11525 | @item target dbug @var{dev} |
| 11526 | dBUG ROM monitor for Motorola ColdFire. |
| 11527 | |
| 11528 | @kindex target est |
| 11529 | @item target est @var{dev} |
| 11530 | EST-300 ICE monitor, running on a CPU32 (M68K) board. |
| 11531 | |
| 11532 | @kindex target rom68k |
| 11533 | @item target rom68k @var{dev} |
| 11534 | ROM 68K monitor, running on an M68K IDP board. |
| 11535 | |
| 11536 | @end table |
| 11537 | |
| 11538 | If @value{GDBN} is configured with @code{m68*-ericsson-*}, it will |
| 11539 | instead have only a single special target command: |
| 11540 | |
| 11541 | @table @code |
| 11542 | |
| 11543 | @kindex target es1800 |
| 11544 | @item target es1800 @var{dev} |
| 11545 | ES-1800 emulator for M68K. |
| 11546 | |
| 11547 | @end table |
| 11548 | |
| 11549 | [context?] |
| 11550 | |
| 11551 | @table @code |
| 11552 | |
| 11553 | @kindex target rombug |
| 11554 | @item target rombug @var{dev} |
| 11555 | ROMBUG ROM monitor for OS/9000. |
| 11556 | |
| 11557 | @end table |
| 11558 | |
| 11559 | @node M88K |
| 11560 | @subsection M88K |
| 11561 | |
| 11562 | @table @code |
| 11563 | |
| 11564 | @kindex target bug |
| 11565 | @item target bug @var{dev} |
| 11566 | BUG monitor, running on a MVME187 (m88k) board. |
| 11567 | |
| 11568 | @end table |
| 11569 | |
| 11570 | @node MIPS Embedded |
| 11571 | @subsection MIPS Embedded |
| 11572 | |
| 11573 | @cindex MIPS boards |
| 11574 | @value{GDBN} can use the MIPS remote debugging protocol to talk to a |
| 11575 | MIPS board attached to a serial line. This is available when |
| 11576 | you configure @value{GDBN} with @samp{--target=mips-idt-ecoff}. |
| 11577 | |
| 11578 | @need 1000 |
| 11579 | Use these @value{GDBN} commands to specify the connection to your target board: |
| 11580 | |
| 11581 | @table @code |
| 11582 | @item target mips @var{port} |
| 11583 | @kindex target mips @var{port} |
| 11584 | To run a program on the board, start up @code{@value{GDBP}} with the |
| 11585 | name of your program as the argument. To connect to the board, use the |
| 11586 | command @samp{target mips @var{port}}, where @var{port} is the name of |
| 11587 | the serial port connected to the board. If the program has not already |
| 11588 | been downloaded to the board, you may use the @code{load} command to |
| 11589 | download it. You can then use all the usual @value{GDBN} commands. |
| 11590 | |
| 11591 | For example, this sequence connects to the target board through a serial |
| 11592 | port, and loads and runs a program called @var{prog} through the |
| 11593 | debugger: |
| 11594 | |
| 11595 | @example |
| 11596 | host$ @value{GDBP} @var{prog} |
| 11597 | @value{GDBN} is free software and @dots{} |
| 11598 | (@value{GDBP}) target mips /dev/ttyb |
| 11599 | (@value{GDBP}) load @var{prog} |
| 11600 | (@value{GDBP}) run |
| 11601 | @end example |
| 11602 | |
| 11603 | @item target mips @var{hostname}:@var{portnumber} |
| 11604 | On some @value{GDBN} host configurations, you can specify a TCP |
| 11605 | connection (for instance, to a serial line managed by a terminal |
| 11606 | concentrator) instead of a serial port, using the syntax |
| 11607 | @samp{@var{hostname}:@var{portnumber}}. |
| 11608 | |
| 11609 | @item target pmon @var{port} |
| 11610 | @kindex target pmon @var{port} |
| 11611 | PMON ROM monitor. |
| 11612 | |
| 11613 | @item target ddb @var{port} |
| 11614 | @kindex target ddb @var{port} |
| 11615 | NEC's DDB variant of PMON for Vr4300. |
| 11616 | |
| 11617 | @item target lsi @var{port} |
| 11618 | @kindex target lsi @var{port} |
| 11619 | LSI variant of PMON. |
| 11620 | |
| 11621 | @kindex target r3900 |
| 11622 | @item target r3900 @var{dev} |
| 11623 | Densan DVE-R3900 ROM monitor for Toshiba R3900 Mips. |
| 11624 | |
| 11625 | @kindex target array |
| 11626 | @item target array @var{dev} |
| 11627 | Array Tech LSI33K RAID controller board. |
| 11628 | |
| 11629 | @end table |
| 11630 | |
| 11631 | |
| 11632 | @noindent |
| 11633 | @value{GDBN} also supports these special commands for MIPS targets: |
| 11634 | |
| 11635 | @table @code |
| 11636 | @item set processor @var{args} |
| 11637 | @itemx show processor |
| 11638 | @kindex set processor @var{args} |
| 11639 | @kindex show processor |
| 11640 | Use the @code{set processor} command to set the type of MIPS |
| 11641 | processor when you want to access processor-type-specific registers. |
| 11642 | For example, @code{set processor @var{r3041}} tells @value{GDBN} |
| 11643 | to use the CPU registers appropriate for the 3041 chip. |
| 11644 | Use the @code{show processor} command to see what MIPS processor @value{GDBN} |
| 11645 | is using. Use the @code{info reg} command to see what registers |
| 11646 | @value{GDBN} is using. |
| 11647 | |
| 11648 | @item set mipsfpu double |
| 11649 | @itemx set mipsfpu single |
| 11650 | @itemx set mipsfpu none |
| 11651 | @itemx show mipsfpu |
| 11652 | @kindex set mipsfpu |
| 11653 | @kindex show mipsfpu |
| 11654 | @cindex MIPS remote floating point |
| 11655 | @cindex floating point, MIPS remote |
| 11656 | If your target board does not support the MIPS floating point |
| 11657 | coprocessor, you should use the command @samp{set mipsfpu none} (if you |
| 11658 | need this, you may wish to put the command in your @value{GDBN} init |
| 11659 | file). This tells @value{GDBN} how to find the return value of |
| 11660 | functions which return floating point values. It also allows |
| 11661 | @value{GDBN} to avoid saving the floating point registers when calling |
| 11662 | functions on the board. If you are using a floating point coprocessor |
| 11663 | with only single precision floating point support, as on the @sc{r4650} |
| 11664 | processor, use the command @samp{set mipsfpu single}. The default |
| 11665 | double precision floating point coprocessor may be selected using |
| 11666 | @samp{set mipsfpu double}. |
| 11667 | |
| 11668 | In previous versions the only choices were double precision or no |
| 11669 | floating point, so @samp{set mipsfpu on} will select double precision |
| 11670 | and @samp{set mipsfpu off} will select no floating point. |
| 11671 | |
| 11672 | As usual, you can inquire about the @code{mipsfpu} variable with |
| 11673 | @samp{show mipsfpu}. |
| 11674 | |
| 11675 | @item set remotedebug @var{n} |
| 11676 | @itemx show remotedebug |
| 11677 | @kindex set remotedebug@r{, MIPS protocol} |
| 11678 | @kindex show remotedebug@r{, MIPS protocol} |
| 11679 | @cindex @code{remotedebug}, MIPS protocol |
| 11680 | @cindex MIPS @code{remotedebug} protocol |
| 11681 | @c FIXME! For this to be useful, you must know something about the MIPS |
| 11682 | @c FIXME...protocol. Where is it described? |
| 11683 | You can see some debugging information about communications with the board |
| 11684 | by setting the @code{remotedebug} variable. If you set it to @code{1} using |
| 11685 | @samp{set remotedebug 1}, every packet is displayed. If you set it |
| 11686 | to @code{2}, every character is displayed. You can check the current value |
| 11687 | at any time with the command @samp{show remotedebug}. |
| 11688 | |
| 11689 | @item set timeout @var{seconds} |
| 11690 | @itemx set retransmit-timeout @var{seconds} |
| 11691 | @itemx show timeout |
| 11692 | @itemx show retransmit-timeout |
| 11693 | @cindex @code{timeout}, MIPS protocol |
| 11694 | @cindex @code{retransmit-timeout}, MIPS protocol |
| 11695 | @kindex set timeout |
| 11696 | @kindex show timeout |
| 11697 | @kindex set retransmit-timeout |
| 11698 | @kindex show retransmit-timeout |
| 11699 | You can control the timeout used while waiting for a packet, in the MIPS |
| 11700 | remote protocol, with the @code{set timeout @var{seconds}} command. The |
| 11701 | default is 5 seconds. Similarly, you can control the timeout used while |
| 11702 | waiting for an acknowledgement of a packet with the @code{set |
| 11703 | retransmit-timeout @var{seconds}} command. The default is 3 seconds. |
| 11704 | You can inspect both values with @code{show timeout} and @code{show |
| 11705 | retransmit-timeout}. (These commands are @emph{only} available when |
| 11706 | @value{GDBN} is configured for @samp{--target=mips-idt-ecoff}.) |
| 11707 | |
| 11708 | The timeout set by @code{set timeout} does not apply when @value{GDBN} |
| 11709 | is waiting for your program to stop. In that case, @value{GDBN} waits |
| 11710 | forever because it has no way of knowing how long the program is going |
| 11711 | to run before stopping. |
| 11712 | @end table |
| 11713 | |
| 11714 | @node PowerPC |
| 11715 | @subsection PowerPC |
| 11716 | |
| 11717 | @table @code |
| 11718 | |
| 11719 | @kindex target dink32 |
| 11720 | @item target dink32 @var{dev} |
| 11721 | DINK32 ROM monitor. |
| 11722 | |
| 11723 | @kindex target ppcbug |
| 11724 | @item target ppcbug @var{dev} |
| 11725 | @kindex target ppcbug1 |
| 11726 | @item target ppcbug1 @var{dev} |
| 11727 | PPCBUG ROM monitor for PowerPC. |
| 11728 | |
| 11729 | @kindex target sds |
| 11730 | @item target sds @var{dev} |
| 11731 | SDS monitor, running on a PowerPC board (such as Motorola's ADS). |
| 11732 | |
| 11733 | @end table |
| 11734 | |
| 11735 | @node PA |
| 11736 | @subsection HP PA Embedded |
| 11737 | |
| 11738 | @table @code |
| 11739 | |
| 11740 | @kindex target op50n |
| 11741 | @item target op50n @var{dev} |
| 11742 | OP50N monitor, running on an OKI HPPA board. |
| 11743 | |
| 11744 | @kindex target w89k |
| 11745 | @item target w89k @var{dev} |
| 11746 | W89K monitor, running on a Winbond HPPA board. |
| 11747 | |
| 11748 | @end table |
| 11749 | |
| 11750 | @node SH |
| 11751 | @subsection Hitachi SH |
| 11752 | |
| 11753 | @table @code |
| 11754 | |
| 11755 | @kindex target hms@r{, with Hitachi SH} |
| 11756 | @item target hms @var{dev} |
| 11757 | A Hitachi SH board attached via serial line to your host. Use special |
| 11758 | commands @code{device} and @code{speed} to control the serial line and |
| 11759 | the communications speed used. |
| 11760 | |
| 11761 | @kindex target e7000@r{, with Hitachi SH} |
| 11762 | @item target e7000 @var{dev} |
| 11763 | E7000 emulator for Hitachi SH. |
| 11764 | |
| 11765 | @kindex target sh3@r{, with SH} |
| 11766 | @kindex target sh3e@r{, with SH} |
| 11767 | @item target sh3 @var{dev} |
| 11768 | @item target sh3e @var{dev} |
| 11769 | Hitachi SH-3 and SH-3E target systems. |
| 11770 | |
| 11771 | @end table |
| 11772 | |
| 11773 | @node Sparclet |
| 11774 | @subsection Tsqware Sparclet |
| 11775 | |
| 11776 | @cindex Sparclet |
| 11777 | |
| 11778 | @value{GDBN} enables developers to debug tasks running on |
| 11779 | Sparclet targets from a Unix host. |
| 11780 | @value{GDBN} uses code that runs on |
| 11781 | both the Unix host and on the Sparclet target. The program |
| 11782 | @code{@value{GDBP}} is installed and executed on the Unix host. |
| 11783 | |
| 11784 | @table @code |
| 11785 | @item remotetimeout @var{args} |
| 11786 | @kindex remotetimeout |
| 11787 | @value{GDBN} supports the option @code{remotetimeout}. |
| 11788 | This option is set by the user, and @var{args} represents the number of |
| 11789 | seconds @value{GDBN} waits for responses. |
| 11790 | @end table |
| 11791 | |
| 11792 | @cindex compiling, on Sparclet |
| 11793 | When compiling for debugging, include the options @samp{-g} to get debug |
| 11794 | information and @samp{-Ttext} to relocate the program to where you wish to |
| 11795 | load it on the target. You may also want to add the options @samp{-n} or |
| 11796 | @samp{-N} in order to reduce the size of the sections. Example: |
| 11797 | |
| 11798 | @example |
| 11799 | sparclet-aout-gcc prog.c -Ttext 0x12010000 -g -o prog -N |
| 11800 | @end example |
| 11801 | |
| 11802 | You can use @code{objdump} to verify that the addresses are what you intended: |
| 11803 | |
| 11804 | @example |
| 11805 | sparclet-aout-objdump --headers --syms prog |
| 11806 | @end example |
| 11807 | |
| 11808 | @cindex running, on Sparclet |
| 11809 | Once you have set |
| 11810 | your Unix execution search path to find @value{GDBN}, you are ready to |
| 11811 | run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} |
| 11812 | (or @code{sparclet-aout-gdb}, depending on your installation). |
| 11813 | |
| 11814 | @value{GDBN} comes up showing the prompt: |
| 11815 | |
| 11816 | @example |
| 11817 | (gdbslet) |
| 11818 | @end example |
| 11819 | |
| 11820 | @menu |
| 11821 | * Sparclet File:: Setting the file to debug |
| 11822 | * Sparclet Connection:: Connecting to Sparclet |
| 11823 | * Sparclet Download:: Sparclet download |
| 11824 | * Sparclet Execution:: Running and debugging |
| 11825 | @end menu |
| 11826 | |
| 11827 | @node Sparclet File |
| 11828 | @subsubsection Setting file to debug |
| 11829 | |
| 11830 | The @value{GDBN} command @code{file} lets you choose with program to debug. |
| 11831 | |
| 11832 | @example |
| 11833 | (gdbslet) file prog |
| 11834 | @end example |
| 11835 | |
| 11836 | @need 1000 |
| 11837 | @value{GDBN} then attempts to read the symbol table of @file{prog}. |
| 11838 | @value{GDBN} locates |
| 11839 | the file by searching the directories listed in the command search |
| 11840 | path. |
| 11841 | If the file was compiled with debug information (option "-g"), source |
| 11842 | files will be searched as well. |
| 11843 | @value{GDBN} locates |
| 11844 | the source files by searching the directories listed in the directory search |
| 11845 | path (@pxref{Environment, ,Your program's environment}). |
| 11846 | If it fails |
| 11847 | to find a file, it displays a message such as: |
| 11848 | |
| 11849 | @example |
| 11850 | prog: No such file or directory. |
| 11851 | @end example |
| 11852 | |
| 11853 | When this happens, add the appropriate directories to the search paths with |
| 11854 | the @value{GDBN} commands @code{path} and @code{dir}, and execute the |
| 11855 | @code{target} command again. |
| 11856 | |
| 11857 | @node Sparclet Connection |
| 11858 | @subsubsection Connecting to Sparclet |
| 11859 | |
| 11860 | The @value{GDBN} command @code{target} lets you connect to a Sparclet target. |
| 11861 | To connect to a target on serial port ``@code{ttya}'', type: |
| 11862 | |
| 11863 | @example |
| 11864 | (gdbslet) target sparclet /dev/ttya |
| 11865 | Remote target sparclet connected to /dev/ttya |
| 11866 | main () at ../prog.c:3 |
| 11867 | @end example |
| 11868 | |
| 11869 | @need 750 |
| 11870 | @value{GDBN} displays messages like these: |
| 11871 | |
| 11872 | @example |
| 11873 | Connected to ttya. |
| 11874 | @end example |
| 11875 | |
| 11876 | @node Sparclet Download |
| 11877 | @subsubsection Sparclet download |
| 11878 | |
| 11879 | @cindex download to Sparclet |
| 11880 | Once connected to the Sparclet target, |
| 11881 | you can use the @value{GDBN} |
| 11882 | @code{load} command to download the file from the host to the target. |
| 11883 | The file name and load offset should be given as arguments to the @code{load} |
| 11884 | command. |
| 11885 | Since the file format is aout, the program must be loaded to the starting |
| 11886 | address. You can use @code{objdump} to find out what this value is. The load |
| 11887 | offset is an offset which is added to the VMA (virtual memory address) |
| 11888 | of each of the file's sections. |
| 11889 | For instance, if the program |
| 11890 | @file{prog} was linked to text address 0x1201000, with data at 0x12010160 |
| 11891 | and bss at 0x12010170, in @value{GDBN}, type: |
| 11892 | |
| 11893 | @example |
| 11894 | (gdbslet) load prog 0x12010000 |
| 11895 | Loading section .text, size 0xdb0 vma 0x12010000 |
| 11896 | @end example |
| 11897 | |
| 11898 | If the code is loaded at a different address then what the program was linked |
| 11899 | to, you may need to use the @code{section} and @code{add-symbol-file} commands |
| 11900 | to tell @value{GDBN} where to map the symbol table. |
| 11901 | |
| 11902 | @node Sparclet Execution |
| 11903 | @subsubsection Running and debugging |
| 11904 | |
| 11905 | @cindex running and debugging Sparclet programs |
| 11906 | You can now begin debugging the task using @value{GDBN}'s execution control |
| 11907 | commands, @code{b}, @code{step}, @code{run}, etc. See the @value{GDBN} |
| 11908 | manual for the list of commands. |
| 11909 | |
| 11910 | @example |
| 11911 | (gdbslet) b main |
| 11912 | Breakpoint 1 at 0x12010000: file prog.c, line 3. |
| 11913 | (gdbslet) run |
| 11914 | Starting program: prog |
| 11915 | Breakpoint 1, main (argc=1, argv=0xeffff21c) at prog.c:3 |
| 11916 | 3 char *symarg = 0; |
| 11917 | (gdbslet) step |
| 11918 | 4 char *execarg = "hello!"; |
| 11919 | (gdbslet) |
| 11920 | @end example |
| 11921 | |
| 11922 | @node Sparclite |
| 11923 | @subsection Fujitsu Sparclite |
| 11924 | |
| 11925 | @table @code |
| 11926 | |
| 11927 | @kindex target sparclite |
| 11928 | @item target sparclite @var{dev} |
| 11929 | Fujitsu sparclite boards, used only for the purpose of loading. |
| 11930 | You must use an additional command to debug the program. |
| 11931 | For example: target remote @var{dev} using @value{GDBN} standard |
| 11932 | remote protocol. |
| 11933 | |
| 11934 | @end table |
| 11935 | |
| 11936 | @node ST2000 |
| 11937 | @subsection Tandem ST2000 |
| 11938 | |
| 11939 | @value{GDBN} may be used with a Tandem ST2000 phone switch, running Tandem's |
| 11940 | STDBUG protocol. |
| 11941 | |
| 11942 | To connect your ST2000 to the host system, see the manufacturer's |
| 11943 | manual. Once the ST2000 is physically attached, you can run: |
| 11944 | |
| 11945 | @example |
| 11946 | target st2000 @var{dev} @var{speed} |
| 11947 | @end example |
| 11948 | |
| 11949 | @noindent |
| 11950 | to establish it as your debugging environment. @var{dev} is normally |
| 11951 | the name of a serial device, such as @file{/dev/ttya}, connected to the |
| 11952 | ST2000 via a serial line. You can instead specify @var{dev} as a TCP |
| 11953 | connection (for example, to a serial line attached via a terminal |
| 11954 | concentrator) using the syntax @code{@var{hostname}:@var{portnumber}}. |
| 11955 | |
| 11956 | The @code{load} and @code{attach} commands are @emph{not} defined for |
| 11957 | this target; you must load your program into the ST2000 as you normally |
| 11958 | would for standalone operation. @value{GDBN} reads debugging information |
| 11959 | (such as symbols) from a separate, debugging version of the program |
| 11960 | available on your host computer. |
| 11961 | @c FIXME!! This is terribly vague; what little content is here is |
| 11962 | @c basically hearsay. |
| 11963 | |
| 11964 | @cindex ST2000 auxiliary commands |
| 11965 | These auxiliary @value{GDBN} commands are available to help you with the ST2000 |
| 11966 | environment: |
| 11967 | |
| 11968 | @table @code |
| 11969 | @item st2000 @var{command} |
| 11970 | @kindex st2000 @var{cmd} |
| 11971 | @cindex STDBUG commands (ST2000) |
| 11972 | @cindex commands to STDBUG (ST2000) |
| 11973 | Send a @var{command} to the STDBUG monitor. See the manufacturer's |
| 11974 | manual for available commands. |
| 11975 | |
| 11976 | @item connect |
| 11977 | @cindex connect (to STDBUG) |
| 11978 | Connect the controlling terminal to the STDBUG command monitor. When |
| 11979 | you are done interacting with STDBUG, typing either of two character |
| 11980 | sequences gets you back to the @value{GDBN} command prompt: |
| 11981 | @kbd{@key{RET}~.} (Return, followed by tilde and period) or |
| 11982 | @kbd{@key{RET}~@key{C-d}} (Return, followed by tilde and control-D). |
| 11983 | @end table |
| 11984 | |
| 11985 | @node Z8000 |
| 11986 | @subsection Zilog Z8000 |
| 11987 | |
| 11988 | @cindex Z8000 |
| 11989 | @cindex simulator, Z8000 |
| 11990 | @cindex Zilog Z8000 simulator |
| 11991 | |
| 11992 | When configured for debugging Zilog Z8000 targets, @value{GDBN} includes |
| 11993 | a Z8000 simulator. |
| 11994 | |
| 11995 | For the Z8000 family, @samp{target sim} simulates either the Z8002 (the |
| 11996 | unsegmented variant of the Z8000 architecture) or the Z8001 (the |
| 11997 | segmented variant). The simulator recognizes which architecture is |
| 11998 | appropriate by inspecting the object code. |
| 11999 | |
| 12000 | @table @code |
| 12001 | @item target sim @var{args} |
| 12002 | @kindex sim |
| 12003 | @kindex target sim@r{, with Z8000} |
| 12004 | Debug programs on a simulated CPU. If the simulator supports setup |
| 12005 | options, specify them via @var{args}. |
| 12006 | @end table |
| 12007 | |
| 12008 | @noindent |
| 12009 | After specifying this target, you can debug programs for the simulated |
| 12010 | CPU in the same style as programs for your host computer; use the |
| 12011 | @code{file} command to load a new program image, the @code{run} command |
| 12012 | to run your program, and so on. |
| 12013 | |
| 12014 | As well as making available all the usual machine registers |
| 12015 | (@pxref{Registers, ,Registers}), the Z8000 simulator provides three |
| 12016 | additional items of information as specially named registers: |
| 12017 | |
| 12018 | @table @code |
| 12019 | |
| 12020 | @item cycles |
| 12021 | Counts clock-ticks in the simulator. |
| 12022 | |
| 12023 | @item insts |
| 12024 | Counts instructions run in the simulator. |
| 12025 | |
| 12026 | @item time |
| 12027 | Execution time in 60ths of a second. |
| 12028 | |
| 12029 | @end table |
| 12030 | |
| 12031 | You can refer to these values in @value{GDBN} expressions with the usual |
| 12032 | conventions; for example, @w{@samp{b fputc if $cycles>5000}} sets a |
| 12033 | conditional breakpoint that suspends only after at least 5000 |
| 12034 | simulated clock ticks. |
| 12035 | |
| 12036 | @node Architectures |
| 12037 | @section Architectures |
| 12038 | |
| 12039 | This section describes characteristics of architectures that affect |
| 12040 | all uses of @value{GDBN} with the architecture, both native and cross. |
| 12041 | |
| 12042 | @menu |
| 12043 | * A29K:: |
| 12044 | * Alpha:: |
| 12045 | * MIPS:: |
| 12046 | @end menu |
| 12047 | |
| 12048 | @node A29K |
| 12049 | @subsection A29K |
| 12050 | |
| 12051 | @table @code |
| 12052 | |
| 12053 | @kindex set rstack_high_address |
| 12054 | @cindex AMD 29K register stack |
| 12055 | @cindex register stack, AMD29K |
| 12056 | @item set rstack_high_address @var{address} |
| 12057 | On AMD 29000 family processors, registers are saved in a separate |
| 12058 | @dfn{register stack}. There is no way for @value{GDBN} to determine the |
| 12059 | extent of this stack. Normally, @value{GDBN} just assumes that the |
| 12060 | stack is ``large enough''. This may result in @value{GDBN} referencing |
| 12061 | memory locations that do not exist. If necessary, you can get around |
| 12062 | this problem by specifying the ending address of the register stack with |
| 12063 | the @code{set rstack_high_address} command. The argument should be an |
| 12064 | address, which you probably want to precede with @samp{0x} to specify in |
| 12065 | hexadecimal. |
| 12066 | |
| 12067 | @kindex show rstack_high_address |
| 12068 | @item show rstack_high_address |
| 12069 | Display the current limit of the register stack, on AMD 29000 family |
| 12070 | processors. |
| 12071 | |
| 12072 | @end table |
| 12073 | |
| 12074 | @node Alpha |
| 12075 | @subsection Alpha |
| 12076 | |
| 12077 | See the following section. |
| 12078 | |
| 12079 | @node MIPS |
| 12080 | @subsection MIPS |
| 12081 | |
| 12082 | @cindex stack on Alpha |
| 12083 | @cindex stack on MIPS |
| 12084 | @cindex Alpha stack |
| 12085 | @cindex MIPS stack |
| 12086 | Alpha- and MIPS-based computers use an unusual stack frame, which |
| 12087 | sometimes requires @value{GDBN} to search backward in the object code to |
| 12088 | find the beginning of a function. |
| 12089 | |
| 12090 | @cindex response time, MIPS debugging |
| 12091 | To improve response time (especially for embedded applications, where |
| 12092 | @value{GDBN} may be restricted to a slow serial line for this search) |
| 12093 | you may want to limit the size of this search, using one of these |
| 12094 | commands: |
| 12095 | |
| 12096 | @table @code |
| 12097 | @cindex @code{heuristic-fence-post} (Alpha, MIPS) |
| 12098 | @item set heuristic-fence-post @var{limit} |
| 12099 | Restrict @value{GDBN} to examining at most @var{limit} bytes in its |
| 12100 | search for the beginning of a function. A value of @var{0} (the |
| 12101 | default) means there is no limit. However, except for @var{0}, the |
| 12102 | larger the limit the more bytes @code{heuristic-fence-post} must search |
| 12103 | and therefore the longer it takes to run. |
| 12104 | |
| 12105 | @item show heuristic-fence-post |
| 12106 | Display the current limit. |
| 12107 | @end table |
| 12108 | |
| 12109 | @noindent |
| 12110 | These commands are available @emph{only} when @value{GDBN} is configured |
| 12111 | for debugging programs on Alpha or MIPS processors. |
| 12112 | |
| 12113 | |
| 12114 | @node Controlling GDB |
| 12115 | @chapter Controlling @value{GDBN} |
| 12116 | |
| 12117 | You can alter the way @value{GDBN} interacts with you by using the |
| 12118 | @code{set} command. For commands controlling how @value{GDBN} displays |
| 12119 | data, see @ref{Print Settings, ,Print settings}. Other settings are |
| 12120 | described here. |
| 12121 | |
| 12122 | @menu |
| 12123 | * Prompt:: Prompt |
| 12124 | * Editing:: Command editing |
| 12125 | * History:: Command history |
| 12126 | * Screen Size:: Screen size |
| 12127 | * Numbers:: Numbers |
| 12128 | * Messages/Warnings:: Optional warnings and messages |
| 12129 | * Debugging Output:: Optional messages about internal happenings |
| 12130 | @end menu |
| 12131 | |
| 12132 | @node Prompt |
| 12133 | @section Prompt |
| 12134 | |
| 12135 | @cindex prompt |
| 12136 | |
| 12137 | @value{GDBN} indicates its readiness to read a command by printing a string |
| 12138 | called the @dfn{prompt}. This string is normally @samp{(@value{GDBP})}. You |
| 12139 | can change the prompt string with the @code{set prompt} command. For |
| 12140 | instance, when debugging @value{GDBN} with @value{GDBN}, it is useful to change |
| 12141 | the prompt in one of the @value{GDBN} sessions so that you can always tell |
| 12142 | which one you are talking to. |
| 12143 | |
| 12144 | @emph{Note:} @code{set prompt} does not add a space for you after the |
| 12145 | prompt you set. This allows you to set a prompt which ends in a space |
| 12146 | or a prompt that does not. |
| 12147 | |
| 12148 | @table @code |
| 12149 | @kindex set prompt |
| 12150 | @item set prompt @var{newprompt} |
| 12151 | Directs @value{GDBN} to use @var{newprompt} as its prompt string henceforth. |
| 12152 | |
| 12153 | @kindex show prompt |
| 12154 | @item show prompt |
| 12155 | Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}} |
| 12156 | @end table |
| 12157 | |
| 12158 | @node Editing |
| 12159 | @section Command editing |
| 12160 | @cindex readline |
| 12161 | @cindex command line editing |
| 12162 | |
| 12163 | @value{GDBN} reads its input commands via the @dfn{readline} interface. This |
| 12164 | @sc{gnu} library provides consistent behavior for programs which provide a |
| 12165 | command line interface to the user. Advantages are @sc{gnu} Emacs-style |
| 12166 | or @dfn{vi}-style inline editing of commands, @code{csh}-like history |
| 12167 | substitution, and a storage and recall of command history across |
| 12168 | debugging sessions. |
| 12169 | |
| 12170 | You may control the behavior of command line editing in @value{GDBN} with the |
| 12171 | command @code{set}. |
| 12172 | |
| 12173 | @table @code |
| 12174 | @kindex set editing |
| 12175 | @cindex editing |
| 12176 | @item set editing |
| 12177 | @itemx set editing on |
| 12178 | Enable command line editing (enabled by default). |
| 12179 | |
| 12180 | @item set editing off |
| 12181 | Disable command line editing. |
| 12182 | |
| 12183 | @kindex show editing |
| 12184 | @item show editing |
| 12185 | Show whether command line editing is enabled. |
| 12186 | @end table |
| 12187 | |
| 12188 | @node History |
| 12189 | @section Command history |
| 12190 | |
| 12191 | @value{GDBN} can keep track of the commands you type during your |
| 12192 | debugging sessions, so that you can be certain of precisely what |
| 12193 | happened. Use these commands to manage the @value{GDBN} command |
| 12194 | history facility. |
| 12195 | |
| 12196 | @table @code |
| 12197 | @cindex history substitution |
| 12198 | @cindex history file |
| 12199 | @kindex set history filename |
| 12200 | @kindex GDBHISTFILE |
| 12201 | @item set history filename @var{fname} |
| 12202 | Set the name of the @value{GDBN} command history file to @var{fname}. |
| 12203 | This is the file where @value{GDBN} reads an initial command history |
| 12204 | list, and where it writes the command history from this session when it |
| 12205 | exits. You can access this list through history expansion or through |
| 12206 | the history command editing characters listed below. This file defaults |
| 12207 | to the value of the environment variable @code{GDBHISTFILE}, or to |
| 12208 | @file{./.gdb_history} (@file{./_gdb_history} on MS-DOS) if this variable |
| 12209 | is not set. |
| 12210 | |
| 12211 | @cindex history save |
| 12212 | @kindex set history save |
| 12213 | @item set history save |
| 12214 | @itemx set history save on |
| 12215 | Record command history in a file, whose name may be specified with the |
| 12216 | @code{set history filename} command. By default, this option is disabled. |
| 12217 | |
| 12218 | @item set history save off |
| 12219 | Stop recording command history in a file. |
| 12220 | |
| 12221 | @cindex history size |
| 12222 | @kindex set history size |
| 12223 | @item set history size @var{size} |
| 12224 | Set the number of commands which @value{GDBN} keeps in its history list. |
| 12225 | This defaults to the value of the environment variable |
| 12226 | @code{HISTSIZE}, or to 256 if this variable is not set. |
| 12227 | @end table |
| 12228 | |
| 12229 | @cindex history expansion |
| 12230 | History expansion assigns special meaning to the character @kbd{!}. |
| 12231 | @ifset have-readline-appendices |
| 12232 | @xref{Event Designators}. |
| 12233 | @end ifset |
| 12234 | |
| 12235 | Since @kbd{!} is also the logical not operator in C, history expansion |
| 12236 | is off by default. If you decide to enable history expansion with the |
| 12237 | @code{set history expansion on} command, you may sometimes need to |
| 12238 | follow @kbd{!} (when it is used as logical not, in an expression) with |
| 12239 | a space or a tab to prevent it from being expanded. The readline |
| 12240 | history facilities do not attempt substitution on the strings |
| 12241 | @kbd{!=} and @kbd{!(}, even when history expansion is enabled. |
| 12242 | |
| 12243 | The commands to control history expansion are: |
| 12244 | |
| 12245 | @table @code |
| 12246 | @kindex set history expansion |
| 12247 | @item set history expansion on |
| 12248 | @itemx set history expansion |
| 12249 | Enable history expansion. History expansion is off by default. |
| 12250 | |
| 12251 | @item set history expansion off |
| 12252 | Disable history expansion. |
| 12253 | |
| 12254 | The readline code comes with more complete documentation of |
| 12255 | editing and history expansion features. Users unfamiliar with @sc{gnu} Emacs |
| 12256 | or @code{vi} may wish to read it. |
| 12257 | @ifset have-readline-appendices |
| 12258 | @xref{Command Line Editing}. |
| 12259 | @end ifset |
| 12260 | |
| 12261 | @c @group |
| 12262 | @kindex show history |
| 12263 | @item show history |
| 12264 | @itemx show history filename |
| 12265 | @itemx show history save |
| 12266 | @itemx show history size |
| 12267 | @itemx show history expansion |
| 12268 | These commands display the state of the @value{GDBN} history parameters. |
| 12269 | @code{show history} by itself displays all four states. |
| 12270 | @c @end group |
| 12271 | @end table |
| 12272 | |
| 12273 | @table @code |
| 12274 | @kindex shows |
| 12275 | @item show commands |
| 12276 | Display the last ten commands in the command history. |
| 12277 | |
| 12278 | @item show commands @var{n} |
| 12279 | Print ten commands centered on command number @var{n}. |
| 12280 | |
| 12281 | @item show commands + |
| 12282 | Print ten commands just after the commands last printed. |
| 12283 | @end table |
| 12284 | |
| 12285 | @node Screen Size |
| 12286 | @section Screen size |
| 12287 | @cindex size of screen |
| 12288 | @cindex pauses in output |
| 12289 | |
| 12290 | Certain commands to @value{GDBN} may produce large amounts of |
| 12291 | information output to the screen. To help you read all of it, |
| 12292 | @value{GDBN} pauses and asks you for input at the end of each page of |
| 12293 | output. Type @key{RET} when you want to continue the output, or @kbd{q} |
| 12294 | to discard the remaining output. Also, the screen width setting |
| 12295 | determines when to wrap lines of output. Depending on what is being |
| 12296 | printed, @value{GDBN} tries to break the line at a readable place, |
| 12297 | rather than simply letting it overflow onto the following line. |
| 12298 | |
| 12299 | Normally @value{GDBN} knows the size of the screen from the terminal |
| 12300 | driver software. For example, on Unix @value{GDBN} uses the termcap data base |
| 12301 | together with the value of the @code{TERM} environment variable and the |
| 12302 | @code{stty rows} and @code{stty cols} settings. If this is not correct, |
| 12303 | you can override it with the @code{set height} and @code{set |
| 12304 | width} commands: |
| 12305 | |
| 12306 | @table @code |
| 12307 | @kindex set height |
| 12308 | @kindex set width |
| 12309 | @kindex show width |
| 12310 | @kindex show height |
| 12311 | @item set height @var{lpp} |
| 12312 | @itemx show height |
| 12313 | @itemx set width @var{cpl} |
| 12314 | @itemx show width |
| 12315 | These @code{set} commands specify a screen height of @var{lpp} lines and |
| 12316 | a screen width of @var{cpl} characters. The associated @code{show} |
| 12317 | commands display the current settings. |
| 12318 | |
| 12319 | If you specify a height of zero lines, @value{GDBN} does not pause during |
| 12320 | output no matter how long the output is. This is useful if output is to a |
| 12321 | file or to an editor buffer. |
| 12322 | |
| 12323 | Likewise, you can specify @samp{set width 0} to prevent @value{GDBN} |
| 12324 | from wrapping its output. |
| 12325 | @end table |
| 12326 | |
| 12327 | @node Numbers |
| 12328 | @section Numbers |
| 12329 | @cindex number representation |
| 12330 | @cindex entering numbers |
| 12331 | |
| 12332 | You can always enter numbers in octal, decimal, or hexadecimal in |
| 12333 | @value{GDBN} by the usual conventions: octal numbers begin with |
| 12334 | @samp{0}, decimal numbers end with @samp{.}, and hexadecimal numbers |
| 12335 | begin with @samp{0x}. Numbers that begin with none of these are, by |
| 12336 | default, entered in base 10; likewise, the default display for |
| 12337 | numbers---when no particular format is specified---is base 10. You can |
| 12338 | change the default base for both input and output with the @code{set |
| 12339 | radix} command. |
| 12340 | |
| 12341 | @table @code |
| 12342 | @kindex set input-radix |
| 12343 | @item set input-radix @var{base} |
| 12344 | Set the default base for numeric input. Supported choices |
| 12345 | for @var{base} are decimal 8, 10, or 16. @var{base} must itself be |
| 12346 | specified either unambiguously or using the current default radix; for |
| 12347 | example, any of |
| 12348 | |
| 12349 | @smallexample |
| 12350 | set radix 012 |
| 12351 | set radix 10. |
| 12352 | set radix 0xa |
| 12353 | @end smallexample |
| 12354 | |
| 12355 | @noindent |
| 12356 | sets the base to decimal. On the other hand, @samp{set radix 10} |
| 12357 | leaves the radix unchanged no matter what it was. |
| 12358 | |
| 12359 | @kindex set output-radix |
| 12360 | @item set output-radix @var{base} |
| 12361 | Set the default base for numeric display. Supported choices |
| 12362 | for @var{base} are decimal 8, 10, or 16. @var{base} must itself be |
| 12363 | specified either unambiguously or using the current default radix. |
| 12364 | |
| 12365 | @kindex show input-radix |
| 12366 | @item show input-radix |
| 12367 | Display the current default base for numeric input. |
| 12368 | |
| 12369 | @kindex show output-radix |
| 12370 | @item show output-radix |
| 12371 | Display the current default base for numeric display. |
| 12372 | @end table |
| 12373 | |
| 12374 | @node Messages/Warnings |
| 12375 | @section Optional warnings and messages |
| 12376 | |
| 12377 | By default, @value{GDBN} is silent about its inner workings. If you are |
| 12378 | running on a slow machine, you may want to use the @code{set verbose} |
| 12379 | command. This makes @value{GDBN} tell you when it does a lengthy |
| 12380 | internal operation, so you will not think it has crashed. |
| 12381 | |
| 12382 | Currently, the messages controlled by @code{set verbose} are those |
| 12383 | which announce that the symbol table for a source file is being read; |
| 12384 | see @code{symbol-file} in @ref{Files, ,Commands to specify files}. |
| 12385 | |
| 12386 | @table @code |
| 12387 | @kindex set verbose |
| 12388 | @item set verbose on |
| 12389 | Enables @value{GDBN} output of certain informational messages. |
| 12390 | |
| 12391 | @item set verbose off |
| 12392 | Disables @value{GDBN} output of certain informational messages. |
| 12393 | |
| 12394 | @kindex show verbose |
| 12395 | @item show verbose |
| 12396 | Displays whether @code{set verbose} is on or off. |
| 12397 | @end table |
| 12398 | |
| 12399 | By default, if @value{GDBN} encounters bugs in the symbol table of an |
| 12400 | object file, it is silent; but if you are debugging a compiler, you may |
| 12401 | find this information useful (@pxref{Symbol Errors, ,Errors reading |
| 12402 | symbol files}). |
| 12403 | |
| 12404 | @table @code |
| 12405 | |
| 12406 | @kindex set complaints |
| 12407 | @item set complaints @var{limit} |
| 12408 | Permits @value{GDBN} to output @var{limit} complaints about each type of |
| 12409 | unusual symbols before becoming silent about the problem. Set |
| 12410 | @var{limit} to zero to suppress all complaints; set it to a large number |
| 12411 | to prevent complaints from being suppressed. |
| 12412 | |
| 12413 | @kindex show complaints |
| 12414 | @item show complaints |
| 12415 | Displays how many symbol complaints @value{GDBN} is permitted to produce. |
| 12416 | |
| 12417 | @end table |
| 12418 | |
| 12419 | By default, @value{GDBN} is cautious, and asks what sometimes seems to be a |
| 12420 | lot of stupid questions to confirm certain commands. For example, if |
| 12421 | you try to run a program which is already running: |
| 12422 | |
| 12423 | @example |
| 12424 | (@value{GDBP}) run |
| 12425 | The program being debugged has been started already. |
| 12426 | Start it from the beginning? (y or n) |
| 12427 | @end example |
| 12428 | |
| 12429 | If you are willing to unflinchingly face the consequences of your own |
| 12430 | commands, you can disable this ``feature'': |
| 12431 | |
| 12432 | @table @code |
| 12433 | |
| 12434 | @kindex set confirm |
| 12435 | @cindex flinching |
| 12436 | @cindex confirmation |
| 12437 | @cindex stupid questions |
| 12438 | @item set confirm off |
| 12439 | Disables confirmation requests. |
| 12440 | |
| 12441 | @item set confirm on |
| 12442 | Enables confirmation requests (the default). |
| 12443 | |
| 12444 | @kindex show confirm |
| 12445 | @item show confirm |
| 12446 | Displays state of confirmation requests. |
| 12447 | |
| 12448 | @end table |
| 12449 | |
| 12450 | @node Debugging Output |
| 12451 | @section Optional messages about internal happenings |
| 12452 | @table @code |
| 12453 | @kindex set debug arch |
| 12454 | @item set debug arch |
| 12455 | Turns on or off display of gdbarch debugging info. The default is off |
| 12456 | @kindex show debug arch |
| 12457 | @item show debug arch |
| 12458 | Displays the current state of displaying gdbarch debugging info. |
| 12459 | @kindex set debug event |
| 12460 | @item set debug event |
| 12461 | Turns on or off display of @value{GDBN} event debugging info. The |
| 12462 | default is off. |
| 12463 | @kindex show debug event |
| 12464 | @item show debug event |
| 12465 | Displays the current state of displaying @value{GDBN} event debugging |
| 12466 | info. |
| 12467 | @kindex set debug expression |
| 12468 | @item set debug expression |
| 12469 | Turns on or off display of @value{GDBN} expression debugging info. The |
| 12470 | default is off. |
| 12471 | @kindex show debug expression |
| 12472 | @item show debug expression |
| 12473 | Displays the current state of displaying @value{GDBN} expression |
| 12474 | debugging info. |
| 12475 | @kindex set debug overload |
| 12476 | @item set debug overload |
| 12477 | Turns on or off display of @value{GDBN} C@t{++} overload debugging |
| 12478 | info. This includes info such as ranking of functions, etc. The default |
| 12479 | is off. |
| 12480 | @kindex show debug overload |
| 12481 | @item show debug overload |
| 12482 | Displays the current state of displaying @value{GDBN} C@t{++} overload |
| 12483 | debugging info. |
| 12484 | @kindex set debug remote |
| 12485 | @cindex packets, reporting on stdout |
| 12486 | @cindex serial connections, debugging |
| 12487 | @item set debug remote |
| 12488 | Turns on or off display of reports on all packets sent back and forth across |
| 12489 | the serial line to the remote machine. The info is printed on the |
| 12490 | @value{GDBN} standard output stream. The default is off. |
| 12491 | @kindex show debug remote |
| 12492 | @item show debug remote |
| 12493 | Displays the state of display of remote packets. |
| 12494 | @kindex set debug serial |
| 12495 | @item set debug serial |
| 12496 | Turns on or off display of @value{GDBN} serial debugging info. The |
| 12497 | default is off. |
| 12498 | @kindex show debug serial |
| 12499 | @item show debug serial |
| 12500 | Displays the current state of displaying @value{GDBN} serial debugging |
| 12501 | info. |
| 12502 | @kindex set debug target |
| 12503 | @item set debug target |
| 12504 | Turns on or off display of @value{GDBN} target debugging info. This info |
| 12505 | includes what is going on at the target level of GDB, as it happens. The |
| 12506 | default is off. |
| 12507 | @kindex show debug target |
| 12508 | @item show debug target |
| 12509 | Displays the current state of displaying @value{GDBN} target debugging |
| 12510 | info. |
| 12511 | @kindex set debug varobj |
| 12512 | @item set debug varobj |
| 12513 | Turns on or off display of @value{GDBN} variable object debugging |
| 12514 | info. The default is off. |
| 12515 | @kindex show debug varobj |
| 12516 | @item show debug varobj |
| 12517 | Displays the current state of displaying @value{GDBN} variable object |
| 12518 | debugging info. |
| 12519 | @end table |
| 12520 | |
| 12521 | @node Sequences |
| 12522 | @chapter Canned Sequences of Commands |
| 12523 | |
| 12524 | Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint |
| 12525 | command lists}), @value{GDBN} provides two ways to store sequences of |
| 12526 | commands for execution as a unit: user-defined commands and command |
| 12527 | files. |
| 12528 | |
| 12529 | @menu |
| 12530 | * Define:: User-defined commands |
| 12531 | * Hooks:: User-defined command hooks |
| 12532 | * Command Files:: Command files |
| 12533 | * Output:: Commands for controlled output |
| 12534 | @end menu |
| 12535 | |
| 12536 | @node Define |
| 12537 | @section User-defined commands |
| 12538 | |
| 12539 | @cindex user-defined command |
| 12540 | A @dfn{user-defined command} is a sequence of @value{GDBN} commands to |
| 12541 | which you assign a new name as a command. This is done with the |
| 12542 | @code{define} command. User commands may accept up to 10 arguments |
| 12543 | separated by whitespace. Arguments are accessed within the user command |
| 12544 | via @var{$arg0@dots{}$arg9}. A trivial example: |
| 12545 | |
| 12546 | @smallexample |
| 12547 | define adder |
| 12548 | print $arg0 + $arg1 + $arg2 |
| 12549 | @end smallexample |
| 12550 | |
| 12551 | @noindent |
| 12552 | To execute the command use: |
| 12553 | |
| 12554 | @smallexample |
| 12555 | adder 1 2 3 |
| 12556 | @end smallexample |
| 12557 | |
| 12558 | @noindent |
| 12559 | This defines the command @code{adder}, which prints the sum of |
| 12560 | its three arguments. Note the arguments are text substitutions, so they may |
| 12561 | reference variables, use complex expressions, or even perform inferior |
| 12562 | functions calls. |
| 12563 | |
| 12564 | @table @code |
| 12565 | |
| 12566 | @kindex define |
| 12567 | @item define @var{commandname} |
| 12568 | Define a command named @var{commandname}. If there is already a command |
| 12569 | by that name, you are asked to confirm that you want to redefine it. |
| 12570 | |
| 12571 | The definition of the command is made up of other @value{GDBN} command lines, |
| 12572 | which are given following the @code{define} command. The end of these |
| 12573 | commands is marked by a line containing @code{end}. |
| 12574 | |
| 12575 | @kindex if |
| 12576 | @kindex else |
| 12577 | @item if |
| 12578 | Takes a single argument, which is an expression to evaluate. |
| 12579 | It is followed by a series of commands that are executed |
| 12580 | only if the expression is true (nonzero). |
| 12581 | There can then optionally be a line @code{else}, followed |
| 12582 | by a series of commands that are only executed if the expression |
| 12583 | was false. The end of the list is marked by a line containing @code{end}. |
| 12584 | |
| 12585 | @kindex while |
| 12586 | @item while |
| 12587 | The syntax is similar to @code{if}: the command takes a single argument, |
| 12588 | which is an expression to evaluate, and must be followed by the commands to |
| 12589 | execute, one per line, terminated by an @code{end}. |
| 12590 | The commands are executed repeatedly as long as the expression |
| 12591 | evaluates to true. |
| 12592 | |
| 12593 | @kindex document |
| 12594 | @item document @var{commandname} |
| 12595 | Document the user-defined command @var{commandname}, so that it can be |
| 12596 | accessed by @code{help}. The command @var{commandname} must already be |
| 12597 | defined. This command reads lines of documentation just as @code{define} |
| 12598 | reads the lines of the command definition, ending with @code{end}. |
| 12599 | After the @code{document} command is finished, @code{help} on command |
| 12600 | @var{commandname} displays the documentation you have written. |
| 12601 | |
| 12602 | You may use the @code{document} command again to change the |
| 12603 | documentation of a command. Redefining the command with @code{define} |
| 12604 | does not change the documentation. |
| 12605 | |
| 12606 | @kindex help user-defined |
| 12607 | @item help user-defined |
| 12608 | List all user-defined commands, with the first line of the documentation |
| 12609 | (if any) for each. |
| 12610 | |
| 12611 | @kindex show user |
| 12612 | @item show user |
| 12613 | @itemx show user @var{commandname} |
| 12614 | Display the @value{GDBN} commands used to define @var{commandname} (but |
| 12615 | not its documentation). If no @var{commandname} is given, display the |
| 12616 | definitions for all user-defined commands. |
| 12617 | |
| 12618 | @end table |
| 12619 | |
| 12620 | When user-defined commands are executed, the |
| 12621 | commands of the definition are not printed. An error in any command |
| 12622 | stops execution of the user-defined command. |
| 12623 | |
| 12624 | If used interactively, commands that would ask for confirmation proceed |
| 12625 | without asking when used inside a user-defined command. Many @value{GDBN} |
| 12626 | commands that normally print messages to say what they are doing omit the |
| 12627 | messages when used in a user-defined command. |
| 12628 | |
| 12629 | @node Hooks |
| 12630 | @section User-defined command hooks |
| 12631 | @cindex command hooks |
| 12632 | @cindex hooks, for commands |
| 12633 | @cindex hooks, pre-command |
| 12634 | |
| 12635 | @kindex hook |
| 12636 | @kindex hook- |
| 12637 | You may define @dfn{hooks}, which are a special kind of user-defined |
| 12638 | command. Whenever you run the command @samp{foo}, if the user-defined |
| 12639 | command @samp{hook-foo} exists, it is executed (with no arguments) |
| 12640 | before that command. |
| 12641 | |
| 12642 | @cindex hooks, post-command |
| 12643 | @kindex hookpost |
| 12644 | @kindex hookpost- |
| 12645 | A hook may also be defined which is run after the command you executed. |
| 12646 | Whenever you run the command @samp{foo}, if the user-defined command |
| 12647 | @samp{hookpost-foo} exists, it is executed (with no arguments) after |
| 12648 | that command. Post-execution hooks may exist simultaneously with |
| 12649 | pre-execution hooks, for the same command. |
| 12650 | |
| 12651 | It is valid for a hook to call the command which it hooks. If this |
| 12652 | occurs, the hook is not re-executed, thereby avoiding infinte recursion. |
| 12653 | |
| 12654 | @c It would be nice if hookpost could be passed a parameter indicating |
| 12655 | @c if the command it hooks executed properly or not. FIXME! |
| 12656 | |
| 12657 | @kindex stop@r{, a pseudo-command} |
| 12658 | In addition, a pseudo-command, @samp{stop} exists. Defining |
| 12659 | (@samp{hook-stop}) makes the associated commands execute every time |
| 12660 | execution stops in your program: before breakpoint commands are run, |
| 12661 | displays are printed, or the stack frame is printed. |
| 12662 | |
| 12663 | For example, to ignore @code{SIGALRM} signals while |
| 12664 | single-stepping, but treat them normally during normal execution, |
| 12665 | you could define: |
| 12666 | |
| 12667 | @example |
| 12668 | define hook-stop |
| 12669 | handle SIGALRM nopass |
| 12670 | end |
| 12671 | |
| 12672 | define hook-run |
| 12673 | handle SIGALRM pass |
| 12674 | end |
| 12675 | |
| 12676 | define hook-continue |
| 12677 | handle SIGLARM pass |
| 12678 | end |
| 12679 | @end example |
| 12680 | |
| 12681 | As a further example, to hook at the begining and end of the @code{echo} |
| 12682 | command, and to add extra text to the beginning and end of the message, |
| 12683 | you could define: |
| 12684 | |
| 12685 | @example |
| 12686 | define hook-echo |
| 12687 | echo <<<--- |
| 12688 | end |
| 12689 | |
| 12690 | define hookpost-echo |
| 12691 | echo --->>>\n |
| 12692 | end |
| 12693 | |
| 12694 | (@value{GDBP}) echo Hello World |
| 12695 | <<<---Hello World--->>> |
| 12696 | (@value{GDBP}) |
| 12697 | |
| 12698 | @end example |
| 12699 | |
| 12700 | You can define a hook for any single-word command in @value{GDBN}, but |
| 12701 | not for command aliases; you should define a hook for the basic command |
| 12702 | name, e.g. @code{backtrace} rather than @code{bt}. |
| 12703 | @c FIXME! So how does Joe User discover whether a command is an alias |
| 12704 | @c or not? |
| 12705 | If an error occurs during the execution of your hook, execution of |
| 12706 | @value{GDBN} commands stops and @value{GDBN} issues a prompt |
| 12707 | (before the command that you actually typed had a chance to run). |
| 12708 | |
| 12709 | If you try to define a hook which does not match any known command, you |
| 12710 | get a warning from the @code{define} command. |
| 12711 | |
| 12712 | @node Command Files |
| 12713 | @section Command files |
| 12714 | |
| 12715 | @cindex command files |
| 12716 | A command file for @value{GDBN} is a file of lines that are @value{GDBN} |
| 12717 | commands. Comments (lines starting with @kbd{#}) may also be included. |
| 12718 | An empty line in a command file does nothing; it does not mean to repeat |
| 12719 | the last command, as it would from the terminal. |
| 12720 | |
| 12721 | @cindex init file |
| 12722 | @cindex @file{.gdbinit} |
| 12723 | @cindex @file{gdb.ini} |
| 12724 | When you start @value{GDBN}, it automatically executes commands from its |
| 12725 | @dfn{init files}, normally called @file{.gdbinit}@footnote{The DJGPP |
| 12726 | port of @value{GDBN} uses the name @file{gdb.ini} instead, due to the |
| 12727 | limitations of file names imposed by DOS filesystems.}. |
| 12728 | During startup, @value{GDBN} does the following: |
| 12729 | |
| 12730 | @enumerate |
| 12731 | @item |
| 12732 | Reads the init file (if any) in your home directory@footnote{On |
| 12733 | DOS/Windows systems, the home directory is the one pointed to by the |
| 12734 | @code{HOME} environment variable.}. |
| 12735 | |
| 12736 | @item |
| 12737 | Processes command line options and operands. |
| 12738 | |
| 12739 | @item |
| 12740 | Reads the init file (if any) in the current working directory. |
| 12741 | |
| 12742 | @item |
| 12743 | Reads command files specified by the @samp{-x} option. |
| 12744 | @end enumerate |
| 12745 | |
| 12746 | The init file in your home directory can set options (such as @samp{set |
| 12747 | complaints}) that affect subsequent processing of command line options |
| 12748 | and operands. Init files are not executed if you use the @samp{-nx} |
| 12749 | option (@pxref{Mode Options, ,Choosing modes}). |
| 12750 | |
| 12751 | @cindex init file name |
| 12752 | On some configurations of @value{GDBN}, the init file is known by a |
| 12753 | different name (these are typically environments where a specialized |
| 12754 | form of @value{GDBN} may need to coexist with other forms, hence a |
| 12755 | different name for the specialized version's init file). These are the |
| 12756 | environments with special init file names: |
| 12757 | |
| 12758 | @cindex @file{.vxgdbinit} |
| 12759 | @itemize @bullet |
| 12760 | @item |
| 12761 | VxWorks (Wind River Systems real-time OS): @file{.vxgdbinit} |
| 12762 | |
| 12763 | @cindex @file{.os68gdbinit} |
| 12764 | @item |
| 12765 | OS68K (Enea Data Systems real-time OS): @file{.os68gdbinit} |
| 12766 | |
| 12767 | @cindex @file{.esgdbinit} |
| 12768 | @item |
| 12769 | ES-1800 (Ericsson Telecom AB M68000 emulator): @file{.esgdbinit} |
| 12770 | @end itemize |
| 12771 | |
| 12772 | You can also request the execution of a command file with the |
| 12773 | @code{source} command: |
| 12774 | |
| 12775 | @table @code |
| 12776 | @kindex source |
| 12777 | @item source @var{filename} |
| 12778 | Execute the command file @var{filename}. |
| 12779 | @end table |
| 12780 | |
| 12781 | The lines in a command file are executed sequentially. They are not |
| 12782 | printed as they are executed. An error in any command terminates execution |
| 12783 | of the command file. |
| 12784 | |
| 12785 | Commands that would ask for confirmation if used interactively proceed |
| 12786 | without asking when used in a command file. Many @value{GDBN} commands that |
| 12787 | normally print messages to say what they are doing omit the messages |
| 12788 | when called from command files. |
| 12789 | |
| 12790 | @value{GDBN} also accepts command input from standard input. In this |
| 12791 | mode, normal output goes to standard output and error output goes to |
| 12792 | standard error. Errors in a command file supplied on standard input do |
| 12793 | not terminate execution of the command file --- execution continues with |
| 12794 | the next command. |
| 12795 | |
| 12796 | @example |
| 12797 | gdb < cmds > log 2>&1 |
| 12798 | @end example |
| 12799 | |
| 12800 | (The syntax above will vary depending on the shell used.) This example |
| 12801 | will execute commands from the file @file{cmds}. All output and errors |
| 12802 | would be directed to @file{log}. |
| 12803 | |
| 12804 | @node Output |
| 12805 | @section Commands for controlled output |
| 12806 | |
| 12807 | During the execution of a command file or a user-defined command, normal |
| 12808 | @value{GDBN} output is suppressed; the only output that appears is what is |
| 12809 | explicitly printed by the commands in the definition. This section |
| 12810 | describes three commands useful for generating exactly the output you |
| 12811 | want. |
| 12812 | |
| 12813 | @table @code |
| 12814 | @kindex echo |
| 12815 | @item echo @var{text} |
| 12816 | @c I do not consider backslash-space a standard C escape sequence |
| 12817 | @c because it is not in ANSI. |
| 12818 | Print @var{text}. Nonprinting characters can be included in |
| 12819 | @var{text} using C escape sequences, such as @samp{\n} to print a |
| 12820 | newline. @strong{No newline is printed unless you specify one.} |
| 12821 | In addition to the standard C escape sequences, a backslash followed |
| 12822 | by a space stands for a space. This is useful for displaying a |
| 12823 | string with spaces at the beginning or the end, since leading and |
| 12824 | trailing spaces are otherwise trimmed from all arguments. |
| 12825 | To print @samp{@w{ }and foo =@w{ }}, use the command |
| 12826 | @samp{echo \@w{ }and foo = \@w{ }}. |
| 12827 | |
| 12828 | A backslash at the end of @var{text} can be used, as in C, to continue |
| 12829 | the command onto subsequent lines. For example, |
| 12830 | |
| 12831 | @example |
| 12832 | echo This is some text\n\ |
| 12833 | which is continued\n\ |
| 12834 | onto several lines.\n |
| 12835 | @end example |
| 12836 | |
| 12837 | produces the same output as |
| 12838 | |
| 12839 | @example |
| 12840 | echo This is some text\n |
| 12841 | echo which is continued\n |
| 12842 | echo onto several lines.\n |
| 12843 | @end example |
| 12844 | |
| 12845 | @kindex output |
| 12846 | @item output @var{expression} |
| 12847 | Print the value of @var{expression} and nothing but that value: no |
| 12848 | newlines, no @samp{$@var{nn} = }. The value is not entered in the |
| 12849 | value history either. @xref{Expressions, ,Expressions}, for more information |
| 12850 | on expressions. |
| 12851 | |
| 12852 | @item output/@var{fmt} @var{expression} |
| 12853 | Print the value of @var{expression} in format @var{fmt}. You can use |
| 12854 | the same formats as for @code{print}. @xref{Output Formats,,Output |
| 12855 | formats}, for more information. |
| 12856 | |
| 12857 | @kindex printf |
| 12858 | @item printf @var{string}, @var{expressions}@dots{} |
| 12859 | Print the values of the @var{expressions} under the control of |
| 12860 | @var{string}. The @var{expressions} are separated by commas and may be |
| 12861 | either numbers or pointers. Their values are printed as specified by |
| 12862 | @var{string}, exactly as if your program were to execute the C |
| 12863 | subroutine |
| 12864 | @c FIXME: the above implies that at least all ANSI C formats are |
| 12865 | @c supported, but it isn't true: %E and %G don't work (or so it seems). |
| 12866 | @c Either this is a bug, or the manual should document what formats are |
| 12867 | @c supported. |
| 12868 | |
| 12869 | @example |
| 12870 | printf (@var{string}, @var{expressions}@dots{}); |
| 12871 | @end example |
| 12872 | |
| 12873 | For example, you can print two values in hex like this: |
| 12874 | |
| 12875 | @smallexample |
| 12876 | printf "foo, bar-foo = 0x%x, 0x%x\n", foo, bar-foo |
| 12877 | @end smallexample |
| 12878 | |
| 12879 | The only backslash-escape sequences that you can use in the format |
| 12880 | string are the simple ones that consist of backslash followed by a |
| 12881 | letter. |
| 12882 | @end table |
| 12883 | |
| 12884 | @node TUI |
| 12885 | @chapter @value{GDBN} Text User Interface |
| 12886 | @cindex TUI |
| 12887 | |
| 12888 | @menu |
| 12889 | * TUI Overview:: TUI overview |
| 12890 | * TUI Keys:: TUI key bindings |
| 12891 | * TUI Commands:: TUI specific commands |
| 12892 | * TUI Configuration:: TUI configuration variables |
| 12893 | @end menu |
| 12894 | |
| 12895 | The @value{GDBN} Text User Interface, TUI in short, |
| 12896 | is a terminal interface which uses the @code{curses} library |
| 12897 | to show the source file, the assembly output, the program registers |
| 12898 | and @value{GDBN} commands in separate text windows. |
| 12899 | The TUI is available only when @value{GDBN} is configured |
| 12900 | with the @code{--enable-tui} configure option (@pxref{Configure Options}). |
| 12901 | |
| 12902 | @node TUI Overview |
| 12903 | @section TUI overview |
| 12904 | |
| 12905 | The TUI has two display modes that can be switched while |
| 12906 | @value{GDBN} runs: |
| 12907 | |
| 12908 | @itemize @bullet |
| 12909 | @item |
| 12910 | A curses (or TUI) mode in which it displays several text |
| 12911 | windows on the terminal. |
| 12912 | |
| 12913 | @item |
| 12914 | A standard mode which corresponds to the @value{GDBN} configured without |
| 12915 | the TUI. |
| 12916 | @end itemize |
| 12917 | |
| 12918 | In the TUI mode, @value{GDBN} can display several text window |
| 12919 | on the terminal: |
| 12920 | |
| 12921 | @table @emph |
| 12922 | @item command |
| 12923 | This window is the @value{GDBN} command window with the @value{GDBN} |
| 12924 | prompt and the @value{GDBN} outputs. The @value{GDBN} input is still |
| 12925 | managed using readline but through the TUI. The @emph{command} |
| 12926 | window is always visible. |
| 12927 | |
| 12928 | @item source |
| 12929 | The source window shows the source file of the program. The current |
| 12930 | line as well as active breakpoints are displayed in this window. |
| 12931 | The current program position is shown with the @samp{>} marker and |
| 12932 | active breakpoints are shown with @samp{*} markers. |
| 12933 | |
| 12934 | @item assembly |
| 12935 | The assembly window shows the disassembly output of the program. |
| 12936 | |
| 12937 | @item register |
| 12938 | This window shows the processor registers. It detects when |
| 12939 | a register is changed and when this is the case, registers that have |
| 12940 | changed are highlighted. |
| 12941 | |
| 12942 | @end table |
| 12943 | |
| 12944 | The source, assembly and register windows are attached to the thread |
| 12945 | and the frame position. They are updated when the current thread |
| 12946 | changes, when the frame changes or when the program counter changes. |
| 12947 | These three windows are arranged by the TUI according to several |
| 12948 | layouts. The layout defines which of these three windows are visible. |
| 12949 | The following layouts are available: |
| 12950 | |
| 12951 | @itemize @bullet |
| 12952 | @item |
| 12953 | source |
| 12954 | |
| 12955 | @item |
| 12956 | assembly |
| 12957 | |
| 12958 | @item |
| 12959 | source and assembly |
| 12960 | |
| 12961 | @item |
| 12962 | source and registers |
| 12963 | |
| 12964 | @item |
| 12965 | assembly and registers |
| 12966 | |
| 12967 | @end itemize |
| 12968 | |
| 12969 | @node TUI Keys |
| 12970 | @section TUI Key Bindings |
| 12971 | @cindex TUI key bindings |
| 12972 | |
| 12973 | The TUI installs several key bindings in the readline keymaps |
| 12974 | (@pxref{Command Line Editing}). |
| 12975 | They allow to leave or enter in the TUI mode or they operate |
| 12976 | directly on the TUI layout and windows. The following key bindings |
| 12977 | are installed for both TUI mode and the @value{GDBN} standard mode. |
| 12978 | |
| 12979 | @table @kbd |
| 12980 | @kindex C-x C-a |
| 12981 | @item C-x C-a |
| 12982 | @kindex C-x a |
| 12983 | @itemx C-x a |
| 12984 | @kindex C-x A |
| 12985 | @itemx C-x A |
| 12986 | Enter or leave the TUI mode. When the TUI mode is left, |
| 12987 | the curses window management is left and @value{GDBN} operates using |
| 12988 | its standard mode writing on the terminal directly. When the TUI |
| 12989 | mode is entered, the control is given back to the curses windows. |
| 12990 | The screen is then refreshed. |
| 12991 | |
| 12992 | @kindex C-x 1 |
| 12993 | @item C-x 1 |
| 12994 | Use a TUI layout with only one window. The layout will |
| 12995 | either be @samp{source} or @samp{assembly}. When the TUI mode |
| 12996 | is not active, it will switch to the TUI mode. |
| 12997 | |
| 12998 | Think of this key binding as the Emacs @kbd{C-x 1} binding. |
| 12999 | |
| 13000 | @kindex C-x 2 |
| 13001 | @item C-x 2 |
| 13002 | Use a TUI layout with at least two windows. When the current |
| 13003 | layout shows already two windows, a next layout with two windows is used. |
| 13004 | When a new layout is chosen, one window will always be common to the |
| 13005 | previous layout and the new one. |
| 13006 | |
| 13007 | Think of it as the Emacs @kbd{C-x 2} binding. |
| 13008 | |
| 13009 | @end table |
| 13010 | |
| 13011 | The following key bindings are handled only by the TUI mode: |
| 13012 | |
| 13013 | @table @key |
| 13014 | @kindex PgUp |
| 13015 | @item PgUp |
| 13016 | Scroll the active window one page up. |
| 13017 | |
| 13018 | @kindex PgDn |
| 13019 | @item PgDn |
| 13020 | Scroll the active window one page down. |
| 13021 | |
| 13022 | @kindex Up |
| 13023 | @item Up |
| 13024 | Scroll the active window one line up. |
| 13025 | |
| 13026 | @kindex Down |
| 13027 | @item Down |
| 13028 | Scroll the active window one line down. |
| 13029 | |
| 13030 | @kindex Left |
| 13031 | @item Left |
| 13032 | Scroll the active window one column left. |
| 13033 | |
| 13034 | @kindex Right |
| 13035 | @item Right |
| 13036 | Scroll the active window one column right. |
| 13037 | |
| 13038 | @kindex C-L |
| 13039 | @item C-L |
| 13040 | Refresh the screen. |
| 13041 | |
| 13042 | @end table |
| 13043 | |
| 13044 | In the TUI mode, the arrow keys are used by the active window |
| 13045 | for scrolling. This means they are not available for readline. It is |
| 13046 | necessary to use other readline key bindings such as @key{C-p}, @key{C-n}, |
| 13047 | @key{C-b} and @key{C-f}. |
| 13048 | |
| 13049 | @node TUI Commands |
| 13050 | @section TUI specific commands |
| 13051 | @cindex TUI commands |
| 13052 | |
| 13053 | The TUI has specific commands to control the text windows. |
| 13054 | These commands are always available, that is they do not depend on |
| 13055 | the current terminal mode in which @value{GDBN} runs. When @value{GDBN} |
| 13056 | is in the standard mode, using these commands will automatically switch |
| 13057 | in the TUI mode. |
| 13058 | |
| 13059 | @table @code |
| 13060 | @item layout next |
| 13061 | @kindex layout next |
| 13062 | Display the next layout. |
| 13063 | |
| 13064 | @item layout prev |
| 13065 | @kindex layout prev |
| 13066 | Display the previous layout. |
| 13067 | |
| 13068 | @item layout src |
| 13069 | @kindex layout src |
| 13070 | Display the source window only. |
| 13071 | |
| 13072 | @item layout asm |
| 13073 | @kindex layout asm |
| 13074 | Display the assembly window only. |
| 13075 | |
| 13076 | @item layout split |
| 13077 | @kindex layout split |
| 13078 | Display the source and assembly window. |
| 13079 | |
| 13080 | @item layout regs |
| 13081 | @kindex layout regs |
| 13082 | Display the register window together with the source or assembly window. |
| 13083 | |
| 13084 | @item focus next | prev | src | asm | regs | split |
| 13085 | @kindex focus |
| 13086 | Set the focus to the named window. |
| 13087 | This command allows to change the active window so that scrolling keys |
| 13088 | can be affected to another window. |
| 13089 | |
| 13090 | @item refresh |
| 13091 | @kindex refresh |
| 13092 | Refresh the screen. This is similar to using @key{C-L} key. |
| 13093 | |
| 13094 | @item update |
| 13095 | @kindex update |
| 13096 | Update the source window and the current execution point. |
| 13097 | |
| 13098 | @item winheight @var{name} +@var{count} |
| 13099 | @itemx winheight @var{name} -@var{count} |
| 13100 | @kindex winheight |
| 13101 | Change the height of the window @var{name} by @var{count} |
| 13102 | lines. Positive counts increase the height, while negative counts |
| 13103 | decrease it. |
| 13104 | |
| 13105 | @end table |
| 13106 | |
| 13107 | @node TUI Configuration |
| 13108 | @section TUI configuration variables |
| 13109 | @cindex TUI configuration variables |
| 13110 | |
| 13111 | The TUI has several configuration variables that control the |
| 13112 | appearance of windows on the terminal. |
| 13113 | |
| 13114 | @table @code |
| 13115 | @item set tui border-kind @var{kind} |
| 13116 | @kindex set tui border-kind |
| 13117 | Select the border appearance for the source, assembly and register windows. |
| 13118 | The possible values are the following: |
| 13119 | @table @code |
| 13120 | @item space |
| 13121 | Use a space character to draw the border. |
| 13122 | |
| 13123 | @item ascii |
| 13124 | Use ascii characters + - and | to draw the border. |
| 13125 | |
| 13126 | @item acs |
| 13127 | Use the Alternate Character Set to draw the border. The border is |
| 13128 | drawn using character line graphics if the terminal supports them. |
| 13129 | |
| 13130 | @end table |
| 13131 | |
| 13132 | @item set tui active-border-mode @var{mode} |
| 13133 | @kindex set tui active-border-mode |
| 13134 | Select the attributes to display the border of the active window. |
| 13135 | The possible values are @code{normal}, @code{standout}, @code{reverse}, |
| 13136 | @code{half}, @code{half-standout}, @code{bold} and @code{bold-standout}. |
| 13137 | |
| 13138 | @item set tui border-mode @var{mode} |
| 13139 | @kindex set tui border-mode |
| 13140 | Select the attributes to display the border of other windows. |
| 13141 | The @var{mode} can be one of the following: |
| 13142 | @table @code |
| 13143 | @item normal |
| 13144 | Use normal attributes to display the border. |
| 13145 | |
| 13146 | @item standout |
| 13147 | Use standout mode. |
| 13148 | |
| 13149 | @item reverse |
| 13150 | Use reverse video mode. |
| 13151 | |
| 13152 | @item half |
| 13153 | Use half bright mode. |
| 13154 | |
| 13155 | @item half-standout |
| 13156 | Use half bright and standout mode. |
| 13157 | |
| 13158 | @item bold |
| 13159 | Use extra bright or bold mode. |
| 13160 | |
| 13161 | @item bold-standout |
| 13162 | Use extra bright or bold and standout mode. |
| 13163 | |
| 13164 | @end table |
| 13165 | |
| 13166 | @end table |
| 13167 | |
| 13168 | @node Emacs |
| 13169 | @chapter Using @value{GDBN} under @sc{gnu} Emacs |
| 13170 | |
| 13171 | @cindex Emacs |
| 13172 | @cindex @sc{gnu} Emacs |
| 13173 | A special interface allows you to use @sc{gnu} Emacs to view (and |
| 13174 | edit) the source files for the program you are debugging with |
| 13175 | @value{GDBN}. |
| 13176 | |
| 13177 | To use this interface, use the command @kbd{M-x gdb} in Emacs. Give the |
| 13178 | executable file you want to debug as an argument. This command starts |
| 13179 | @value{GDBN} as a subprocess of Emacs, with input and output through a newly |
| 13180 | created Emacs buffer. |
| 13181 | @c (Do not use the @code{-tui} option to run @value{GDBN} from Emacs.) |
| 13182 | |
| 13183 | Using @value{GDBN} under Emacs is just like using @value{GDBN} normally except for two |
| 13184 | things: |
| 13185 | |
| 13186 | @itemize @bullet |
| 13187 | @item |
| 13188 | All ``terminal'' input and output goes through the Emacs buffer. |
| 13189 | @end itemize |
| 13190 | |
| 13191 | This applies both to @value{GDBN} commands and their output, and to the input |
| 13192 | and output done by the program you are debugging. |
| 13193 | |
| 13194 | This is useful because it means that you can copy the text of previous |
| 13195 | commands and input them again; you can even use parts of the output |
| 13196 | in this way. |
| 13197 | |
| 13198 | All the facilities of Emacs' Shell mode are available for interacting |
| 13199 | with your program. In particular, you can send signals the usual |
| 13200 | way---for example, @kbd{C-c C-c} for an interrupt, @kbd{C-c C-z} for a |
| 13201 | stop. |
| 13202 | |
| 13203 | @itemize @bullet |
| 13204 | @item |
| 13205 | @value{GDBN} displays source code through Emacs. |
| 13206 | @end itemize |
| 13207 | |
| 13208 | Each time @value{GDBN} displays a stack frame, Emacs automatically finds the |
| 13209 | source file for that frame and puts an arrow (@samp{=>}) at the |
| 13210 | left margin of the current line. Emacs uses a separate buffer for |
| 13211 | source display, and splits the screen to show both your @value{GDBN} session |
| 13212 | and the source. |
| 13213 | |
| 13214 | Explicit @value{GDBN} @code{list} or search commands still produce output as |
| 13215 | usual, but you probably have no reason to use them from Emacs. |
| 13216 | |
| 13217 | @quotation |
| 13218 | @emph{Warning:} If the directory where your program resides is not your |
| 13219 | current directory, it can be easy to confuse Emacs about the location of |
| 13220 | the source files, in which case the auxiliary display buffer does not |
| 13221 | appear to show your source. @value{GDBN} can find programs by searching your |
| 13222 | environment's @code{PATH} variable, so the @value{GDBN} input and output |
| 13223 | session proceeds normally; but Emacs does not get enough information |
| 13224 | back from @value{GDBN} to locate the source files in this situation. To |
| 13225 | avoid this problem, either start @value{GDBN} mode from the directory where |
| 13226 | your program resides, or specify an absolute file name when prompted for the |
| 13227 | @kbd{M-x gdb} argument. |
| 13228 | |
| 13229 | A similar confusion can result if you use the @value{GDBN} @code{file} command to |
| 13230 | switch to debugging a program in some other location, from an existing |
| 13231 | @value{GDBN} buffer in Emacs. |
| 13232 | @end quotation |
| 13233 | |
| 13234 | By default, @kbd{M-x gdb} calls the program called @file{gdb}. If |
| 13235 | you need to call @value{GDBN} by a different name (for example, if you keep |
| 13236 | several configurations around, with different names) you can set the |
| 13237 | Emacs variable @code{gdb-command-name}; for example, |
| 13238 | |
| 13239 | @example |
| 13240 | (setq gdb-command-name "mygdb") |
| 13241 | @end example |
| 13242 | |
| 13243 | @noindent |
| 13244 | (preceded by @kbd{M-:} or @kbd{ESC :}, or typed in the @code{*scratch*} buffer, or |
| 13245 | in your @file{.emacs} file) makes Emacs call the program named |
| 13246 | ``@code{mygdb}'' instead. |
| 13247 | |
| 13248 | In the @value{GDBN} I/O buffer, you can use these special Emacs commands in |
| 13249 | addition to the standard Shell mode commands: |
| 13250 | |
| 13251 | @table @kbd |
| 13252 | @item C-h m |
| 13253 | Describe the features of Emacs' @value{GDBN} Mode. |
| 13254 | |
| 13255 | @item M-s |
| 13256 | Execute to another source line, like the @value{GDBN} @code{step} command; also |
| 13257 | update the display window to show the current file and location. |
| 13258 | |
| 13259 | @item M-n |
| 13260 | Execute to next source line in this function, skipping all function |
| 13261 | calls, like the @value{GDBN} @code{next} command. Then update the display window |
| 13262 | to show the current file and location. |
| 13263 | |
| 13264 | @item M-i |
| 13265 | Execute one instruction, like the @value{GDBN} @code{stepi} command; update |
| 13266 | display window accordingly. |
| 13267 | |
| 13268 | @item M-x gdb-nexti |
| 13269 | Execute to next instruction, using the @value{GDBN} @code{nexti} command; update |
| 13270 | display window accordingly. |
| 13271 | |
| 13272 | @item C-c C-f |
| 13273 | Execute until exit from the selected stack frame, like the @value{GDBN} |
| 13274 | @code{finish} command. |
| 13275 | |
| 13276 | @item M-c |
| 13277 | Continue execution of your program, like the @value{GDBN} @code{continue} |
| 13278 | command. |
| 13279 | |
| 13280 | @emph{Warning:} In Emacs v19, this command is @kbd{C-c C-p}. |
| 13281 | |
| 13282 | @item M-u |
| 13283 | Go up the number of frames indicated by the numeric argument |
| 13284 | (@pxref{Arguments, , Numeric Arguments, Emacs, The @sc{gnu} Emacs Manual}), |
| 13285 | like the @value{GDBN} @code{up} command. |
| 13286 | |
| 13287 | @emph{Warning:} In Emacs v19, this command is @kbd{C-c C-u}. |
| 13288 | |
| 13289 | @item M-d |
| 13290 | Go down the number of frames indicated by the numeric argument, like the |
| 13291 | @value{GDBN} @code{down} command. |
| 13292 | |
| 13293 | @emph{Warning:} In Emacs v19, this command is @kbd{C-c C-d}. |
| 13294 | |
| 13295 | @item C-x & |
| 13296 | Read the number where the cursor is positioned, and insert it at the end |
| 13297 | of the @value{GDBN} I/O buffer. For example, if you wish to disassemble code |
| 13298 | around an address that was displayed earlier, type @kbd{disassemble}; |
| 13299 | then move the cursor to the address display, and pick up the |
| 13300 | argument for @code{disassemble} by typing @kbd{C-x &}. |
| 13301 | |
| 13302 | You can customize this further by defining elements of the list |
| 13303 | @code{gdb-print-command}; once it is defined, you can format or |
| 13304 | otherwise process numbers picked up by @kbd{C-x &} before they are |
| 13305 | inserted. A numeric argument to @kbd{C-x &} indicates that you |
| 13306 | wish special formatting, and also acts as an index to pick an element of the |
| 13307 | list. If the list element is a string, the number to be inserted is |
| 13308 | formatted using the Emacs function @code{format}; otherwise the number |
| 13309 | is passed as an argument to the corresponding list element. |
| 13310 | @end table |
| 13311 | |
| 13312 | In any source file, the Emacs command @kbd{C-x SPC} (@code{gdb-break}) |
| 13313 | tells @value{GDBN} to set a breakpoint on the source line point is on. |
| 13314 | |
| 13315 | If you accidentally delete the source-display buffer, an easy way to get |
| 13316 | it back is to type the command @code{f} in the @value{GDBN} buffer, to |
| 13317 | request a frame display; when you run under Emacs, this recreates |
| 13318 | the source buffer if necessary to show you the context of the current |
| 13319 | frame. |
| 13320 | |
| 13321 | The source files displayed in Emacs are in ordinary Emacs buffers |
| 13322 | which are visiting the source files in the usual way. You can edit |
| 13323 | the files with these buffers if you wish; but keep in mind that @value{GDBN} |
| 13324 | communicates with Emacs in terms of line numbers. If you add or |
| 13325 | delete lines from the text, the line numbers that @value{GDBN} knows cease |
| 13326 | to correspond properly with the code. |
| 13327 | |
| 13328 | @c The following dropped because Epoch is nonstandard. Reactivate |
| 13329 | @c if/when v19 does something similar. ---doc@cygnus.com 19dec1990 |
| 13330 | @ignore |
| 13331 | @kindex Emacs Epoch environment |
| 13332 | @kindex Epoch |
| 13333 | @kindex inspect |
| 13334 | |
| 13335 | Version 18 of @sc{gnu} Emacs has a built-in window system |
| 13336 | called the @code{epoch} |
| 13337 | environment. Users of this environment can use a new command, |
| 13338 | @code{inspect} which performs identically to @code{print} except that |
| 13339 | each value is printed in its own window. |
| 13340 | @end ignore |
| 13341 | |
| 13342 | @include annotate.texi |
| 13343 | @include gdbmi.texinfo |
| 13344 | |
| 13345 | @node GDB Bugs |
| 13346 | @chapter Reporting Bugs in @value{GDBN} |
| 13347 | @cindex bugs in @value{GDBN} |
| 13348 | @cindex reporting bugs in @value{GDBN} |
| 13349 | |
| 13350 | Your bug reports play an essential role in making @value{GDBN} reliable. |
| 13351 | |
| 13352 | Reporting a bug may help you by bringing a solution to your problem, or it |
| 13353 | may not. But in any case the principal function of a bug report is to help |
| 13354 | the entire community by making the next version of @value{GDBN} work better. Bug |
| 13355 | reports are your contribution to the maintenance of @value{GDBN}. |
| 13356 | |
| 13357 | In order for a bug report to serve its purpose, you must include the |
| 13358 | information that enables us to fix the bug. |
| 13359 | |
| 13360 | @menu |
| 13361 | * Bug Criteria:: Have you found a bug? |
| 13362 | * Bug Reporting:: How to report bugs |
| 13363 | @end menu |
| 13364 | |
| 13365 | @node Bug Criteria |
| 13366 | @section Have you found a bug? |
| 13367 | @cindex bug criteria |
| 13368 | |
| 13369 | If you are not sure whether you have found a bug, here are some guidelines: |
| 13370 | |
| 13371 | @itemize @bullet |
| 13372 | @cindex fatal signal |
| 13373 | @cindex debugger crash |
| 13374 | @cindex crash of debugger |
| 13375 | @item |
| 13376 | If the debugger gets a fatal signal, for any input whatever, that is a |
| 13377 | @value{GDBN} bug. Reliable debuggers never crash. |
| 13378 | |
| 13379 | @cindex error on valid input |
| 13380 | @item |
| 13381 | If @value{GDBN} produces an error message for valid input, that is a |
| 13382 | bug. (Note that if you're cross debugging, the problem may also be |
| 13383 | somewhere in the connection to the target.) |
| 13384 | |
| 13385 | @cindex invalid input |
| 13386 | @item |
| 13387 | If @value{GDBN} does not produce an error message for invalid input, |
| 13388 | that is a bug. However, you should note that your idea of |
| 13389 | ``invalid input'' might be our idea of ``an extension'' or ``support |
| 13390 | for traditional practice''. |
| 13391 | |
| 13392 | @item |
| 13393 | If you are an experienced user of debugging tools, your suggestions |
| 13394 | for improvement of @value{GDBN} are welcome in any case. |
| 13395 | @end itemize |
| 13396 | |
| 13397 | @node Bug Reporting |
| 13398 | @section How to report bugs |
| 13399 | @cindex bug reports |
| 13400 | @cindex @value{GDBN} bugs, reporting |
| 13401 | |
| 13402 | A number of companies and individuals offer support for @sc{gnu} products. |
| 13403 | If you obtained @value{GDBN} from a support organization, we recommend you |
| 13404 | contact that organization first. |
| 13405 | |
| 13406 | You can find contact information for many support companies and |
| 13407 | individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs |
| 13408 | distribution. |
| 13409 | @c should add a web page ref... |
| 13410 | |
| 13411 | In any event, we also recommend that you send bug reports for |
| 13412 | @value{GDBN} to this addresses: |
| 13413 | |
| 13414 | @example |
| 13415 | bug-gdb@@gnu.org |
| 13416 | @end example |
| 13417 | |
| 13418 | @strong{Do not send bug reports to @samp{info-gdb}, or to |
| 13419 | @samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do |
| 13420 | not want to receive bug reports. Those that do have arranged to receive |
| 13421 | @samp{bug-gdb}. |
| 13422 | |
| 13423 | The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which |
| 13424 | serves as a repeater. The mailing list and the newsgroup carry exactly |
| 13425 | the same messages. Often people think of posting bug reports to the |
| 13426 | newsgroup instead of mailing them. This appears to work, but it has one |
| 13427 | problem which can be crucial: a newsgroup posting often lacks a mail |
| 13428 | path back to the sender. Thus, if we need to ask for more information, |
| 13429 | we may be unable to reach you. For this reason, it is better to send |
| 13430 | bug reports to the mailing list. |
| 13431 | |
| 13432 | As a last resort, send bug reports on paper to: |
| 13433 | |
| 13434 | @example |
| 13435 | @sc{gnu} Debugger Bugs |
| 13436 | Free Software Foundation Inc. |
| 13437 | 59 Temple Place - Suite 330 |
| 13438 | Boston, MA 02111-1307 |
| 13439 | USA |
| 13440 | @end example |
| 13441 | |
| 13442 | The fundamental principle of reporting bugs usefully is this: |
| 13443 | @strong{report all the facts}. If you are not sure whether to state a |
| 13444 | fact or leave it out, state it! |
| 13445 | |
| 13446 | Often people omit facts because they think they know what causes the |
| 13447 | problem and assume that some details do not matter. Thus, you might |
| 13448 | assume that the name of the variable you use in an example does not matter. |
| 13449 | Well, probably it does not, but one cannot be sure. Perhaps the bug is a |
| 13450 | stray memory reference which happens to fetch from the location where that |
| 13451 | name is stored in memory; perhaps, if the name were different, the contents |
| 13452 | of that location would fool the debugger into doing the right thing despite |
| 13453 | the bug. Play it safe and give a specific, complete example. That is the |
| 13454 | easiest thing for you to do, and the most helpful. |
| 13455 | |
| 13456 | Keep in mind that the purpose of a bug report is to enable us to fix the |
| 13457 | bug. It may be that the bug has been reported previously, but neither |
| 13458 | you nor we can know that unless your bug report is complete and |
| 13459 | self-contained. |
| 13460 | |
| 13461 | Sometimes people give a few sketchy facts and ask, ``Does this ring a |
| 13462 | bell?'' Those bug reports are useless, and we urge everyone to |
| 13463 | @emph{refuse to respond to them} except to chide the sender to report |
| 13464 | bugs properly. |
| 13465 | |
| 13466 | To enable us to fix the bug, you should include all these things: |
| 13467 | |
| 13468 | @itemize @bullet |
| 13469 | @item |
| 13470 | The version of @value{GDBN}. @value{GDBN} announces it if you start |
| 13471 | with no arguments; you can also print it at any time using @code{show |
| 13472 | version}. |
| 13473 | |
| 13474 | Without this, we will not know whether there is any point in looking for |
| 13475 | the bug in the current version of @value{GDBN}. |
| 13476 | |
| 13477 | @item |
| 13478 | The type of machine you are using, and the operating system name and |
| 13479 | version number. |
| 13480 | |
| 13481 | @item |
| 13482 | What compiler (and its version) was used to compile @value{GDBN}---e.g. |
| 13483 | ``@value{GCC}--2.8.1''. |
| 13484 | |
| 13485 | @item |
| 13486 | What compiler (and its version) was used to compile the program you are |
| 13487 | debugging---e.g. ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP |
| 13488 | C Compiler''. For GCC, you can say @code{gcc --version} to get this |
| 13489 | information; for other compilers, see the documentation for those |
| 13490 | compilers. |
| 13491 | |
| 13492 | @item |
| 13493 | The command arguments you gave the compiler to compile your example and |
| 13494 | observe the bug. For example, did you use @samp{-O}? To guarantee |
| 13495 | you will not omit something important, list them all. A copy of the |
| 13496 | Makefile (or the output from make) is sufficient. |
| 13497 | |
| 13498 | If we were to try to guess the arguments, we would probably guess wrong |
| 13499 | and then we might not encounter the bug. |
| 13500 | |
| 13501 | @item |
| 13502 | A complete input script, and all necessary source files, that will |
| 13503 | reproduce the bug. |
| 13504 | |
| 13505 | @item |
| 13506 | A description of what behavior you observe that you believe is |
| 13507 | incorrect. For example, ``It gets a fatal signal.'' |
| 13508 | |
| 13509 | Of course, if the bug is that @value{GDBN} gets a fatal signal, then we |
| 13510 | will certainly notice it. But if the bug is incorrect output, we might |
| 13511 | not notice unless it is glaringly wrong. You might as well not give us |
| 13512 | a chance to make a mistake. |
| 13513 | |
| 13514 | Even if the problem you experience is a fatal signal, you should still |
| 13515 | say so explicitly. Suppose something strange is going on, such as, your |
| 13516 | copy of @value{GDBN} is out of synch, or you have encountered a bug in |
| 13517 | the C library on your system. (This has happened!) Your copy might |
| 13518 | crash and ours would not. If you told us to expect a crash, then when |
| 13519 | ours fails to crash, we would know that the bug was not happening for |
| 13520 | us. If you had not told us to expect a crash, then we would not be able |
| 13521 | to draw any conclusion from our observations. |
| 13522 | |
| 13523 | @item |
| 13524 | If you wish to suggest changes to the @value{GDBN} source, send us context |
| 13525 | diffs. If you even discuss something in the @value{GDBN} source, refer to |
| 13526 | it by context, not by line number. |
| 13527 | |
| 13528 | The line numbers in our development sources will not match those in your |
| 13529 | sources. Your line numbers would convey no useful information to us. |
| 13530 | |
| 13531 | @end itemize |
| 13532 | |
| 13533 | Here are some things that are not necessary: |
| 13534 | |
| 13535 | @itemize @bullet |
| 13536 | @item |
| 13537 | A description of the envelope of the bug. |
| 13538 | |
| 13539 | Often people who encounter a bug spend a lot of time investigating |
| 13540 | which changes to the input file will make the bug go away and which |
| 13541 | changes will not affect it. |
| 13542 | |
| 13543 | This is often time consuming and not very useful, because the way we |
| 13544 | will find the bug is by running a single example under the debugger |
| 13545 | with breakpoints, not by pure deduction from a series of examples. |
| 13546 | We recommend that you save your time for something else. |
| 13547 | |
| 13548 | Of course, if you can find a simpler example to report @emph{instead} |
| 13549 | of the original one, that is a convenience for us. Errors in the |
| 13550 | output will be easier to spot, running under the debugger will take |
| 13551 | less time, and so on. |
| 13552 | |
| 13553 | However, simplification is not vital; if you do not want to do this, |
| 13554 | report the bug anyway and send us the entire test case you used. |
| 13555 | |
| 13556 | @item |
| 13557 | A patch for the bug. |
| 13558 | |
| 13559 | A patch for the bug does help us if it is a good one. But do not omit |
| 13560 | the necessary information, such as the test case, on the assumption that |
| 13561 | a patch is all we need. We might see problems with your patch and decide |
| 13562 | to fix the problem another way, or we might not understand it at all. |
| 13563 | |
| 13564 | Sometimes with a program as complicated as @value{GDBN} it is very hard to |
| 13565 | construct an example that will make the program follow a certain path |
| 13566 | through the code. If you do not send us the example, we will not be able |
| 13567 | to construct one, so we will not be able to verify that the bug is fixed. |
| 13568 | |
| 13569 | And if we cannot understand what bug you are trying to fix, or why your |
| 13570 | patch should be an improvement, we will not install it. A test case will |
| 13571 | help us to understand. |
| 13572 | |
| 13573 | @item |
| 13574 | A guess about what the bug is or what it depends on. |
| 13575 | |
| 13576 | Such guesses are usually wrong. Even we cannot guess right about such |
| 13577 | things without first using the debugger to find the facts. |
| 13578 | @end itemize |
| 13579 | |
| 13580 | @c The readline documentation is distributed with the readline code |
| 13581 | @c and consists of the two following files: |
| 13582 | @c rluser.texinfo |
| 13583 | @c inc-hist.texinfo |
| 13584 | @c Use -I with makeinfo to point to the appropriate directory, |
| 13585 | @c environment var TEXINPUTS with TeX. |
| 13586 | @include rluser.texinfo |
| 13587 | @include inc-hist.texinfo |
| 13588 | |
| 13589 | |
| 13590 | @node Formatting Documentation |
| 13591 | @appendix Formatting Documentation |
| 13592 | |
| 13593 | @cindex @value{GDBN} reference card |
| 13594 | @cindex reference card |
| 13595 | The @value{GDBN} 4 release includes an already-formatted reference card, ready |
| 13596 | for printing with PostScript or Ghostscript, in the @file{gdb} |
| 13597 | subdirectory of the main source directory@footnote{In |
| 13598 | @file{gdb-@value{GDBVN}/gdb/refcard.ps} of the version @value{GDBVN} |
| 13599 | release.}. If you can use PostScript or Ghostscript with your printer, |
| 13600 | you can print the reference card immediately with @file{refcard.ps}. |
| 13601 | |
| 13602 | The release also includes the source for the reference card. You |
| 13603 | can format it, using @TeX{}, by typing: |
| 13604 | |
| 13605 | @example |
| 13606 | make refcard.dvi |
| 13607 | @end example |
| 13608 | |
| 13609 | The @value{GDBN} reference card is designed to print in @dfn{landscape} |
| 13610 | mode on US ``letter'' size paper; |
| 13611 | that is, on a sheet 11 inches wide by 8.5 inches |
| 13612 | high. You will need to specify this form of printing as an option to |
| 13613 | your @sc{dvi} output program. |
| 13614 | |
| 13615 | @cindex documentation |
| 13616 | |
| 13617 | All the documentation for @value{GDBN} comes as part of the machine-readable |
| 13618 | distribution. The documentation is written in Texinfo format, which is |
| 13619 | a documentation system that uses a single source file to produce both |
| 13620 | on-line information and a printed manual. You can use one of the Info |
| 13621 | formatting commands to create the on-line version of the documentation |
| 13622 | and @TeX{} (or @code{texi2roff}) to typeset the printed version. |
| 13623 | |
| 13624 | @value{GDBN} includes an already formatted copy of the on-line Info |
| 13625 | version of this manual in the @file{gdb} subdirectory. The main Info |
| 13626 | file is @file{gdb-@value{GDBVN}/gdb/gdb.info}, and it refers to |
| 13627 | subordinate files matching @samp{gdb.info*} in the same directory. If |
| 13628 | necessary, you can print out these files, or read them with any editor; |
| 13629 | but they are easier to read using the @code{info} subsystem in @sc{gnu} |
| 13630 | Emacs or the standalone @code{info} program, available as part of the |
| 13631 | @sc{gnu} Texinfo distribution. |
| 13632 | |
| 13633 | If you want to format these Info files yourself, you need one of the |
| 13634 | Info formatting programs, such as @code{texinfo-format-buffer} or |
| 13635 | @code{makeinfo}. |
| 13636 | |
| 13637 | If you have @code{makeinfo} installed, and are in the top level |
| 13638 | @value{GDBN} source directory (@file{gdb-@value{GDBVN}}, in the case of |
| 13639 | version @value{GDBVN}), you can make the Info file by typing: |
| 13640 | |
| 13641 | @example |
| 13642 | cd gdb |
| 13643 | make gdb.info |
| 13644 | @end example |
| 13645 | |
| 13646 | If you want to typeset and print copies of this manual, you need @TeX{}, |
| 13647 | a program to print its @sc{dvi} output files, and @file{texinfo.tex}, the |
| 13648 | Texinfo definitions file. |
| 13649 | |
| 13650 | @TeX{} is a typesetting program; it does not print files directly, but |
| 13651 | produces output files called @sc{dvi} files. To print a typeset |
| 13652 | document, you need a program to print @sc{dvi} files. If your system |
| 13653 | has @TeX{} installed, chances are it has such a program. The precise |
| 13654 | command to use depends on your system; @kbd{lpr -d} is common; another |
| 13655 | (for PostScript devices) is @kbd{dvips}. The @sc{dvi} print command may |
| 13656 | require a file name without any extension or a @samp{.dvi} extension. |
| 13657 | |
| 13658 | @TeX{} also requires a macro definitions file called |
| 13659 | @file{texinfo.tex}. This file tells @TeX{} how to typeset a document |
| 13660 | written in Texinfo format. On its own, @TeX{} cannot either read or |
| 13661 | typeset a Texinfo file. @file{texinfo.tex} is distributed with GDB |
| 13662 | and is located in the @file{gdb-@var{version-number}/texinfo} |
| 13663 | directory. |
| 13664 | |
| 13665 | If you have @TeX{} and a @sc{dvi} printer program installed, you can |
| 13666 | typeset and print this manual. First switch to the the @file{gdb} |
| 13667 | subdirectory of the main source directory (for example, to |
| 13668 | @file{gdb-@value{GDBVN}/gdb}) and type: |
| 13669 | |
| 13670 | @example |
| 13671 | make gdb.dvi |
| 13672 | @end example |
| 13673 | |
| 13674 | Then give @file{gdb.dvi} to your @sc{dvi} printing program. |
| 13675 | |
| 13676 | @node Installing GDB |
| 13677 | @appendix Installing @value{GDBN} |
| 13678 | @cindex configuring @value{GDBN} |
| 13679 | @cindex installation |
| 13680 | |
| 13681 | @value{GDBN} comes with a @code{configure} script that automates the process |
| 13682 | of preparing @value{GDBN} for installation; you can then use @code{make} to |
| 13683 | build the @code{gdb} program. |
| 13684 | @iftex |
| 13685 | @c irrelevant in info file; it's as current as the code it lives with. |
| 13686 | @footnote{If you have a more recent version of @value{GDBN} than @value{GDBVN}, |
| 13687 | look at the @file{README} file in the sources; we may have improved the |
| 13688 | installation procedures since publishing this manual.} |
| 13689 | @end iftex |
| 13690 | |
| 13691 | The @value{GDBN} distribution includes all the source code you need for |
| 13692 | @value{GDBN} in a single directory, whose name is usually composed by |
| 13693 | appending the version number to @samp{gdb}. |
| 13694 | |
| 13695 | For example, the @value{GDBN} version @value{GDBVN} distribution is in the |
| 13696 | @file{gdb-@value{GDBVN}} directory. That directory contains: |
| 13697 | |
| 13698 | @table @code |
| 13699 | @item gdb-@value{GDBVN}/configure @r{(and supporting files)} |
| 13700 | script for configuring @value{GDBN} and all its supporting libraries |
| 13701 | |
| 13702 | @item gdb-@value{GDBVN}/gdb |
| 13703 | the source specific to @value{GDBN} itself |
| 13704 | |
| 13705 | @item gdb-@value{GDBVN}/bfd |
| 13706 | source for the Binary File Descriptor library |
| 13707 | |
| 13708 | @item gdb-@value{GDBVN}/include |
| 13709 | @sc{gnu} include files |
| 13710 | |
| 13711 | @item gdb-@value{GDBVN}/libiberty |
| 13712 | source for the @samp{-liberty} free software library |
| 13713 | |
| 13714 | @item gdb-@value{GDBVN}/opcodes |
| 13715 | source for the library of opcode tables and disassemblers |
| 13716 | |
| 13717 | @item gdb-@value{GDBVN}/readline |
| 13718 | source for the @sc{gnu} command-line interface |
| 13719 | |
| 13720 | @item gdb-@value{GDBVN}/glob |
| 13721 | source for the @sc{gnu} filename pattern-matching subroutine |
| 13722 | |
| 13723 | @item gdb-@value{GDBVN}/mmalloc |
| 13724 | source for the @sc{gnu} memory-mapped malloc package |
| 13725 | @end table |
| 13726 | |
| 13727 | The simplest way to configure and build @value{GDBN} is to run @code{configure} |
| 13728 | from the @file{gdb-@var{version-number}} source directory, which in |
| 13729 | this example is the @file{gdb-@value{GDBVN}} directory. |
| 13730 | |
| 13731 | First switch to the @file{gdb-@var{version-number}} source directory |
| 13732 | if you are not already in it; then run @code{configure}. Pass the |
| 13733 | identifier for the platform on which @value{GDBN} will run as an |
| 13734 | argument. |
| 13735 | |
| 13736 | For example: |
| 13737 | |
| 13738 | @example |
| 13739 | cd gdb-@value{GDBVN} |
| 13740 | ./configure @var{host} |
| 13741 | make |
| 13742 | @end example |
| 13743 | |
| 13744 | @noindent |
| 13745 | where @var{host} is an identifier such as @samp{sun4} or |
| 13746 | @samp{decstation}, that identifies the platform where @value{GDBN} will run. |
| 13747 | (You can often leave off @var{host}; @code{configure} tries to guess the |
| 13748 | correct value by examining your system.) |
| 13749 | |
| 13750 | Running @samp{configure @var{host}} and then running @code{make} builds the |
| 13751 | @file{bfd}, @file{readline}, @file{mmalloc}, and @file{libiberty} |
| 13752 | libraries, then @code{gdb} itself. The configured source files, and the |
| 13753 | binaries, are left in the corresponding source directories. |
| 13754 | |
| 13755 | @need 750 |
| 13756 | @code{configure} is a Bourne-shell (@code{/bin/sh}) script; if your |
| 13757 | system does not recognize this automatically when you run a different |
| 13758 | shell, you may need to run @code{sh} on it explicitly: |
| 13759 | |
| 13760 | @example |
| 13761 | sh configure @var{host} |
| 13762 | @end example |
| 13763 | |
| 13764 | If you run @code{configure} from a directory that contains source |
| 13765 | directories for multiple libraries or programs, such as the |
| 13766 | @file{gdb-@value{GDBVN}} source directory for version @value{GDBVN}, @code{configure} |
| 13767 | creates configuration files for every directory level underneath (unless |
| 13768 | you tell it not to, with the @samp{--norecursion} option). |
| 13769 | |
| 13770 | You can run the @code{configure} script from any of the |
| 13771 | subordinate directories in the @value{GDBN} distribution if you only want to |
| 13772 | configure that subdirectory, but be sure to specify a path to it. |
| 13773 | |
| 13774 | For example, with version @value{GDBVN}, type the following to configure only |
| 13775 | the @code{bfd} subdirectory: |
| 13776 | |
| 13777 | @example |
| 13778 | @group |
| 13779 | cd gdb-@value{GDBVN}/bfd |
| 13780 | ../configure @var{host} |
| 13781 | @end group |
| 13782 | @end example |
| 13783 | |
| 13784 | You can install @code{@value{GDBP}} anywhere; it has no hardwired paths. |
| 13785 | However, you should make sure that the shell on your path (named by |
| 13786 | the @samp{SHELL} environment variable) is publicly readable. Remember |
| 13787 | that @value{GDBN} uses the shell to start your program---some systems refuse to |
| 13788 | let @value{GDBN} debug child processes whose programs are not readable. |
| 13789 | |
| 13790 | @menu |
| 13791 | * Separate Objdir:: Compiling @value{GDBN} in another directory |
| 13792 | * Config Names:: Specifying names for hosts and targets |
| 13793 | * Configure Options:: Summary of options for configure |
| 13794 | @end menu |
| 13795 | |
| 13796 | @node Separate Objdir |
| 13797 | @section Compiling @value{GDBN} in another directory |
| 13798 | |
| 13799 | If you want to run @value{GDBN} versions for several host or target machines, |
| 13800 | you need a different @code{gdb} compiled for each combination of |
| 13801 | host and target. @code{configure} is designed to make this easy by |
| 13802 | allowing you to generate each configuration in a separate subdirectory, |
| 13803 | rather than in the source directory. If your @code{make} program |
| 13804 | handles the @samp{VPATH} feature (@sc{gnu} @code{make} does), running |
| 13805 | @code{make} in each of these directories builds the @code{gdb} |
| 13806 | program specified there. |
| 13807 | |
| 13808 | To build @code{gdb} in a separate directory, run @code{configure} |
| 13809 | with the @samp{--srcdir} option to specify where to find the source. |
| 13810 | (You also need to specify a path to find @code{configure} |
| 13811 | itself from your working directory. If the path to @code{configure} |
| 13812 | would be the same as the argument to @samp{--srcdir}, you can leave out |
| 13813 | the @samp{--srcdir} option; it is assumed.) |
| 13814 | |
| 13815 | For example, with version @value{GDBVN}, you can build @value{GDBN} in a |
| 13816 | separate directory for a Sun 4 like this: |
| 13817 | |
| 13818 | @example |
| 13819 | @group |
| 13820 | cd gdb-@value{GDBVN} |
| 13821 | mkdir ../gdb-sun4 |
| 13822 | cd ../gdb-sun4 |
| 13823 | ../gdb-@value{GDBVN}/configure sun4 |
| 13824 | make |
| 13825 | @end group |
| 13826 | @end example |
| 13827 | |
| 13828 | When @code{configure} builds a configuration using a remote source |
| 13829 | directory, it creates a tree for the binaries with the same structure |
| 13830 | (and using the same names) as the tree under the source directory. In |
| 13831 | the example, you'd find the Sun 4 library @file{libiberty.a} in the |
| 13832 | directory @file{gdb-sun4/libiberty}, and @value{GDBN} itself in |
| 13833 | @file{gdb-sun4/gdb}. |
| 13834 | |
| 13835 | One popular reason to build several @value{GDBN} configurations in separate |
| 13836 | directories is to configure @value{GDBN} for cross-compiling (where |
| 13837 | @value{GDBN} runs on one machine---the @dfn{host}---while debugging |
| 13838 | programs that run on another machine---the @dfn{target}). |
| 13839 | You specify a cross-debugging target by |
| 13840 | giving the @samp{--target=@var{target}} option to @code{configure}. |
| 13841 | |
| 13842 | When you run @code{make} to build a program or library, you must run |
| 13843 | it in a configured directory---whatever directory you were in when you |
| 13844 | called @code{configure} (or one of its subdirectories). |
| 13845 | |
| 13846 | The @code{Makefile} that @code{configure} generates in each source |
| 13847 | directory also runs recursively. If you type @code{make} in a source |
| 13848 | directory such as @file{gdb-@value{GDBVN}} (or in a separate configured |
| 13849 | directory configured with @samp{--srcdir=@var{dirname}/gdb-@value{GDBVN}}), you |
| 13850 | will build all the required libraries, and then build GDB. |
| 13851 | |
| 13852 | When you have multiple hosts or targets configured in separate |
| 13853 | directories, you can run @code{make} on them in parallel (for example, |
| 13854 | if they are NFS-mounted on each of the hosts); they will not interfere |
| 13855 | with each other. |
| 13856 | |
| 13857 | @node Config Names |
| 13858 | @section Specifying names for hosts and targets |
| 13859 | |
| 13860 | The specifications used for hosts and targets in the @code{configure} |
| 13861 | script are based on a three-part naming scheme, but some short predefined |
| 13862 | aliases are also supported. The full naming scheme encodes three pieces |
| 13863 | of information in the following pattern: |
| 13864 | |
| 13865 | @example |
| 13866 | @var{architecture}-@var{vendor}-@var{os} |
| 13867 | @end example |
| 13868 | |
| 13869 | For example, you can use the alias @code{sun4} as a @var{host} argument, |
| 13870 | or as the value for @var{target} in a @code{--target=@var{target}} |
| 13871 | option. The equivalent full name is @samp{sparc-sun-sunos4}. |
| 13872 | |
| 13873 | The @code{configure} script accompanying @value{GDBN} does not provide |
| 13874 | any query facility to list all supported host and target names or |
| 13875 | aliases. @code{configure} calls the Bourne shell script |
| 13876 | @code{config.sub} to map abbreviations to full names; you can read the |
| 13877 | script, if you wish, or you can use it to test your guesses on |
| 13878 | abbreviations---for example: |
| 13879 | |
| 13880 | @smallexample |
| 13881 | % sh config.sub i386-linux |
| 13882 | i386-pc-linux-gnu |
| 13883 | % sh config.sub alpha-linux |
| 13884 | alpha-unknown-linux-gnu |
| 13885 | % sh config.sub hp9k700 |
| 13886 | hppa1.1-hp-hpux |
| 13887 | % sh config.sub sun4 |
| 13888 | sparc-sun-sunos4.1.1 |
| 13889 | % sh config.sub sun3 |
| 13890 | m68k-sun-sunos4.1.1 |
| 13891 | % sh config.sub i986v |
| 13892 | Invalid configuration `i986v': machine `i986v' not recognized |
| 13893 | @end smallexample |
| 13894 | |
| 13895 | @noindent |
| 13896 | @code{config.sub} is also distributed in the @value{GDBN} source |
| 13897 | directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}). |
| 13898 | |
| 13899 | @node Configure Options |
| 13900 | @section @code{configure} options |
| 13901 | |
| 13902 | Here is a summary of the @code{configure} options and arguments that |
| 13903 | are most often useful for building @value{GDBN}. @code{configure} also has |
| 13904 | several other options not listed here. @inforef{What Configure |
| 13905 | Does,,configure.info}, for a full explanation of @code{configure}. |
| 13906 | |
| 13907 | @example |
| 13908 | configure @r{[}--help@r{]} |
| 13909 | @r{[}--prefix=@var{dir}@r{]} |
| 13910 | @r{[}--exec-prefix=@var{dir}@r{]} |
| 13911 | @r{[}--srcdir=@var{dirname}@r{]} |
| 13912 | @r{[}--norecursion@r{]} @r{[}--rm@r{]} |
| 13913 | @r{[}--target=@var{target}@r{]} |
| 13914 | @var{host} |
| 13915 | @end example |
| 13916 | |
| 13917 | @noindent |
| 13918 | You may introduce options with a single @samp{-} rather than |
| 13919 | @samp{--} if you prefer; but you may abbreviate option names if you use |
| 13920 | @samp{--}. |
| 13921 | |
| 13922 | @table @code |
| 13923 | @item --help |
| 13924 | Display a quick summary of how to invoke @code{configure}. |
| 13925 | |
| 13926 | @item --prefix=@var{dir} |
| 13927 | Configure the source to install programs and files under directory |
| 13928 | @file{@var{dir}}. |
| 13929 | |
| 13930 | @item --exec-prefix=@var{dir} |
| 13931 | Configure the source to install programs under directory |
| 13932 | @file{@var{dir}}. |
| 13933 | |
| 13934 | @c avoid splitting the warning from the explanation: |
| 13935 | @need 2000 |
| 13936 | @item --srcdir=@var{dirname} |
| 13937 | @strong{Warning: using this option requires @sc{gnu} @code{make}, or another |
| 13938 | @code{make} that implements the @code{VPATH} feature.}@* |
| 13939 | Use this option to make configurations in directories separate from the |
| 13940 | @value{GDBN} source directories. Among other things, you can use this to |
| 13941 | build (or maintain) several configurations simultaneously, in separate |
| 13942 | directories. @code{configure} writes configuration specific files in |
| 13943 | the current directory, but arranges for them to use the source in the |
| 13944 | directory @var{dirname}. @code{configure} creates directories under |
| 13945 | the working directory in parallel to the source directories below |
| 13946 | @var{dirname}. |
| 13947 | |
| 13948 | @item --norecursion |
| 13949 | Configure only the directory level where @code{configure} is executed; do not |
| 13950 | propagate configuration to subdirectories. |
| 13951 | |
| 13952 | @item --target=@var{target} |
| 13953 | Configure @value{GDBN} for cross-debugging programs running on the specified |
| 13954 | @var{target}. Without this option, @value{GDBN} is configured to debug |
| 13955 | programs that run on the same machine (@var{host}) as @value{GDBN} itself. |
| 13956 | |
| 13957 | There is no convenient way to generate a list of all available targets. |
| 13958 | |
| 13959 | @item @var{host} @dots{} |
| 13960 | Configure @value{GDBN} to run on the specified @var{host}. |
| 13961 | |
| 13962 | There is no convenient way to generate a list of all available hosts. |
| 13963 | @end table |
| 13964 | |
| 13965 | There are many other options available as well, but they are generally |
| 13966 | needed for special purposes only. |
| 13967 | |
| 13968 | @node Maintenance Commands |
| 13969 | @appendix Maintenance Commands |
| 13970 | @cindex maintenance commands |
| 13971 | @cindex internal commands |
| 13972 | |
| 13973 | In addition to commands intended for @value{GDBN} users, @value{GDBN} |
| 13974 | includes a number of commands intended for @value{GDBN} developers. |
| 13975 | These commands are provided here for reference. |
| 13976 | |
| 13977 | @table @code |
| 13978 | @kindex maint info breakpoints |
| 13979 | @item @anchor{maint info breakpoints}maint info breakpoints |
| 13980 | Using the same format as @samp{info breakpoints}, display both the |
| 13981 | breakpoints you've set explicitly, and those @value{GDBN} is using for |
| 13982 | internal purposes. Internal breakpoints are shown with negative |
| 13983 | breakpoint numbers. The type column identifies what kind of breakpoint |
| 13984 | is shown: |
| 13985 | |
| 13986 | @table @code |
| 13987 | @item breakpoint |
| 13988 | Normal, explicitly set breakpoint. |
| 13989 | |
| 13990 | @item watchpoint |
| 13991 | Normal, explicitly set watchpoint. |
| 13992 | |
| 13993 | @item longjmp |
| 13994 | Internal breakpoint, used to handle correctly stepping through |
| 13995 | @code{longjmp} calls. |
| 13996 | |
| 13997 | @item longjmp resume |
| 13998 | Internal breakpoint at the target of a @code{longjmp}. |
| 13999 | |
| 14000 | @item until |
| 14001 | Temporary internal breakpoint used by the @value{GDBN} @code{until} command. |
| 14002 | |
| 14003 | @item finish |
| 14004 | Temporary internal breakpoint used by the @value{GDBN} @code{finish} command. |
| 14005 | |
| 14006 | @item shlib events |
| 14007 | Shared library events. |
| 14008 | |
| 14009 | @end table |
| 14010 | |
| 14011 | @end table |
| 14012 | |
| 14013 | |
| 14014 | @node Remote Protocol |
| 14015 | @appendix @value{GDBN} Remote Serial Protocol |
| 14016 | |
| 14017 | There may be occasions when you need to know something about the |
| 14018 | protocol---for example, if there is only one serial port to your target |
| 14019 | machine, you might want your program to do something special if it |
| 14020 | recognizes a packet meant for @value{GDBN}. |
| 14021 | |
| 14022 | In the examples below, @samp{<-} and @samp{->} are used to indicate |
| 14023 | transmitted and received data respectfully. |
| 14024 | |
| 14025 | @cindex protocol, @value{GDBN} remote serial |
| 14026 | @cindex serial protocol, @value{GDBN} remote |
| 14027 | @cindex remote serial protocol |
| 14028 | All @value{GDBN} commands and responses (other than acknowledgments) are |
| 14029 | sent as a @var{packet}. A @var{packet} is introduced with the character |
| 14030 | @samp{$}, the actual @var{packet-data}, and the terminating character |
| 14031 | @samp{#} followed by a two-digit @var{checksum}: |
| 14032 | |
| 14033 | @example |
| 14034 | @code{$}@var{packet-data}@code{#}@var{checksum} |
| 14035 | @end example |
| 14036 | @noindent |
| 14037 | |
| 14038 | @cindex checksum, for @value{GDBN} remote |
| 14039 | @noindent |
| 14040 | The two-digit @var{checksum} is computed as the modulo 256 sum of all |
| 14041 | characters between the leading @samp{$} and the trailing @samp{#} (an |
| 14042 | eight bit unsigned checksum). |
| 14043 | |
| 14044 | Implementors should note that prior to @value{GDBN} 5.0 the protocol |
| 14045 | specification also included an optional two-digit @var{sequence-id}: |
| 14046 | |
| 14047 | @example |
| 14048 | @code{$}@var{sequence-id}@code{:}@var{packet-data}@code{#}@var{checksum} |
| 14049 | @end example |
| 14050 | |
| 14051 | @cindex sequence-id, for @value{GDBN} remote |
| 14052 | @noindent |
| 14053 | That @var{sequence-id} was appended to the acknowledgment. @value{GDBN} |
| 14054 | has never output @var{sequence-id}s. Stubs that handle packets added |
| 14055 | since @value{GDBN} 5.0 must not accept @var{sequence-id}. |
| 14056 | |
| 14057 | @cindex acknowledgment, for @value{GDBN} remote |
| 14058 | When either the host or the target machine receives a packet, the first |
| 14059 | response expected is an acknowledgment: either @samp{+} (to indicate |
| 14060 | the package was received correctly) or @samp{-} (to request |
| 14061 | retransmission): |
| 14062 | |
| 14063 | @example |
| 14064 | <- @code{$}@var{packet-data}@code{#}@var{checksum} |
| 14065 | -> @code{+} |
| 14066 | @end example |
| 14067 | @noindent |
| 14068 | |
| 14069 | The host (@value{GDBN}) sends @var{command}s, and the target (the |
| 14070 | debugging stub incorporated in your program) sends a @var{response}. In |
| 14071 | the case of step and continue @var{command}s, the response is only sent |
| 14072 | when the operation has completed (the target has again stopped). |
| 14073 | |
| 14074 | @var{packet-data} consists of a sequence of characters with the |
| 14075 | exception of @samp{#} and @samp{$} (see @samp{X} packet for additional |
| 14076 | exceptions). |
| 14077 | |
| 14078 | Fields within the packet should be separated using @samp{,} @samp{;} or |
| 14079 | @samp{:}. Except where otherwise noted all numbers are represented in |
| 14080 | HEX with leading zeros suppressed. |
| 14081 | |
| 14082 | Implementors should note that prior to @value{GDBN} 5.0, the character |
| 14083 | @samp{:} could not appear as the third character in a packet (as it |
| 14084 | would potentially conflict with the @var{sequence-id}). |
| 14085 | |
| 14086 | Response @var{data} can be run-length encoded to save space. A @samp{*} |
| 14087 | means that the next character is an @sc{ascii} encoding giving a repeat count |
| 14088 | which stands for that many repetitions of the character preceding the |
| 14089 | @samp{*}. The encoding is @code{n+29}, yielding a printable character |
| 14090 | where @code{n >=3} (which is where rle starts to win). The printable |
| 14091 | characters @samp{$}, @samp{#}, @samp{+} and @samp{-} or with a numeric |
| 14092 | value greater than 126 should not be used. |
| 14093 | |
| 14094 | Some remote systems have used a different run-length encoding mechanism |
| 14095 | loosely refered to as the cisco encoding. Following the @samp{*} |
| 14096 | character are two hex digits that indicate the size of the packet. |
| 14097 | |
| 14098 | So: |
| 14099 | @example |
| 14100 | "@code{0* }" |
| 14101 | @end example |
| 14102 | @noindent |
| 14103 | means the same as "0000". |
| 14104 | |
| 14105 | The error response returned for some packets includes a two character |
| 14106 | error number. That number is not well defined. |
| 14107 | |
| 14108 | For any @var{command} not supported by the stub, an empty response |
| 14109 | (@samp{$#00}) should be returned. That way it is possible to extend the |
| 14110 | protocol. A newer @value{GDBN} can tell if a packet is supported based |
| 14111 | on that response. |
| 14112 | |
| 14113 | A stub is required to support the @samp{g}, @samp{G}, @samp{m}, @samp{M}, |
| 14114 | @samp{c}, and @samp{s} @var{command}s. All other @var{command}s are |
| 14115 | optional. |
| 14116 | |
| 14117 | Below is a complete list of all currently defined @var{command}s and |
| 14118 | their corresponding response @var{data}: |
| 14119 | @page |
| 14120 | @multitable @columnfractions .30 .30 .40 |
| 14121 | @item Packet |
| 14122 | @tab Request |
| 14123 | @tab Description |
| 14124 | |
| 14125 | @item extended mode |
| 14126 | @tab @code{!} |
| 14127 | @tab |
| 14128 | Enable extended mode. In extended mode, the remote server is made |
| 14129 | persistent. The @samp{R} packet is used to restart the program being |
| 14130 | debugged. |
| 14131 | @item |
| 14132 | @tab reply @samp{OK} |
| 14133 | @tab |
| 14134 | The remote target both supports and has enabled extended mode. |
| 14135 | |
| 14136 | @item last signal |
| 14137 | @tab @code{?} |
| 14138 | @tab |
| 14139 | Indicate the reason the target halted. The reply is the same as for step |
| 14140 | and continue. |
| 14141 | @item |
| 14142 | @tab reply |
| 14143 | @tab see below |
| 14144 | |
| 14145 | |
| 14146 | @item reserved |
| 14147 | @tab @code{a} |
| 14148 | @tab Reserved for future use |
| 14149 | |
| 14150 | @item set program arguments @strong{(reserved)} |
| 14151 | @tab @code{A}@var{arglen}@code{,}@var{argnum}@code{,}@var{arg}@code{,...} |
| 14152 | @tab |
| 14153 | @item |
| 14154 | @tab |
| 14155 | @tab |
| 14156 | Initialized @samp{argv[]} array passed into program. @var{arglen} |
| 14157 | specifies the number of bytes in the hex encoded byte stream @var{arg}. |
| 14158 | See @file{gdbserver} for more details. |
| 14159 | @item |
| 14160 | @tab reply @code{OK} |
| 14161 | @item |
| 14162 | @tab reply @code{E}@var{NN} |
| 14163 | |
| 14164 | @item set baud @strong{(deprecated)} |
| 14165 | @tab @code{b}@var{baud} |
| 14166 | @tab |
| 14167 | Change the serial line speed to @var{baud}. JTC: @emph{When does the |
| 14168 | transport layer state change? When it's received, or after the ACK is |
| 14169 | transmitted. In either case, there are problems if the command or the |
| 14170 | acknowledgment packet is dropped.} Stan: @emph{If people really wanted |
| 14171 | to add something like this, and get it working for the first time, they |
| 14172 | ought to modify ser-unix.c to send some kind of out-of-band message to a |
| 14173 | specially-setup stub and have the switch happen "in between" packets, so |
| 14174 | that from remote protocol's point of view, nothing actually |
| 14175 | happened.} |
| 14176 | |
| 14177 | @item set breakpoint @strong{(deprecated)} |
| 14178 | @tab @code{B}@var{addr},@var{mode} |
| 14179 | @tab |
| 14180 | Set (@var{mode} is @samp{S}) or clear (@var{mode} is @samp{C}) a |
| 14181 | breakpoint at @var{addr}. @emph{This has been replaced by the @samp{Z} and |
| 14182 | @samp{z} packets.} |
| 14183 | |
| 14184 | @item continue |
| 14185 | @tab @code{c}@var{addr} |
| 14186 | @tab |
| 14187 | @var{addr} is address to resume. If @var{addr} is omitted, resume at |
| 14188 | current address. |
| 14189 | @item |
| 14190 | @tab reply |
| 14191 | @tab see below |
| 14192 | |
| 14193 | @item continue with signal |
| 14194 | @tab @code{C}@var{sig}@code{;}@var{addr} |
| 14195 | @tab |
| 14196 | Continue with signal @var{sig} (hex signal number). If |
| 14197 | @code{;}@var{addr} is omitted, resume at same address. |
| 14198 | @item |
| 14199 | @tab reply |
| 14200 | @tab see below |
| 14201 | |
| 14202 | @item toggle debug @strong{(deprecated)} |
| 14203 | @tab @code{d} |
| 14204 | @tab |
| 14205 | toggle debug flag. |
| 14206 | |
| 14207 | @item detach |
| 14208 | @tab @code{D} |
| 14209 | @tab |
| 14210 | Detach @value{GDBN} from the remote system. Sent to the remote target before |
| 14211 | @value{GDBN} disconnects. |
| 14212 | @item |
| 14213 | @tab reply @emph{no response} |
| 14214 | @tab |
| 14215 | @value{GDBN} does not check for any response after sending this packet. |
| 14216 | |
| 14217 | @item reserved |
| 14218 | @tab @code{e} |
| 14219 | @tab Reserved for future use |
| 14220 | |
| 14221 | @item reserved |
| 14222 | @tab @code{E} |
| 14223 | @tab Reserved for future use |
| 14224 | |
| 14225 | @item reserved |
| 14226 | @tab @code{f} |
| 14227 | @tab Reserved for future use |
| 14228 | |
| 14229 | @item reserved |
| 14230 | @tab @code{F} |
| 14231 | @tab Reserved for future use |
| 14232 | |
| 14233 | @item read registers |
| 14234 | @tab @code{g} |
| 14235 | @tab Read general registers. |
| 14236 | @item |
| 14237 | @tab reply @var{XX...} |
| 14238 | @tab |
| 14239 | Each byte of register data is described by two hex digits. The bytes |
| 14240 | with the register are transmitted in target byte order. The size of |
| 14241 | each register and their position within the @samp{g} @var{packet} are |
| 14242 | determined by the @value{GDBN} internal macros @var{REGISTER_RAW_SIZE} and |
| 14243 | @var{REGISTER_NAME} macros. The specification of several standard |
| 14244 | @code{g} packets is specified below. |
| 14245 | @item |
| 14246 | @tab @code{E}@var{NN} |
| 14247 | @tab for an error. |
| 14248 | |
| 14249 | @item write regs |
| 14250 | @tab @code{G}@var{XX...} |
| 14251 | @tab |
| 14252 | See @samp{g} for a description of the @var{XX...} data. |
| 14253 | @item |
| 14254 | @tab reply @code{OK} |
| 14255 | @tab for success |
| 14256 | @item |
| 14257 | @tab reply @code{E}@var{NN} |
| 14258 | @tab for an error |
| 14259 | |
| 14260 | @item reserved |
| 14261 | @tab @code{h} |
| 14262 | @tab Reserved for future use |
| 14263 | |
| 14264 | @item set thread |
| 14265 | @tab @code{H}@var{c}@var{t...} |
| 14266 | @tab |
| 14267 | Set thread for subsequent operations (@samp{m}, @samp{M}, @samp{g}, |
| 14268 | @samp{G}, et.al.). @var{c} = @samp{c} for thread used in step and |
| 14269 | continue; @var{t...} can be -1 for all threads. @var{c} = @samp{g} for |
| 14270 | thread used in other operations. If zero, pick a thread, any thread. |
| 14271 | @item |
| 14272 | @tab reply @code{OK} |
| 14273 | @tab for success |
| 14274 | @item |
| 14275 | @tab reply @code{E}@var{NN} |
| 14276 | @tab for an error |
| 14277 | |
| 14278 | @c FIXME: JTC: |
| 14279 | @c 'H': How restrictive (or permissive) is the thread model. If a |
| 14280 | @c thread is selected and stopped, are other threads allowed |
| 14281 | @c to continue to execute? As I mentioned above, I think the |
| 14282 | @c semantics of each command when a thread is selected must be |
| 14283 | @c described. For example: |
| 14284 | @c |
| 14285 | @c 'g': If the stub supports threads and a specific thread is |
| 14286 | @c selected, returns the register block from that thread; |
| 14287 | @c otherwise returns current registers. |
| 14288 | @c |
| 14289 | @c 'G' If the stub supports threads and a specific thread is |
| 14290 | @c selected, sets the registers of the register block of |
| 14291 | @c that thread; otherwise sets current registers. |
| 14292 | |
| 14293 | @item cycle step @strong{(draft)} |
| 14294 | @tab @code{i}@var{addr}@code{,}@var{nnn} |
| 14295 | @tab |
| 14296 | Step the remote target by a single clock cycle. If @code{,}@var{nnn} is |
| 14297 | present, cycle step @var{nnn} cycles. If @var{addr} is present, cycle |
| 14298 | step starting at that address. |
| 14299 | |
| 14300 | @item signal then cycle step @strong{(reserved)} |
| 14301 | @tab @code{I} |
| 14302 | @tab |
| 14303 | See @samp{i} and @samp{S} for likely syntax and semantics. |
| 14304 | |
| 14305 | @item reserved |
| 14306 | @tab @code{j} |
| 14307 | @tab Reserved for future use |
| 14308 | |
| 14309 | @item reserved |
| 14310 | @tab @code{J} |
| 14311 | @tab Reserved for future use |
| 14312 | |
| 14313 | @item kill request |
| 14314 | @tab @code{k} |
| 14315 | @tab |
| 14316 | FIXME: @emph{There is no description of how to operate when a specific |
| 14317 | thread context has been selected (i.e.@: does 'k' kill only that thread?)}. |
| 14318 | |
| 14319 | @item reserved |
| 14320 | @tab @code{l} |
| 14321 | @tab Reserved for future use |
| 14322 | |
| 14323 | @item reserved |
| 14324 | @tab @code{L} |
| 14325 | @tab Reserved for future use |
| 14326 | |
| 14327 | @item read memory |
| 14328 | @tab @code{m}@var{addr}@code{,}@var{length} |
| 14329 | @tab |
| 14330 | Read @var{length} bytes of memory starting at address @var{addr}. |
| 14331 | Neither @value{GDBN} nor the stub assume that sized memory transfers are assumed |
| 14332 | using word alligned accesses. FIXME: @emph{A word aligned memory |
| 14333 | transfer mechanism is needed.} |
| 14334 | @item |
| 14335 | @tab reply @var{XX...} |
| 14336 | @tab |
| 14337 | @var{XX...} is mem contents. Can be fewer bytes than requested if able |
| 14338 | to read only part of the data. Neither @value{GDBN} nor the stub assume that |
| 14339 | sized memory transfers are assumed using word alligned accesses. FIXME: |
| 14340 | @emph{A word aligned memory transfer mechanism is needed.} |
| 14341 | @item |
| 14342 | @tab reply @code{E}@var{NN} |
| 14343 | @tab @var{NN} is errno |
| 14344 | |
| 14345 | @item write mem |
| 14346 | @tab @code{M}@var{addr},@var{length}@code{:}@var{XX...} |
| 14347 | @tab |
| 14348 | Write @var{length} bytes of memory starting at address @var{addr}. |
| 14349 | @var{XX...} is the data. |
| 14350 | @item |
| 14351 | @tab reply @code{OK} |
| 14352 | @tab for success |
| 14353 | @item |
| 14354 | @tab reply @code{E}@var{NN} |
| 14355 | @tab |
| 14356 | for an error (this includes the case where only part of the data was |
| 14357 | written). |
| 14358 | |
| 14359 | @item reserved |
| 14360 | @tab @code{n} |
| 14361 | @tab Reserved for future use |
| 14362 | |
| 14363 | @item reserved |
| 14364 | @tab @code{N} |
| 14365 | @tab Reserved for future use |
| 14366 | |
| 14367 | @item reserved |
| 14368 | @tab @code{o} |
| 14369 | @tab Reserved for future use |
| 14370 | |
| 14371 | @item reserved |
| 14372 | @tab @code{O} |
| 14373 | @tab Reserved for future use |
| 14374 | |
| 14375 | @item read reg @strong{(reserved)} |
| 14376 | @tab @code{p}@var{n...} |
| 14377 | @tab |
| 14378 | See write register. |
| 14379 | @item |
| 14380 | @tab return @var{r....} |
| 14381 | @tab The hex encoded value of the register in target byte order. |
| 14382 | |
| 14383 | @item write reg |
| 14384 | @tab @code{P}@var{n...}@code{=}@var{r...} |
| 14385 | @tab |
| 14386 | Write register @var{n...} with value @var{r...}, which contains two hex |
| 14387 | digits for each byte in the register (target byte order). |
| 14388 | @item |
| 14389 | @tab reply @code{OK} |
| 14390 | @tab for success |
| 14391 | @item |
| 14392 | @tab reply @code{E}@var{NN} |
| 14393 | @tab for an error |
| 14394 | |
| 14395 | @item general query |
| 14396 | @tab @code{q}@var{query} |
| 14397 | @tab |
| 14398 | Request info about @var{query}. In general @value{GDBN} queries |
| 14399 | have a leading upper case letter. Custom vendor queries should use a |
| 14400 | company prefix (in lower case) ex: @samp{qfsf.var}. @var{query} may |
| 14401 | optionally be followed by a @samp{,} or @samp{;} separated list. Stubs |
| 14402 | must ensure that they match the full @var{query} name. |
| 14403 | @item |
| 14404 | @tab reply @code{XX...} |
| 14405 | @tab Hex encoded data from query. The reply can not be empty. |
| 14406 | @item |
| 14407 | @tab reply @code{E}@var{NN} |
| 14408 | @tab error reply |
| 14409 | @item |
| 14410 | @tab reply @samp{} |
| 14411 | @tab Indicating an unrecognized @var{query}. |
| 14412 | |
| 14413 | @item general set |
| 14414 | @tab @code{Q}@var{var}@code{=}@var{val} |
| 14415 | @tab |
| 14416 | Set value of @var{var} to @var{val}. See @samp{q} for a discussing of |
| 14417 | naming conventions. |
| 14418 | |
| 14419 | @item reset @strong{(deprecated)} |
| 14420 | @tab @code{r} |
| 14421 | @tab |
| 14422 | Reset the entire system. |
| 14423 | |
| 14424 | @item remote restart |
| 14425 | @tab @code{R}@var{XX} |
| 14426 | @tab |
| 14427 | Restart the program being debugged. @var{XX}, while needed, is ignored. |
| 14428 | This packet is only available in extended mode. |
| 14429 | @item |
| 14430 | @tab |
| 14431 | no reply |
| 14432 | @tab |
| 14433 | The @samp{R} packet has no reply. |
| 14434 | |
| 14435 | @item step |
| 14436 | @tab @code{s}@var{addr} |
| 14437 | @tab |
| 14438 | @var{addr} is address to resume. If @var{addr} is omitted, resume at |
| 14439 | same address. |
| 14440 | @item |
| 14441 | @tab reply |
| 14442 | @tab see below |
| 14443 | |
| 14444 | @item step with signal |
| 14445 | @tab @code{S}@var{sig}@code{;}@var{addr} |
| 14446 | @tab |
| 14447 | Like @samp{C} but step not continue. |
| 14448 | @item |
| 14449 | @tab reply |
| 14450 | @tab see below |
| 14451 | |
| 14452 | @item search |
| 14453 | @tab @code{t}@var{addr}@code{:}@var{PP}@code{,}@var{MM} |
| 14454 | @tab |
| 14455 | Search backwards starting at address @var{addr} for a match with pattern |
| 14456 | @var{PP} and mask @var{MM}. @var{PP} and @var{MM} are 4 |
| 14457 | bytes. @var{addr} must be at least 3 digits. |
| 14458 | |
| 14459 | @item thread alive |
| 14460 | @tab @code{T}@var{XX} |
| 14461 | @tab Find out if the thread XX is alive. |
| 14462 | @item |
| 14463 | @tab reply @code{OK} |
| 14464 | @tab thread is still alive |
| 14465 | @item |
| 14466 | @tab reply @code{E}@var{NN} |
| 14467 | @tab thread is dead |
| 14468 | |
| 14469 | @item reserved |
| 14470 | @tab @code{u} |
| 14471 | @tab Reserved for future use |
| 14472 | |
| 14473 | @item reserved |
| 14474 | @tab @code{U} |
| 14475 | @tab Reserved for future use |
| 14476 | |
| 14477 | @item reserved |
| 14478 | @tab @code{v} |
| 14479 | @tab Reserved for future use |
| 14480 | |
| 14481 | @item reserved |
| 14482 | @tab @code{V} |
| 14483 | @tab Reserved for future use |
| 14484 | |
| 14485 | @item reserved |
| 14486 | @tab @code{w} |
| 14487 | @tab Reserved for future use |
| 14488 | |
| 14489 | @item reserved |
| 14490 | @tab @code{W} |
| 14491 | @tab Reserved for future use |
| 14492 | |
| 14493 | @item reserved |
| 14494 | @tab @code{x} |
| 14495 | @tab Reserved for future use |
| 14496 | |
| 14497 | @item write mem (binary) |
| 14498 | @tab @code{X}@var{addr}@code{,}@var{length}@var{:}@var{XX...} |
| 14499 | @tab |
| 14500 | @var{addr} is address, @var{length} is number of bytes, @var{XX...} is |
| 14501 | binary data. The characters @code{$}, @code{#}, and @code{0x7d} are |
| 14502 | escaped using @code{0x7d}. |
| 14503 | @item |
| 14504 | @tab reply @code{OK} |
| 14505 | @tab for success |
| 14506 | @item |
| 14507 | @tab reply @code{E}@var{NN} |
| 14508 | @tab for an error |
| 14509 | |
| 14510 | @item reserved |
| 14511 | @tab @code{y} |
| 14512 | @tab Reserved for future use |
| 14513 | |
| 14514 | @item reserved |
| 14515 | @tab @code{Y} |
| 14516 | @tab Reserved for future use |
| 14517 | |
| 14518 | @item remove break or watchpoint @strong{(draft)} |
| 14519 | @tab @code{z}@var{t}@code{,}@var{addr}@code{,}@var{length} |
| 14520 | @tab |
| 14521 | See @samp{Z}. |
| 14522 | |
| 14523 | @item insert break or watchpoint @strong{(draft)} |
| 14524 | @tab @code{Z}@var{t}@code{,}@var{addr}@code{,}@var{length} |
| 14525 | @tab |
| 14526 | @var{t} is type: @samp{0} - software breakpoint, @samp{1} - hardware |
| 14527 | breakpoint, @samp{2} - write watchpoint, @samp{3} - read watchpoint, |
| 14528 | @samp{4} - access watchpoint; @var{addr} is address; @var{length} is in |
| 14529 | bytes. For a software breakpoint, @var{length} specifies the size of |
| 14530 | the instruction to be patched. For hardware breakpoints and watchpoints |
| 14531 | @var{length} specifies the memory region to be monitored. To avoid |
| 14532 | potential problems with duplicate packets, the operations should be |
| 14533 | implemented in an idempotent way. |
| 14534 | @item |
| 14535 | @tab reply @code{E}@var{NN} |
| 14536 | @tab for an error |
| 14537 | @item |
| 14538 | @tab reply @code{OK} |
| 14539 | @tab for success |
| 14540 | @item |
| 14541 | @tab @samp{} |
| 14542 | @tab If not supported. |
| 14543 | |
| 14544 | @item reserved |
| 14545 | @tab <other> |
| 14546 | @tab Reserved for future use |
| 14547 | |
| 14548 | @end multitable |
| 14549 | |
| 14550 | The @samp{C}, @samp{c}, @samp{S}, @samp{s} and @samp{?} packets can |
| 14551 | receive any of the below as a reply. In the case of the @samp{C}, |
| 14552 | @samp{c}, @samp{S} and @samp{s} packets, that reply is only returned |
| 14553 | when the target halts. In the below the exact meaning of @samp{signal |
| 14554 | number} is poorly defined. In general one of the UNIX signal numbering |
| 14555 | conventions is used. |
| 14556 | |
| 14557 | @multitable @columnfractions .4 .6 |
| 14558 | |
| 14559 | @item @code{S}@var{AA} |
| 14560 | @tab @var{AA} is the signal number |
| 14561 | |
| 14562 | @item @code{T}@var{AA}@var{n...}@code{:}@var{r...}@code{;}@var{n...}@code{:}@var{r...}@code{;}@var{n...}@code{:}@var{r...}@code{;} |
| 14563 | @tab |
| 14564 | @var{AA} = two hex digit signal number; @var{n...} = register number |
| 14565 | (hex), @var{r...} = target byte ordered register contents, size defined |
| 14566 | by @code{REGISTER_RAW_SIZE}; @var{n...} = @samp{thread}, @var{r...} = |
| 14567 | thread process ID, this is a hex integer; @var{n...} = other string not |
| 14568 | starting with valid hex digit. @value{GDBN} should ignore this |
| 14569 | @var{n...}, @var{r...} pair and go on to the next. This way we can |
| 14570 | extend the protocol. |
| 14571 | |
| 14572 | @item @code{W}@var{AA} |
| 14573 | @tab |
| 14574 | The process exited, and @var{AA} is the exit status. This is only |
| 14575 | applicable for certains sorts of targets. |
| 14576 | |
| 14577 | @item @code{X}@var{AA} |
| 14578 | @tab |
| 14579 | The process terminated with signal @var{AA}. |
| 14580 | |
| 14581 | @item @code{N}@var{AA}@code{;}@var{t...}@code{;}@var{d...}@code{;}@var{b...} @strong{(obsolete)} |
| 14582 | @tab |
| 14583 | @var{AA} = signal number; @var{t...} = address of symbol "_start"; |
| 14584 | @var{d...} = base of data section; @var{b...} = base of bss section. |
| 14585 | @emph{Note: only used by Cisco Systems targets. The difference between |
| 14586 | this reply and the "qOffsets" query is that the 'N' packet may arrive |
| 14587 | spontaneously whereas the 'qOffsets' is a query initiated by the host |
| 14588 | debugger.} |
| 14589 | |
| 14590 | @item @code{O}@var{XX...} |
| 14591 | @tab |
| 14592 | @var{XX...} is hex encoding of @sc{ascii} data. This can happen at any time |
| 14593 | while the program is running and the debugger should continue to wait |
| 14594 | for 'W', 'T', etc. |
| 14595 | |
| 14596 | @end multitable |
| 14597 | |
| 14598 | The following set and query packets have already been defined. |
| 14599 | |
| 14600 | @multitable @columnfractions .2 .2 .6 |
| 14601 | |
| 14602 | @item current thread |
| 14603 | @tab @code{q}@code{C} |
| 14604 | @tab Return the current thread id. |
| 14605 | @item |
| 14606 | @tab reply @code{QC}@var{pid} |
| 14607 | @tab |
| 14608 | Where @var{pid} is a HEX encoded 16 bit process id. |
| 14609 | @item |
| 14610 | @tab reply * |
| 14611 | @tab Any other reply implies the old pid. |
| 14612 | |
| 14613 | @item all thread ids |
| 14614 | @tab @code{q}@code{fThreadInfo} |
| 14615 | @item |
| 14616 | @tab @code{q}@code{sThreadInfo} |
| 14617 | @tab |
| 14618 | Obtain a list of active thread ids from the target (OS). Since there |
| 14619 | may be too many active threads to fit into one reply packet, this query |
| 14620 | works iteratively: it may require more than one query/reply sequence to |
| 14621 | obtain the entire list of threads. The first query of the sequence will |
| 14622 | be the @code{qf}@code{ThreadInfo} query; subsequent queries in the |
| 14623 | sequence will be the @code{qs}@code{ThreadInfo} query. |
| 14624 | @item |
| 14625 | @tab |
| 14626 | @tab NOTE: replaces the @code{qL} query (see below). |
| 14627 | @item |
| 14628 | @tab reply @code{m}@var{<id>} |
| 14629 | @tab A single thread id |
| 14630 | @item |
| 14631 | @tab reply @code{m}@var{<id>},@var{<id>...} |
| 14632 | @tab a comma-separated list of thread ids |
| 14633 | @item |
| 14634 | @tab reply @code{l} |
| 14635 | @tab (lower case 'el') denotes end of list. |
| 14636 | @item |
| 14637 | @tab |
| 14638 | @tab |
| 14639 | In response to each query, the target will reply with a list of one |
| 14640 | or more thread ids, in big-endian hex, separated by commas. GDB will |
| 14641 | respond to each reply with a request for more thread ids (using the |
| 14642 | @code{qs} form of the query), until the target responds with @code{l} |
| 14643 | (lower-case el, for @code{'last'}). |
| 14644 | |
| 14645 | @item extra thread info |
| 14646 | @tab @code{q}@code{ThreadExtraInfo}@code{,}@var{id} |
| 14647 | @tab |
| 14648 | @item |
| 14649 | @tab |
| 14650 | @tab |
| 14651 | Where @var{<id>} is a thread-id in big-endian hex. |
| 14652 | Obtain a printable string description of a thread's attributes from |
| 14653 | the target OS. This string may contain anything that the target OS |
| 14654 | thinks is interesting for @value{GDBN} to tell the user about the thread. |
| 14655 | The string is displayed in @value{GDBN}'s @samp{info threads} display. |
| 14656 | Some examples of possible thread extra info strings are "Runnable", or |
| 14657 | "Blocked on Mutex". |
| 14658 | @item |
| 14659 | @tab reply @var{XX...} |
| 14660 | @tab |
| 14661 | Where @var{XX...} is a hex encoding of @sc{ascii} data, comprising the |
| 14662 | printable string containing the extra information about the thread's |
| 14663 | attributes. |
| 14664 | |
| 14665 | @item query @var{LIST} or @var{threadLIST} @strong{(deprecated)} |
| 14666 | @tab @code{q}@code{L}@var{startflag}@var{threadcount}@var{nextthread} |
| 14667 | @tab |
| 14668 | @item |
| 14669 | @tab |
| 14670 | @tab |
| 14671 | Obtain thread information from RTOS. Where: @var{startflag} (one hex |
| 14672 | digit) is one to indicate the first query and zero to indicate a |
| 14673 | subsequent query; @var{threadcount} (two hex digits) is the maximum |
| 14674 | number of threads the response packet can contain; and @var{nextthread} |
| 14675 | (eight hex digits), for subsequent queries (@var{startflag} is zero), is |
| 14676 | returned in the response as @var{argthread}. |
| 14677 | @item |
| 14678 | @tab |
| 14679 | @tab NOTE: this query is replaced by the @code{q}@code{fThreadInfo} |
| 14680 | query (see above). |
| 14681 | @item |
| 14682 | @tab reply @code{q}@code{M}@var{count}@var{done}@var{argthread}@var{thread...} |
| 14683 | @tab |
| 14684 | @item |
| 14685 | @tab |
| 14686 | @tab |
| 14687 | Where: @var{count} (two hex digits) is the number of threads being |
| 14688 | returned; @var{done} (one hex digit) is zero to indicate more threads |
| 14689 | and one indicates no further threads; @var{argthreadid} (eight hex |
| 14690 | digits) is @var{nextthread} from the request packet; @var{thread...} is |
| 14691 | a sequence of thread IDs from the target. @var{threadid} (eight hex |
| 14692 | digits). See @code{remote.c:parse_threadlist_response()}. |
| 14693 | |
| 14694 | @item compute CRC of memory block |
| 14695 | @tab @code{q}@code{CRC:}@var{addr}@code{,}@var{length} |
| 14696 | @tab |
| 14697 | @item |
| 14698 | @tab reply @code{E}@var{NN} |
| 14699 | @tab An error (such as memory fault) |
| 14700 | @item |
| 14701 | @tab reply @code{C}@var{CRC32} |
| 14702 | @tab A 32 bit cyclic redundancy check of the specified memory region. |
| 14703 | |
| 14704 | @item query sect offs |
| 14705 | @tab @code{q}@code{Offsets} |
| 14706 | @tab |
| 14707 | Get section offsets that the target used when re-locating the downloaded |
| 14708 | image. @emph{Note: while a @code{Bss} offset is included in the |
| 14709 | response, @value{GDBN} ignores this and instead applies the @code{Data} |
| 14710 | offset to the @code{Bss} section.} |
| 14711 | @item |
| 14712 | @tab reply @code{Text=}@var{xxx}@code{;Data=}@var{yyy}@code{;Bss=}@var{zzz} |
| 14713 | |
| 14714 | @item thread info request |
| 14715 | @tab @code{q}@code{P}@var{mode}@var{threadid} |
| 14716 | @tab |
| 14717 | @item |
| 14718 | @tab |
| 14719 | @tab |
| 14720 | Returns information on @var{threadid}. Where: @var{mode} is a hex |
| 14721 | encoded 32 bit mode; @var{threadid} is a hex encoded 64 bit thread ID. |
| 14722 | @item |
| 14723 | @tab reply * |
| 14724 | @tab |
| 14725 | See @code{remote.c:remote_unpack_thread_info_response()}. |
| 14726 | |
| 14727 | @item remote command |
| 14728 | @tab @code{q}@code{Rcmd,}@var{COMMAND} |
| 14729 | @tab |
| 14730 | @item |
| 14731 | @tab |
| 14732 | @tab |
| 14733 | @var{COMMAND} (hex encoded) is passed to the local interpreter for |
| 14734 | execution. Invalid commands should be reported using the output string. |
| 14735 | Before the final result packet, the target may also respond with a |
| 14736 | number of intermediate @code{O}@var{OUTPUT} console output |
| 14737 | packets. @emph{Implementors should note that providing access to a |
| 14738 | stubs's interpreter may have security implications}. |
| 14739 | @item |
| 14740 | @tab reply @code{OK} |
| 14741 | @tab |
| 14742 | A command response with no output. |
| 14743 | @item |
| 14744 | @tab reply @var{OUTPUT} |
| 14745 | @tab |
| 14746 | A command response with the hex encoded output string @var{OUTPUT}. |
| 14747 | @item |
| 14748 | @tab reply @code{E}@var{NN} |
| 14749 | @tab |
| 14750 | Indicate a badly formed request. |
| 14751 | |
| 14752 | @item |
| 14753 | @tab reply @samp{} |
| 14754 | @tab |
| 14755 | When @samp{q}@samp{Rcmd} is not recognized. |
| 14756 | |
| 14757 | @item symbol lookup |
| 14758 | @tab @code{qSymbol::} |
| 14759 | @tab |
| 14760 | Notify the target that @value{GDBN} is prepared to serve symbol lookup |
| 14761 | requests. Accept requests from the target for the values of symbols. |
| 14762 | @item |
| 14763 | @tab |
| 14764 | @tab |
| 14765 | @item |
| 14766 | @tab reply @code{OK} |
| 14767 | @tab |
| 14768 | The target does not need to look up any (more) symbols. |
| 14769 | @item |
| 14770 | @tab reply @code{qSymbol:}@var{sym_name} |
| 14771 | @tab |
| 14772 | @sp 2 |
| 14773 | @noindent |
| 14774 | The target requests the value of symbol @var{sym_name} (hex encoded). |
| 14775 | @value{GDBN} may provide the value by using the |
| 14776 | @code{qSymbol:}@var{sym_value}:@var{sym_name} |
| 14777 | message, described below. |
| 14778 | |
| 14779 | @item symbol value |
| 14780 | @tab @code{qSymbol:}@var{sym_value}:@var{sym_name} |
| 14781 | @tab |
| 14782 | @sp 1 |
| 14783 | @noindent |
| 14784 | Set the value of SYM_NAME to SYM_VALUE. |
| 14785 | @item |
| 14786 | @tab |
| 14787 | @tab |
| 14788 | @var{sym_name} (hex encoded) is the name of a symbol whose value |
| 14789 | the target has previously requested. |
| 14790 | @item |
| 14791 | @tab |
| 14792 | @tab |
| 14793 | @var{sym_value} (hex) is the value for symbol @var{sym_name}. |
| 14794 | If @value{GDBN} cannot supply a value for @var{sym_name}, then this |
| 14795 | field will be empty. |
| 14796 | @item |
| 14797 | @tab reply @code{OK} |
| 14798 | @tab |
| 14799 | The target does not need to look up any (more) symbols. |
| 14800 | @item |
| 14801 | @tab reply @code{qSymbol:}@var{sym_name} |
| 14802 | @tab |
| 14803 | @sp 2 |
| 14804 | @noindent |
| 14805 | The target requests the value of a new symbol @var{sym_name} (hex encoded). |
| 14806 | @value{GDBN} will continue to supply the values of symbols (if available), |
| 14807 | until the target ceases to request them. |
| 14808 | |
| 14809 | @end multitable |
| 14810 | |
| 14811 | The following @samp{g}/@samp{G} packets have previously been defined. |
| 14812 | In the below, some thirty-two bit registers are transferred as sixty-four |
| 14813 | bits. Those registers should be zero/sign extended (which?) to fill the |
| 14814 | space allocated. Register bytes are transfered in target byte order. |
| 14815 | The two nibbles within a register byte are transfered most-significant - |
| 14816 | least-significant. |
| 14817 | |
| 14818 | @multitable @columnfractions .5 .5 |
| 14819 | |
| 14820 | @item MIPS32 |
| 14821 | @tab |
| 14822 | All registers are transfered as thirty-two bit quantities in the order: |
| 14823 | 32 general-purpose; sr; lo; hi; bad; cause; pc; 32 floating-point |
| 14824 | registers; fsr; fir; fp. |
| 14825 | |
| 14826 | @item MIPS64 |
| 14827 | @tab |
| 14828 | All registers are transfered as sixty-four bit quantities (including |
| 14829 | thirty-two bit registers such as @code{sr}). The ordering is the same |
| 14830 | as @code{MIPS32}. |
| 14831 | |
| 14832 | @end multitable |
| 14833 | |
| 14834 | Example sequence of a target being re-started. Notice how the restart |
| 14835 | does not get any direct output: |
| 14836 | |
| 14837 | @example |
| 14838 | <- @code{R00} |
| 14839 | -> @code{+} |
| 14840 | @emph{target restarts} |
| 14841 | <- @code{?} |
| 14842 | -> @code{+} |
| 14843 | -> @code{T001:1234123412341234} |
| 14844 | <- @code{+} |
| 14845 | @end example |
| 14846 | |
| 14847 | Example sequence of a target being stepped by a single instruction: |
| 14848 | |
| 14849 | @example |
| 14850 | <- @code{G1445...} |
| 14851 | -> @code{+} |
| 14852 | <- @code{s} |
| 14853 | -> @code{+} |
| 14854 | @emph{time passes} |
| 14855 | -> @code{T001:1234123412341234} |
| 14856 | <- @code{+} |
| 14857 | <- @code{g} |
| 14858 | -> @code{+} |
| 14859 | -> @code{1455...} |
| 14860 | <- @code{+} |
| 14861 | @end example |
| 14862 | |
| 14863 | |
| 14864 | @include fdl.texi |
| 14865 | |
| 14866 | @node Index |
| 14867 | @unnumbered Index |
| 14868 | |
| 14869 | @printindex cp |
| 14870 | |
| 14871 | @tex |
| 14872 | % I think something like @colophon should be in texinfo. In the |
| 14873 | % meantime: |
| 14874 | \long\def\colophon{\hbox to0pt{}\vfill |
| 14875 | \centerline{The body of this manual is set in} |
| 14876 | \centerline{\fontname\tenrm,} |
| 14877 | \centerline{with headings in {\bf\fontname\tenbf}} |
| 14878 | \centerline{and examples in {\tt\fontname\tentt}.} |
| 14879 | \centerline{{\it\fontname\tenit\/},} |
| 14880 | \centerline{{\bf\fontname\tenbf}, and} |
| 14881 | \centerline{{\sl\fontname\tensl\/}} |
| 14882 | \centerline{are used for emphasis.}\vfill} |
| 14883 | \page\colophon |
| 14884 | % Blame: doc@cygnus.com, 1991. |
| 14885 | @end tex |
| 14886 | |
| 14887 | @bye |