Balazs Benics

The `z3` constraint solver is not supported. z3 refutation is supported though. Ask CodeChecker about the `--z3=on` flag. I think they should simply drop it. Can I close this?

The `z3` constraint solver is not supported. z3 refutation is supported though. Ask CodeChecker about the `--z3=on` flag. I think they should simply drop it. Can I close this?

It seems working on my side. However, I noted you had a typo: `ANALYZER_ASSSERT` -> `ANALYZER_ASSERT` It should fix your issue. Let me know.

I could not reproduce your issue. ```bash cat > def.h api.c

Could you please share the reproducer c++ file? Also the clang --version would help a lot. I tried to reconstruct a dead store example according to your first plist, but...

Have you tried setting the `LD_PRELOAD` or `LD_LIBRARY_PATH` envvars to let the CodeChecker (thus the `ldlogger.so`) to find the suitable `glibc` shared library? `ldlogger` was build for `x86_64` right? It...

I believe all these paths point to executable files. About sourcing the virtual environment, I don't know. We should probably do something about that.

Confirmed. Thanks for reporting it. It seems like we shouldn't have hardcoded one of our internal plugin names. You probably won't have it available xD Your proposed fix should work....

According to my experiments, it seems like we don't even need to pass the `-plugin` nor the `-fplugin` options. For me, the `-load` is enough to get the checkers working....

This works for me: ```bash CC_ANALYZERS_FROM_PATH=yes \ PATH="/path/to/llvm-project/build/bin:$PATH" \ CC_CLANGSA_PLUGIN_DIR=/path/to/myplugins \ CodeChecker checkers -o rows # It lists not only the builtin checkers, but the plugin ones! ``` Where `CC_CLANGSA_PLUGIN_DIR`...