It is possible that, for some programs, when issuing a step over command to gdb, the delay until the operation is completed is unacceptably large. For a sample triggering this issue, see libopencm3 example libopencm3-examples\examples\stm32\f4\stm32f4-discovery\usart, stepping over this code:
for (i = 0; i < 3000000; i++) { /* Wait a bit. */
__asm__("NOP"); // STEP OVER THIS LINE
}
Provide some workaround for this, it is very frustrating for the user.
It is possible that, for some programs, when issuing a
step overcommand to gdb, the delay until the operation is completed is unacceptably large. For a sample triggering this issue, see libopencm3 examplelibopencm3-examples\examples\stm32\f4\stm32f4-discovery\usart, stepping over this code:Provide some workaround for this, it is very frustrating for the user.