From: jtc@redback.com (J.T. Conklin)
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: gdb@sources.redhat.com
Subject: Re: Who owns gdbserver?
Date: Thu, 21 Jun 2001 12:40:00 -0000 [thread overview]
Message-ID: <5mae318vuv.fsf@jtc.redback.com> (raw)
In-Reply-To: <20010620221224.A19552@nevyn.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <dmj+@andrew.cmu.edu> writes:
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.
I am interested in the future of the remote protocol, and remote.c and
gdbserver by extension. I am the remote.c co-maintainer, and have
been known to hack on gdbserver from time to time. But mainly that's
minor cleanup and adding support for additional NetBSD ports.
Daniel> I am considering some fairly invasive changes to it, between
Daniel> some signal problems I've been having, more Linux ports, and
Daniel> threads. It would be nice to establish a clear owner before I
Daniel> do that.
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.
--jtc
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~2001-06-21 12:40 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 [this message]
2001-06-22 8:28 ` Andrew Cagney
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=5mae318vuv.fsf@jtc.redback.com \
--to=jtc@redback.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