From: Daniel Jacobowitz <drow@mvista.com>
To: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: [RFC] upload/download command
Date: Mon, 17 Nov 2003 15:26:00 -0000 [thread overview]
Message-ID: <20031117152619.GA10659@nevyn.them.org> (raw)
In-Reply-To: <03e601c3ad1e$3b2f0ff0$0202040a@catdog>
On Mon, Nov 17, 2003 at 10:19:44AM -0500, Kris Warkentin wrote:
> Our QNX pdebug protocol supports an upload/download command. This is handy
> for putting binaries onto target system and getting back things like
> corefiles. Andrew had wanted me to start a discussion on the subject.
>
> I would like to keep these things in our protocol but it might be useful to
> generalize the interface out to core gdb. What I'm thinking is that I
> create a general upload/download command that uses a hook into the target's
> code for any special functionality. We could have a general one for native
> targets which would basically be 'copy' (probably not all that useful but
> there for completeness) and just print 'not implemented' for targets which
> don't define the hooks.
Rather don't implement it for native I think... hm, might be easier to
test the core parts if we did.
> Any ideas, comments, suggestions, etc.?
For starters, how about describing how it works in your protocol?
Obviously this could be useful to gdbserver. For mechanics, it may
want to be another target_read_partial()...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-11-17 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 15:18 Kris Warkentin
2003-11-17 15:26 ` Daniel Jacobowitz [this message]
2003-11-17 15:34 ` Kris Warkentin
2003-11-17 15:39 ` Daniel Jacobowitz
2003-11-17 15:51 ` Andrew Cagney
2003-11-17 15:42 ` Andrew Cagney
2003-11-17 16:22 Ken Dyck
2003-11-17 18:01 ` Kris Warkentin
2003-11-18 3:08 ` Andrew Cagney
2003-11-18 15:03 ` Kris Warkentin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031117152619.GA10659@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox