Re: [PATCH] Make file transfer commands work with all (native) targets.

Pedro Alves
2013-07-01T16:34:05Z

On 07/01/2013 03:28 PM, Tom Tromey wrote:

> Eli> But putting files on a remote target puts them on the board, no?
> Eli> There's no analogous place in native debugging.
>
> There's the local filesystem.
> You can run gdbserver locally and still use these commands.
>
>>>> Without a good use case, having "remote get" serve like a poor man's
>>>> 'cp' is confusing, IMO.
>>>
>>> Would you be OK with, or prefer, adding "target get/put/delete", leaving
>>> the "remote" variants in place?
>
> Eli> I guess so, but then won't you lose backward compatibility?
>
> He means to leave the "remote" variants in place.

Yep.

Though I somehow missed realizing "target get/put/delete"
conflicts with the usual sense we use "target foo" commands
for... The next obvious one, "file", is taken too...
"target-file" or "fileio" would be my next choices. Either
changes tab completion behavior for "target" and "file", forcing
the user to type a space, so perhaps not 100% ideal.
Making "remote put/get/delete" was a lot simpler. :-)

For MI, I'd still make -target-file-get work with native
targets without adding new commands. These are not documented
as only working with remote targets. If the frontend wants
to restrict them to remotes, it can do that itself before
calling into GDB.

--
Pedro Alves