From: Quality Quorum <qqi@world.std.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Jacobowitz <dmj+@andrew.cmu.edu>, gdb@sources.redhat.com
Subject: Re: Who owns gdbserver?
Date: Thu, 28 Jun 2001 07:41:00 -0000 [thread overview]
Message-ID: <Pine.SGI.4.21.0106281036540.19466-100000@world.std.com> (raw)
In-Reply-To: <3B3AB1DF.9020500@cygnus.com>
On Thu, 28 Jun 2001, Andrew Cagney wrote:
>
> > My current inclination is that, after we enumerate precisely what
> > interfaces are needed, we may need to break some of the nat and tdep
> > files up into smaller pieces, so that gdbserver can link in the parts
> > it really needs - and the parts it can reasonably include the support
> > code for.
>
>
> Sounds good in theory, there is a catch-22 though. Doing any cleanup is
> a lot easier with everything multi-arch.
>
> I'm happy for, short term, there to be a slightly bloated GDBserver, if
> it means that people concentrate more on getting things multi-arched.
IMHO, the only thing truly shared between gdbserver and gdb
is register map - so it seems feasible to me to keep gdbserver
as an entity completely separate from gdb.
>
> Andrew
>
Thanks,
Aleksey
next prev parent reply other threads:[~2001-06-28 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 13:30 John S. Kallal
2001-06-22 8:42 ` Andrew Cagney
2001-06-22 9:04 ` Daniel Jacobowitz
2001-06-27 21:26 ` Andrew Cagney
2001-06-28 7:41 ` Quality Quorum [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-20 22:12 Daniel Jacobowitz
2001-06-21 12:40 ` J.T. Conklin
2001-06-22 8:28 ` Andrew Cagney
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=Pine.SGI.4.21.0106281036540.19466-100000@world.std.com \
--to=qqi@world.std.com \
--cc=ac131313@cygnus.com \
--cc=dmj+@andrew.cmu.edu \
--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