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
ERROR: Uncaught Windows exception (EXCEPTION_STACK_OVERFLOW) #15885
Comments
|
Hi @eelbaz1,
That's correct, because it's failing on a single file, and not on the complete project, we consider this non-fatal.
Either the source file is very big, makes very heavy use of templates, or it's a bug in the C/C++ extractor. Would you be able to try with CodeQL 2.16.4 to see if the problem persists? That version contains a number of improvements/bug fixes in the C/C++ extractor code. |
|
Hi @jketema, Thanks for the response! build-tracer.log database-create.log |
|
Thanks for testing with 2.16.4.
That's not exceptionally big, so there must be something else going on. Looking at the latest log you shared. Am I correct that the line immediately after is ? Or is there something in between? |
|
nothing in between for the first two errors: the third error looks like this: |
|
Thanks. That unfortunately does not contain a lot of information (which can happen). Would it be possible for you to share the code on which this is happening? It will basically be impossible to debug this otherwise. |
|
Thanks for the help! but i cannot share the source code currently |
|
If you want to help debug this further, one thing could do is the run of the source files with this problem through the compiler's preprocessor to see if the problem still occurs. If is does, you could use creduce to create a much smaller file that exhibits the same problem and which is possibly shareable. Unfortunately, creduce is a bit cumbersome to setup on Windows, so I full understand if you don't want to go that route. |
fail during database create command
codeql database create -l=cpp -s=X:\MyProject -c=X:\MyProject\Build.cmd X:\MyProject\codeqlDB\01aef961-9707-40cb-b5ea-111d8acfb7b4observed in versions: 2.15.4, 2.16.3
despite the error, the command exit with code 0
what could be the cause of this issue? the error repeat itself 3 times on different files
build-tracer.log
dataset-import.log
The text was updated successfully, but these errors were encountered: