* Patch to gdbmi.texinfo
@ 2000-07-23 9:33 Dmitry S. Sivachenko
2000-07-23 12:18 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Dmitry S. Sivachenko @ 2000-07-23 9:33 UTC (permalink / raw)
To: gdb-patches
Hello!
Please apply this patch to gdbmi.texinfo (this is a patch against
rev. 1.6).
It changes GDB --> @value{GDBN},
gdb --> @value{GDBP} (where appropriate),
and fixes a number of typos.
Thank you in advance,
Dima.
Index: gdbmi.texinfo
===================================================================
RCS file: /home/cvs/en-gdbman/gdbmi.texinfo,v
retrieving revision 1.2
diff -u -r1.2 gdbmi.texinfo
--- gdbmi.texinfo 2000/07/08 16:20:31 1.2
+++ gdbmi.texinfo 2000/07/23 16:28:15
@@ -58,7 +58,7 @@
@unnumberedsec Function and Purpose
@cindex @sc{gdb/mi}, its purpose
-@sc{gdb/mi} is a line based machine oriented text interface to GDB. It is
+@sc{gdb/mi} is a line based machine oriented text interface to @value{GDBN}. It is
specifically intended to support the development of systems which use
the debugger as just one small component of a larger system.
@@ -151,7 +151,7 @@
@item @var{cli-command} @expansion{}
@code{[ @var{token} ] @var{cli-command} @var{nl}}, where
-@var{cli-command} is any existing GDB CLI command.
+@var{cli-command} is any existing @value{GDBN} CLI command.
@item @var{mi-command} @expansion{}
@code{[ @var{token} ] "-" @var{operation} ( " " @var{option} )*
@@ -333,7 +333,7 @@
@item
@cindex log output in @sc{gdb/mi}
-@var{log-stream-output} is output text coming from GDB's internals, for
+@var{log-stream-output} is output text coming from @value{GDBN}'s internals, for
instance messages that should be displayed as part of an error log. All
the log output is prefixed by @samp{&}.
@end itemize
@@ -405,9 +405,9 @@
@cindex compatibility, @sc{gdb/mi} and CLI
@cindex @sc{gdb/mi}, compatibility with CLI
-To help users familiar with GDB's existing CLI interface, @sc{gdb/mi}
+To help users familiar with @value{GDBN}'s existing CLI interface, @sc{gdb/mi}
accepts existing CLI commands. As specified by the syntax, such
-commands can be directly entered into the @sc{gdb/mi} interface and GDB will
+commands can be directly entered into the @sc{gdb/mi} interface and @value{GDBN} will
respond.
This mechanism is provided as an aid to developers of @sc{gdb/mi}
@@ -447,7 +447,7 @@
running.
@item "^error" "," @var{c-string}
-@cindex ^error
+@findex ^error
The operation failed. The @code{@var{c-string}} contains the corresponding
error message.
@end table
@@ -457,13 +457,13 @@
@cindex @sc{gdb/mi}, stream records
@cindex stream records in @sc{gdb/mi}
-GDB internally maintains a number of output streams: the console, the
+@value{GDBN} internally maintains a number of output streams: the console, the
target, and the log. The output intended for each of these streams is
funneled through the @sc{gdb/mi} interface using @dfn{stream records}.
Each stream record begins with a unique @dfn{prefix character} which
identifies its stream (@pxref{GDB/MI Output Syntax, , @sc{gdb/mi} Output
-Syntax}). In addition to the prefix, each stream record contains a
+Syntax}). In addition to the prefix, each stream record contains a
@code{@var{string-output}}. This is either raw text (with an implicit new
line) or a quoted C string (which does not contain an implicit newline).
@@ -477,7 +477,7 @@
target.
@item "&" @var{string-output}
-The LOG stream contains debugging messages being produced by GDB's
+The log stream contains debugging messages being produced by @value{GDBN}'s
internals.
@end table
@@ -512,7 +512,7 @@
@subheading Motivation
-The motivation for this collection of commands
+The motivation for this collection of commands.
@subheading Introduction
@@ -525,12 +525,12 @@
@subsubheading Synopsis
@example
- -command @var{args}...
+ -command @var{args}@dots{}
@end example
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB CLI command.
+The corresponding @value{GDBN} CLI command.
@subsubheading Result
@@ -564,27 +564,27 @@
the @samp{-break-list} command, see the description of the
@samp{-break-list} command below.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{ignore}.
+The corresponding @value{GDBN} command is @samp{ignore}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-break-insert main
^done,bkpt=@{number="1",addr="0x000100d0",file="hello.c",line="5"@}
-(gdb)
+(@value{GDBP})
-break-after 1 3
~
^done
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
addr="0x000100d0",func="main",file="hello.c",line="5",times="0",
ignore="3"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@ignore
@@ -596,7 +596,7 @@
@end ignore
-@subheading -break-condition
+@subheading The -break-condition Command
@findex -break-condition
@subsubheading Synopsis
@@ -610,23 +610,23 @@
@samp{-break-list} output (see the description of the @samp{-break-list}
command below).
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{condition}.
+The corresponding @value{GDBN} command is @samp{condition}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-break-condition 1 1
^done
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
addr="0x000100d0",func="main",file="hello.c",line="5",cond="1",
times="0",ignore="3"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@subheading The @code{-break-delete} Command
@@ -639,22 +639,22 @@
@end example
Delete the breakpoint(s) whose number(s) are specified in the argument
-list. This is obviously reflected in the breakpoint list.
+list. This is obviously reflected in the breakpoint list.
-@subsubheading GDB command
+@subsubheading @value{GDBN} command
-The corresponding GDB command is @samp{delete}.
+The corresponding @value{GDBN} command is @samp{delete}.
@subsubheading Example
@example
-(gdb)
+(@value{GDBP})
-break-delete 1
^done
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{@}
-(gdb)
+(@value{GDBP})
@end example
@subheading The @code{-break-disable} Command
@@ -669,22 +669,22 @@
Disable the named @var{breakpoint}(s). The field @samp{enabled} in the
break list is now set to @samp{n} for the named @var{breakpoint}(s).
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{disable}.
+The corresponding @value{GDBN} command is @samp{disable}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-break-disable 2
^done
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="2",type="breakpoint",disp="keep",enabled="n",
addr="0x000100d0",func="main",file="hello.c",line="5",times="0"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@subheading The @code{-break-enable} Command
@@ -698,22 +698,22 @@
Enable (previously disabled) @var{breakpoint}(s).
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{enable}.
+The corresponding @value{GDBN} command is @samp{enable}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-break-enable 2
^done
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
addr="0x000100d0",func="main",file="hello.c",line="5",times="0"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@subheading The @code{-break-info} Command
@@ -728,9 +728,9 @@
@c REDUNDANT???
Get information about a single breakpoint.
-@subsubheading GDB command
+@subsubheading @value{GDBN} command
-The corresponding GDB command is @samp{info break @var{breakpoint}}.
+The corresponding @value{GDBN} command is @samp{info break @var{breakpoint}}.
@subsubheading Example
N.A.
@@ -786,7 +786,7 @@
@end example
@noindent
-where @var{number} is the GDB number for this breakpoint, @var{funcname}
+where @var{number} is the @value{GDBN} number for this breakpoint, @var{funcname}
is the name of the function where the breakpoint was inserted,
@var{filename} is the name of the source file which contains this
function, and @var{lineno} is the source line number within that file.
@@ -794,32 +794,32 @@
Note: this format is open to change.
@c An out-of-band breakpoint instead of part of the result?
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB commands are @samp{break}, @samp{tbreak},
+The corresponding @value{GDBN} commands are @samp{break}, @samp{tbreak},
@samp{hbreak}, @samp{thbreak}, and @samp{rbreak}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-break-insert main
^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",line="4"@}
-(gdb)
+(@value{GDBP})
-break-insert -t foo
^done,bkpt=@{number="2",addr="0x00010774",file="recursive2.c",line="11"@}
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
addr="0x0001072c", func="main",file="recursive2.c",line="4",times="0"@},
bkpt=@{number="2",type="breakpoint",disp="del",enabled="y",
addr="0x00010774",func="foo",file="recursive2.c",line="11",times="0"@}@}
-(gdb)
+(@value{GDBP})
-break-insert -r foo.*
~int foo(int, int);
^done,bkpt=@{number="3",addr="0x00010774",file="recursive2.c",line="11"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@subheading The @code{-break-list} Command
@@ -848,37 +848,37 @@
@item What
logical location of the breakpoint, expressed by function name, file
name, line number
-@item times
+@item Times
number of times the breakpoint has been hit
@end table
If there are no breakpoints or watchpoints, the BreakpointTable field is
an empty list.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{info break}.
+The corresponding @value{GDBN} command is @samp{info break}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
addr="0x000100d0",func="main",file="hello.c",line="5",times="0"@},
bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
addr="0x00010114",func="foo",file="hello.c",line="13",times="0"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
Here's an example of the result when there are no breakpoints:
@smallexample
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{@}
-(gdb)
+(@value{GDBP})
@end smallexample
@subheading The @code{-break-watch} Command
@@ -902,9 +902,9 @@
Note that @samp{-break-list} will report a single list of watchpoints and
breakpoints inserted.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB commands are @samp{watch}, @samp{awatch}, and
+The corresponding @value{GDBN} commands are @samp{watch}, @samp{awatch}, and
@samp{rwatch}.
@subsubheading Example
@@ -912,41 +912,41 @@
Setting a watchpoint on a variable in the @code{main} function:
@smallexample
-(gdb)
+(@value{GDBP})
-break-watch x
^done,wpt=@{number="2",exp="x"@}
-(gdb)
+(@value{GDBP})
-exec-continue
^running
^done,reason="watchpoint-trigger",wpt=@{number="2",exp="x"@},
value=@{old="-268439212",new="55"@},
frame=@{func="main",args=@{@},file="recursive2.c",line="5"@}
-(gdb)
+(@value{GDBP})
@end smallexample
-Setting a watchpoint on a variable local to a function. GDB will stop
+Setting a watchpoint on a variable local to a function. @value{GDBN} will stop
the program execution twice: first for the variable changing value, then
for the watchpoint going out of scope.
@smallexample
-(gdb)
+(@value{GDBP})
-break-watch C
^done,wpt=@{number="5",exp="C"@}
-(gdb)
+(@value{GDBP})
-exec-continue
^running
^done,reason="watchpoint-trigger",
wpt=@{number="5",exp="C"@},value=@{old="-276895068",new="3"@},
frame=@{func="callee4",args=@{@},
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
-(gdb)
+(@value{GDBP})
-exec-continue
^running
^done,reason="watchpoint-scope",wpnum="5",
frame=@{func="callee3",args=@{@{name="strarg",
value="0x11940 \"A string argument.\""@}@},
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
-(gdb)
+(@value{GDBP})
@end smallexample
Listing breakpoints and watchpoints, at different points in the program
@@ -954,10 +954,10 @@
deleted.
@smallexample
-(gdb)
+(@value{GDBP})
-break-watch C
^done,wpt=@{number="2",exp="C"@}
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
@@ -965,14 +965,14 @@
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"@},
bkpt=@{number="2",type="watchpoint",disp="keep",
enabled="y",addr="",what="C",times="0"@}@}
-(gdb)
+(@value{GDBP})
-exec-continue
^running
^done,reason="watchpoint-trigger",wpt=@{number="2",exp="C"@},
value=@{old="-276895068",new="3"@},
frame=@{func="callee4",args=@{@},
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
@@ -980,20 +980,20 @@
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"@},
bkpt=@{number="2",type="watchpoint",disp="keep",
enabled="y",addr="",what="C",times="-5"@}@}
-(gdb)
+(@value{GDBP})
-exec-continue
^running
^done,reason="watchpoint-scope",wpnum="2",
frame=@{func="callee3",args=@{@{name="strarg",
value="0x11940 \"A string argument.\""@}@},
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
-(gdb)
+(@value{GDBP})
-break-list
^done,BreakpointTable=@{hdr=@{"Num","Type","Disp","Enb","Address","What"@},
bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
addr="0x00010734",func="callee4",
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -1048,7 +1048,7 @@
are displayed.
@item @var{mode}
is either 0 (meaning only disassembly) or 1 (meaning mixed source and
-disassembly)
+disassembly).
@end table
@subsubheading Result
@@ -1065,7 +1065,7 @@
Note that whatever included in the instruction field, is not manipulated
directely by flathead, i.e. it is not possible to adjust its format.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
There's no direct mapping from this command to the CLI.
@@ -1074,7 +1074,7 @@
Disassemble from the current value of @code{$pc} to @code{$pc + 20}:
@smallexample
-(gdb)
+(@value{GDBP})
-data-disassemble -s $pc -e "$pc + 20" -- 0
^done,
asm_insns=@{
@@ -1088,7 +1088,7 @@
inst="sethi %hi(0x11800), %o2"@},
@{address="0x000107d0",func-name="main",offset="20",
inst="or %o2, 0x168, %o4\t! 0x11968 <_lib_version+48>"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
Disassemble the whole @code{main} function. Line 32 is part of
@@ -1103,16 +1103,16 @@
inst="mov 2, %o0"@},
@{address="0x000107c4",func-name="main",offset="8",
inst="sethi %hi(0x11800), %o2"@},
-[...]
+[@dots{}]
@{address="0x0001081c",func-name="main",offset="96",inst="ret "@},
@{address="0x00010820",func-name="main",offset="100",inst="restore "@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
Disassemble 3 instructions from the start of @code{main}:
@smallexample
-(gdb)
+(@value{GDBP})
-data-disassemble -f basics.c -l 32 -n 3 -- 0
^done,asm_insns=@{
@{address="0x000107bc",func-name="main",offset="0",
@@ -1121,13 +1121,13 @@
inst="mov 2, %o0"@},
@{address="0x000107c4",func-name="main",offset="8",
inst="sethi %hi(0x11800), %o2"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
Disassemble 3 instructions from the start of @code{main} in mixed mode:
@smallexample
-(gdb)
+(@value{GDBP})
-data-disassemble -f basics.c -l 32 -n 3 -- 1
^done,asm_insns=@{
src_and_asm_line=@{line="31",
@@ -1143,7 +1143,7 @@
inst="mov 2, %o0"@},
@{address="0x000107c4",func-name="main",offset="8",
inst="sethi %hi(0x11800), %o2"@}@}@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1160,32 +1160,32 @@
inferior function call. The function call will execute synchronously.
If the expression contains spaces, it must be enclosed in double quotes.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB commands are @samp{print}, @samp{output}, and
+The corresponding @value{GDBN} commands are @samp{print}, @samp{output}, and
@samp{call}. In @code{gdbtk} only, there's a corresponding
@samp{gdb_eval} command.
@subsubheading Example
In the following example, the numbers that precede the commands are the
-@dfn{tokens} described in @ref{GDB/MI Command Syntax, , @sc{gdb/mi}
+@dfn{tokens} described in @ref{GDB/MI Command Syntax, ,@sc{gdb/mi}
Command Syntax}. Notice how @sc{gdb/mi} returns the same tokens in its
output.
@smallexample
211-data-evaluate-expression A
211^done,value="1"
-(gdb)
+(@value{GDBP})
311-data-evaluate-expression &A
311^done,value="0xefffeb7c"
-(gdb)
+(@value{GDBP})
411-data-evaluate-expression A+3
411^done,value="4"
-(gdb)
+(@value{GDBP})
511-data-evaluate-expression "A + 3"
511^done,value="4"
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1200,29 +1200,29 @@
Display a list of the registers that have changed.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-GDB doesn't have a direct analog for this command; @code{gdbtk} has the
-corresponding command @samp{gdb_changed_register_list}.
+@value{GDBN} doesn't have a direct analog for this command; @code{gdbtk}
+has the corresponding command @samp{gdb_changed_register_list}.
@subsubheading Example
On a PPC MBX board:
@smallexample
-(gdb)
+(@value{GDBP})
-exec-continue
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="breakpoint-hit",bkptno="1",frame=@{func="main",
args=@{@},file="try.c",line="5"@}
-(gdb)
+(@value{GDBP})
-data-list-changed-registers
^done,changed-registers=@{"0","1","2","4","5","6","7","8","9",
"10","11","13","14","15","16","17","18","19","20","21","22","23",
"24","25","26","27","28","30","31","64","65","66","67","69"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1240,9 +1240,9 @@
integer numbers are given as arguments, it will print a list of the
names of the registers corresponding to the arguments.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-GDB does not have a command which corresponds to
+@value{GDBN} does not have a command which corresponds to
@samp{-data-list-register-names}. In @code{gdbtk} there is a
corresponding command @samp{gdb_regnames}.
@@ -1250,7 +1250,7 @@
For the PPC MBX board:
@smallexample
-(gdb)
+(@value{GDBP})
-data-list-register-names
^done,register-names=@{"r0","r1","r2","r3","r4","r5","r6","r7",
"r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18",
@@ -1259,10 +1259,10 @@
"f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20",
"f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31",
"pc","ps","cr","lr","ctr","xer"@}
-(gdb)
+(@value{GDBP})
-data-list-register-names 1 2 3
^done,register-names=@{"r1","r2","r3"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@subheading The @code{-data-list-register-values} Command
@@ -1296,10 +1296,10 @@
Natural
@end table
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB commands are @samp{info reg}, @samp{info all-reg},
-and (in @code{gdbtk}) @samp{gdb_fetch_registers}.
+The corresponding @value{GDBN} commands are @samp{info reg}, @samp{info
+all-reg}, and (in @code{gdbtk}) @samp{gdb_fetch_registers}.
@subsubheading Example
@@ -1307,11 +1307,11 @@
don't appear in the actual output):
@smallexample
-(gdb)
+(@value{GDBP})
-data-list-register-values r 64 65
^done,register-values=@{@{number="64",value="0xfe00a300"@},
@{number="65",value="0x00029002"@}@}
-(gdb)
+(@value{GDBP})
-data-list-register-values x
^done,register-values=@{@{number="0",value="0xfe0043c8"@},
@{number="1",value="0x3fff88"@},@{number="2",value="0xfffffffe"@},
@@ -1349,7 +1349,7 @@
@{number="65",value="0x29002"@},@{number="66",value="0x202f04b5"@},
@{number="67",value="0xfe0043b0"@},@{number="68",value="0xfe00b3e4"@},
@{number="69",value="0x20002b03"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1375,8 +1375,8 @@
@item @var{word-format}
The format to be used to print the memory words. The notation is the
-same as for GDB's @code{print} command (@pxref{Output Formats, , Output
-formats}).
+same as for @value{GDBN}'s @code{print} command (@pxref{Output Formats,
+,Output formats}).
@item @var{word-size}
The size of each memory word in bytes.
@@ -1410,19 +1410,19 @@
@samp{next-row} and @samp{prev-row}, @samp{next-page} and
@samp{prev-page}.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{x}. @code{gdbtk} has
-@samp{gdb_get_mem} memory read.
+The corresponding @value{GDBN} command is @samp{x}. @code{gdbtk} has
+@samp{gdb_get_mem} memory read command.
@subsubheading Example
Read six bytes of memory starting at @code{bytes+6} but then offset by
-@code{-6} bytes. Format as three rows of two columns. One byte per
+@code{-6} bytes. Format as three rows of two columns. One byte per
word. Display each word in hex.
@smallexample
-(gdb)
+(@value{GDBP})
9-data-read-memory -o -6 -- bytes+6 x 1 3 2
9^done,addr="0x00001390",nr-bytes="6",total-bytes="6",
next-row="0x00001396",prev-row="0x0000138e",next-page="0x00001396",
@@ -1430,20 +1430,20 @@
@{addr="0x00001390",data=@{"0x00","0x01"@}@},
@{addr="0x00001392",data=@{"0x02","0x03"@}@},
@{addr="0x00001394",data=@{"0x04","0x05"@}@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
Read two bytes of memory starting at address @code{shorts + 64} and
display as a single word formatted in decimal.
@smallexample
-(gdb)
+(@value{GDBP})
5-data-read-memory shorts+64 d 2 1 1
5^done,addr="0x00001510",nr-bytes="2",total-bytes="2",
next-row="0x00001512",prev-row="0x0000150e",
next-page="0x00001512",prev-page="0x0000150e",memory=@{
@{addr="0x00001510",data=@{"128"@}@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
Read thirty two bytes of memory starting at @code{bytes+16} and format
@@ -1451,7 +1451,7 @@
used as the non-printable character.
@smallexample
-(gdb)
+(@value{GDBP})
4-data-read-memory bytes+16 x 1 8 4 x
4^done,addr="0x000013a0",nr-bytes="32",total-bytes="32",
next-row="0x000013c0",prev-row="0x0000139c",
@@ -1464,7 +1464,7 @@
@{addr="0x000013b4",data=@{"0x24","0x25","0x26","0x27"@},ascii="$%&'"@},
@{addr="0x000013b8",data=@{"0x28","0x29","0x2a","0x2b"@},ascii="()*+"@},
@{addr="0x000013bc",data=@{"0x2c","0x2d","0x2e","0x2f"@},ascii=",-./"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@subheading The @code{-display-delete} Command
@@ -1478,9 +1478,9 @@
Delete the display @var{number}.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{delete display}.
+The corresponding @value{GDBN} command is @samp{delete display}.
@subsubheading Example
N.A.
@@ -1497,9 +1497,9 @@
Disable display @var{number}.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{disable display}.
+The corresponding @value{GDBN} command is @samp{disable display}.
@subsubheading Example
N.A.
@@ -1516,9 +1516,9 @@
Enable display @var{number}.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{enable display}.
+The corresponding @value{GDBN} command is @samp{enable display}.
@subsubheading Example
N.A.
@@ -1535,9 +1535,9 @@
Display @var{expression} every time the program stops.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{display}.
+The corresponding @value{GDBN} command is @samp{display}.
@subsubheading Example
N.A.
@@ -1554,9 +1554,9 @@
List the displays. Do not show the current values.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{info display}.
+The corresponding @value{GDBN} command is @samp{info display}.
@subsubheading Example
N.A.
@@ -1571,19 +1571,19 @@
-environment-cd @var{pathdir}
@end example
-Set GDB's working directory.
+Set @value{GDBN}'s working directory.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{cd}.
+The corresponding @value{GDBN} command is @samp{cd}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-environment-cd /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1598,17 +1598,17 @@
Add directory @var{pathdir} to beginning of search path for source files.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{dir}.
+The corresponding @value{GDBN} command is @samp{dir}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-environment-directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1623,17 +1623,17 @@
Add directories to beginning of search path for object files.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{path}.
+The corresponding @value{GDBN} command is @samp{path}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-environment-path /kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1648,18 +1648,18 @@
Show the current working directory.
-@subsubheading GDB command
+@subsubheading @value{GDBN} command
-The corresponding GDB command is @samp{pwd}.
+The corresponding @value{GDBN} command is @samp{pwd}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-environment-pwd
~Working directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb.
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -1669,7 +1669,7 @@
@subsubheading Program termination
As a result of execution, the inferior program can run to completion, if
-it doesn't encouter any breakpoints. In this case the ouput will
+it doesn't encouter any breakpoints. In this case the output will
include an exit code, if the program has exited exceptionally.
@subsubheading Examples:
@@ -1678,33 +1678,33 @@
Program exited normally:
@smallexample
-(gdb)
+(@value{GDBP})
-exec-run
^running
-(gdb)
+(@value{GDBP})
x = 55
*stopped,reason="exited-normally"
-(gdb)
+(@value{GDBP})
@end smallexample
@noindent
Program exited exceptionally:
@smallexample
-(gdb)
+(@value{GDBP})
-exec-run
^running
-(gdb)
+(@value{GDBP})
x = 55
*stopped,reason="exited",exit-code="01"
-(gdb)
+(@value{GDBP})
@end smallexample
Another way the program can terminate is if it receives a signal such as
@code{SIGINT}. In this case, @sc{gdb/mi} displays this:
@smallexample
-(gdb)
+(@value{GDBP})
*stopped,reason="exited-signalled",signal-name="SIGINT",
signal-meaning="Interrupt"
@end smallexample
@@ -1721,9 +1721,9 @@
Kill the inferior running program.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{kill}.
+The corresponding @value{GDBN} command is @samp{kill}.
@subsubheading Example
N.A.
@@ -1741,9 +1741,9 @@
Set the inferior program arguments, to be used in the next
@samp{-exec-run}.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{set args}.
+The corresponding @value{GDBN} command is @samp{set args}.
@subsubheading Example
@@ -1763,20 +1763,20 @@
Asynchronous command. Resumes the execution of the inferior program
until a breakpoint is encountered, or until the inferior exits.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB corresponding is @samp{continue}.
+The corresponding @value{GDBN} corresponding is @samp{continue}.
@subsubheading Example
@smallexample
-exec-continue
^running
-(gdb)
+(@value{GDBP})
@@Hello world
*stopped,reason="breakpoint-hit",bkptno="2",frame=@{func="foo",args=@{@},
file="hello.c",line="13"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1793,9 +1793,9 @@
until the current function is exited. Displays the results returned by
the function.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{finish}.
+The corresponding @value{GDBN} command is @samp{finish}.
@subsubheading Example
@@ -1804,25 +1804,26 @@
@smallexample
-exec-finish
^running
-(gdb)
+(@value{GDBP})
@@hello from foo
*stopped,reason="function-finished",frame=@{func="main",args=@{@},
file="hello.c",line="7"@}
-(gdb)
+(@value{GDBP})
@end smallexample
-Function returning other than @code{void}. The name of the internal GDB
-variable storing the result is printed, together with the value itself.
+Function returning other than @code{void}. The name of the internal
+@value{GDBN} variable storing the result is printed, together with the
+value itself.
@smallexample
-exec-finish
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="function-finished",frame=@{addr="0x000107b0",func="foo",
args=@{@{name="a",value="1"@},@{name="b",value="9"@}@},
file="recursive2.c",line="14"@},
gdb-result-var="$1",return-value="0"
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1835,35 +1836,35 @@
-exec-interrupt
@end example
-Asynchronous command. Interrupts the background execution of the target.
+Asynchronous command. Interrupts the background execution of the target.
Note how the token associated with the stop message is the one for the
execution command that has been interrupted. The token for the interrupt
-itself only appears in the '^done' output. If the user is trying to
+itself only appears in the '@code{^done}' output. If the user is trying to
interrupt a non-running program, an error message will be printed.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{interrupt}.
+The corresponding @value{GDBN} command is @samp{interrupt}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
111-exec-continue
111^running
-(gdb)
+(@value{GDBP})
222-exec-interrupt
222^done
-(gdb)
+(@value{GDBP})
111*stopped,signal-name="SIGINT",signal-meaning="Interrupt",
frame=@{addr="0x00010140",func="foo",args=@{@},file="try.c",line="13"@}
-(gdb)
+(@value{GDBP})
-(gdb)
+(@value{GDBP})
-exec-interrupt
^error,msg="mi_cmd_exec_interrupt: Inferior not executing."
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1879,18 +1880,18 @@
Asynchronous command. Resumes execution of the inferior program, stopping
when the beginning of the next source line is reached.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{next}.
+The corresponding @value{GDBN} command is @samp{next}.
@subsubheading Example
@smallexample
-exec-next
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="end-stepping-range",line="8",file="hello.c"
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1908,21 +1909,21 @@
the program stops at an instruction in the middle of a source line, the
address will be printed as well.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{nexti}.
+The corresponding @value{GDBN} command is @samp{nexti}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-exec-next-instruction
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="end-stepping-range",
addr="0x000100d4",line="5",file="hello.c"
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1938,34 +1939,34 @@
Makes current function return immediately. Doesn't execute the inferior.
Displays the new current frame.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{return}.
+The corresponding @value{GDBN} command is @samp{return}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
200-break-insert callee4
200^done,bkpt=@{number="1",addr="0x00010734",
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}
-(gdb)
+(@value{GDBP})
000-exec-run
000^running
-(gdb)
+(@value{GDBP})
000*stopped,reason="breakpoint-hit",bkptno="1",
frame=@{func="callee4",args=@{@},
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}
-(gdb)
+(@value{GDBP})
205-break-delete
205^done
-(gdb)
+(@value{GDBP})
111-exec-return
111^done,frame=@{level="0 ",func="callee3",
args=@{@{name="strarg",
value="0x11940 \"A string argument.\""@}@},
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -1982,23 +1983,23 @@
beginning. The inferior executes until either a breakpoint is
encountered or the program exits.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{run}.
+The corresponding @value{GDBN} command is @samp{run}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-break-insert main
^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",line="4"@}
-(gdb)
+(@value{GDBP})
-exec-run
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="breakpoint-hit",bkptno="1",
frame=@{func="main",args=@{@},file="recursive2.c",line="4"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -2013,9 +2014,9 @@
Print the arguments of the program.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{show args}.
+The corresponding @value{GDBN} command is @samp{show args}.
@subsubheading Example
N.A.
@@ -2036,9 +2037,9 @@
source line is not a function call. If it is, stop at the first
instruction of the called function.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{step}.
+The corresponding @value{GDBN} command is @samp{step}.
@subsubheading Example
@@ -2047,11 +2048,11 @@
@smallexample
-exec-step
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="end-stepping-range",
frame=@{func="foo",args=@{@{name="a",value="10"@},
@{name="b",value="0"@}@},file="recursive2.c",line="11"@}
-(gdb)
+(@value{GDBP})
@end smallexample
Regular stepping:
@@ -2059,9 +2060,9 @@
@smallexample
-exec-step
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="end-stepping-range",line="14",file="recursive2.c"
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -2075,33 +2076,33 @@
@end example
Asynchronous command. Resumes the inferior which executes one machine
-instruction. The output, once GDB has stopped, will vary depending on
+instruction. The output, once @value{GDBN} has stopped, will vary depending on
whether we have stopped in the middle of a source line or not. In the
former case, the address at which the program stopped will be printed as
well.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{stepi}.
+The corresponding @value{GDBN} command is @samp{stepi}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-exec-step-instruction
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="end-stepping-range",
frame=@{func="foo",args=@{@},file="try.c",line="10"@}
-(gdb)
+(@value{GDBP})
-exec-step-instruction
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="end-stepping-range",
frame=@{addr="0x000100f4",func="foo",args=@{@},file="try.c",line="10"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -2119,21 +2120,21 @@
executes until a source line greater than the current one is reached.
The reason for stopping in this case will be ``location-reached''.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{until}.
+The corresponding @value{GDBN} command is @samp{until}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-exec-until recursive2.c:6
^running
-(gdb)
+(@value{GDBP})
x = 55
*stopped,reason="location-reached",frame=@{func="main",args=@{@},
file="recursive2.c",line="6"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@ignore
@@ -2154,21 +2155,21 @@
Specify the executable file to be debugged. This file is the one from
which the symbol table is also read. If no file is specified, the
command clears the executable and symbol information. If breakpoints
-are set when using this command with no arguments, gdb will produce
+are set when using this command with no arguments, @value{GDBN} will produce
error messages. Otherwise, no output is produced, except a completion
notification.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{file}.
+The corresponding @value{GDBN} command is @samp{file}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -2183,21 +2184,21 @@
Specify the executable file to be debugged. Unlike
@samp{-file-exec-and-symbols}, the symbol table is @emph{not} read
-from this file. If used without argument, GDB clears the information
+from this file. If used without argument, @value{GDBN} clears the information
about the executable file. No output is produced, except a completion
notification.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{exec-file}.
+The corresponding @value{GDBN} command is @samp{exec-file}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-file-exec-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -2212,9 +2213,9 @@
List the sections of the current executable file.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The GDB command @samp{info file} shows, among the rest, the same
+The @value{GDBN} command @samp{info file} shows, among the rest, the same
information as this command. @code{gdbtk} has a corresponding command
@samp{gdb_load_info}.
@@ -2233,9 +2234,9 @@
List the source files for the current executable.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-There's no GDB command which directly corresponds to this one.
+There's no @value{GDBN} command which directly corresponds to this one.
@code{gdbtk} has an analogous command @samp{gdb_listfiles}.
@subsubheading Example
@@ -2253,9 +2254,9 @@
List the shared libraries in the program.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{info shared}.
+The corresponding @value{GDBN} command is @samp{info shared}.
@subsubheading Example
N.A.
@@ -2272,9 +2273,9 @@
List symbol files.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{info file} (part of it).
+The corresponding @value{GDBN} command is @samp{info file} (part of it).
@subsubheading Example
N.A.
@@ -2290,25 +2291,25 @@
@end example
Read symbol table info from the specified @var{file} argument. When
-used without arguments, clears GDB's symbol table info. No output is
+used without arguments, clears @value{GDBN}'s symbol table info. No output is
produced, except for a completion notification.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{symbol-file}.
+The corresponding @value{GDBN} command is @samp{symbol-file}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-file-symbol-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@node GDB/MI Miscellaneous Commands
-@section Miscellaneous GDB commands in @sc{gdb/mi}
+@section Miscellaneous @value{GDBN} commands in @sc{gdb/mi}
@c @subheading -gdb-complete
@@ -2321,16 +2322,16 @@
-gdb-exit
@end example
-Exit GDB immediately.
+Exit @value{GDBN} immediately.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
Approximately corresponds to @samp{quit}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-gdb-exit
@end smallexample
@@ -2343,20 +2344,20 @@
-gdb-set
@end example
-Set an internal GDB variable.
+Set an internal @value{GDBN} variable.
@c IS THIS A DOLLAR VARIABLE? OR SOMETHING LIKE ANNOTATE ?????
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{set}.
+The corresponding @value{GDBN} command is @samp{set}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-gdb-set $foo=3
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -2369,19 +2370,19 @@
-gdb-show
@end example
-Show the current value of a GDB variable.
+Show the current value of a @value{GDBN} variable.
-@subsubheading GDB command
+@subsubheading @value{GDBN} command
-The corresponding GDB command is @samp{show}.
+The corresponding @value{GDBN} command is @samp{show}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-gdb-show annotate
^done,value="0"
-(gdb)
+(@value{GDBP})
@end smallexample
@c @subheading -gdb-source
@@ -2396,11 +2397,11 @@
-gdb-version
@end example
-Show version information for GDB. Used mostly in testing.
+Show version information for @value{GDBN}. Used mostly in testing.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-There's no equivalent GDB command. GDB by default shows this
+There's no equivalent @value{GDBN} command. @value{GDBN} by default shows this
information when you start an interactive session.
@subsubheading Example
@@ -2408,7 +2409,7 @@
@c This example modifies the actual output from GDB to avoid overfull
@c box in TeX.
@smallexample
-(gdb)
+(@value{GDBP})
-gdb-version
~GNU gdb 5.2.1
~Copyright 2000 Free Software Foundation, Inc.
@@ -2421,7 +2422,7 @@
~This GDB was configured as
"--host=sparc-sun-solaris2.5.1 --target=ppc-eabi".
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@ignore
@@ -2489,9 +2490,9 @@
Get info on the current frame.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{info frame} or @samp{frame}
+The corresponding @value{GDBN} command is @samp{info frame} or @samp{frame}
(without arguments).
@subsubheading Example
@@ -2509,31 +2510,31 @@
Return the depth of the stack. If the integer argument @var{max-depth}
is specified, do not count beyond @var{max-depth} frames.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-There's no equivalent GDB command.
+There's no equivalent @value{GDBN} command.
@subsubheading Example
For a stack with frame levels 0 through 11:
@smallexample
-(gdb)
+(@value{GDBP})
-stack-info-depth
^done,depth="12"
-(gdb)
+(@value{GDBP})
-stack-info-depth 4
^done,depth="4"
-(gdb)
+(@value{GDBP})
-stack-info-depth 12
^done,depth="12"
-(gdb)
+(@value{GDBP})
-stack-info-depth 11
^done,depth="11"
-(gdb)
+(@value{GDBP})
-stack-info-depth 13
^done,depth="12"
-(gdb)
+(@value{GDBP})
@end smallexample
@subheading The @code{-stack-list-arguments} Command
@@ -2555,16 +2556,16 @@
0 means that only the names of the arguments are listed, a value of 1
means that both names and values of the arguments are printed.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-GDB does not have an equivalent command. @code{gdbtk} has a
+@value{GDBN} does not have an equivalent command. @code{gdbtk} has a
@samp{gdb_get_args} command which partially overlaps with the
functionality of @samp{-stack-list-arguments}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-stack-list-frames
^done,
stack=@{
@@ -2578,7 +2579,7 @@
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="27"@},
frame=@{level="4 ",addr="0x000107e0",func="main",
file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="32"@}@}
-(gdb)
+(@value{GDBP})
-stack-list-arguments 0
^done,
stack-args=@{
@@ -2587,7 +2588,7 @@
frame=@{level="2",args=@{name="intarg",name="strarg"@}@},
frame=@{level="3",args=@{name="intarg",name="strarg",name="fltarg"@}@},
frame=@{level="4",args=@{@}@}@}
-(gdb)
+(@value{GDBP})
-stack-list-arguments 1
^done,
stack-args=@{
@@ -2602,15 +2603,15 @@
@{name="strarg",value="0x11940 \"A string argument.\""@},
@{name="fltarg",value="3.5"@}@}@},
frame=@{level="4",args=@{@}@}@}
-(gdb)
+(@value{GDBP})
-stack-list-arguments 0 2 2
^done,stack-args=@{frame=@{level="2",args=@{name="intarg",name="strarg"@}@}@}
-(gdb)
+(@value{GDBP})
-stack-list-arguments 1 2 2
^done,stack-args=@{frame=@{level="2",
args=@{@{name="intarg",value="2"@},
@{name="strarg",value="0x11940 \"A string argument.\""@}@}@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@c @subheading -stack-list-exception-handlers
@@ -2646,16 +2647,16 @@
levels are between the two arguments (inclusive). If the two arguments
are equal, it shows the single frame at the corresponding level.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB commands are @samp{backtrace} and @samp{where}.
+The corresponding @value{GDBN} commands are @samp{backtrace} and @samp{where}.
@subsubheading Example
Full stack backtrace:
@smallexample
-(gdb)
+(@value{GDBP})
-stack-list-frames
^done,stack=
@{frame=@{level="0 ",addr="0x0001076c",func="foo",
@@ -2682,13 +2683,13 @@
file="recursive2.c",line="14"@},
frame=@{level="11",addr="0x00010738",func="main",
file="recursive2.c",line="4"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
-Show frames between low_frame and high_frame:
+Show frames between @var{low_frame} and @var{high_frame}:
@smallexample
-(gdb)
+(@value{GDBP})
-stack-list-frames 3 5
^done,stack=
@{frame=@{level="3 ",addr="0x000107a4",func="foo",
@@ -2697,18 +2698,18 @@
file="recursive2.c",line="14"@},
frame=@{level="5 ",addr="0x000107a4",func="foo",
file="recursive2.c",line="14"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
Show a single frame:
@smallexample
-(gdb)
+(@value{GDBP})
-stack-list-frames 3 3
^done,stack=
@{frame=@{level="3 ",addr="0x000107a4",func="foo",
file="recursive2.c",line="14"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -2725,21 +2726,21 @@
argument of 0 prints only the names of the variables, with argument of 1
prints also their values.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-@samp{info locals} in GDB, @samp{gdb_get_locals} in @code{gdbtk}.
+@samp{info locals} in @value{GDBN}, @samp{gdb_get_locals} in @code{gdbtk}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-stack-list-locals 0
^done,locals=@{name="A",name="B",name="C"@}
-(gdb)
+(@value{GDBP})
-stack-list-locals 1
^done,locals=@{@{name="A",value="1"@},@{name="B",value="2"@},
@{name="C",value="3"@}@}
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -2755,18 +2756,18 @@
Change the current frame. Select a different frame @var{framenum} on
the stack.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB commands are @samp{frame}, @samp{up}, @samp{down},
-@samp{select-frame}, @samp{up-silent}, and @samp{down-silent}.
+The corresponding @value{GDBN} commands are @samp{frame}, @samp{up},
+@samp{down}, @samp{select-frame}, @samp{up-silent}, and @samp{down-silent}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-stack-select-frame 2
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -2785,9 +2786,9 @@
Describe where @var{symbol} is stored.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{info address}.
+The corresponding @value{GDBN} command is @samp{info address}.
@subsubheading Example
N.A.
@@ -2804,10 +2805,10 @@
Show the file for the symbol.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-There's no equivalent GDB command. @code{gdbtk} has
-@samp{gdb_filnd_file}.
+There's no equivalent @value{GDBN} command. @code{gdbtk} has
+@samp{gdb_find_file}.
@subsubheading Example
N.A.
@@ -2824,7 +2825,7 @@
Show which function the symbol lives in.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
@samp{gdb_get_function} in @code{gdbtk}.
@@ -2843,10 +2844,10 @@
Show the core addresses of the code for a source line.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB comamnd is @samp{info line}. @code{gdbtk} has the
-@samp{gdb_get_line} @samp{gdb_get_file} commands.
+The corresponding @value{GDBN} comamnd is @samp{info line}.
+@code{gdbtk} has the @samp{gdb_get_line} and @samp{gdb_get_file} commands.
@subsubheading Example
N.A.
@@ -2863,9 +2864,9 @@
Describe what symbol is at location @var{addr}.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{info symbol}.
+The corresponding @value{GDBN} command is @samp{info symbol}.
@subsubheading Example
N.A.
@@ -2882,10 +2883,10 @@
List the functions in the executable.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-@samp{info functions} in GDB, @samp{gdb_listfunc} @samp{gdb_search} in
-@code{gdbtk}.
+@samp{info functions} in @value{GDBN}, @samp{gdb_listfunc} and
+@samp{gdb_search} in @code{gdbtk}.
@subsubheading Example
N.A.
@@ -2902,9 +2903,9 @@
List all the type names.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding commands are @samp{info types} in GDB,
+The corresponding commands are @samp{info types} in @value{GDBN},
@samp{gdb_search} in @code{gdbtk}.
@subsubheading Example
@@ -2922,9 +2923,9 @@
List all the global and static variable names.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-@samp{info variables} in GDB, @samp{gdb_search} in @code{gdbtk}.
+@samp{info variables} in @value{GDBN}, @samp{gdb_search} in @code{gdbtk}.
@subsubheading Example
N.A.
@@ -2939,7 +2940,7 @@
-symbol-locate
@end example
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
@samp{gdb_loc} in @code{gdbtk}.
@@ -2958,9 +2959,9 @@
Show type of @var{variable}.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{ptype}, @code{gdbtk} has
+The corresponding @value{GDBN} command is @samp{ptype}, @code{gdbtk} has
@samp{gdb_obj_variable}.
@subsubheading Example
@@ -2981,11 +2982,11 @@
-target-attach @var{pid} | @var{file}
@end example
-Attach to a process @var{pid} or a file @var{file} outside of GDB.
+Attach to a process @var{pid} or a file @var{file} outside of @value{GDBN}.
-@subsubheading GDB command
+@subsubheading @value{GDBN} command
-The corresponding GDB command is @samp{attach}.
+The corresponding @value{GDBN} command is @samp{attach}.
@subsubheading Example
N.A.
@@ -3003,9 +3004,9 @@
Compare data of section @var{section} on target to the exec file.
Without the argument, all sections are compared.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The GDB equivalent is @samp{compare-sections}.
+The @value{GDBN} equivalent is @samp{compare-sections}.
@subsubheading Example
N.A.
@@ -3022,17 +3023,17 @@
Disconnect from the remote target. There's no output.
-@subsubheading GDB command
+@subsubheading @value{GDBN} command
-The corresponding GDB command is @samp{detach}.
+The corresponding @value{GDBN} command is @samp{detach}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-target-detach
^done
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -3078,11 +3079,11 @@
@end table
@noindent
-At the end, a summary is printed.
+At the end, a summary is printed.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{load}.
+The corresponding @value{GDBN} command is @samp{load}.
@subsubheading Example
@@ -3090,7 +3091,7 @@
have been broken down so that they can fit onto a page.
@smallexample
-(gdb)
+(@value{GDBP})
-target-download
+download,@{section=".text",section-size="6668",total-size="9880"@}
+download,@{section=".text",section-sent="512",section-size="6668",
@@ -3136,7 +3137,7 @@
total-sent="9796",total-size="9880"@}
^done,address="0x10004",load-size="9880",transfer-rate="6586",
write-rate="429"
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -3152,9 +3153,9 @@
Provide information on the state of the target (whether it is running or
not, for instance).
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-There's no equivalent GDB command.
+There's no equivalent @value{GDBN} command.
@subsubheading Example
N.A.
@@ -3171,9 +3172,9 @@
List the possible targets to connect to.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{help target}.
+The corresponding @value{GDBN} command is @samp{help target}.
@subsubheading Example
N.A.
@@ -3190,7 +3191,7 @@
Describe the current target.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
The corresponding information is printed by @samp{info file} (among
other things).
@@ -3210,7 +3211,7 @@
@c ????
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
No equivalent.
@@ -3224,10 +3225,10 @@
@subsubheading Synopsis
@example
- -target-select @var{type} @var{parameters ...}
+ -target-select @var{type} @var{parameters @dots{}}
@end example
-Connect GDB to the remote target. This command takes two args:
+Connect @value{GDBN} to the remote target. This command takes two args:
@table @samp
@item @var{type}
@@ -3245,17 +3246,17 @@
args=@{@var{arg list}@}
@end smallexample
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{target}.
+The corresponding @value{GDBN} command is @samp{target}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-target-select async /dev/ttya
^connected,addr="0xfe00a300",func="??",args=@{@}
-(gdb)
+(@value{GDBP})
@end smallexample
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -3272,7 +3273,7 @@
-thread-info
@end example
-@subsubheading GDB command
+@subsubheading @value{GDBN} command
No equivalent.
@@ -3289,9 +3290,9 @@
-thread-list-all-threads
@end example
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The equivalent GDB command is @samp{info threads}.
+The equivalent @value{GDBN} command is @samp{info threads}.
@subsubheading Example
N.A.
@@ -3306,10 +3307,10 @@
-thread-list-ids
@end example
-Produces a list of the currently known gdb thread ids. At the end of the
-list it also prints the total number of such threads.
+Produces a list of the currently known @value{GDBN} thread ids. At the
+end of the list it also prints the total number of such threads.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
Part of @samp{info threads} supplies the same information.
@@ -3318,21 +3319,21 @@
No threads present, besides the main process.
@smallexample
-(gdb)
+(@value{GDBP})
-thread-list-ids
^done,thread-ids=@{@},number-of-threads="0"
-(gdb)
+(@value{GDBP})
@end smallexample
Several threads.
@smallexample
-(gdb)
+(@value{GDBP})
-thread-list-ids
^done,thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@},
number-of-threads="3"
-(gdb)
+(@value{GDBP})
@end smallexample
@@ -3348,31 +3349,31 @@
Make @var{threadnum} the current thread. It prints the number of the new
current thread, and the topmost frame for that thread.
-@subsubheading GDB Command
+@subsubheading @value{GDBN} Command
-The corresponding GDB command is @samp{thread}.
+The corresponding @value{GDBN} command is @samp{thread}.
@subsubheading Example
@smallexample
-(gdb)
+(@value{GDBP})
-exec-next
^running
-(gdb)
+(@value{GDBP})
*stopped,reason="end-stepping-range",thread-id="2",line="187",
file="../../../devo/gdb/testsuite/gdb.threads/linux-dp.c"
-(gdb)
+(@value{GDBP})
-thread-list-ids
^done,
thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@},
number-of-threads="3"
-(gdb)
+(@value{GDBP})
-thread-select 3
^done,new-thread-id="3",
frame=@{level="0 ",func="vprintf",
args=@{@{name="format",value="0x8048e9c \"%*s%c %d %c\\n\""@},
@{name="arg",value="0x2"@}@},file="vprintf.c",line="31"@}
-(gdb)
+(@value{GDBP})
@end smallexample
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -3435,7 +3436,7 @@
@end enumerate
The original interface was designed to be used by Tcl code, so it was
-slightly changed so it could be used through flathead. This document
+slightly changed so it could be used through flathead. This section
describes the flathead operations that will be available and gives some
hints about their use.
@@ -3551,7 +3552,7 @@
This operation returns the name, number of children and the type of the
object created. Type is returned as a string as the ones generated by
-the GDB CLI:
+the @value{GDBN} CLI:
@example
name="@var{name}",numchild="N",type="@var{type}"
@@ -3652,7 +3653,8 @@
@end example
Returns the type of the specified variable @var{name}. The type is
-returned as a string in the same format as it is output by the GDB CLI:
+returned as a string in the same format as it is output by the
+@value{GDBN} CLI:
@example
type=@var{typename}
@@ -3766,7 +3768,7 @@
The output from @sc{gdb/mi} consists of zero or more out-of-band records
optionally followed by a single result record, the result record being
for the most recent command input. The sequence is terminated by
-``(gdb)''.
+``(@value{GDBP})''.
Asynchronous @sc{gdb/mi} output is similar.
@@ -3775,7 +3777,7 @@
@table @code
@item @var{output} @expansion{}
-@{ @var{out-of-band-record} @} @code{[} @var{result-record} @code{]} "(gdb)" @var{nl}
+@{ @var{out-of-band-record} @} @code{[} @var{result-record} @code{]} "(@value{GDBP})" @var{nl}
@item @var{result-record} @expansion{}
@code{[} @var{token} @code{]} "^" @var{result-class} @{ "," @var{result} @} @var{nl}
@@ -3889,9 +3891,9 @@
All the target output is prefixed by the prefix ``@@''.
@item
-@var{log-stream-output} is output text coming from GDB's internals, for
-instance messages that should be displayed as part of an error log. All
-the log output is prefixed by the prefix ``&''.
+@var{log-stream-output} is output text coming from @value{GDBN}'s
+internals, for instance messages that should be displayed as part of an
+error log. All the log output is prefixed by the prefix ``&''.
@end itemize
From msokolov@ivan.Harhan.ORG Sun Jul 23 09:44:00 2000
From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: binutils@sources.redhat.com, gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: PATCH to top level: don't use dirname in configure
Date: Sun, 23 Jul 2000 09:44:00 -0000
Message-id: <0007231642.AA21279@ivan.Harhan.ORG>
X-SW-Source: 2000-07/msg00239.html
Content-length: 1682
Jeffrey A Law <law@cygnus.com> wrote:
> ## this sed command emulates the dirname command
> dstdir=`echo $dst | sed -e 's,[^/]*$,,;s,/$,,;s,^$,.,'`
>
> [...]
>
> Michael -- can you verify the sed command I provided above does the right
> thing for you?
Yes, it does.
So would you like a patch like the one below?
--
Michael Sokolov Harhan Engineering Laboratory
Public Service Agent International Free Computing Task Force
International Engineering and Science Task Force
615 N GOOD LATIMER EXPY STE #4
DALLAS TX 75204-5852 USA
Phone: +1-214-824-7693 (Harhan Eng Lab office)
E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)
2000-07-23 Michael Sokolov <msokolov@ivan.Harhan.ORG>
* configure (topsrcdir): Don't use dirname.
Index: configure
===================================================================
RCS file: /cvs/src/src/configure,v
retrieving revision 1.10
diff -c -r1.10 configure
*** configure 2000/07/22 08:20:10 1.10
--- configure 2000/07/23 16:37:44
***************
*** 518,524 ****
configsub=`echo ${progname} | sed 's/configure$/config.sub/'`
moveifchange=`echo ${progname} | sed 's/configure$/move-if-change/'`
! topsrcdir=`cd \`dirname ${progname}\`; pwd`
# this is a hack. sun4 must always be a valid host alias or this will fail.
--- 518,525 ----
configsub=`echo ${progname} | sed 's/configure$/config.sub/'`
moveifchange=`echo ${progname} | sed 's/configure$/move-if-change/'`
! ## the sed command below emulates the dirname command
! topsrcdir=`cd \`echo ${progname} | sed -e 's,[^/]*$,,;s,/$,,;s,^$,.,'\`; pwd`
# this is a hack. sun4 must always be a valid host alias or this will fail.
From law@cygnus.com Sun Jul 23 10:43:00 2000
From: Jeffrey A Law <law@cygnus.com>
To: msokolov@ivan.Harhan.ORG (Michael Sokolov)
Cc: binutils@sources.redhat.com, gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: PATCH to top level: don't use dirname in configure
Date: Sun, 23 Jul 2000 10:43:00 -0000
Message-id: <13150.964374198@upchuck>
References: <0007231642.AA21279@ivan.Harhan.ORG>
X-SW-Source: 2000-07/msg00240.html
Content-length: 956
In message < 0007231642.AA21279@ivan.Harhan.ORG >you write:
> Jeffrey A Law <law@cygnus.com> wrote:
>
> > ## this sed command emulates the dirname command
> > dstdir=`echo $dst | sed -e 's,[^/]*$,,;s,/$,,;s,^$,.,'`
> >
> > [...]
> >
> > Michael -- can you verify the sed command I provided above does the right
> > thing for you?
>
> Yes, it does.
>
> So would you like a patch like the one below?
>
> --
> Michael Sokolov Harhan Engineering Laboratory
> Public Service Agent International Free Computing Task Force
> International Engineering and Science Task Force
> 615 N GOOD LATIMER EXPY STE #4
> DALLAS TX 75204-5852 USA
>
> Phone: +1-214-824-7693 (Harhan Eng Lab office)
> E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)
>
> 2000-07-23 Michael Sokolov <msokolov@ivan.Harhan.ORG>
>
> * configure (topsrcdir): Don't use dirname.
Thanks. Installed.
jeff
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Patch to gdbmi.texinfo
2000-07-23 9:33 Patch to gdbmi.texinfo Dmitry S. Sivachenko
@ 2000-07-23 12:18 ` Eli Zaretskii
0 siblings, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2000-07-23 12:18 UTC (permalink / raw)
To: Dmitry S. Sivachenko; +Cc: gdb-patches
> Date: Sun, 23 Jul 2000 20:32:56 +0400 (MSD)
> From: "Dmitry S. Sivachenko" <dima@Chg.RU>
>
> Please apply this patch to gdbmi.texinfo (this is a patch against
> rev. 1.6).
>
> It changes GDB --> @value{GDBN},
> gdb --> @value{GDBP} (where appropriate),
> and fixes a number of typos.
Thanks, I will apply them.
However, in the future please don't mix mechanistic string-replace
type of changes with real patches which change markup or content.
Like this, for instance:
-@cindex ^error
+@findex ^error
It is very easy to miss such real changes in the middle of gobs of
boring replacements, and fail to consider them. Calling such changes
``typos'' is not really accurate, either ;-).
From dima@Chg.RU Sun Jul 23 12:30:00 2000
From: Dmitry Sivachenko <dima@Chg.RU>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re[2]: Patch to gdbmi.texinfo
Date: Sun, 23 Jul 2000 12:30:00 -0000
Message-id: <9810414720.20000723232700@Chg.RU>
References: <200007231632.UAA48345@chg.ru> <200007231918.PAA13698@indy.delorie.com>
X-SW-Source: 2000-07/msg00242.html
Content-length: 910
Hello Eli,
Sunday, July 23, 2000, 11:18:29 PM, you wrote:
>> Date: Sun, 23 Jul 2000 20:32:56 +0400 (MSD)
>> From: "Dmitry S. Sivachenko" <dima@Chg.RU>
>>
>> Please apply this patch to gdbmi.texinfo (this is a patch against
>> rev. 1.6).
>>
>> It changes GDB --> @value{GDBN},
>> gdb --> @value{GDBP} (where appropriate),
>> and fixes a number of typos.
EZ> Thanks, I will apply them.
EZ> However, in the future please don't mix mechanistic string-replace
EZ> type of changes with real patches which change markup or content.
EZ> Like this, for instance:
EZ> -@cindex ^error
EZ> +@findex ^error
EZ> It is very easy to miss such real changes in the middle of gobs of
EZ> boring replacements, and fail to consider them. Calling such changes
EZ> ``typos'' is not really accurate, either ;-).
OK, thanks for your hints!
--
Best regards,
Dmitry mailto:dima@Chg.RU
^ permalink raw reply [flat|nested] 4+ messages in thread
* Patch to gdbmi.texinfo
@ 2000-08-21 13:03 Dmitry S. Sivachenko
2000-08-23 3:49 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Dmitry S. Sivachenko @ 2000-08-21 13:03 UTC (permalink / raw)
To: gdb-patches
Hello!
Please apply this patch to gdbmi.texinfo.
It was made agaist latest revision of gdbmi.texinfo.
It fixes several typos and markup bugs, missed by me in my previous patch.
Thank you in advance,
Dima.
Index: gdbmi.texinfo
===================================================================
RCS file: /home/cvs/en-gdbman/gdbmi.texinfo,v
retrieving revision 1.3
diff -u -r1.3 gdbmi.texinfo
--- gdbmi.texinfo 2000/07/29 14:29:42 1.3
+++ gdbmi.texinfo 2000/08/19 12:05:07
@@ -158,7 +158,7 @@
@code{[} " --" @code{]} ( " " @var{parameter} )* @var{nl}}
@item @var{token} @expansion{}
-@code{"any sequence of digits"}
+"any sequence of digits"
@item @var{option} @expansion{}
@code{"-" @var{parameter} [ " " @var{parameter} ]}
@@ -167,7 +167,7 @@
@code{@var{non-blank-sequence} | @var{c-string}}
@item @var{operation} @expansion{}
-@emph{any of the operations described in this document}
+@emph{any of the operations described in this chapter}
@item @var{non-blank-sequence} @expansion{}
@emph{anything, provided it doesn't contain special characters such as
@@ -180,6 +180,7 @@
@code{CR | CR-LF}
@end table
+@noindent
Notes:
@itemize @bullet
@@ -193,7 +194,7 @@
@item
Some @sc{mi} commands accept optional arguments as part of the parameter
-list. Each option is identified by a leading @samp{-} (dash) and may be
+list. Each option is identified by a leading @samp{-} (dash) and may be
followed by an optional argument parameter. Options occur first in the
parameter list and can be delimited from normal parameters using
@samp{--} (this is useful when some parameters begin with a dash).
@@ -217,7 +218,7 @@
The output from @sc{gdb/mi} consists of zero or more out-of-band records
followed, optionally, by a single result record. This result record
is for the most recent command. The sequence of output records is
-terminated by @samp{(gdb)}.
+terminated by @samp{(@value{GDBP})}.
If an input command was prefixed with a @code{@var{token}} then the
corresponding output for that command will also be prefixed by that same
@@ -283,6 +284,7 @@
@emph{any sequence of digits}.
@end table
+@noindent
In addition, the following are still being developed:
@table @code
@@ -290,6 +292,7 @@
This action is currently undefined.
@end table
+@noindent
Notes:
@itemize @bullet
@@ -299,8 +302,8 @@
@item
The @code{@var{token}} is from the corresponding request. If an execution
command is interrupted by the @samp{-exec-interrupt} command, the
-@var{token} associated with the `*stopped' message is the one of the
-original execution command, not the one of the interrupt-command.
+@var{token} associated with the @samp{*stopped} message is the one of the
+original execution command, not the one of the interrupt command.
@item
@cindex status output in @sc{gdb/mi}
@@ -359,7 +362,7 @@
@example
-> -stop
-<- (gdb)
+<- (@value{GDBP})
@end example
@noindent
@@ -367,7 +370,7 @@
@example
<- *stop,reason="stop",address="0x123",source="a.c:123"
-<- (gdb)
+<- (@value{GDBP})
@end example
@subsubheading Simple CLI Command
@@ -378,7 +381,7 @@
@example
-> print 1+2
<- ~3\n
-<- (gdb)
+<- (@value{GDBP})
@end example
@subsubheading Command With Side Effects
@@ -386,7 +389,7 @@
@example
-> -symbol-file xyz.exe
<- *breakpoint,nr="3",address="0x123",source="a.c:123"
-<- (gdb)
+<- (@value{GDBP})
@end example
@subsubheading A Bad Command
@@ -396,7 +399,7 @@
@example
-> -rubbish
<- error,"Rubbish not found"
-<- (gdb)
+<- (@value{GDBP})
@end example
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -437,8 +440,8 @@
@table @code
@findex ^done
@item "^done" [ "," @var{results} ]
-The synchronous operation was successful, @code{@var{results}} is the return
-value.
+The synchronous operation was successful, @code{@var{results}} are the return
+values.
@item "^running"
@findex ^running
@@ -503,10 +506,10 @@
@section @sc{gdb/mi} Command Description Format
The remaining sections describe blocks of commands. Each block of
-commands is laid out in a fashion similar to this chapter.
+commands is laid out in a fashion similar to this section.
Note the the line breaks shown in the examples are here only for
-readability. They don't appear in the real output.
+readability. They don't appear in the real output.
Also note that the commands with a non-available example (N.A.@:) are
not yet implemented.
@@ -596,7 +599,7 @@
@end ignore
-@subheading The -break-condition Command
+@subheading The @code{-break-condition} Command
@findex -break-condition
@subsubheading Synopsis
@@ -852,8 +855,8 @@
number of times the breakpoint has been hit
@end table
-If there are no breakpoints or watchpoints, the BreakpointTable field is
-an empty list.
+If there are no breakpoints or watchpoints, the @code{BreakpointTable}
+field is an empty list.
@subsubheading @value{GDBN} Command
@@ -1053,7 +1056,7 @@
@subsubheading Result
-The output for each instruction is composed of two fields:
+The output for each instruction is composed of four fields:
@itemize @bullet
@item Address
@@ -1406,7 +1409,7 @@
in @samp{nr-bytes} and the starting address used to read memory in
@samp{addr}.
-The address of the next/previous page or row is available in
+The address of the next/previous row or page is available in
@samp{next-row} and @samp{prev-row}, @samp{next-page} and
@samp{prev-page}.
@@ -1447,7 +1450,7 @@
@end smallexample
Read thirty two bytes of memory starting at @code{bytes+16} and format
-as eight rows of four columns. Include a string encoding with @code{x}
+as eight rows of four columns. Include a string encoding with @samp{x}
used as the non-printable character.
@smallexample
@@ -1621,7 +1624,7 @@
-environment-path ( @var{pathdir} )+
@end example
-Add directories to beginning of search path for object files.
+Add directories @var{pathdir} to beginning of search path for object files.
@subsubheading @value{GDBN} Command
@@ -1672,7 +1675,7 @@
it doesn't encounter any breakpoints. In this case the output will
include an exit code, if the program has exited exceptionally.
-@subsubheading Examples:
+@subsubheading Examples
@noindent
Program exited normally:
@@ -2118,7 +2121,7 @@
Asynchronous command. Executes the inferior until the @var{location}
specified in the argument is reached. If there is no argument, the inferior
executes until a source line greater than the current one is reached.
-The reason for stopping in this case will be ``location-reached''.
+The reason for stopping in this case will be @samp{location-reached}.
@subsubheading @value{GDBN} Command
@@ -3316,7 +3319,7 @@
@subsubheading Example
-No threads present, besides the main process.
+No threads present, besides the main process:
@smallexample
(@value{GDBP})
@@ -3326,7 +3329,7 @@
@end smallexample
-Several threads.
+Several threads:
@smallexample
(@value{GDBP})
@@ -3445,10 +3448,10 @@
least, the following operations:
@itemize @bullet
-@item -gdb-show output-radix
-@item -stack-list-arguments
-@item -stack-list-locals
-@item -stack-select-frame
+@item @code{-gdb-show} @code{output-radix}
+@item @code{-stack-list-arguments}
+@item @code{-stack-list-locals}
+@item @code{-stack-select-frame}
@end itemize
@subheading Introduction to Variable Objects in @sc{gdb/mi}
@@ -3479,29 +3482,29 @@
@item @strong{Operation}
@tab @strong{Description}
-@item -var-create
+@item @code{-var-create}
@tab create a variable object
-@item -var-delete
+@item @code{-var-delete}
@tab delete the variable object and its children
-@item -var-set-format
+@item @code{-var-set-format}
@tab set the display format of this variable
-@item -var-show-format
+@item @code{-var-show-format}
@tab show the display format of this variable
-@item -var-info-num-children
+@item @code{-var-info-num-children}
@tab tells how many children this object has
-@item -var-list-children
+@item @code{-var-list-children}
@tab return a list of the object's children
-@item -var-info-type
+@item @code{-var-info-type}
@tab show the type of this variable object
-@item -var-info-expression
+@item @code{-var-info-expression}
@tab print what this variable object represents
-@item -var-show-attributes
+@item @code{-var-show-attributes}
@tab is this variable editable? does it exist here?
-@item -var-evaluate-expression
+@item @code{-var-evaluate-expression}
@tab get the value of this variable
-@item -var-assign
+@item @code{-var-assign}
@tab set the value of this variable
-@item -var-update
+@item @code{-var-update}
@tab update the variable and its children
@end multitable
@@ -3526,7 +3529,7 @@
The @var{name} parameter is the string by which the object can be
referenced. It must be unique. If @samp{-} is specified, the varobj
-system will generate a string "varNNNNNN'' automatically. It will be
+system will generate a string ``varNNNNNN'' automatically. It will be
unique provided that one does not specify @var{name} on that format.
The command fails if a duplicate name is found.
@@ -3542,10 +3545,10 @@
@samp{*@var{addr}}, where @var{addr} is the address of a memory cell
@item
-@samp{*@var{addr}-@var{addr}} -- a memory address range (TBD)
+@samp{*@var{addr}-@var{addr}} --- a memory address range (TBD)
@item
-@samp{$@var{regname}} -- a CPU register name
+@samp{$@var{regname}} --- a CPU register name
@end itemize
@subsubheading Result
@@ -3605,7 +3608,7 @@
Returns the format used to display the value of the object @var{name}.
@example
- format @expansion{}
+ @var{format} @expansion{}
@var{format-spec}
@end example
@@ -3639,7 +3642,7 @@
@example
numchild=@var{n},children=@{@{name=@var{name},
- numchild=@var{n},type=@var{type}@},(repeats N times)@}
+ numchild=@var{n},type=@var{type}@},@r{(repeats N times)}@}
@end example
@@ -3724,7 +3727,7 @@
@end example
Assigns the value of @var{expression} to the variable object specified
-by @var{name}. The object must be ``editable''.
+by @var{name}. The object must be @samp{editable}.
@subheading The @code{-var-update} Command
@findex -var-update
@@ -3768,16 +3771,16 @@
The output from @sc{gdb/mi} consists of zero or more out-of-band records
optionally followed by a single result record, the result record being
for the most recent command input. The sequence is terminated by
-``(@value{GDBP})''.
+@samp{(@value{GDBP})}.
Asynchronous @sc{gdb/mi} output is similar.
Each output record directly associated with an input command is prefixed
-by the input commands @code{@var{token}}.
+by the input command's @code{@var{token}}.
@table @code
@item @var{output} @expansion{}
-@{ @var{out-of-band-record} @} @code{[} @var{result-record} @code{]} "(@value{GDBP})" @var{nl}
+@{ @var{out-of-band-record} @} @code{[} @var{result-record} @code{]} "@code{(@value{GDBP})}" @var{nl}
@item @var{result-record} @expansion{}
@code{[} @var{token} @code{]} "^" @var{result-class} @{ "," @var{result} @} @var{nl}
@@ -3862,38 +3865,38 @@
@item
The @code{@var{token}} is from the corresponding request. If an execution
-command is interrupted by the -exec-interrupt command, the token
+command is interrupted by the @code{-exec-interrupt} command, the token
associated with the `*stopped' message is the one of the original
-execution command, not the one of the interrupt-command.
+execution command, not the one of the interrupt command.
@item
-@var{status-async-output} contains on-going status information about the progress
-of a slow operation. It can be discarded. All status output is prefixed by
-the prefix `+'.
+@var{status-async-output} contains on-going status information about the
+progress of a slow operation. It can be discarded. All status output is
+prefixed by the prefix @samp{+}.
@item
@var{exec-async-output} contains asynchronous state change on the target
-(stopped, started, disappeared). All async output is prefixed by
-the prefix `*'.
+(stopped, started, disappeared). All async output is prefixed by
+the prefix @samp{*}.
@item
-@var{notify-async-output} contains supplementary information that the client should
-handle (new breakpoint information). All notify output is prefixed by
-the prefix `='.
+@var{notify-async-output} contains supplementary information that the
+client should handle (new breakpoint information). All notify output is
+prefixed by the prefix @samp{=}.
@item
@var{console-stream-output} is output that should be displayed as is, in the
-console. It is the textual response to a CLI command. All the console
-output is prefixed by the prefix ``~''.
+console. It is the textual response to a CLI command. All the console
+output is prefixed by the prefix @samp{~}.
@item
@var{target-stream-output} is the output produced by the target program.
-All the target output is prefixed by the prefix ``@@''.
+All the target output is prefixed by the prefix @samp{@@}.
@item
@var{log-stream-output} is output text coming from @value{GDBN}'s
internals, for instance messages that should be displayed as part of an
-error log. All the log output is prefixed by the prefix ``&''.
+error log. All the log output is prefixed by the prefix @samp{&}.
@end itemize
From chastain@cygnus.com Mon Aug 21 13:16:00 2000
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: [RFA] [PATCH] handle timeout in read_frame
Date: Mon, 21 Aug 2000 13:16:00 -0000
Message-id: <200008212018.NAA01965@train2.cygnus.com>
X-SW-Source: 2000-08/msg00281.html
Content-length: 2111
This patch fixes a timeout bug in remote.c.
If a timeout occurs while reading the packet checksum, read_frame
treats the timeout as an ordinary input character with a value of "-2".
gdb not only loses that frame: it throws an error out of fromhex.
This causes a lot of random testsuite failures with the message "Reply
contains invalid hex digit -2".
Testing: first, find a host, target, and testsuite that suffer from the
"invalid hex digit -2" problem. I used a Red Hat Linux 6.0 box for the
host, i386-pc-aout for the target and call-ar-st.exp for the testsuite.
Here's an excerpt from gdb.log before the patch:
Reply contains invalid hex digit -2
FAIL: gdb.base/call-ar-st.exp: (timeout) print print_array_rep(*list1, *list2, *list3)
After the patch, these errors go away.
Michael Elizabeth Chastain
<chastain@redhat.com>
"love without fear"
===
Index: remote.c
===================================================================
RCS file: /cvs/src/src/gdb/remote.c,v
retrieving revision 1.21
diff -c -3 -p -r1.21 remote.c
*** remote.c 2000/08/18 22:52:23 1.21
--- remote.c 2000/08/21 19:50:11
*************** read_frame (char *buf,
*** 3871,3882 ****
case '#':
{
unsigned char pktcsum;
buf[bc] = '\0';
! pktcsum = fromhex (readchar (remote_timeout)) << 4;
! pktcsum |= fromhex (readchar (remote_timeout));
if (csum == pktcsum)
return bc;
--- 3871,3895 ----
case '#':
{
unsigned char pktcsum;
+ int check_0 = 0;
+ int check_1 = 0;
buf[bc] = '\0';
! check_0 = readchar (remote_timeout);
! if (check_0 >= 0)
! check_1 = readchar (remote_timeout);
!
! if (check_0 == SERIAL_TIMEOUT || check_1 == SERIAL_TIMEOUT)
! {
! if (remote_debug)
! fputs_filtered ("Timeout in checksum, retrying\n", gdb_stdlog);
! return -1;
! }
! else if (check_0 < 0 || check_1 < 0)
! error ("Communication error in checksum");
+ pktcsum = (fromhex (check_0) << 4) | fromhex (check_1);
if (csum == pktcsum)
return bc;
From taylor@cygnus.com Mon Aug 21 14:32:00 2000
From: David Taylor <taylor@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: gdbarch.sh -- sh vs bash
Date: Mon, 21 Aug 2000 14:32:00 -0000
Message-id: <200008212131.RAA29172@texas.cygnus.com>
X-SW-Source: 2000-08/msg00282.html
Content-length: 1102
gdbarch.sh used to have the line:
#!/usr/local/bin/bash -u
but it was recently changed to:
#!/bin/sh -u
Unfortunately, sh doesn't currently work for this script.
Using /bin/sh (on Solaris 7 anyway), does not produce any errors but
generates a gdbarch.h which is significantly different than that
produced by bash -- in particular, if you make no changes to the
script and regenerate the gdbarch.? files, the sh generated copy of
gdbarch.h (possibly gdbarch.c as well -- I didn't check) has code
like:
/* Number of bits in a float for the target machine. */
extern float_bit gdbarch_8 * sizeof (float) (struct gdbarch *gdbarch);
extern void set_gdbarch_8 * sizeof (float) (struct gdbarch *gdbarch, float_bit 8 * sizeof (float));
#if GDB_MULTI_ARCH
#if (GDB_MULTI_ARCH > GDB_MULTI_ARCH_PARTIAL) || !defined (int)
#define int (gdbarch_8 * sizeof (float) (current_gdbarch))
#endif
#endif
which results in most of gdb not compiling...
So, either bash needs to be used to regenerate the files or the
differences between bash and sh need to be investigated...
From kevinb@cygnus.com Mon Aug 21 15:08:00 2000
From: Kevin Buettner <kevinb@cygnus.com>
To: David Taylor <taylor@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: gdbarch.sh -- sh vs bash
Date: Mon, 21 Aug 2000 15:08:00 -0000
Message-id: <1000821220839.ZM27382@ocotillo.lan>
References: <200008212131.RAA29172@texas.cygnus.com> <taylor@cygnus.com>
X-SW-Source: 2000-08/msg00283.html
Content-length: 364
On Aug 21, 5:31pm, David Taylor wrote:
> So, either bash needs to be used to regenerate the files or the
> differences between bash and sh need to be investigated...
It should also be noted that versions of bash before version 2.X (for
some value of X) will not work either. Specifically, 1.14.7 (which is
the default on Red Hat 6.2 box) will not work.
Kevin
From brolley@redhat.com Tue Aug 22 13:26:00 2000
From: Dave Brolley <brolley@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: sim: rfa: disassembly in cgen-based trace
Date: Tue, 22 Aug 2000 13:26:00 -0000
Message-id: <39A2E246.782E40A9@redhat.com>
X-SW-Source: 2000-08/msg00284.html
Content-length: 616
Hi,
The attached patch fixes a problem with incorrectly displayed
disassembly in the trace output of cgen-based simulators.
Basically, the trace output was accessing fields which were not
ever written into the insn word. The patch ensures that, when an
insn fits into an integer, then the entire insn is written there,
not just the bits represented by base-insn-bitsize. Insns which
do not fit into an integer are handled by another mechanism.
OK to commit?
Dave
2000-08-22 Dave Brolley <brolley@redhat.com>
* cgen-trace.c (sim_cgen_disassemble_insn): Make sure entire insn is
in insn_value if it will fit.
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Patch to gdbmi.texinfo
2000-08-21 13:03 Dmitry S. Sivachenko
@ 2000-08-23 3:49 ` Eli Zaretskii
0 siblings, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2000-08-23 3:49 UTC (permalink / raw)
To: dima; +Cc: gdb-patches
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
> Date: Tue, 22 Aug 2000 00:03:41 +0400 (MSD)
> From: "Dmitry S. Sivachenko" <dima@Chg.RU>
>
> Please apply this patch to gdbmi.texinfo.
> It was made agaist latest revision of gdbmi.texinfo.
>
> It fixes several typos and markup bugs, missed by me in my previous patch.
Applied. Thanks!
From DJBARROW@de.ibm.com Wed Aug 23 04:58:00 2000
From: DJBARROW@de.ibm.com
To: gdb-patches@sourceware.cygnus.com
Subject: Re posting patches on linux for s/390
Date: Wed, 23 Aug 2000 04:58:00 -0000
Message-id: <C1256944.004190C7.00@d12mta09.de.ibm.com>
X-SW-Source: 2000-08/msg00286.html
Content-length: 637
Hi,
I've been asked to move the Linux for S/390 gdb patches to the official
distribution,
I would like to make contact with the official maintainer.
IBM managed to negociate directly & came to an aggreement with Richard
Stallmans Legal adviser about putting
patches against 4.18. However we now have patches against 5.0 & possibly
need patches against an even
newer version of the sources.
Please get back to me asap so we can get the ball rolling on this.
D.J. Barrow Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-08-23 3:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-07-23 9:33 Patch to gdbmi.texinfo Dmitry S. Sivachenko
2000-07-23 12:18 ` Eli Zaretskii
2000-08-21 13:03 Dmitry S. Sivachenko
2000-08-23 3:49 ` Eli Zaretskii
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox