-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Name lookup in expressions not working on Windows #24863
Comments
TestCompletion is also failing because of this bug |
Right now the following tests are marked as failing because of this bug and they are failing: TestCModules.py |
I'd be curious if the native pdb reader fixes any of these. I don't yet recommend running the full test suite against the native PDB reader, but it might be interesting to try running individual tests against it and see if it fixes any of them. Name lookup in expressions depends on having a high quality AST reconstruction from the debug info, and I know from the tests I've written that in the native PDB reader we do a better job of this in many cases than the DIA based PDB reader. If you're interested in trying, you can set LLDB_USE_NATIVE_PDB_READER=1 in your environment and then try a targeted run of just these tests. It would be interesting to know if it makes a difference. |
I ran the suite with LLDB_USE_NATIVE_PDB_READER=1 and I got the same results. |
This test is annotated with but is currently passing for me on FreeBSD 13 locally, and in Cirrus-CI |
Extended Description
Name lookup for types and symbols is not working properly. This is currently causing (at a minimum) the following tests to fail.
TestChar1632T.py
TestRdar12991846.py
TestConstVariables.py
TestCallCPPFunction.py
TestCallStopAndContinue.py
TestCallUserDefinedFunction.py
TestCModules.py
TestCPPThis.py
TestExprs2.py
TestOverloadedFunctions.py
TestRvalueReferences.py
Errors can occur either when a value is cast to a specific type (as in the case of TestChar1632T.py), when a function is called (as in the case of TestCallCPPFunction.py), or in other scenarios as well.
It's possible that there are multiple underlying causes for the above failures. If so, please create a separate bug for tracking the sub-issues.
The text was updated successfully, but these errors were encountered: