On Monday 23 November 2009, Thomas Kindler wrote: > When single stepping on a STM32, I'm constantly caught in interrupt > handler code. This makes debugging almost impossible for non-trivial > programs with timer and other peripheral interrupts. > > I have seen that there's an "cortex_m3 maskisr on/off" command, but it's > awkward to use from eclipse.
Does that solve the problem you're facing though? > There seems to be no way to issue monitor > commands to OpenOCD during a debug session, or even bind commands to a > GUI button (perhaps a nice feature for Zylin-CDT?). > > Is there a good way to tell OpenOCD to mask ISRs after hitting a > breakpoint/single-stepping, but re-enable interrupts on run? If "monitor cortex_m3 maskisr on" (or "off") suffices, surely you can script things so GDB runs automatically? Or maybe not; I don't use GDB much. All I can say is that I've worked with debuggers that were built around KSH, specifically so that they could embed such scripting ... anywhere. :) I'm afraid I can't be of much help here. Though I can wonder whether this isn't something that would be a good match for "monitor mode" support ... where you can debug one task with the aid of some debug code linked into your program, while in the background the interrupts are firing and their handlers are doing their work. Making OpenOCD support that might be a good project someday. (The chainsaw IRQ handler should probably not be held off. - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
