MartinNowack

The labels "suggestions" and "discussions" sound too generic to me. Projects is a good way to go.

The hoisting is indeed an issue. @YikeZhou Can you use the option `--klee-call-optimisation=false` and check if this solves your problem? There is a longer discussion here #1059 and here #1008.

@jryans That sounds super interesting. Just to clarify, KLEE supports debug information as long as your bitcode is compiled with it, i.e. `clang-13 -O1 -g -c -emit-llvm` would emit debug...

@ccadar Can you remove the line in: https://github.com/klee/klee/blob/master/utils/sanitizers/lsan.txt to not ignore this leak anymore?

While it's almost two years later, we finally managed to increase the minimal required version of CMake on KLEE's side. Thanks for the patience and great solver!

@ccadar Some required checks should be removed before this PR could be merged.

Great! For the documentation, it is already in https://klee-se.org/build-script/ last section and the only thing missing is that we have to manually push those built images to https://github.com/orgs/klee/packages. But this...

@ccadar Well, no they have not been all addressed. Here are my thoughts on it, this might be a more general thing on how to handle such cases - less...

@ccadar Yes, I'm working on it. It's already in progress.

I would like to break the tie on this. In general I see good arguments from all sides, so thank you for this fruitful discussion. Here are my two cents...