Re: [PATCH 7/7] Access executable from remote system when first inferior appears

Gary Benson
2015-04-16T09:30:19Z

Pedro Alves wrote:
> Missed the manual bit:
> On 04/15/2015 02:55 PM, Gary Benson wrote:
> > [snip]
>
> This looks right, but it's not what I was thinking. The "attach"
> reference was just to give an example of where we document that gdb
> find the program for the user. I think we should say something like
> that in the "target remote" documentation too.

Ah, I see what you mean. How about the following? If it's ok I'll
merge that piece with this final patch.

Cheers,
Gary

---
2015-04-16 Gary Benson <gbenson@redhat.com>

* gdb.texinfo (Connecting to a Remote Target): Mention that
GDB can access program files from remote targets that support
qXfer:exec-file:read and Host I/O packets.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 964f9c4..e7872dd 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -18952,10 +18952,16 @@
@node Connecting
@section Connecting to a Remote Target

-On the @value{GDBN} host machine, you will need an unstripped copy of
-your program, since @value{GDBN} needs symbol and debugging information.
-Start up @value{GDBN} as usual, using the name of the local copy of your
-program as the first argument.
+@value{GDBN} needs an unstripped copy of your program to access symbol
+and debugging information. Some remote targets@footnote{@xref{qXfer
+executable filename read}, and @ref{Host I/O Packets}.} allow
+@value{GDBN} to access program files over the same connection used to
+communicate with @value{GDBN}. With such a target, the only command
+you need is @code{target remote}. If the target you are using does
+not have this support then you will need an unstripped copy of your
+program on the @value{GDBN} host machine. Start up @value{GDBN} as
+usual, using the name of the local copy of your program as the first
+argument.

@cindex @code{target remote}
@value{GDBN} can communicate with the target over a serial line, or