Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

condition extractor -- dumping partial dumps #31

Open
tregua87 opened this issue Aug 23, 2023 · 0 comments
Open

condition extractor -- dumping partial dumps #31

tregua87 opened this issue Aug 23, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@tregua87
Copy link
Collaborator

Make the extractor able to dump function constraints right after the analysis terminates.

Add an additional flag to the tool (e.g., --partial_dump ??).

Probably add something like

if (OutputType == OutType::txt) {
    FunctionConditionsSet::storeIntoTextFile(
        fun_cond_set, OutputFile, verbose >= Verbosity::v1);
} else if (OutputType == OutType::json) {
    FunctionConditionsSet::storeIntoJsonFile(
        fun_cond_set, OutputFile, verbose >= Verbosity::v1);
} else if (OutputType == OutType::stdo) {
    SVFUtil::outs() << fun_cond_set.toString(verbose >= Verbosity::v1);
}

at around this line.

Then, add a cleaning method for FunctionConditionSet (here)

Partial results should be stored in a dedicated folder (another flag? a tmp folder?) and then grouped together through a dedicated tool (e.g., a python script to be invoked afterward).

@tregua87 tregua87 self-assigned this Aug 23, 2023
@tregua87 tregua87 changed the title analysis partial dumps condition extractor -- dumping partial dumps Aug 23, 2023
@tregua87 tregua87 added the enhancement New feature or request label Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants