gdbtui - Linux Command

Size: px

Start display at page:

Download "gdbtui - Linux Command"

Angela Hubbard
5 years ago
Views:

1 tui tui - Linux Command -batch -cd= dir -f -b bps -tty= dev -s sym -e prog -se prog -c core cmds -d dir prog core procid]] SYNOPSIS -help-nx-q DESCRIPTION The purpose of a debugger such as GDB is to allow you to see what is â â insideâ â another program while it executesâ or what another going on program was 1 / 6

2 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 behavior. Â 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. Fortran support will be added when a GNU Fortran compiler is ready. GDB is invoked with the shell command. Once started, it reads com- mands from the terminal until you tell it to exit with the GDB command quit. You can get online help from itself by using the command help. You can run 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: program You can also start with both an executable program and a core specified: program core You can, instead, specify a process ID as a second argument, if you want to debug a running process: bt Backtrace: display the program stack. print expr Display the value of an expression. c Continue running your program (after stopping, e.g. at a break- point). next Execute next program line (after stopping); step over any func- tion calls in the line. edit : ] function look at the program line where it is presently stopped. list : ] 2 / 6

3 function type the text of the program in the vicinity of where it is presently stopped. step Execute next program line (after stopping); step into any func- tion calls in the line. help name ] Show information about GDB command name, or general information about using GDB. quit Exit from GDB. For full details on GDB, see Using GDB: A Guide to the GNU Source-Level Debugger, by Richard M. Stallman and Roland H. Pesch. The same text is available online as the entry in the info program. OPTIONS Any arguments other than options specify an executable and core (or process ID); that is, the first argument encountered with no associated option flag is equivalent to a â -se â option, and the second, if any, is equivalent to a â -c â option if itâ s the name of a. Many options have both long and short forms; both are shown here. The long forms are also recognized if you truncate them, so long as enough of the option is present to be unambiguous. (If you prefer, you can flag option arguments with â + â rather than â - â, though we illustrate the more usual convention.) All the options and command line arguments you give are processed in sequential order. The order makes a 3 / 6

4 difference when the â â option is used. -help -h List all options, with brief explanations. -se= Read symbol table from and use it as the executable. -core= dump. -c Use as a core dump to examine. -command=. -directory= directory Execute GDB commands from -d directory Add directory to the path to search for source s. -nx -n Do not execute commands from any â.init â initialization s. Normally, the commands in these s are executed after all the command options and arguments have been processed. -quiet -q 4 / 6

5 â â Quietâ â. Do not print the introductory and copyright mes- sages. These messages are also suppressed in batch mode. -batch Run in batch mode. Exit with status 0 after processing all the command s specified with â â (and â.init â, if not inhib- ited). Exit with nonzero status if an error occurs in executing the GDB commands in the command s. Batch mode may be useful for running GDB as a filter, for exam- ple to download and run a program on another computer; in order to make this more useful, the message Program exited normally. standard, recognizable fashion each time a stack frame is dis- played (which includes each time the program stops). This rec- ognizable format looks like two â 32 â characters, followed by the name, line number and character position separated by colons, and a newline. The Emacs-to-GDB interface program uses the two â 32 â characters as a signal to display the source code for the frame. -b bps Set the line speed (baud rate or bits per second) of any serial interface used by GDB for remote debugging. -tty= device Run using device for your programâ s standard input and output. SEE ALSO â â entry in info ; Using GDB: A Guide to the GNU Source-Level 5 / 6

6 Debugger, Richard M. Stallman and Roland H. Pesch, July COPYING Copyright (c) 1991 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this man- ual into another language, under the above conditions for modified ver- sions, except that this permission notice may be included in transla- tions approved by the Free Software Foundation instead of in the origi- nal English. GNU Tools 22may2002 (1) Linux Help documents. These manual pages will also work for Red Hat 5.2 Man(1) output converted with man2html Joomla SEO powered by JoomSEF 6 / 6

GDB QUICK REFERENCE GDB Version 4

GDB QUICK REFERENCE GDB Version 4 Essential Commands gdb program [core] debug program [using coredump core] b [file:]function run [arglist] bt p expr c n s set breakpoint at function [in file] start your