Actions
Feature #7877
openBenchExec should be used properly
Status:
New
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
01/20/2017
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
Now BenchExec is used in such a way that we can not support:
- collecting multiple error traces from verifiers
- support arbitrary verifiers from SV-COMP
- For collecting error traces the local client should use paths provided by verifier to find the resulting witnesses. Right now the corresponding code is hardcoded into both VTG strategy and local client especially for CPAchecker.
- The vcloud client uses home made functions for processing results, it should use a library functions provided for that purpose. It will enable support for all features of BenchExec including correct path for collecting results and proper determination of verdicts.
No data to display
Actions