(1) Looked at the forum for "debug timer interrupts", but couldn't see a match for this 'bug'.
(2) Not sure if this should be here or GCC forum;
but here goes:
How do I get the debugger to ignore timer interrupts?
I'm happily stepping through code, and every 10 or 20 lines, or if there's a serial Tx, bam!, the debugger jumps to the timer ISR.
That's no too bad, since the ISR is one line:
The problem is that after the ISR exits, you can be down into some low level routine, typically a RS232 or I2C routine, which might be 5 or 7 levels below the code that I was debugging.
Returning from this always problematic, since comms typically involves plenty of loops, e.g., to transmit buffers, etc.
Other IDEs, e.g., RowleyCrossStudio(for ARM + GCC) do not have this 'problem'.
How can I get the debugger not to step into the ISR?
Thanks, "That's just another burr in my socks" Alf