This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Make file transfer commands work with all (native) targets. (was: Re: [PATCH 04/16] push remote_desc into struct remote_state)
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <palves at redhat dot com>
- Cc: tromey at redhat dot com, gdb-patches at sourceware dot org
- Date: Fri, 28 Jun 2013 20:44:14 +0300
- Subject: Re: [PATCH] Make file transfer commands work with all (native) targets. (was: Re: [PATCH 04/16] push remote_desc into struct remote_state)
- References: <1371835506-15691-1-git-send-email-tromey at redhat dot com> <1371835506-15691-5-git-send-email-tromey at redhat dot com> <51C880C5 dot 6050307 at redhat dot com> <87bo6rmhin dot fsf at fleche dot redhat dot com> <51CDBAF6 dot 4040209 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 28 Jun 2013 17:33:58 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: gdb-patches@sourceware.org
>
> > Pedro> remote_file_get could nowadays be using the target_fileio_XXX methods
> > Pedro> instead of remote_hostio_XXX, and therefore the command could be
> > Pedro> generalized to work with all targets.
>
> Actually, doing this is quite easy, so I went ahead, in the name
> of local/remote feature parity. We can connect to a local gdbserver
> and do file transfer in the local system; there seems to be no
> reason we can't do it with native debugging too.
>
> WDYT?
What is the use case?
Without a good use case, having "remote get" serve like a poor man's
'cp' is confusing, IMO.