You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm facing an issue where, from what I can tell, the config file IS properly appended to the command, but for some reason, the options in it are not applied, but when they are added to the command line directly, they are.
I've added an excerpt of the log for both cases:
with "codechecker.executor.arguments": "--disable clang-diagnostic-sign-compare":
It can be seen that both expand to the same final command, but the second one using the config file still has clang-diagnostic-sign-compare enabled.
The command here has a different binary path, but that's just because there is no config supplied. I can verify that it's the same when the config file is still used (and unrelated parameters appended), and as long as the option is directly in the settings, it is applied, and if it is in the config file, it isn't.
Thanks for any help!
The text was updated successfully, but these errors were encountered:
I think the reason for the config file not working is because it's supposed to take each argument separately, so the full command line is parsed as if it was passed as ".../cli.py" "analyze" "--output" ".codechecker/reports" "--disable clang-diagnostic-sign-compare", and not as "--disable" "clang-diagnostic-sign-compare" or "--disable=clang-diagnostic-sign-compare".
Two potential fixes could be to write --disable= instead of --disable , or break it up into multiple arguments such as "analyze": [ "--disable", "..." ].
I'm facing an issue where, from what I can tell, the config file IS properly appended to the command, but for some reason, the options in it are not applied, but when they are added to the command line directly, they are.
I've added an excerpt of the log for both cases:
with
"codechecker.executor.arguments": "--disable clang-diagnostic-sign-compare"
:and with
"codechecker.executor.arguments": "--config codechecker.json"
andcodechecker.json
:It can be seen that both expand to the same final command, but the second one using the config file still has clang-diagnostic-sign-compare enabled.
The command here has a different binary path, but that's just because there is no config supplied. I can verify that it's the same when the config file is still used (and unrelated parameters appended), and as long as the option is directly in the settings, it is applied, and if it is in the config file, it isn't.
Thanks for any help!
The text was updated successfully, but these errors were encountered: