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
[SR-4204] LLDB fails printing variables when self
refers to an empty struct
#4637
Comments
Hm. That often means the project is set to compile with optimizations on, but it sounds like that's not the case? |
Comment by Marc Knaup (JIRA) @belkadan yep, the build using Debug configuration and both, the app target and the framework, use |
Comment by Marc Knaup (JIRA) @belkadan I've just found a simple repro: it happens in all methods of structs which have no stored properties. |
Oh, that makes a lot of sense. We of course don't bother representing such a struct with any memory at run time, but that makes LLDB think there's no Tagging in jingham@apple.com (JIRA User). |
@swift-ci create |
marc (JIRA User) I seem to be experiencing this issue in Xcode 9.3. I'm getting a slightly different error though:
I'm using a static struct with all static functions and a single static let property. |
Comment by Michael Helmbrecht (JIRA) Getting the same error as @allenhumphreys; using an empty enum with all static methods in Xcode 9.3. |
Comment by Worth Baker (JIRA) Also getting this error on Xcode 9.3 when attempting lldb operations (po) on a struct with no properties and only static methods: "Couldn't apply expression side effects : couldn't get the data for variable self". Swapping the item from struct to class seems to fix the issue. |
Getting the same error (couldn't get the data for variable self) in Xcode 9.4, when trying to print out a variable in static method in a non-empty struct (has let properties). |
Environment
Xcode 8.3 beta 4
Additional Detail from JIRA
md5: 2712502f1f5b9c6b70b6428e42cd954e
is duplicated by:
Issue Description:
LLDB fails in 2 of the following cases:
The text was updated successfully, but these errors were encountered: