From: Chris Genly <chgenly@gmail.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: gdb@sourceware.org
Subject: Re: MI register groups
Date: Mon, 15 Jun 2009 18:43:00 -0000 [thread overview]
Message-ID: <ed4903890906151143g127ca954sde97ded03a1a0f5d@mail.gmail.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA079763AC@ecamlmw720.eamcs.ericsson.se>
Yes I saw that. Thanks. You are right that it would probably be
easier. But I'd prefer to contribute to the Eclipse DSF project
rather than having to apply patches to my source every time a new DSF
is released. I'm hoping in the long run defining register groups in
MI and providing patches to the DSF people will be less work. We'll
see. I may regret it. :-)
On Mon, Jun 15, 2009 at 11:24 AM, Marc Khouzam<marc.khouzam@ericsson.com> wrote:
>> -----Original Message-----
> /**
> * For the GDB GDBMI implementation there is only on group. The GPR and FPU registers are grouped into
> * one set. We are going to hard wire this set as the "General Registers".
> */
>
> And then everything about register groups is being done without using MI or GDB.
> If such an approach is sufficient for you, it would be much easier to get done.
>
> Marc
>
next prev parent reply other threads:[~2009-06-15 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 18:10 Chris Genly
2009-06-15 18:25 ` Marc Khouzam
2009-06-15 18:43 ` Chris Genly [this message]
[not found] ` <ed4903890906151141w1300057g98606b5a3a38fbe2@mail.gmail.com>
2009-06-15 18:44 ` Marc Khouzam
2009-06-15 18:34 ` Vladimir Prus
2009-06-15 18:48 ` Chris Genly
2009-06-15 19:22 ` Vladimir Prus
2009-06-15 19:25 ` Chris Genly
2009-06-15 20:18 ` Daniel Jacobowitz
2009-06-15 18:34 ` Daniel Jacobowitz
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=ed4903890906151143g127ca954sde97ded03a1a0f5d@mail.gmail.com \
--to=chgenly@gmail.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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