From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Doc corrections to gdb.texinfo
Date: Sat, 17 Feb 2007 10:14:00 -0000 [thread overview]
Message-ID: <uire1ks4m.fsf@gnu.org> (raw)
In-Reply-To: <17877.11293.529807.644028@kahikatea.snap.net.nz> (message from Nick Roberts on Fri, 16 Feb 2007 16:59:25 +1300)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Fri, 16 Feb 2007 16:59:25 +1300
>
> Probably obvious, but not committed just in case.
>
> OK to commit?
Thanks, all the changes are okay with me, with the exception of this
one:
> *************** Out of @value{GDBN}}).
> *** 11458,11465 ****
> Occasionally it is necessary to change to a different file during a
> @value{GDBN} session. Or you may run @value{GDBN} and forget to
> specify a file you want to use. Or you are debugging a remote target
> ! via @code{gdbserver} (@pxref{Server, file}). In these situations the
> ! @value{GDBN} commands to specify new files are useful.
>
> @table @code
> @cindex executable file
> --- 11458,11466 ----
> Occasionally it is necessary to change to a different file during a
> @value{GDBN} session. Or you may run @value{GDBN} and forget to
> specify a file you want to use. Or you are debugging a remote target
> ! via @code{gdbserver} (@pxref{Server, , Using the gdbserver
> ! program}). In these situations the @value{GDBN} commands to specify
> ! new files are useful.
>
> @table @code
> @cindex executable file
Can you explain why you thought this change was necessary?
next prev parent reply other threads:[~2007-02-17 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 3:59 Nick Roberts
2007-02-17 10:14 ` Eli Zaretskii [this message]
2007-02-17 21:33 ` Nick Roberts
2007-02-18 4:28 ` Eli Zaretskii
2007-02-18 8:06 ` Nick Roberts
2007-02-18 20:18 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uire1ks4m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox