This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 7/7] Access executable from remote system when first inferior appears
- From: Pedro Alves <palves at redhat dot com>
- To: Gary Benson <gbenson at redhat dot com>
- Cc: Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sourceware dot org
- Date: Thu, 16 Apr 2015 10:53:39 +0100
- Subject: Re: [PATCH 7/7] Access executable from remote system when first inferior appears
- Authentication-results: sourceware.org; auth=none
- References: <1427887341-31819-1-git-send-email-gbenson at redhat dot com> <1427887341-31819-8-git-send-email-gbenson at redhat dot com> <552E3C6B dot 2090300 at redhat dot com> <20150415135555 dot GA18079 at blade dot nx> <552E8E34 dot 4030006 at redhat dot com> <20150416093013 dot GB18779 at blade dot nx>
On 04/16/2015 10:30 AM, Gary Benson wrote:
> -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.
Even if the target supports this, if the target's file copy is
stripped, which it usually is, you'll still need to manually pass the
unstripped program to gdb. I think we should rephrase it a bit making
sure that is clear.
Maybe something like this? :
-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, unless the remote
+program file is stripped, the only command you need is
+@code{target remote}. Otherwise, start up @value{GDBN} using the
+name of the local unstripped copy of your program as the first
+argument, or use the @code{file} command.
Thanks,
Pedro Alves