This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Question :GDB remote protocol for smp target control through JTAG
- From: Tom Tromey <tromey at redhat dot com>
- To: Jaouen Michel <michel dot jaouen at yahoo dot fr>
- Cc: gdb-patches ml <gdb-patches at sourceware dot org>
- Date: Tue, 17 May 2011 12:05:08 -0600
- Subject: Re: Question :GDB remote protocol for smp target control through JTAG
- References: <609701.45771.qm@web24901.mail.ird.yahoo.com>
>>>>> "Jaouen" == Jaouen Michel <michel.jaouen@yahoo.fr> writes:
Jaouen> I am currently using a gdb client connected to a a remote server
Jaouen> (openocd) for debugging 2 cortex_a9 (0 and 1) running linux in
Jaouen> smp.
I can't comment on your remote protocol changes, as I don't know enough
about that.
Jaouen> print $_core => display the core number played in gdb client.
Jaouen> set $_core=($==1?0:1) => fix the display of the other core beeing at next continue (a fake continue is perfomed)
Jaouen> set $_core=-1ÂÂ => fix that next continue is real continue.
Jaouen> What are the comments on this additional feature for remote debugging.
It would be better to have a more command-oriented interface to this,
like the rest of gdb does. Using a magic convenience variable is
unusual.
E.g., you could have "info cpus" and a new "cpu" command, or something
along those lines.
Tom