From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Remove HAVE_UINTPTR_T from gdb_thread_db.h
Date: Thu, 26 May 2011 17:39:00 -0000 [thread overview]
Message-ID: <1306431533.2008.18.camel@hactar> (raw)
In-Reply-To: <4DD0B8D8.9060004@codesourcery.com>
On Mon, 2011-05-16 at 13:40 +0800, Yao Qi wrote:
> On 05/15/2011 01:07 AM, Joel Brobecker wrote:
> >> When I am trying to move gdb_thread_db.h to common/ dir,
> >
> > I am so sorry for not having the time to work on this project,
> > and so it make me uncomfortable saying this without offering
> > advice, but I still feel uncomfortable about not having a clear
> > plan, and not knowing where we are going with this. I'm afraid
> > that the end result might be a tighter inter-dependency between
> > GDB and GDBserver instead of GDB and GDBserver sitting on top
> > of a common API (we could call it a mini libgdb).
>
> I wrote up plan in wiki http://sourceware.org/gdb/wiki/Common . I am
> not good at naming a project, so I name it as "Common" temporally.
>
> The plan is not done. I will complete it, and fill in with more details.
>
> Comments are welcome, and thanks in advance to put up with my writing.
I'm not familiar with gdbserver but would it make sense to make
gdbserver internally use the target_ops vector? That would make GDB's
-nat.c files usable without modification in gdbserver. Then it would be
a matter of porting the gdbserver's additional features which GDB native
doesn't have.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2011-05-26 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 6:22 Yao Qi
2011-05-14 17:07 ` Joel Brobecker
2011-05-16 5:41 ` Yao Qi
2011-05-26 17:39 ` Thiago Jung Bauermann [this message]
2011-05-27 18:45 ` Tom Tromey
2011-05-30 15:55 ` Joel Brobecker
2011-05-26 8:10 ` [committed] " Yao Qi
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=1306431533.2008.18.camel@hactar \
--to=bauerman@br.ibm.com \
--cc=brobecker@adacore.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