Skip to content

Conversation

@Michael137
Copy link

When stopped in a hidden frame (either because we selected the hidden frame or hit a breakpoint inside it), a user most likely is intersted in exploring the immediate frames around it. But currently issuing up/down commands will unconditionally skip over all hidden frames.

This patch makes it so up/down commands don't skip hidden frames if the frame we started it was a hidden frame.

(cherry picked from commit 4749bf5)

… when navigating up/down (llvm#166394)

When stopped in a hidden frame (either because we selected the hidden
frame or hit a breakpoint inside it), a user most likely is intersted in
exploring the immediate frames around it. But currently issuing
`up`/`down` commands will unconditionally skip over all hidden frames.

This patch makes it so `up`/`down` commands don't skip hidden frames if
the frame we started it was a hidden frame.

(cherry picked from commit 4749bf5)
@Michael137
Copy link
Author

@swift-ci test

@Michael137 Michael137 merged commit 22188a0 into stable/21.x Nov 5, 2025
3 checks passed
@Michael137 Michael137 deleted the lldb/hidden-frame-to-21.x branch November 5, 2025 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants