This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: A copy/save command ...


On Thu, Jan 03, 2002 at 04:02:37AM -0500, Andrew Cagney wrote:
> Hello,
> 
> To toss out an idea.  One of those oft mentioned missing features is a 
> command to read/write binary data to/from GDB's target memory.  There is 
> the load command, but that works on object files (readable via BFD).
> 
> Anyway, I've two vague thoughts on the syntax/semantics:
> 
> 1. (gdb) copy <expression> <file>
> 
> The result of <expression> is written to the raw file.  This expoits the 
> fact that GDB stores an expression in target form in host memory. 
> Consequently, the copy command just writes that raw data to the file.
> 
> 
> 2. (gdb) copy <address> <length> <file>
> or (gdb) copy/<length> <address> <file>
> 
> or similar.  A more traditional <address>/<length> approach. 
> ``copy/<length>'' comes from ``x/<length>''.
> 
> 
> better suggestions welcome.

Perhaps not the best name - we want to be able to both read and write,
and it's not clear which way copy goes.  I don't want to end up doing
magic thinking that ``this looks like an address, not a filename'' to
figure that out.

Perhaps read/write?  But that's still not clear which way is which. 
load/store would be perfect but load is already used.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]