z3 VS codechecker

See https://cacm.acm.org/magazines/2023/6/273222-the-silent-revo... and also modern production rules engines like https://drools.org/

Oddly, back when “expert system shells” were cool people thought 10,000 rules were difficult to handle, now 1,000,000 might not be a problem at all. Back then the RETE algorithm was still under development and people were using linear search and not hash tables to do their lookups.

Also https://github.com/Z3Prover/z3

Note “the semantic web” is both an advance and a retreat in that OWL is a subset of first order logic which is really decidable and sorta kinda fast. It can do a lot but people aren’t really happy with what it can do.

Code correctness is a lost art. I requirement to think in abstractions is what scares a lot of devs to avoid it. The higher abstraction language (formal specs) focus on a dedicated language to describe code, whereas lower abstractions (code contracts) basically replace validation logic with a better model.

C# once had Code Contracts[1]; a simple yet powerful way to make formal specifications. The contracts was checked at compile time using the Z3 SMT solver[2]. It was unfortunately deprecated after a few years[3] and once removed from the .NET Runtime it was declared dead.

The closest thing C# now have is probably Dafny[4] while the C# dev guys still try to figure out how to implement it directly in the language[5].

[1] https://www.microsoft.com/en-us/research/project/code-contra...

[2] https://github.com/Z3Prover/z3

[3] https://github.com/microsoft/CodeContracts

[4] https://github.com/dafny-lang/dafny

[5] https://github.com/dotnet/csharplang/issues/105

I believe, Nim also has this functionality, although, it uses the [0]Z3Prover tool with a nim frontend [1]"DrNim" for proving.

[0]https://github.com/Z3Prover/z3

Don't get me wrong, there are times when Microsoft got it right the first time that was technically far superior to their competitors. Windows IOCP was theoretically capable of doing C10K as far back in 1994-95 when there wasn't any hardware support yet and UNIX world was bickering over how to do asynchronous I/O. Years later POSIX came up with select which was a shoddy little shit in comparison. Linux caved in finally only as recently as 2019 and implemented io_uring. Microsoft research has contributed some very interesting things to computer science like Z3 SAT solver and in collaboration with INRIA made languages like F* and Low* for formal specification and verification. But all this dwarfs in comparison to all the harm they did.

Z3 theorem prover SMT solver might help you.

Other than that, you should look at Z3 which is pretty damn good at these sort of theorems/constraints.

In the end I used Z3 Julia bindings instead. The hardest part was to get the result back from it, because I kept running into assertion violations from inside Z3

I'm trying to learn a little bit about Predicate Transformer Semantics (PTS) as part of a quick exploration of Z3.

> And you propose me instead to go and reverse engineer library Js code which I am not that proficient in, and rewrite all code in Java instead?..

Yes, rather than demand others cater to your whims, frankly.

Do you realise how hypocritical it sounds to complain that you are not proficient in Javascript, when others might not be proficient in ?

