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

>>>>
That's what the step/next commands are designed to do. GDB will keep 
stepping until it sees a line change. I suppose a "continue" command 
here would be more appropriate, as GDB will send it once and keep 
waiting for the outcome. stepi/nexti would be undesirable given they 
will stop after a single instruction.
<<<<

Thanks that makes some level of sense. Stepi also works fine. It just seemed a little odd that the desired behavior would be to lock up GDB if a user accidentally did a "step" on a jump to $ instruction. You can't even get out with ^C. I had to kill the debug server to regain control of GDB.