From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Create src/gdb/common, move signals.c there.
Date: Sat, 28 Feb 2009 01:11:00 -0000 [thread overview]
Message-ID: <20090227221417.GB12904@caradoc.them.org> (raw)
In-Reply-To: <20090205215202.CE0251C7A1E@localhost>
On Thu, Feb 05, 2009 at 01:52:02PM -0800, Doug Evans wrote:
> Some code is shared between gdb and gdbserver, and over time more
> code will be shared. And I think the lack of explicit sharing
> is complicating progress.
I, personally, do not think that sharing code between gdb and
gdbserver is very useful. There's no defined common API that shared
code could rely on, and the internals are pretty different.
> This patch does these things:
>
> 1) Create src/gdb/common, and adds -I's to $(src)/common to the Makefiles.
> 2) Pull the duplicate decls of the functions in signals.c out of
> gdb/target.h and gdbserver/server.h and put them in common/gdb_signals.h.
> 3) Move signals/signals.c to common/signals.c, and cleans up signals.c
> a bit.
This patch seems fine on its own merits, though.
> - maybe(!) move regformats to common, though it's big enough
> and standalone enough that I don't have an opinion on it
Not sure what the point of this would be, that code is just for
gdbserver.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-02-27 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 21:52 Doug Evans
2009-02-24 20:30 ` Doug Evans
2009-02-25 10:26 ` teawater
2009-02-28 1:11 ` Daniel Jacobowitz [this message]
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=20090227221417.GB12904@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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