From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: dje@google.com (Doug Evans)
Cc: pedro@codesourcery.com (Pedro Alves),
gdb@sourceware.org, karl.leplat@parrot.com (karl leplat)
Subject: Re: How to use gdbserver for X86 host with arm-linux target ?
Date: Wed, 14 Sep 2011 12:27:00 -0000 [thread overview]
Message-ID: <201109141227.p8ECRQ9Z008918@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <CADPb22T2-mJ5T7H6JNU7JE9J0KpzZAgCuun73zi_WXqrwMg33w@mail.gmail.com> from "Doug Evans" at Sep 13, 2011 10:28:14 AM
Doug Evans wrote:
> On Mon, Sep 12, 2011 at 6:48 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> > There's code in native arm port of gdb to support hardware breakpoints
> > and watchpoints (arm-linux-nat.c). =A0Someone interested should be able
> > to port it to gdbserver.
>
> Seems like this another example where gdb suffers from having two code
> bases (gdb, gdbserver) to implement the same functionality.
Yes. What I'd really like to see in the long term would be to move
gdbserver over to use the same "struct target_ops" interface as GDB
to talk to its platform back ends, and then provide native targets
as stand-alone implementations of that interface that can be linked
with both GDB and gdbserver. The remote protocol would then become
a 1:1 marshalling of target_ops ...
But that's a significant effort, and would require a bit of cleanup
of target_ops first, I guess.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2011-09-14 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 11:25 karl leplat
2011-09-12 13:48 ` Pedro Alves
2011-09-12 17:24 ` Ulrich Weigand
2011-09-13 17:28 ` Doug Evans
2011-09-14 12:27 ` Ulrich Weigand [this message]
2011-09-14 19:36 ` 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=201109141227.p8ECRQ9Z008918@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=karl.leplat@parrot.com \
--cc=pedro@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