This action might not be possible to undo. Are you sure you want to continue?
NAME gdb - The GNU Debugger SYNOPSIS gdb [-help] [-nx] [-q] [-batch] [-cd=dir] [-f] [-b bps] [-tty=dev] [-s symfile] [-e prog] [-se prog] [-c core] [-x cmds] [-d dir] [prog [core|procID]] [options] --args prog [arguments]
gdbtui [options] DESCRIPTION The purpose of a debugger such as GDB is to allow you to see what is goi ng on ``inside'' another program while it executesâ or what another program was doing at the moment it crashed. GDB can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act: Â· Start your program, specifying anything that might affect its behavâ ior. Make your program stop on specified conditions. Examine what has happened, when your program has stopped. Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another.
Â· Â· Â·
You can use GDB to debug programs written in C, C++, and Modula-2. Fortr an support will be added when a GNU Fortran compiler is ready. GDB is invoked with the shell command gdb. Once started, it reads comman ds from the terminal until you tell it to exit with the GDB command quit. Y ou can get online help from gdb itself by using the command help. You can run gdb with no arguments or options; but the most usual way to start GDB is with one argument or two, specifying an executable program as the argument: gdb program
step over any functi Continue running your program (after stopping. or general informati on about using GDB. if you want to debug a running process: gdb program 1234 would attach GDB to process 1234 (unless you also have a file named `1234 '. at a brea For full details on GDB.g. list [file:]function type the text of the program in the vicinity of where it is presently stopped.You can also start with both an executable program and a core file spec iâ fied: gdb program core You can. help [name] Show information about GDB command name. quit el Exit from GDB. bt Backtrace: display the program stack. instead. next on calls in the line. see Using GDB: A Guide to the GNU Source-Lev . Here are some of the most frequently needed GDB commands: break [file:]function Set a breakpoint at function (in file). edit [file:]function look at the program line where it is presently stopped. specify a process ID as a second argument. Execute next program line (after stopping). GDB does check for a core file first). run [arglist] Start your program (with arglist. print expr Display the value of an expression. step into any functi Execute next program line (after stopping). e. step on calls in the line. if specified). c kâ point).
though we illustrate the more usual convention. (If you prefer. The long forms are al so recognized if you truncate them. instead of t The order makes a difference when the `-x' option . that is. is equivalent to a `-c' option if it's the name of a file. Exit with nonzero status if an error occurs in executing the G DB commands in the command files. Pesch. in order to ma ke this more useful.Debugger. so long as enough of the option is prese nt to be unambiguous. Many options ha ve both long and short forms. the first argument encountered with no associat ed option flag is equivalent to a `-se' option. OPTIONS The same text Any arguments other than options specify an executable file and core fi le (or process ID). is available online as the gdb entry in the info program. Stallman and Roland H. the message Program exited normally. by Richard M. for example to download and run a program on another computer. both are shown here. -core=FILE Use file file as a core dump to examine.) All the options and command line arguments you give are processed in sequential order.gdbinit'. and the second. (which is ordinarily issued whenever a program running under G DB control terminates) is not issued when running in batch mode. -b bps Set the line speed (baud rate or bits per second) of any seri al interface used by GDB for remote debugging. -batch Run in batch mode. -c FILE. Batch mode may be useful for running GDB as a filter. if not inhibited ). -cd=directory Run GDB using directory as its working directory. if any. you can flag option arguments with ` +' rather than `-'. is used. Exit with status 0 after processing all the co mâ mand files specified with `-x' (and `.
with brief explanations. re câ ognizable fashion each time a stack frame is displayed (whi ch includes each time the program stops). Normally. -f. -tty=device This recognizable form . -n. the commands in these files are executed after all t he command options and arguments have been processed. It tel ls GDB to output the full file name and line number in a standard. -d DIRECTORY. -fullname Emacs sets this option when it runs GDB as a subprocess. -s FILE.gdbinit' initialization file s. -e FILE. -nx Do not execute commands from any `. li ne number and character position separated by colons. q. at looks like two ` 32' characters. -symbols=FILE Read symbol table from file file. and for examining pure data in conjunction with a core dump. followed by the file name. -se=file Read symbol table from file file and use it as the executable file . and a newlin e. -exec=FILE Use file file as the executable file to execute when appropriat e.he current directory. -quiet ``Quiet''. The Emacs-to-GDB interface program uses the two ` 32' characters as a signal to display the source code for the frame. -h. These messages are also suppressed in batch mode. Do not print the introductory and copyright message s. -directory=DIRECTORY Add directory to the path to search for source files. -help List all options.
under the above conditions for modified version s. -tui Run GDB using a text (console) user interface. Pesch. GNU Tools 1) 22may2002 gdb( . Richard M. Stallman and Roland H. Permission is granted to copy and distribute modified versions of this ma nâ ual under the conditions for verbatim copying. COPYING Copyright (c) 1991. SEE ALSO `gdb' entry in info. -command=FILE Execute GDB commands from file file. Inc. Permission is granted to copy and distribute translations of this manu al into another language. -write Enable writing into executable and core files. provided that the enti re resulting derived work is distributed under the terms of a permissi on notice identical to this one. Using GDB: A Guide to the GNU Source-Level Debugge r. --args Pass arguments after the program name to the program when it is ru n. -x FILE. July 1991. 2010 Free Software Foundation.Run using device for your program's standard input and output. Permission is granted to make and distribute verbatim copies of this manu al provided the copyright notice and this permission notice are preserved on all copies. except that this permission notice may be included in translations approv ed by the Free Software Foundation instead of in the original English.