Step causes GDB to spin in infinite loop when PC doesn't change

[Denio, Mike]

>>>>
I recall we used to have some issues like that, where GDB wouldn't stop 
stepping and would give you enough time to ctrl-C your way out of it, 
but they were fixed as far as I recall.

Are you using non-stop mode with synchronous commands? You might want to 
try sending asynchronous commands (passing &), that way GDB will give 
you the prompt instantly and you will have full control again. You can 
then issue an interruption (interrupt -a) to stop everything.
<<<<

Again, its not so much "what is the right command to use?" as it is "what happens if the user sends the wrong command?".

I'm still new to this, but my interpretation of "step" was "step until the high level language instruction is complete, even if its multiple opcodes". This makes sense to me, to step over C instructions or multi opcode pseudo ops. The interpretation of "step" that makes less sense to me is "keep calling step until the PC changes", because if the PC didn't change after the first step, why would it ever change?

I appreciate the feedback however, and I'll just tell users to be careful with the step command.

Mike