From: Doug Evans <dje@google.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: duplicated code in gdb and gdbserver
Date: Mon, 10 Jan 2011 16:35:00 -0000 [thread overview]
Message-ID: <AANLkTi=WSW8snse3PaNZTYnax6Mo6+F=Pah6JKo8=B2R@mail.gmail.com> (raw)
In-Reply-To: <20110110155413.GE17302@redhat.com>
On Mon, Jan 10, 2011 at 7:54 AM, Frank Ch. Eigler <fche@redhat.com> wrote:
> dje wrote:
>
>> > [...]�A library API for the remote protocol [...].
>>
>> Yeah, like Joel, it isn't clear what is meant here.
>> Can you elaborate?
>
> Just that non-gdb tools needing to perform remote process control
> could speak to gdbserver too, mediated if necessary by a new library
> slightly abstracting the TCP/IP stuff.
So native "gdb hello" would have to fork gdbserver. Ah.
That is one way to go.
It would give us the impetus to get multiprocess debugging across fork
working well (which Tom wants for gcc). 1/2 :-)
Still, in the end it seems more complicated than having gdb link in
the same library that gdbserver does.
And with such a library, I'd make it so that "non-gdb tools" could use it too.
For example, it would make easier the building of gdbservers that need
to speak something other than the remote protocol.
next prev parent reply other threads:[~2011-01-10 16:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 15:23 Yao Qi
2011-01-07 16:37 ` Doug Evans
2011-01-08 3:34 ` Yao Qi
2011-01-08 5:17 ` Joel Brobecker
2011-01-10 13:39 ` Frank Ch. Eigler
2011-01-10 14:09 ` Joel Brobecker
2011-01-10 15:10 ` Frank Ch. Eigler
2011-01-10 15:50 ` Paul Koning
2011-01-10 15:51 ` Doug Evans
2011-01-10 15:54 ` Frank Ch. Eigler
2011-01-10 16:35 ` Doug Evans [this message]
2011-01-10 19:02 ` Frank Ch. Eigler
2011-01-11 23:35 ` Joel Brobecker
2011-01-11 23:38 ` Joel Brobecker
2011-01-12 0:30 ` Frank Ch. Eigler
2011-01-12 17:54 ` Doug Evans
2011-01-12 18:06 ` Doug Evans
2011-01-12 18:43 ` Paul Koning
2011-01-12 19:04 ` Doug Evans
2011-01-12 20:09 ` Joel Brobecker
2011-01-12 20:48 ` Frank Ch. Eigler
2011-01-14 17:04 ` Doug Evans
2011-01-12 15:47 ` Tom Tromey
2011-01-07 17:17 ` Stan Shebs
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='AANLkTi=WSW8snse3PaNZTYnax6Mo6+F=Pah6JKo8=B2R@mail.gmail.com' \
--to=dje@google.com \
--cc=fche@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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