From: Fernando Nasser Date: Fri, 20 Sep 2002 15:07:15 +0000 (+0000) Subject: From 2002-07-02 George Helffrich X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=878854263f6ac589407dc73ea1361d2075b00677;p=binutils-gdb.git From 2002-07-02 George Helffrich * cli/cli-cmds.c (list_command): New function. Implements the new cli edit command. (_init_cli_cmds): Add new command definition. * gdb.1: Document edit command. * doc/gdb.texinfo: Document edit command. --- diff --git a/gdb/ChangeLog b/gdb/ChangeLog index f3cc92b24f1..ec776f7ffed 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,4 +1,13 @@ -2002-09-13 Fernando Nasser +2002-09-20 Fernando Nasser + + From 2002-07-02 George Helffrich + * cli/cli-cmds.c (list_command): New function. Implements the new + cli edit command. + (_init_cli_cmds): Add new command definition. + * gdb.1: Document edit command. + * doc/gdb.texinfo: Document edit command. + +2002-09-20 Fernando Nasser * source.c: Make global variables current_source_symtab and current_source_line static. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 39768cb36fd..ceaa21a14bc 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -31,7 +31,10 @@ @set EDITION Ninth @c !!set GDB manual's revision date -@set DATE December 2001 +@set DATE June 2002 + +@c !!set GDB edit command default editor +@set EDITOR /bin/ex @c THIS MANUAL REQUIRES TEXINFO 4.0 OR LATER. @@ -3926,7 +3929,10 @@ For example: After such a printout, the @code{list} command with no arguments prints ten lines centered on the point of execution in the frame. -@xref{List, ,Printing source lines}. +You can also edit the program at the point of execution with your favorite +editing program by typing @code{edit}. +@xref{List, ,Printing source lines}, +for details. @table @code @kindex down-silently @@ -4033,6 +4039,7 @@ prefer to use Emacs facilities to view source; see @ref{Emacs, ,Using @menu * List:: Printing source lines +* Edit:: Editing source files * Search:: Searching source files * Source Path:: Specifying source directories * Machine Code:: Source and machine code @@ -4155,6 +4162,71 @@ Specifies the line containing the program address @var{address}. @var{address} may be any expression. @end table +@node Edit +@section Editing source files +@cindex editing source files + +@kindex edit +@kindex e @r{(@code{edit})} +To edit the lines in a source file, use the @code{edit} command. +The editing program of your choice +is invoked with the current line set to +the active line in the program. +Alternatively, there are several ways to specify what part of the file you +want to print if you want to see other parts of the program. + +Here are the forms of the @code{edit} command most commonly used: + +@table @code +@item edit +Edit the current source file at the active line number in the program. + +@item edit @var{number} +Edit the current source file with @var{number} as the active line number. + +@item edit @var{function} +Edit the file containing @var{function} at the beginning of its definition. + +@item edit @var{filename}:@var{number} +Specifies line @var{number} in the source file @var{filename}. + +@item edit @var{filename}:@var{function} +Specifies the line that begins the body of the +function @var{function} in the file @var{filename}. You only need the +file name with a function name to avoid ambiguity when there are +identically named functions in different source files. + +@item edit *@var{address} +Specifies the line containing the program address @var{address}. +@var{address} may be any expression. +@end table + +@subsection Choosing your editor +You can customize @value{GDBN} to use any editor you want +@footnote{ +The only restriction is that your editor (say @code{ex}), recognizes the +following command-line syntax: +@example +ex +@var{number} file +@end example +The optional numeric value +@var{number} designates the active line in the file. +}. +By default, it is @value{EDITOR}, but you can change this by setting the +environment variable @code{EDITOR} before using +@value{GDBN}. +For example, to configure @value{GDBN} to use the @code{vi} editor, you +could use these commands with the @code{sh} shell: +@example +EDITOR=/usr/bin/vi +export EDITOR +gdb ... +@end example +or in the @code{csh} shell, +@example +setenv EDITOR /usr/bin/vi +gdb ... +@end example + @node Search @section Searching source files @cindex searching diff --git a/gdb/gdb.1 b/gdb/gdb.1 index 5872f989c64..f3f4bdb2ffd 100644 --- a/gdb/gdb.1 +++ b/gdb/gdb.1 @@ -1,7 +1,7 @@ .\" Copyright 1991, 1999 Free Software Foundation, Inc. .\" See section COPYING for conditions for redistribution .\" $Id$ -.TH gdb 1 "4nov1991" "GNU Tools" "GNU Tools" +.TH gdb 1 "22may2002" "GNU Tools" "GNU Tools" .SH NAME gdb \- The GNU Debugger .SH SYNOPSIS @@ -150,6 +150,12 @@ Execute next program line (after stopping); step \c \& any function calls in the line. .TP +.B edit \fR[\|\fIfile\fB:\fR\|]\fIfunction +look at the program line where it is presently stopped. +.TP +.B list \fR[\|\fIfile\fB:\fR\|]\fIfunction +type the text of the program in the vicinity of where it is presently stopped. +.TP .B step Execute next program line (after stopping); step \c .I into\c