ronald@UCDAVIS.EDU (10/12/89)
Here is a man page for gdb-3.3. Use it as you see fit (and in good health). ------------------------- cut here -------------------------------------- .TH GDB 1 "30 September 1989" "Version 3.3" .de BP .sp .ti -.2i \(** .. .SH NAME gdb \- GNU project source-level debugger .SH SYNOPSIS .B gdb [ .B \-nx ] [ .B \-q ] [ .B \-batch ] [ .B \-fullname ] [ .B \-se objfil ] [ .B \-c corfil ] [ .B \-x cmdfil ] [ .B \-d directory ] [ objfil [ corfil ]] .SH WARNING This man page is an extract of the documentation of the .I GNU debugger and is limited to the meaning of the options. It is updated only occasionally, because the GNU project does not use nroff. For complete, current documentation, refer to the Info file .B gdb or the DVI file .B gdb.dvi which are made from the Texinfo source file .BR gdb.texinfo . .SH DESCRIPTION The purpose of a debugger such as GDB is to allow you to execute another program while examining what is going on inside it. We call the other program ``your program'' or ``the program being debugged''. .sp GDB can do four kinds of things (plus other things in support of these): .BP Start the program, specifying anything that might affect its behavior. .BP Make the program stop on specified conditions. .BP Examine what has happened, when the program has stopped, so that you can see bugs happen. .BP Change things in the program, so you can correct the effects of one bug and go on to learn about another without having to recompile first. .P GDB can be used to debug programs written in C and C++. Pascal support is being implemented, and Fortran support will be added when a GNU Fortran compiler is written. .SH OPTIONS When you invoke GDB, you can specify arguments telling it what files to operate on and what other things to do. All the options and command line arguments given are processed in sequential order. The order makes a difference when the .B \-x option is used. .TP .B \-nx Do not execute commands from the init files .BR .gdbinit . Normally, the commands in these files are executed after all the command options and arguments have been processed. .TP .B \-q ``Quiet''. Do not print the usual introductory messages. .TP .B \-batch Run in batch mode. Exit with code 0 after processing all the command files specified with .B \-x (and .BR .gdbinit , if not inhibited). Exit with nonzero status if an error occurs in executing the GDB commands in the command files. .TP .B \-fullname This option is used when Emacs runs GDB as a subprocess. It tells GDB to output the full file name and line number in a standard, recognizable fashion each time a stack frame is displayed (which includes each time the program stops). This recognizable format looks like two .B \e032 characters, followed by the file name, line number and character position separated by colons, and a newline. The Emacs-to-GDB interface program uses the two .B \e032 characters as a signal to display the source code for the frame. .TP .BI \-s " objfil" Read symbol table from file .IR objfil . .TP .BI \-e " objfil" Use file .I objfil as the executable file to execute when appropriate, and for examining pure data in conjunction with a core dump. .TP .BI \-se " objfil" Read symbol table from file .I objfil and use it as the executable file. .TP .BI \-c " corfil" Use file .IR corfil as a core dump to examine. .TP .BI \-x " cmdfil" Execute GDB commands from file .IR cmdfil . .TP .BI \-d " directory" Add .I directory to the path to search for source files. .P If there are arguments to GDB that are not options or associated with options, the first one specifies the symbol table and executable file name (as if it were preceded by .BR \-se ) and the second one specifies a core dump file name (as if it were preceded by .BR \-c ). .SH FILES \&.gdbinit GDB initialization file .SH "SEE ALSO" gcc(1), g++(1), a.out(4), core(4), syms(4). .SH BUGS Bugs should be reported to .BR bug-gdb@prep.ai.mit.edu . Bugs tend actually to be fixed if they can be isolated, so it is in your interest to report them in such a way that they can be easily reproduced. .SH COPYING Copyright (c) 1989 Free Software Foundation, Inc. .P 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. .P 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. .P Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. .SH AUTHORS See the GNU GDB Manual for the contributors to GNU GDB. --------------------- cut here-------------------------------------------- -- Ronald Cole | uucp: cvms!ronald voice: +1 916 895 8321 Senior Software Engineer | internet: csusac!cvms!ronald@ucdavis.edu CVM Systems +---------------------------------------------------- "If you can't be good, be careful. If you can't be careful, give me a call."