-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
General issue: Randomly happens com.semmle.util.exception.CatastrophicError: End of file found while looking for '.pop' with a C++ project #11586
Comments
@github/codeql-c-extractor : Would you mind taking a look, please? |
Hi @changyuheng Thanks for the report. This is different from #9929. One of the files produced during tracing seems to be incomplete, causing your problem. Version 2.6.3 of the CodeQL CLI is frozen in time, so we cannot get this fixed for that version. However, I would like to know if this problem still occurs with the latest version of the CLI, so we can fix the problem in the next version if it still occurs. This won't work in combination with the supplemental tools, unfortunately. Would you be willing to create a database with the latest CLI version, which can be found here? Then, if the failure still occurs, would you be willing to share the Thanks. |
Hi @jketema, I'm willing to create the database for you. But if the latest CodeQL CLI is not compatible with https://github.com/microsoft/Windows-Driver-Developer-Supplemental-Tools, I'm afraid I have no methods to do it. |
The steps from https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/static-tools-and-codeql#building-your-codeql-database also apply to the latest CodeQL CLI. It's just the analysis step that is not likely to work, but that's not relevant here. |
I see what you're saying. I guess the database will be compatible. Do you mean I can let the CI use the latest CodeQL CLI to create the database, then use the compatible CodeQL CLI to do the analysis, and whenever I see the creation of the database fails, I sent the database to you? I think I can do that. There is just another issue that complicates the process: |
@changyuheng It seems the failure is occurring when the database is created. To determine whether this failure persists in the newer version of CodeQL CLI, @jketema is recommending that you do the following:
If the problem does persist in v2.11.5, a bug will need to be created in CodeQL CLI to track and resolve this issue to get you unblocked. |
Thank you for the clearance. However, the issue does not happen every time, so instead of manually reproducing it, I guess I have to put it into our CI. |
@changyuheng Apologies for not responding earlier. It's as @lauragonzalezzz says.
Or write a script that creates the database, checks whether the error occurred, and repeats if it doesn't. You might first want to try that with the 2.6.3 CLI to see whether you can make that work. |
Thank you for replying. I can write a dedicate verification script. As I mentioned earlier it's a bit complicated. |
Hi @jketema, @lauragonzalezzz, and @hvitved, thank you all for your kind response. With I'll keep doing my test for a week. I'll let you know if I reproduce the issue. But I currently consider this a hardware issue, so I'm gonna close this issue for now. Thank you so much again for your support. |
Hi @changyuheng If that didn't even work, would it be possible for you to share a copy of the |
Hi @jketema, is this the log that CodeQL CLI will generate? Unfortunately, I didn't keep the original CodeQL CLI environment. Or do you mean the log file of that problematic round I created in my build process? |
It's one of the files that you can find in the database directory once you've tried to create a database. |
I didn't keep the database directory; I'm sorry! I consider that as part of the build results and my current config will remove results every time starting another build. |
No worries. Closing this again for now, as there's not much we can do at this point. Feel free to reopen at any time. |
Hi @jketema, I just replicated a similar issue on another computer. Could you please let me know what information you may like to check?
|
If possible, I'd like a copy of the Note The file contains mentions of file names and possibly some references to source code we could not parse, so before sharing, please make sure these are not sensitive. |
Hi @jketema, the log files build-tracer and database-create contain the file names as well as function names. Because this is a proprietary repository, I cannot share the logs with you. Sorry about that. But thanks for your support anyhow! |
No worries, I was sort of expecting that. You could have a look to see if there are any |
The only
But successful builds have the same |
By limiting the threads I was able to run the build without any problems on a computer with 32 GB RAM installed. I also have another machine that has 128 GB RAM installed that has been running the same code building with the number of threads bound to the CPU count for more than a year without any issues. I believe the root case was the shortage of RAM. CC: @mandyhs |
The symptom is pretty much the same with #9929 but the issue does not happen 100% of the time.
CodeQL CLI version:
2.6.3
CodeQL queries version:
lgtm/1.29.0
Windows Driver Developer Supplemental Tools version:
WHCP_22H2
microsoft/Windows-Driver-Developer-Supplemental-Tools#38
The text was updated successfully, but these errors were encountered: