PR# 12170 Run to This Point doesn't stop unless hit count matches

Selecting Run to This Point does not work correctly (in my view) when
there is a hit count setting (such as Break When Hit Count Equals)
or when When Hits specifies "Continue Execution" when breakpoint is hit.
This might be a conscious design decision, but I think Run to This Point
should *always* stop if execution reaches that point.  If one wants the
other behavior (i.e., if one wants the Hit Count and When Hits conditions
to be applied), one can just click either Start or Continue.  Note that
if I set a condition "False" on a breakpoint and run to that breakpoint,
execution *does* stop, which I think is the correct behavior.

The current behavior seems to be that the tests for whether to break and
whether to continue execution are applied when I select Run to This Point.
I think they should not be applied.

I think that behavior is reasonable.  If Run to this Point always stops at
that point, ignoring whether hit count meets the previously set criteria and
ignoring whether the condition (if any) evaluates to true, then printing any
When Hits messages or incrementing the hit count would be a little strange.

So I think the implemented behavior is fine.

This issue is now fixed by revision rev#67249.

Please not that if you use "Run To This Point" feature, if there was a break point, it won't be treated as a breakpoint, i.e: no print message, no hit count incrementation, no condition evaluation ... it will just stop as requested.

Do you agree with this behavior ?