From: Yao Qi <yao@codesourcery.com>
To: Doug Evans <dje@google.com>, Stan Shebs <stan@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: duplicated code in gdb and gdbserver
Date: Sat, 08 Jan 2011 03:34:00 -0000 [thread overview]
Message-ID: <4D27DB30.4080603@codesourcery.com> (raw)
In-Reply-To: <AANLkTinMZ6hchkv1h+H265Eu7+Zsb4GizJ2XA5-VUnEO@mail.gmail.com>
On 01/08/2011 12:37 AM, Doug Evans wrote:
> Another example is individual target support. E.g., merging common
> bits of gdb's ${target}-nat.c files with gdbserver's ${target}-low.c
> files.
On 01/08/2011 01:17 AM, Stan Shebs wrote:
> One thing that we could be doing in addition to moving code is to
> scrutinize gdb/*-nat.c and friends, and abstract out some API for any
> in-GDB-itself assumptions. Hopefully that will help to minimize the
> need for #ifdef GDBSERVER hacks as we refactor the code.
Doug and Stan,
Thanks for your pointers and suggestions. Looks like it is not a small
piece of work, and IMO, merging common parts of gdb's ${target}-nat.c
and gdbserver's ${target}-low.c can be a starting point. I'll write
patches for this.
--
Yao Qi
next prev parent reply other threads:[~2011-01-08 3:34 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 [this message]
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
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=4D27DB30.4080603@codesourcery.com \
--to=yao@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@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