Force run to cursor not working with bundled gdb
Hi,
I've been using CLion for a few months now, I was previously using visual studio. When debugging there is one feature that I would sometimes need and it was the Set Next Statement. It would force the PC to be set to the desired location so you could properly investigate. I would have guessed that the Force run to cursor would have been the same thing but I have never managed to make it do what I want.
For example:
-I hit a breakpoint foo.cpp at line 196.
-I step over a few times, execution is now at line 200
-I set the cursor to 196 and do Force run to cursor
When using the bundled gdb, the PC jumps to a completely different location in the file (line 800 in a different method).
When using the bundled lldb, the PC jumps correctly to line 196.
I am using CLion.2018
Regards
Marc-Andre Hebert
Please sign in to leave a comment.
Hello! Thanks for the detailed description.
Please enable debugger logging as described here, reproduce the issue with GDB and send the resulting idea.log file to clion-support at jetbrains.com. Please also add the link to this thread in the email. Thank you in advance.