From: Daniel Jacobowitz <drow@false.org>
To: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sourceware.org
Subject: Re: [RFC] plugin/extension interface
Date: Sat, 03 Dec 2005 03:33:00 -0000 [thread overview]
Message-ID: <20051203033336.GA23537@nevyn.them.org> (raw)
In-Reply-To: <43910D47.2070300@netspace.net.au>
On Sat, Dec 03, 2005 at 02:13:11PM +1100, Russell Shaw wrote:
> The way gdb works, when i type: target avrjtagice -d /dev/ttyS2,
> gdb uses (or registers) using: void _initialize_remote_jtag (void).
Incorrect; that happens at GDB startup.
> If the functions (or framework) used in these target interfaces are
> documented, the problems would be solved with little other than a bit
> of documentation work.
Not unless we declared them a public interface. That means supporting
them, preserving compatibility, et cetera. We are not prepared to do
that.
> I couldn't use the default target protocol, because i wasn't interfacing
> to an end target. I was interfacing to an ICE debugger (that already had
> its own protocol) for the target.
>
> I did it to replace the current hack of having an extra program on the
> pc that converts between the default gdb target protocol, and this ICE-
> specific protocol.
>
> The conversion hack was extremely slow, clumsy, fault-intolerant, and
> error-prone.
I would need to know a lot more about these problems, but it is very
likely that they are problems with the conversion program - not with
the concept. If they were problems with the remote protocol, we would
be interested in fixing them.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-03 3:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 18:25 Andrew STUBBS
2005-12-02 18:49 ` Eli Zaretskii
2005-12-02 19:23 ` Daniel Jacobowitz
2005-12-02 19:36 ` Mark Kettenis
2005-12-02 22:12 ` Jim Blandy
2005-12-02 22:16 ` Daniel Jacobowitz
2005-12-02 22:41 ` Mark Kettenis
2005-12-02 23:07 ` Jim Blandy
2005-12-02 23:13 ` Bob Rossi
2005-12-02 23:32 ` Daniel Jacobowitz
2005-12-03 0:57 ` Jim Blandy
2005-12-03 2:32 ` Daniel Jacobowitz
2005-12-03 2:41 ` Russell Shaw
2005-12-03 2:45 ` Daniel Jacobowitz
2005-12-03 3:13 ` Russell Shaw
2005-12-03 3:33 ` Daniel Jacobowitz [this message]
2005-12-03 4:05 ` Russell Shaw
2005-12-03 4:14 ` Daniel Jacobowitz
2005-12-03 4:44 ` Russell Shaw
2005-12-03 4:49 ` Daniel Jacobowitz
2005-12-03 5:25 ` Russell Shaw
2005-12-03 12:49 ` [commit] Clarify "monitor" command (was: [RFC] plugin/extension interface) Eli Zaretskii
2005-12-03 12:51 ` [commit] Clarify "monitor" command Russell Shaw
2005-12-03 16:08 ` [commit] Clarify "monitor" command (was: [RFC] plugin/extension interface) Daniel Jacobowitz
2005-12-03 5:06 ` [RFC] plugin/extension interface Russell Shaw
2005-12-03 5:12 ` Daniel Jacobowitz
2005-12-03 9:29 ` Eli Zaretskii
2005-12-03 9:50 ` Russell Shaw
2005-12-03 9:57 ` Eli Zaretskii
2005-12-03 2:41 ` Bob Rossi
2005-12-05 16:17 ` Andrew STUBBS
2005-12-05 16:34 ` Bob Rossi
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=20051203033336.GA23537@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rjshaw@netspace.net.au \
/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