Hi All,
I am trying
to use DSF C/C++ Remote Application
debug launch to debug a MIPS target using a cross compiled MIPS gdb
(based on
gdb 6.8) and a MIPS GDB Server which can communicate with MIPS target
using an EJTAG
probe. I am able to connect to the target successfully. But I am bit
confused
on why the register view lists lot of “Unknown”
registers with value as “Error:
Failed
to execute MI command: -data-list-register-values x 0 Error message
from
debugger back end: bad register number” before and after
the normal MIPS registers. (see attached screen shot)
When I
tried to debug MIPS target with CDT Hardware
Debugger launch configuration (which uses the CDI MI implementation)
using the
same gdb and GDB Server this behaviour was not there. I checked the
output of -data-list-register-names
MI command and I
can see lot of empty strings(“”) in the register name list before
and after MISP register names.
Is it some
difference in the way DSF MI and CDT MI implementation
interprets the output of -data-list-register-names
is causing the issue?
Thanks,
Jiju George