Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: jtc@redback.com
Cc: Daniel Jacobowitz <dmj+@andrew.cmu.edu>, gdb@sources.redhat.com
Subject: Re: Who owns gdbserver?
Date: Fri, 22 Jun 2001 08:28:00 -0000	[thread overview]
Message-ID: <3B336403.4090207@cygnus.com> (raw)
In-Reply-To: <5mae318vuv.fsf@jtc.redback.com>

> Daniel> No one admits to it, in MAINTAINERS at least...
> 
> I think Stan did, among other things.  As I recall, he realized that
> he wasn't in a position to maintain things properly and stepped back
> from that role.  No one picked up it up since then.


Yes, that is correct.  I'll update the hall of fame.

 
> I'm not sure I'm up to the task of taking on gdbserver on a full time 
> basis, but as a blanket-write-priv maintainer and given my interests
> with remote, I'll certainly help you along.
> 
> Daniel> On a related note, I'm trying to think of a way to eliminate
> Daniel> some of the crasser code duplication between gdb and gdbserver
> Daniel> - or rather, right now it's mostly a lack of code duplication,
> Daniel> causing gdbserver not to work terribly well.
> 
> This has been a outstanding issue for some time.  



I know of the following:

	o	G packet layout

		Here it has been suggested that
		some G packet spec be created so that
		both GDb and GDBSERVER can use it with
		out duplicating that spec.

	o	other arch info

		Core GDB is using multi-arch which means
		that gdbserver can no longer use the
		the current suite of macros with out some
		level of change.

	o	ptrace et.al.

		Since these tend to use gdbarch info they
		have the same problem.

Andrew




  reply	other threads:[~2001-06-22  8:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20 22:12 Daniel Jacobowitz
2001-06-21 12:40 ` J.T. Conklin
2001-06-22  8:28   ` Andrew Cagney [this message]
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

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=3B336403.4090207@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=dmj+@andrew.cmu.edu \
    --cc=gdb@sources.redhat.com \
    --cc=jtc@redback.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