Fix conditional breakpoint evaluation when stepping onto breakpoint #943
+14
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@xusheng6 identified that LLDB will incorrectly report the stop reason as
Breakpointinstead ofSingleStepwhen stepping onto an instruction that has a breakpoint set. This caused conditional breakpoints to evaluate their condition even when the user explicitly stepped to that location which continues execution unexpectedly. #941 (comment)This fix tracks the last adapter operation and skips condition evaluation when the operation was a step (StepInto, StepOver, StepReturn, or their other variants). Condition evaluation now happens only when hitting breakpoints during Go/Continue operations.