Hi Anders and all Anders Montonen wrote:
> On Mar 5, 2012, at 11:49, John Dallaway wrote: > >> In the short term, I will look at creating a GDB target description file >> that we can use to accommodate the larger register set returned by our >> stubs. > > Here's one I've been using when debugging via OpenOCD: > > <http://www.mail-archive.com/openocd-development@lists.berlios.de/msg18182.html> Thank you for the pointer. That target description works fine for me, but I noticed that it uses the org.gnu.gdb.arm.core feature which describes the "cpsr" register. That register is named "xpsr" in GDB's default M-profile feature: http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/features/arm-m-profile.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=src It seems appropriate to use the org.gnu.gdb.arm.m-profile feature rather than the org.gnu.gdb.arm.core feature and therefore adopt the register naming used by current GDB for M-profile targets. However, this might possibly cause problems for people who have existing GDB scripts developed for arm-eabi-gdb 6.8.50.20080706 that reference the cpsr register by name. Does anyone care about this? John Dallaway eCos maintainer http://www.dallaway.org.uk/john
