From: Eli Zaretskii Date: Tue, 9 May 2000 08:24:34 +0000 (+0000) Subject: * gdb.texinfo: Proofreading changes from Brian Youmans. X-Git-Tag: readline-pre-41-import~537 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=598ca718d00001789f64d2669c56f87acea2b3ca;p=external%2Fbinutils.git * gdb.texinfo: Proofreading changes from Brian Youmans. --- diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 0ca8611..98bffde 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2000-05-09 Eli Zaretskii + + * gdb.texinfo: Proofreading changes from Brian Youmans. + 2000-05-01 Nick Duffek * gdb.texinfo (Command Files): Mention -x, use @enumerate for diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 2f46626..daba4a3 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -8754,7 +8754,7 @@ void (*exceptionHook)() = 0; @noindent but if before calling @code{set_debug_traps}, you set it to point to a -function in your program; that function is called when +function in your program, that function is called when @code{@value{GDBN}} continues after stopping on a trap (for example, bus error). The function indicated by @code{exceptionHook} is called with one parameter: an @code{int} which is the exception number. @@ -8928,7 +8928,7 @@ So: @noindent means the same as "0000". -The error response, returned for some packets includes a two character +The error response returned for some packets includes a two character error number. That number is not well defined. For any @var{command} not supported by the stub, an empty response @@ -8942,7 +8942,7 @@ optional. Below is a complete list of all currently defined @var{command}s and their corresponding response @var{data}: - +@page @multitable @columnfractions .30 .30 .40 @item Packet @tab Request @@ -8952,7 +8952,7 @@ their corresponding response @var{data}: @tab @code{!} @tab Use the extended remote protocol. Sticky---only needs to be set once. -The extended remote protocol support the @samp{R} packet. +The extended remote protocol supports the @samp{R} packet. @item @tab reply @samp{} @tab @@ -8977,6 +8977,9 @@ and continue. @item set program arguments @strong{(reserved)} @tab @code{A}@var{arglen}@code{,}@var{argnum}@code{,}@var{arg}@code{,...} @tab +@item +@tab +@tab Initialized @samp{argv[]} array passed into program. @var{arglen} specifies the number of bytes in the hex encoded byte stream @var{arg}. See @file{gdbserver} for more details. @@ -9023,7 +9026,7 @@ Continue with signal @var{sig} (hex signal number). If @tab reply @tab see below -@item toggle debug @emph{(deprecated)} +@item toggle debug @strong{(deprecated)} @tab @code{d} @tab toggle debug flag. @@ -9036,7 +9039,7 @@ Detach @value{GDBN} from the remote system. Sent to the remote target before @item @tab reply @emph{no response} @tab -@value{GDBN} does not check for any response after sending this packet +@value{GDBN} does not check for any response after sending this packet. @item reserved @tab @code{e} @@ -9219,7 +9222,7 @@ digits for each byte in the register (target byte order). @item general query @tab @code{q}@var{query} @tab -Request info about @var{query}. In general @value{GDBN} @var{query}'s +Request info about @var{query}. In general @value{GDBN} queries have a leading upper case letter. Custom vendor queries should use a company prefix (in lower case) ex: @samp{qfsf.var}. @var{query} may optionally be followed by a @samp{,} or @samp{;} separated list. Stubs @@ -9240,7 +9243,7 @@ must ensure that they match the full @var{query} name. Set value of @var{var} to @var{val}. See @samp{q} for a discussing of naming conventions. -@item reset @emph{(deprecated)} +@item reset @strong{(deprecated)} @tab @code{r} @tab Reset the entire system. @@ -9534,6 +9537,9 @@ offset to the @code{Bss} section.} @item thread info request @tab @code{q}@code{P}@var{mode}@var{threadid} @tab +@item +@tab +@tab Returns information on @var{threadid}. Where: @var{mode} is a hex encoded 32 bit mode; @var{threadid} is a hex encoded 64 bit thread ID. @item @@ -9544,6 +9550,9 @@ See @code{remote.c:remote_unpack_thread_info_response()}. @item remote command @tab @code{q}@code{Rcmd,}@var{COMMAND} @tab +@item +@tab +@tab @var{COMMAND} (hex encoded) is passed to the local interpreter for execution. Invalid commands should be reported using the output string. Before the final result packet, the target may also respond with a