From: Joel Brobecker <brobecker@adacore.com>
To: Paul Koning <paul_koning@dell.com>
Cc: gdb@sourceware.org
Subject: Re: GDB code reuse for gdbserver?
Date: Thu, 07 Oct 2010 18:47:00 -0000 [thread overview]
Message-ID: <20101007184722.GG2813@adacore.com> (raw)
In-Reply-To: <2CFC588D-558C-42F0-B7F1-BE6D68E9BA15@dell.com>
> 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).
I think that Pedro also mentioned that the GNU/Linux nat support was now
better in gdbserver as well.
That being said, I don't see this as an obvious task. But I would
certainly welcome it.
--
Joel
next prev parent reply other threads:[~2010-10-07 18:47 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 [this message]
2010-10-07 18:50 ` Michael Snyder
2010-10-07 18:58 ` Paul Koning
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=20101007184722.GG2813@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=paul_koning@dell.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