Go use Z3 if you need a prover in C++ (or Java), its far more robust (provided its the type you're after) than someones 700 LoC JavaScript implementation.

https://github.com/Z3Prover/z3

python3 new.py docker-php-extension-installer: https://github.com/mlocati/docker-php-extension-installer codechecker: https://github.com/Ericsson/codechecker SingleFileZ: https://github.com/gildas-lormeau/SingleFileZ china-dictatorship: https://github.com/cirosantilli/china-dictatorship vscode-docker: https://github.com/microsoft/vscode-docker flask-bones: https://github.com/cburmeister/flask-bones ProjectFib: https://github.com/anantdgoel/ProjectFib S3Mock: https://github.com/adobe/S3Mock home: https://github.com/gege-circle/home docker-php: https://github.com/chialab/docker-php dockbix-xxl: https://github.com/monitoringartist/dockbix-xxl wind-layer: https://github.com/sakitam-fdd/wind-layer powerstrip: https://github.com/ClusterHQ/powerstrip selenium-jupiter: https://github.com/bonigarcia/selenium-jupiter gnome-shell-extension-docker: https://github.com/gpouilloux/gnome-shell-extension-docker hacktoberfest-2022: https://github.com/docker/hacktoberfest-2022 azure-docker-extension: https://github.com/Azure/azure-docker-extension pgrocks-fdw: https://github.com/vidardb/pgrocks-fdw docker-php-yii2: https://github.com/dmstr/docker-php-yii2 docker-community-extensions: https://github.com/collabnix/docker-community-extensions alpine-php-fpm: https://github.com/joseluisq/alpine-php-fpm autoview-tradingview-chrome-docker-bot: https://github.com/IAMtheIAM/autoview-tradingview-chrome-docker-bot .config: https://github.com/zszszszsz/.config docker-phpfpm: https://github.com/adhocore/docker-phpfpm coc-docker: https://github.com/josa42/coc-docker china-dictatorhsip-6: https://github.com/cirosantilli/china-dictatorhsip-6 testcontainers-spock: https://github.com/testcontainers/testcontainers-spock Dockery: https://github.com/oslabs-beta/Dockery docker-extension: https://github.com/tailscale/docker-extension volumes-backup-extension: https://github.com/docker/volumes-backup-extension ajeetraina@Docker-Ajeet-Singh-Rainas-MacBook-Pro chatgpt % vi new.py ajeetraina@Docker-Ajeet-Singh-Rainas-MacBook-Pro chatgpt % python3 new.py .config: https://github.com/zszszszsz/.config Dockery: https://github.com/oslabs-beta/Dockery docker-extension: https://github.com/tailscale/docker-extension ransomware: https://github.com/abhir98/ransomware jfrog-docker-desktop-extension: https://github.com/jfrog/jfrog-docker-desktop-extension dd-extension-lgtm: https://github.com/cedricziel/dd-extension-lgtm openshift-dd-ext: https://github.com/redhat-developer/openshift-dd-ext k9s-dd-extension: https://github.com/spurin/k9s-dd-extension pgadmin4-docker-extension: https://github.com/marcelo-ochoa/pgadmin4-docker-extension trivy-docker-extension: https://github.com/aquasecurity/trivy-docker-extension drone-ci-docker-extension: https://github.com/harness/drone-ci-docker-extension docker-extension: https://github.com/loopDelicious/docker-extension swagger-editor-docker-extension: https://github.com/n-murphy/swagger-editor-docker-extension wasm-docker-extension: https://github.com/cmrigney/wasm-docker-extension microcks-docker-desktop-extension: https://github.com/microcks/microcks-docker-desktop-extension docker-extension-golang-playground: https://github.com/rumpl/docker-extension-golang-playground diveintoansible-extension: https://github.com/spurin/diveintoansible-extension docker-desktop-extension: https://github.com/okteto/docker-desktop-extension docker-extension-rabbitmq: https://github.com/Yogendra0Sharma/docker-extension-rabbitmq docker-storj-extension: https://github.com/elek/docker-storj-extension github-registry-docker-desktop-extension: https://github.com/peacecwz/github-registry-docker-desktop-extension docker-desktop-extension-issues: https://github.com/mutagen-io/docker-desktop-extension-issues sdw-docker-extension: https://github.com/marcelo-ochoa/sdw-docker-extension vcluster-dd-extension: https://github.com/loft-sh/vcluster-dd-extension extension-docker-desktop: https://github.com/epinio/extension-docker-desktop asyncapi-studio-docker-extension: https://github.com/thiyagu06/asyncapi-studio-docker-extension gefyra-docker-desktop-extension: https://github.com/gefyrahq/gefyra-docker-desktop-extension oraclexe-docker-extension: https://github.com/marcelo-ochoa/oraclexe-docker-extension docker-extensions-101: https://github.com/collabnix/docker-extensions-101 step-ca-docker-extension: https://github.com/hslatman/step-ca-docker-extension

Regarding problems on clang-tidy - have you looked into Codechecker? It is based on clang tidy but also supports cppcheck and marking issues as false positives/will not fix etc... https://github.com/Ericsson/codechecker

I've been down the llvm / clang / mlir rabbit hole recently and drank this : https://codechecker.readthedocs.io ...

Seconding `rr` as suggested by @tux3, it's great for debugging.

Also, the sanitizers for GCC and Clang (https://github.com/google/sanitizers), and the Clang static analyzer (and tidy too) through CodeChecker (https://codechecker.readthedocs.io/).

For the Clang static analyzer, make sure your LLVM toolchain has the Z3 support enabled (OK in Debian stable for example), and enable cross translation units (CTU) analysis too for better results.

If you have the bandwidth, I'd also recommend using something like https://github.com/Ericsson/codechecker which allows you to add results of analysis/tests to a database. This would in turn allow you to set your "stable" branch pipelines to fail if the diff of problems between runs shows you've introduced more issues that haven't been marked as addressed.

Another open source alternative is CodeChecker [1] with the Clang static analyzer [2]. Make sure the Clang toolchain has been compiled with Z3 [3] support for better results (it's the case in Debian stable), particularly for code doing bit operations. It supports cross files analysis ("cross translation units" or CTU), which last time I checked was not the case for IKOS and helps improve diagnostics.

It's not completely turn key if you use it for a cross compiled code base, but once set-up I prefer it to another professional tool: much less false alarms. Although it's good to have both, each one found issues not seen by the other.

  [1] https://github.com/Ericsson/codechecker