5 comments
Comment actions Permalink

Why doesn't this post get a reply; it's incredibly annoying. Currently, every time while debugging, Clion (2022.3, Build #CL-223.7571.171) halts at the orange arrow (execution point) somewhere early in my code and I have to continue (F9) through a loop many times until my code hits the place where I am interested in. If it was a breakpoint, I could remove it. But it's not; it seems to be the run-to-execution-point which I didn't (intentionally) invoke. Setting the execution point to the place I am interested in doesn't help. It just reverts to this place. I also tried moving it in the same function: same result: it just reverts to this wrong place.

 

Is there a way to turn off / unset the execution point (orange arrow) and the 'run-to-execution-point' behavior. I use breakpoints.

0
Comment actions Permalink

Hi Pum!

Such situations might happen when the breakpoint is set at one line and is actually resolved at the other line. Please see https://youtrack.jetbrains.com/issue/CPP-6237

You can check that by executing br l in case of LLDB or info breakpoints in case of GDB in the Debugger console.

0
Comment actions Permalink

Hey Anna, well, that is clear. Thanks very much for helping me. 

0
Comment actions Permalink

Yea, but not very helpful is it.

0
Comment actions Permalink

Mitch Raful there is no way to disable the arrow.

BTW there is a feature request to somehow mark actual breakpoint location when it is set on a line without code or have multiple locations - https://youtrack.jetbrains.com/issue/CPP-8609 . Feel free to comment or upvote it. See https://intellij-support.jetbrains.com/hc/en-us/articles/207241135-How-to-follow-YouTrack-issues-and-receive-notifications if you are not familiar with YouTrack.

0

Please sign in to leave a comment.