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
[C++] querying was stuck on Call.getArgument without detailed log #16068
Comments
Thank you for reaching out with this performance issue. Can you please share the entire log file with us (the one you already posted a snippet of)? In general, here are some guidelines for optimising CodeQL queries that the team has written up in the CodeQL documentation: |
Hi @ginsbach , thanks for your replying, and I've invited you in my private repo to check the entire log file. And thanks for your reference. Hope to your reply. Thank you. |
I will launch another issue for this question |
Could you tell us more about the pattern you are trying to detect with this query? Rather than writing the logic yourself for matching function return values to function call expressions, the CodeQL dataflow library for C/C++ may be able to handle this for you already. I don't know your definition of |
Hi @adityasharad , thanks for your reply and sorry for my delay. As you can see in my posted query, it's a part of recursive backtracing And in some cases, return value Feel free to contact my if anything is unclaer. Thanks again. |
related log:
My query has been running far far more than 669s, but no further output log, it's confusing for me to debug.
Related query:
These LoCs are for checking whether a
FunctionCall
's returnedExpr
is from (local taint) its arguments, and determine what's next on recursive back-tracingisTarget()
.I'm using a out-dated version of CodeQL CLI, maybe I'll update my tool chains first. But still hope to be helped~
The text was updated successfully, but these errors were encountered: