1

The debugger itself seems to work fine, but my problem is : When I set a breakpoint in the gutter and then I properly run the debugger, the code stop at my breakpoint, but it doesn't stop before executing the code line at the breakpoint, it stops after having executed it.

Even when I step over the code, the line in yellow has always been executed instead of being the next line to be executed..

I've looked in the preferences menu of CS50 IDE, but didn't find anything. Does someone has a solution ?

Improve this question
3
  • This happens to me too. Tough thing when you are debugging...hope this gets answered because I have had to resort to archaic methods...printf()
    – Karthik Krishnan
    Commented May 14, 2017 at 13:15
  • I use debug50 a lot and have never experienced such a problem. Can you add a specific example and how it was determined that the line in question already executed?
    – DinoCoderSaurus
    Commented May 14, 2017 at 17:51
  • You should try update50. It may resolve your problem.
    – MIB
    Commented May 20, 2017 at 7:58

1 Answer 1

Reset to default
0

Try make clean. This worked for me. Then run make. and it will recompile all the files. Then rerun debug50

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .