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
Codeql database create fails when building mozilla #16001
Comments
|
Could you zip up and upload the database directory? It will contain the logs of what is probably a crash midway through writing a compressed trap file. |
Of course. Here's the zip of database directory. Thanks for your help |
|
It seems that there are indeed around 360 files on which we crash, as @smowton already suspected. These seem internal errors in the C/C++ frontend that we use. You might want to re-try with CodeQL 2.16.4 or later, as that includes some C/C++ frontend improvements, which may solve your issues. Note that this concerns less than 10% of source files being compiled, so you still should have a fairly complete database. |
Thanks for your suggestion. I tried it again with CodeQL 2.16.5 and I think it worked better but the issue persists. Which is way lesser files than what it should be. Do you think there's a way I could fix this? I appreciate your help. |
I'm trying to build mozilla from this repo and create a cpp codeql database.
In order to that, I first run
./mach configureand after it's done, I run the following command to create the database:~/codeql/codeql database create mozilla4 --language=c-cpp --command="./mach build"Which builds mozilla successfully, but it fails in the importing trap file stage. I have included the logs for creating the database and importing dataset.
A glance of the errors is like:
I can build mozilla separately following similar steps, but when I try to create a database it fails. The database is created in the end, but some of the files are missing and are not added to the database.
Can someone please point me to the right direction on how to solve this issue?
The text was updated successfully, but these errors were encountered: