This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Date: Sat, 6 Mar 2004 18:08:35 -0500 From: Daniel Jacobowitz <drow@false.org>
Seem OK?
Thanks for the documentation patch, but I have 2 minor comments:
@item set debug target Turns on or off display of @value{GDBN} target debugging info. This info includes what is going on at the target level of GDB, as it happens. The -default is off. +default is 0. Set it to 1 to track events, and to 2 to also track the +value of large memory transfers. This flag must be set before connecting +to the target or saying @code{run}.
. I'm not sure I understand this sentence--do you mean to say that
_if_ the flag is set, it must be set _before_ connecting and
before "run"?
Yeah, that's correct. "set debug target" must be given before the target command. If I remember correctly, it inserts a layer in the target stack.
If so, I suggest to use @emph and/or @strong to make sure the reader understands you, and maybe rephrase slightly to make sure the wording is less ambiguous.
. Since in this context "run" is something the user types, it should be @kbd{run}, not @code{run}.
Otherwise, it is okay to go in.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |