This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc/rfa] [4/4] SPU enhancements: GDB/MI extensions
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: matinata at br dot ibm dot com
- Cc: Ulrich Weigand <uweigand at de dot ibm dot com>, Daniel Jacobowitz <drow at false dot org>, gdb-patches at sourceware dot org, eliz at gnu dot org
- Date: Fri, 22 Jun 2007 10:22:51 +1200
- Subject: Re: [rfc/rfa] [4/4] SPU enhancements: GDB/MI extensions
- References: <200706142004.l5EK4vTO021141@d12av02.megacenter.de.ibm.com> <1182392605.4974.58.camel@rmm-tp>
> So, roughly, a spu-info-dma would be transformed in to something like
> this:
>
> -arch-info dma
> ^done
> (gdb)
I'm out of my depth but isn't all this really target information, i.e., I
could be on an i386 debugging spu remotely?
It's for you to decide if you want to display the information as for variable
objects or not but presumably there might be other architectures that
want provide similar output, e.g, "info mytarget dma". So I think a further
command is needed:
(gdb)
-target-name
^done,value="spu"
(gdb)
-target-info-list
^done,infos=[name="event",name="signal","name=mailbox",name="dma",name="proxydma"]
> -arch-info-list-children dma
> ^done,numchild="6",children=[child={name="dma.type",exp="type",
> numchild="0",type="int"},child={name="dma.mask",exp="mask",
> numchild="0",type="int"},child={name="dma.status",exp="status",
> numchild="0",type="int"},child={name="dma.stall_and_notify",
>...
--
Nick http://www.inet.net.nz/~nickrob