scripts/cpa.sh -svcomp23 -heap 4000M -benchmark -timelimit '900 s' -stats -spec /mnt/goblint-svcomp/goblint-bench/bench/concrat/properties/no-data-race.prp -64 /mnt/goblint-svcomp/goblint-bench/bench/concrat/pigz/main.c


--------------------------------------------------------------------------------


Running CPAchecker with Java heap of size 4000M.
Running CPAchecker with default stack size (1024k). Specify a larger value with -stack if needed.
Language C detected and set for analysis (CPAMain.detectFrontendLanguageIfNecessary, INFO)

Using the following resource limits: CPU-time limit of 900s (ResourceLimitChecker.fromConfiguration, INFO)

CPAchecker 2.2 (OpenJDK 64-Bit Server VM 17.0.8.1) started (CPAchecker.run, INFO)

Parsing CFA from file(s) "/mnt/goblint-svcomp/goblint-bench/bench/concrat/pigz/main.c" (CPAchecker.parse, INFO)

Error: Parsing failed (Integer value is too large to be represented by the highest possible type (unsigned long long int): 18446744073709551615.) (EclipseCParser.buildCFA, SEVERE)

Please make sure that the code can be compiled by a compiler.
If the code was not preprocessed, please use a C preprocessor
or specify the -preprocess command-line argument.
If the error still occurs, please send this error message
together with the input file to cpachecker-users@googlegroups.com.
 (CPAchecker.run, INFO)


CPAchecker general statistics
-----------------------------

Time for analysis setup:          1.712s
  Time for loading CPAs:          0.000s
  Time for loading parser:        0.269s
  Time for CFA construction:      1.418s
    Time for parsing file(s):     0.856s
    Time for AST to CFA:          0.416s
    Time for CFA sanity check:    0.000s
    Time for post-processing:     0.000s
Time for Analysis:                0.000s
CPU time for analysis:            0.000s
Total time for CPAchecker:        1.712s
Total CPU time for CPAchecker:    0.790s
Time for statistics:              0.007s

Time for Garbage Collector:       0.039s (in 5 runs)
Garbage Collector(s) used:    Copy, MarkSweepCompact

More details about the verification run can be found in the directory "./output".
