[SR-4638] Make file level variables "frame" variables when you aren't in an explicit function #4634
Labels
Comments
|
Comment by Jim Ingham (JIRA) The variables you refer to are really file level variables, and as such will show up in the output of "target variable". And in normal debug sessions where you are in the context of some function in that file, you would NOT want frame variable to show these variables. But because you are debugging a file that has no explicit function, your code is in some sense running at the file level context, and so we should pretend that these file level variables are actually frame variables, which we don't do at present. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attachment: Download
Environment
Swift 3.1, macOS, Ubuntu 16.10
Additional Detail from JIRA
md5: f02574aa83e8bfbea72e10f66803433a
Issue Description:
Steps to reproduce
Unzip swift-lldb-frame-variable.zip
cd App
rm -rf .build
swift build
lldb ./.build/debug/App
breakpoint set --line 4
run
frame variable
Actual Behavior
"frame variable" doesn't display any variables informations
Expected Behavior
"frame variable" displayed variables informations
Versions
OSs:
macOS 10.12.4
Ubuntu 16.10
Swift versions:
macOS: Apple Swift version 3.1 (swiftlang-802.0.51 clang-802.0.41), Target: x86_64-apple-macosx10.9
Linux: Swift version 3.1 (swift-3.1-RELEASE) Target: x86_64-unknown-linux-gnu
LLDB versions:
macOS: lldb-370.0.40, Swift-3.1
Linux: lldb version 4.0.0 (git@github.com:apple/swift-lldb.git revision ab05d1ed7cd81032110419ed8be77aa721ff62df), Swift-3.1 (revision 2dddbaf9c390094e37b45d83419ecf61d3707667), clang revision 9772bf511a32353fad73e38fdfc501d5fccb50d2, llvm revision a7c680da5182d29e2c6441d484a307b695902c64
Additional information
Project generated with SwiftPM
The text was updated successfully, but these errors were encountered: