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 05:12:00 -0000 [thread overview]
Message-ID: <20051203051254.GA25062@nevyn.them.org> (raw)
In-Reply-To: <439127B7.5040709@netspace.net.au>
On Sat, Dec 03, 2005 at 04:05:59PM +1100, Russell Shaw wrote:
> Russell Shaw wrote:
> >Daniel Jacobowitz wrote:
> >
> >>On Sat, Dec 03, 2005 at 03:05:25PM +1100, Russell Shaw wrote:
> >>
> ...
> >With all the interfaces in gdb subdirectories, all the example code that
> >anyone could ever want for adding support for new hardware, is already
> >there to look at (i looked at gdb-6.3/gdb/remote*.c to start my one).
>
> Maybe these subdirectories should actually be for each cpu type,
> and any hardware debugger protocols should be in a subdirectory
> of that.
>
> This would simplify the source tree of gdb *alot*.
>
> Currently:
>
> gdb-6.3/gdb/remote-hms.c
> gdb-6.3/gdb/h8300-tdep.c
>
> New:
>
> gdb-6.3/gdb/h8300/remote/hms.c
> gdb-6.3/gdb/h8300/tdep.c
We've talked about doing this before, but some people like it and
others don't, so we've left alone - also, CVS notoriously doesn't like
renaming files. It doesn't make a whole lot of difference.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-03 5:12 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 ` Bob Rossi
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
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 [this message]
2005-12-03 9:29 ` Eli Zaretskii
2005-12-03 9:50 ` Russell Shaw
2005-12-03 9:57 ` Eli Zaretskii
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=20051203051254.GA25062@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