From: Daniel Jacobowitz <drow@false.org>
To: Chris Genly <chgenly@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: MI register groups
Date: Mon, 15 Jun 2009 18:34:00 -0000 [thread overview]
Message-ID: <20090615183439.GA25415@caradoc.them.org> (raw)
In-Reply-To: <ed4903890906151110m3a651125u3504ac3b8fe8608f@mail.gmail.com>
On Mon, Jun 15, 2009 at 11:10:02AM -0700, Chris Genly wrote:
> I'm working on an Eclipse interface to a debugger produced by the
> company I work for. I notice Both GDB and Eclipse support the concept
> of register groups. But MI does not support the concept of register
> groups. I'd like to extend the MI spec to include register groups.
> Who would I talk to about this?
This list is the right place.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-06-15 18:34 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
[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 [this message]
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=20090615183439.GA25415@caradoc.them.org \
--to=drow@false.org \
--cc=chgenly@gmail.com \
--cc=gdb@sourceware.org \
/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