On Mon, Jul 16, 2012 at 4:58 PM, Akos Vandra <[email protected]> wrote: > When stopping the debugger in a ISR on cortex-m3, the content of the > LR is 0xFFFFFFFx, so when the code branches to that address the return > from interrupt is done. However at the moment when gdb does not know > this, and tries to access the memory at this address, which casues the > mentioned errors. Maybe there should be a check for this address, or > something?
It could perhaps be advantageous to detect this address being read and fail immediately, instead of trying to perform the read. For one thing, we can (possibly) stop the confusing error message from being printed. It also avoids the extra transfer, which probably saves some (tiny amount of) time every step. It doesn't fix the versaloon hanging, though, since that probably happens for any failed access which we can't special case. Moreover, GDB really should be aware of this special value for armv7-m targets, so a correct stack trace can be followed across an exception boundary. I don't know if there's any progress on this in GDB. /Andreas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
