Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: [rfc/rfa] [4/4] SPU enhancements: GDB/MI extensions
Date: Mon, 04 Jun 2007 20:22:00 -0000	[thread overview]
Message-ID: <20070604202224.GA26302@caradoc.them.org> (raw)
In-Reply-To: <200706042013.l54KD3da002950@d12av02.megacenter.de.ibm.com>

On Mon, Jun 04, 2007 at 10:13:03PM +0200, Ulrich Weigand wrote:
> That might be a good idea in general, but in this particular case,
> preparing the data requires quite a bit of effort and knowledge of
> the data format.  I'm not sure I'd want to describe the effects of,
> say, info_spu_dma_cmdlist in XML.  I also want to avoid having to
> duplicate that processing in GDB and the IDE ...

Right, but I didn't mean something quite that ambitious.  What does
the IDE end up doing with the output of these commands, and does it
want to parse them or just display them as text?

I have a half-finished sketch of a register groups interface that lets
GDB present arbitrary control structures from the target as
"registers" to the front end.  There will be a generic MI command to
get groups of these things and the individual members will show up
through -var-list-children as varobjs.  But that may not be suitable.

Another option would be something like this, if the output of the MI
commands is general enough.  Excuse my MI syntax if it's completely
wrong, please.

-> -arch-info-list
<- ^done,infos=["spu dma", "spu signals"]
-> -arch-info "spu dma"
<- ^done,[whatever]

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-04 20:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 19:34 Ulrich Weigand
2007-06-02 20:38 ` Eli Zaretskii
2007-06-03 13:29   ` Ulrich Weigand
2007-06-03 16:45     ` Eli Zaretskii
2007-06-04 20:00 ` Daniel Jacobowitz
2007-06-04 20:13   ` Ulrich Weigand
2007-06-04 20:22     ` Daniel Jacobowitz [this message]
2007-06-04 22:59       ` Ulrich Weigand
2007-06-05 11:12         ` Daniel Jacobowitz
2007-06-14 20:05           ` Ulrich Weigand
2007-06-21  2:23             ` Ricardo Marin Matinata
2007-06-21 22:22               ` Nick Roberts
2007-06-22 20:53               ` Jim Blandy
2007-06-20  0:28 Nick Roberts

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=20070604202224.GA26302@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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