Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Koning <paul_koning@dell.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: GDB code reuse for gdbserver?
Date: Thu, 07 Oct 2010 18:58:00 -0000	[thread overview]
Message-ID: <9FA13E39-CC58-4BF7-ABC3-EBC473D4DADD@dell.com> (raw)
In-Reply-To: <4CAE1687.6040008@vmware.com>


On Oct 7, 2010, at 2:50 PM, Michael Snyder wrote:

> Joel Brobecker wrote:
>>> Does this make sense?  (In other words, would such an approach be
>>> welcomed?)
>> I think we talked about this a few weeks back.  The answer is a definite
>> yes.  What we should do, IMO, is have GDB depend on the gdbserver code.
>> That way, we can think of implementing a gdbserver as the first step
>> towards implementing a native GDB (or seen differently, if you have
>> implemented a native GDB, then you should have a gdbserver for free).

Interesting.  I had thought of it as the other way around, mostly because gdb is far more complete than gdbserver.

>> I think that Pedro also mentioned that the GNU/Linux nat support was now
>> better in gdbserver as well.

I didn't realize that...

>> That being said, I don't see this as an obvious task. But I would
>> certainly welcome it.
> 
> 
> Topic for the BoF?

Unfortunately I can't be there.

My reason for poking at this is (for the moment) NetBSD, which isn't supported at all in gdbserver.  There are bits in the NetBSD stream but those are not complete (thread support is an issue).  And while I could do it the existing way, i.e., do the work twice, it seemed to make sense to do it once and cover both use cases.

> 
> My sketchy memory suggests that there is an issue with licensing.
> Is not gdbserver somehow less restrictively licensed than gdb?

It doesn't look that way; both have GPL 3 on them in the current rev.

	paul


      reply	other threads:[~2010-10-07 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 18:37 Paul Koning
2010-10-07 18:47 ` Joel Brobecker
2010-10-07 18:50   ` Michael Snyder
2010-10-07 18:58     ` Paul Koning [this message]

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=9FA13E39-CC58-4BF7-ABC3-EBC473D4DADD@dell.com \
    --to=paul_koning@dell.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.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