-
Notifications
You must be signed in to change notification settings - Fork 339
[cherry-pick][lldb] Fix stepping through conformance methods #10505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cherry-pick][lldb] Fix stepping through conformance methods #10505
Conversation
We already check this boolean in the `if` statement two lines above.
A future patch will need to create a new constructor for this class, and extracting code out of its sole existing constructor will make this easier. This commit creates a helper function for the code computing the target frame to step out to.
A subsequent commit will create a new constructor for ThreadPlanStepOut, which needs to reuse much of the same logic of the existing constructor. This commit places all of that reusable logic into a separate function.
…6163) The function QueueThreadPlanForStepOutNoShouldStop has the semantics of "go this parent frame"; ThreadPlanStepOut needs to respect that, not skipping over any frames it finds uninteresting. This commit creates a constructor that respects such instruction.
@swift-ci test |
fcab55a
to
fddb994
Compare
Forgot to disable the test on linux/windows. |
@swift-ci test |
Han, the new test is failing as if the fix weren't there.. |
@swift-ci test macos platform |
Have we always done CI with debug symbols for the swift std lib? |
Yup, confirmed, the presence of debug symbols in the standard library is causing this test to behave differently because we treat |
@swift-ci test |
fddb994
to
1bd67e3
Compare
@swift-ci test |
This PR cherry-picks the upstream LLVM commits fixing stepping through conformance methods.