Fabian Schiebel

Your question seems to have multiple parts. Let's answer them one by one. 1. Getting the source function for a taint leak: We are not propagating this information and as...

After merging, this branch can be deleted

To reduce merge conflicts, we should first merge #516. However, comments are also welcome before^^

Yes, internally we are already working on it, so eventually it will be part of phasar. However, it will take quite some time due to the inherent complexity of the...

Hi @Ayohbk, I could reproduce your bug. It appears that the analysis is indeed correct here. This is, because it cannot know that the function `CRYPTO_malloc` is a memory allocator...

Hi @JJ2nu, there is currently no way of getting path information from PhASAR's analyses. However, we are working on a path sensitive analysis. We will eventually integrate it into open-source...

Yes, unfortunately, we didn't have time for creating a documentation regarding this yet.

LLVM removed CFLAndersAA and CFLSteensAA for LLVM15, so we will get rid of them as well (#610). Theremaining BasicAA and TBAA should be easier to get thread-safe

Plugins were removed from phasar

See https://github.com/secure-software-engineering/phasar/wiki/Coding-Conventions#include-vs-forward-declaration