phasar

phasar copied to clipboard

PointsToInfo.cpp:64:3: error: implicit instantiation of undefined template 'std::vector<const llvm::Value *>'

2

- [x] I have searched open and closed issues for duplicates - [x] I made sure that I am not using an old project version (DO: pull PhASAR, update git...

yurivict

See #718

fabianbs96

Phasar conflicts with the pre-installed nlohmann-json during the run-time

3

- [x] I have searched open and closed issues for duplicates - [x] I made sure that I am not using an old project version (DO: pull PhASAR, update git...

yurivict

Tutorial (https://phasar.org/tutorial/) doesn't explain how to run Phasar

3

It only explains how to build it. It also says: > You can check if your installation works properly, by just typing in: > \> phasar but the phasar-2403 doesn't...

yurivict

A problem when build call graph in methd

1

Hi, I have a qusetion about how phasar build call graph. I find call graph miss some virtual call edges when I set the param "**ExactMatch**" to true in method...

ms-sky

Implementing Sparse IDE after Karakaya et al. https://doi.org/10.48550/arXiv.2401.14813 We NEED some handling of aliasing in the sparse CFG, otherwise the level of sparsity is too bad for analyzing LLVM IR

fabianbs96

In the process to make `nlohmann::json` and implementation detail (and not having any nlohmann type in our public APIs), we: 1. Deprecate all `getAsJson()` functions 2. Add `printAsJson()` functions that...

fabianbs96

The phasar-library `phasar_controller` is only used in `phasar-cli` and it is closely tied to it. Also, it does not fit well into our folder structure where all components that use...

fabianbs96

Phasar does not support exit() as exit points when calling getAllExitPoints()

2

I am using an old branch f-IDESolverStrategy because I need PropagateOntoStrategy in my project. (https://github.com/secure-software-engineering/phasar/tree/f-IDESolverStrategy) Recently, I find that Phasar does not support using `exit()` as exit point of function....

yuffon

The `LLVMBasedICFG` has too many tasks and is therefore hard to maintain and violates the single responsibility principle. This PR splits the `LLVMBasedICFG` into three parts: Callgraph-construction (`LLVMBasedCallGraphBuilder`), global ctors/dtors...

fabianbs96