Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Doug Evans <dje@google.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 19:02:00 -0000	[thread overview]
Message-ID: <20110110190139.GF17302@redhat.com> (raw)
In-Reply-To: <AANLkTi=WSW8snse3PaNZTYnax6Mo6+F=Pah6JKo8=B2R@mail.gmail.com>

Hi, Doug -

dje wrote:
> [...]
> 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.

That's true.

> For example, it would make easier the building of gdbservers that
> need to speak something other than the remote protocol.

I guess it depends on how many new abstractions one wishes to invent.
The remote protocol is well-proven, so experimental design is not
needed.  New protocols may have associated state machines that are
sufficiently close to the remote protocol that one can bridge to them
easily, or sufficiently far that gdb infrun/core changes would be
needed.  It depends.  Until one comes along though, I would propose
going with what we know.

- FChE


  reply	other threads:[~2011-01-10 19:02 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
2011-01-10 19:02           ` Frank Ch. Eigler [this message]
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=20110110190139.GF17302@redhat.com \
    --to=fche@redhat.com \
    --cc=dje@google.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