omitted from this list, we would like to add your names!
@end quotation
+@c codespell:ignore-begin
So that they may not regard their many labors as thankless, we
particularly thank those who shepherded @value{GDBN} through major
releases:
Weimin Pan, David Faust and Jose E. Marchesi contributed support for
the Linux kernel BPF virtual architecture. This work was sponsored by
Oracle.
+@c codespell:ignore-end
@node Sample Session
@chapter A Sample @value{GDBN} Session
the manually specified language (see @ref{Manually, ,Set Language Manually}).
The syntax of the regular expression is the standard one used with tools
-like @file{grep}. Note that this is different from the syntax used by
+like @file{grep}.
+@c codespell:ignore-begin
+Note that this is different from the syntax used by
shells, so for instance @code{foo*} matches all functions that include
-an @code{fo} followed by zero or more @code{o}s. There is an implicit
-@code{.*} leading and trailing the regular expression you supply, so to
-match only functions that begin with @code{foo}, use @code{^foo}.
+an @code{fo} followed by zero or more @code{o}s.
+@c codespell:ignore-end
+There is an implicit @code{.*} leading and trailing the regular expression you
+supply, so to match only functions that begin with @code{foo}, use @code{^foo}.
@cindex non-member C@t{++} functions, set breakpoint in
When debugging C@t{++} programs, @code{rbreak} is useful for setting
@table @code
@kindex search
@kindex forward-search
+@c codespell:ignore-begin
@kindex fo @r{(@code{forward-search})}
+@c codespell:ignore-end
@cindex @code{$_} and commands that search source files
@item forward-search @var{regexp}
@itemx search @var{regexp}
starting with the one following the last line listed, for a match for
@var{regexp}. It lists the line that is found and saves it in the
convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience
-Variables}). You can use the synonym @samp{search @var{regexp}}
-or abbreviate the command name as @code{fo}.
+Variables}).
+@c codespell:ignore-begin
+You can use the synonym @samp{search @var{regexp}} or abbreviate the command
+name as @code{fo}.
+@c codespell:ignore-end
@kindex reverse-search
@item reverse-search @var{regexp}
When IBT is enabled, the CPU implements a state machine that tracks
indirect @code{JMP} and @code{CALL} instructions. The state machine can
be either IDLE or WAIT_FOR_ENDBRANCH. When a @code{JMP} or @code{CALL} is
-executed the state machine chages to the WAIT_FOR_ENDBRANCH state. In
+executed the state machine changes to the WAIT_FOR_ENDBRANCH state. In
WAIT_FOR_ENDBRANCH state the next instruction in the program stream
must be an @code{ENDBR} instruction, otherwise the processor signals a
control protection exception. After executing a @code{ENDBR} instruction
dependent and sometimes can be changed with OSC 4 sequences, e.g.
"\033]4;1;rgb:00/FF/00\033\\". A hexadecimal 24-bit TrueColor is specified in
the format @samp{#RRGGBB} where RR, GG and BB are the 2-digit hexadecimal
-integers specifiing the intensity of the red, green and blue color components,
+integers specifying the intensity of the red, green and blue color components,
respectively.
It is the responsibility of the user to verify that the terminal supports
@subsubheading Example
+@c codespell:ignore-begin
@smallexample
(gdb)
-environment-cd /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
^done
(gdb)
@end smallexample
+@c codespell:ignore-end
@findex -environment-directory
@subsubheading Example
+@c codespell:ignore-begin
@smallexample
(gdb)
-environment-directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
^done,source-path="$cdir:$cwd"
(gdb)
@end smallexample
+@c codespell:ignore-end
@findex -environment-path
@subsubheading Example
+@c codespell:ignore-begin
@smallexample
(gdb)
-environment-path
^done,path="/usr/local/bin:/usr/bin"
(gdb)
@end smallexample
+@c codespell:ignore-end
@findex -environment-pwd
@subsubheading Example
+@c codespell:ignore-begin
@smallexample
(gdb)
-environment-pwd
^done,cwd="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb"
(gdb)
@end smallexample
+@c codespell:ignore-end
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@node GDB/MI Thread Commands
@subsubheading Example
+@c codespell:ignore-begin
@smallexample
(gdb)
-file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
^done
(gdb)
@end smallexample
+@c codespell:ignore-end
@findex -file-exec-file
@subsubheading Example
+@c codespell:ignore-begin
@smallexample
(gdb)
-file-exec-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
^done
(gdb)
@end smallexample
+@c codespell:ignore-end
@ignore
@subsubheading Example
+@c codespell:ignore-begin
@smallexample
(gdb)
-file-symbol-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
^done
(gdb)
@end smallexample
+@c codespell:ignore-end
@ignore
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
(@pxref{Agent Expressions}). The @samp{agent} version produces an
expression useful for data collection, such as by tracepoints, while
@samp{maint agent-eval} produces an expression that evaluates directly
-to a result. For instance, a collection expression for @code{globa +
-globb} will include bytecodes to record four bytes of memory at each
-of the addresses of @code{globa} and @code{globb}, while discarding
-the result of the addition, while an evaluation expression will do the
-addition and return the sum.
+to a result.
+@c codespell:ignore-begin
+For instance, a collection expression for @code{globa + globb} will include
+bytecodes to record four bytes of memory at each of the addresses of
+@code{globa} and @code{globb}, while discarding the result of the addition,
+while an evaluation expression will do the addition and return the sum.
+@c codespell:ignore-end
If @code{-at} is given, generate remote agent bytecode for all the
addresses to which @var{linespec} resolves (@pxref{Linespec
Locations}).
characters between the leading @samp{$} and the trailing @samp{#} (an
eight bit unsigned checksum).
-Implementors should note that prior to @value{GDBN} 5.0 the protocol
+Implementers should note that prior to @value{GDBN} 5.0 the protocol
specification also included an optional two-digit @var{sequence-id}:
@smallexample
@samp{:}. Except where otherwise noted all numbers are represented in
@sc{hex} with leading zeros suppressed.
-Implementors should note that prior to @value{GDBN} 5.0, the character
+Implementers should note that prior to @value{GDBN} 5.0, the character
@samp{:} could not appear as the third character in a packet (as it
would potentially conflict with the @var{sequence-id}).
execution. Invalid commands should be reported using the output
string. Before the final result packet, the target may also respond
with a number of intermediate @samp{O@var{output}} console output
-packets. @emph{Implementors should note that providing access to a
+packets. @emph{Implementers should note that providing access to a
stubs's interpreter may have security implications}.
Reply:
projects / thirdparty / binutils-gdb.git / commitdiff
