|Re: Step over doesn't let me run one line at a time [message #1774938 is a reply to message #1774702]
||Sun, 22 October 2017 02:19
Registered: October 2012
A common reason for seemingly erratic debugging behavior is failure to turn off all optimization. |
With GCC, you should compile with "-g -O0" (minus-capitalO-zero).
If optimization is already off, you may need to post a small example that illustrates what you are seeing.
It's not at all clear what you are describing.
What do you mean by: "starts to run, and it doesn't stop"?
Do you mean it runs to completion or otherwise terminates?
Perhaps the function is calling exit.
Perhaps it isn't returning to the point after the call (because of stack corruption, for example).
You may need to step into the function and single step to discover what it is doing.
[Updated on: Wed, 25 October 2017 03:21]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01814 seconds