-
Notifications
You must be signed in to change notification settings - Fork 744
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
On LLVM 9.0.0-1.5.2 clang.clang_createIndex() hangs indefinitely #830
Comments
It's possible something's changed between 8.0.0 and 9.0.0. |
LLVM doesn't officially support DLLs on Windows. @delthas was able to come up with a hack that used to work well, but a few things changed with LLVM 9.0.0 requiring an update from Visual Studio 2015 to 2017. I guess we'll need to figure out how to make that work well again... |
What changed was mainly the need to add |
It looks like building DLLs on Windows is now kind of supported: https://reviews.llvm.org/D56774 |
While starting to debug this, I found something interesting. The
Because of that it may end up trying to load itself in an infinite loop, but it doesn't explain why it's not failing at load time... Well, in any case, that's probably something that needs to be fixed :) |
Thanks for reporting this. A colleague of mine is also looking into this. We have tried different combinations of compilation flags and trying to pinpoint the change that causes the issue, but so far no success. I will let him know of your finding. |
Good news, it looks like disabling that buggy |
I'm Menno's colleague. This fix does seem to do the trick indeed. Thanks! |
The workaround has been released with version 1.5.3. Thanks again for reporting and for testing! |
We updated our llvm-platform dependency from version 8.0.0-1.5.1 to 9.0.0-1.5.2. After updating we are unable to use the clang API, because it hangs on clang.clang_createIndex(). We can easily reproduce it by running the provided ClangASTVisitorExample with llvm-platform 9.0.0-1.5.2 dependency on windows x64.
The text was updated successfully, but these errors were encountered: