java -Xmx8000000000 -Xss4m -jar ./plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar -data @noDefault -ultimatedata ./data -tc ../../../trunk/examples/toolchains/TreeAutomizer.xml -s ../../../trunk/examples/settings/chc/TreeAutomizer/TreeAutomizerStandardSettings.epf -i /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringConcatenation03_jayhorn-tmp_5.smt2 -------------------------------------------------------------------------------- This is Ultimate 0.1.24-1d12a10 [2019-03-21 19:58:09,978 INFO L170 SettingsManager]: Resetting all preferences to default values... [2019-03-21 19:58:09,982 INFO L174 SettingsManager]: Resetting UltimateCore preferences to default values [2019-03-21 19:58:09,995 INFO L177 SettingsManager]: Ultimate Commandline Interface provides no preferences, ignoring... [2019-03-21 19:58:09,996 INFO L174 SettingsManager]: Resetting Boogie Preprocessor preferences to default values [2019-03-21 19:58:09,997 INFO L174 SettingsManager]: Resetting Boogie Procedure Inliner preferences to default values [2019-03-21 19:58:09,998 INFO L174 SettingsManager]: Resetting Abstract Interpretation preferences to default values [2019-03-21 19:58:10,000 INFO L174 SettingsManager]: Resetting LassoRanker preferences to default values [2019-03-21 19:58:10,002 INFO L174 SettingsManager]: Resetting Reaching Definitions preferences to default values [2019-03-21 19:58:10,002 INFO L174 SettingsManager]: Resetting SyntaxChecker preferences to default values [2019-03-21 19:58:10,003 INFO L177 SettingsManager]: Büchi Program Product provides no preferences, ignoring... [2019-03-21 19:58:10,004 INFO L174 SettingsManager]: Resetting LTL2Aut preferences to default values [2019-03-21 19:58:10,005 INFO L174 SettingsManager]: Resetting PEA to Boogie preferences to default values [2019-03-21 19:58:10,006 INFO L174 SettingsManager]: Resetting BlockEncodingV2 preferences to default values [2019-03-21 19:58:10,007 INFO L174 SettingsManager]: Resetting ChcToBoogie preferences to default values [2019-03-21 19:58:10,008 INFO L174 SettingsManager]: Resetting AutomataScriptInterpreter preferences to default values [2019-03-21 19:58:10,009 INFO L174 SettingsManager]: Resetting BuchiAutomizer preferences to default values [2019-03-21 19:58:10,010 INFO L174 SettingsManager]: Resetting CACSL2BoogieTranslator preferences to default values [2019-03-21 19:58:10,012 INFO L174 SettingsManager]: Resetting CodeCheck preferences to default values [2019-03-21 19:58:10,014 INFO L174 SettingsManager]: Resetting InvariantSynthesis preferences to default values [2019-03-21 19:58:10,015 INFO L174 SettingsManager]: Resetting RCFGBuilder preferences to default values [2019-03-21 19:58:10,016 INFO L174 SettingsManager]: Resetting TraceAbstraction preferences to default values [2019-03-21 19:58:10,019 INFO L177 SettingsManager]: TraceAbstractionConcurrent provides no preferences, ignoring... [2019-03-21 19:58:10,019 INFO L177 SettingsManager]: TraceAbstractionWithAFAs provides no preferences, ignoring... [2019-03-21 19:58:10,020 INFO L174 SettingsManager]: Resetting TreeAutomizer preferences to default values [2019-03-21 19:58:10,020 INFO L174 SettingsManager]: Resetting IcfgToChc preferences to default values [2019-03-21 19:58:10,021 INFO L174 SettingsManager]: Resetting IcfgTransformer preferences to default values [2019-03-21 19:58:10,022 INFO L177 SettingsManager]: ReqToTest provides no preferences, ignoring... [2019-03-21 19:58:10,022 INFO L174 SettingsManager]: Resetting Boogie Printer preferences to default values [2019-03-21 19:58:10,023 INFO L174 SettingsManager]: Resetting ChcSmtPrinter preferences to default values [2019-03-21 19:58:10,024 INFO L174 SettingsManager]: Resetting ReqPrinter preferences to default values [2019-03-21 19:58:10,025 INFO L174 SettingsManager]: Resetting Witness Printer preferences to default values [2019-03-21 19:58:10,026 INFO L177 SettingsManager]: Boogie PL CUP Parser provides no preferences, ignoring... [2019-03-21 19:58:10,026 INFO L174 SettingsManager]: Resetting CDTParser preferences to default values [2019-03-21 19:58:10,027 INFO L177 SettingsManager]: AutomataScriptParser provides no preferences, ignoring... [2019-03-21 19:58:10,027 INFO L177 SettingsManager]: ReqParser provides no preferences, ignoring... [2019-03-21 19:58:10,027 INFO L174 SettingsManager]: Resetting SmtParser preferences to default values [2019-03-21 19:58:10,028 INFO L174 SettingsManager]: Resetting Witness Parser preferences to default values [2019-03-21 19:58:10,029 INFO L181 SettingsManager]: Finished resetting all preferences to default values... [2019-03-21 19:58:10,029 INFO L98 SettingsManager]: Beginning loading settings from /storage/repos/ultimate/releaseScripts/default/UAutomizer-linux/../../../trunk/examples/settings/chc/TreeAutomizer/TreeAutomizerStandardSettings.epf [2019-03-21 19:58:10,038 INFO L110 SettingsManager]: Loading preferences was successful [2019-03-21 19:58:10,038 INFO L112 SettingsManager]: Preferences different from defaults after loading the file: [2019-03-21 19:58:10,040 INFO L131 SettingsManager]: Preferences of TreeAutomizer differ from their defaults: [2019-03-21 19:58:10,040 INFO L133 SettingsManager]: * SMT solver=Internal_SMTInterpol [2019-03-21 19:58:10,042 INFO L131 SettingsManager]: Preferences of SmtParser differ from their defaults: [2019-03-21 19:58:10,042 INFO L133 SettingsManager]: * Use TreeAutomizer as solver for the given file (assumes the file contains Horn clauses only).=true [2019-03-21 19:58:10,081 INFO L81 nceAwareModelManager]: Repository-Root is: /tmp [2019-03-21 19:58:10,097 INFO L259 ainManager$Toolchain]: [Toolchain 1]: Applicable parser(s) successfully (re)initialized [2019-03-21 19:58:10,101 INFO L215 ainManager$Toolchain]: [Toolchain 1]: Toolchain selected. [2019-03-21 19:58:10,103 INFO L271 PluginConnector]: Initializing SmtParser... [2019-03-21 19:58:10,103 INFO L276 PluginConnector]: SmtParser initialized [2019-03-21 19:58:10,104 INFO L430 ainManager$Toolchain]: [Toolchain 1]: Parsing single file: /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringConcatenation03_jayhorn-tmp_5.smt2 [2019-03-21 19:58:10,183 INFO L210 SmtParser]: Parsing .smt2 file as a set of Horn Clauses unknown [2019-03-21 19:58:15,397 INFO L251 SmtParser]: Succesfully executed SMT file /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringConcatenation03_jayhorn-tmp_5.smt2 [2019-03-21 19:58:15,401 INFO L297 ainManager$Toolchain]: ####################### [Toolchain 1] ####################### [2019-03-21 19:58:15,403 INFO L131 ToolchainWalker]: Walking toolchain with 1 elements. [2019-03-21 19:58:15,403 INFO L113 PluginConnector]: ------------------------TreeAutomizer---------------------------- [2019-03-21 19:58:15,403 INFO L271 PluginConnector]: Initializing TreeAutomizer... [2019-03-21 19:58:15,405 INFO L276 PluginConnector]: TreeAutomizer initialized [2019-03-21 19:58:15,406 INFO L185 PluginConnector]: Executing the observer TreeAutomizerObserver from plugin TreeAutomizer for "de.uni_freiburg.informatik.ultimate.source.smtparser OTHER 21.03 07:58:15" (1/1) ... [2019-03-21 19:58:15,434 INFO L144 PredicateUnifier]: Initialized classic predicate unifier Received shutdown request... [2019-03-21 20:00:42,331 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,332 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,334 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,335 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,336 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,337 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,338 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,339 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,340 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,341 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,342 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,343 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,344 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,345 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,346 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,347 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,348 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,350 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,350 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,351 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,353 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,354 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,355 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,356 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,357 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,358 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,359 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,365 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,366 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,366 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,369 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,370 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,371 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,375 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,376 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,378 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,379 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,380 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,381 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,382 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,383 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,384 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,393 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,394 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,394 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,400 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,401 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,402 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,404 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,405 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,406 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,408 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,409 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,411 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,412 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,412 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,413 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,417 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,418 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,420 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,422 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,422 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,423 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,427 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,428 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,430 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,431 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,432 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,433 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,434 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,436 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,436 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,437 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,438 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,438 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,440 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,441 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,442 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,445 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,446 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,447 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,448 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,449 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,450 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,451 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,452 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,453 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,455 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,455 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,456 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,463 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,463 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,464 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,465 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,466 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,467 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,468 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,469 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,470 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,471 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,471 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,472 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,473 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,473 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,475 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,476 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,477 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,478 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,480 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,480 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,481 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,483 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,484 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,485 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,486 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,487 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,488 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,490 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,491 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,492 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,492 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,493 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,494 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,495 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,496 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,497 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,500 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,501 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,502 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,508 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,509 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,513 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,514 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,518 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,520 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,520 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,521 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,523 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,524 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,525 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,527 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,528 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,529 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,531 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,532 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,533 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,535 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,536 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,541 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,543 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,545 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,547 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,548 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,553 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,555 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,556 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,556 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 20:00:42,825 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__Block1_6_85_Int|) (<= |c_hhv__Block1_6_85_Int| 0)) is different from false [2019-03-21 20:00:42,826 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__Block1_6_85_Int|) (<= |c_hhv__Block1_6_85_Int| 0)) is different from true [2019-03-21 20:00:42,832 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__post_73_Int|) (<= |c_hhv__post_73_Int| 0)) is different from false [2019-03-21 20:00:42,832 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__post_73_Int|) (<= |c_hhv__post_73_Int| 0)) is different from true [2019-03-21 20:00:42,834 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__Block0_73_Int|) (<= |c_hhv__Block0_73_Int| 0)) is different from false [2019-03-21 20:00:42,834 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__Block0_73_Int|) (<= |c_hhv__Block0_73_Int| 0)) is different from true [2019-03-21 20:00:42,837 WARN L838 $PredicateComparison]: unable to prove that (and (<= |c_hhv__Block2_1_73_Int| 0) (<= 0 |c_hhv__Block2_1_73_Int|)) is different from false [2019-03-21 20:00:42,838 WARN L860 $PredicateComparison]: unable to prove that (and (<= |c_hhv__Block2_1_73_Int| 0) (<= 0 |c_hhv__Block2_1_73_Int|)) is different from true [2019-03-21 20:00:42,838 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__Block2_73_Int|) (<= |c_hhv__Block2_73_Int| 0)) is different from false [2019-03-21 20:00:42,839 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__Block2_73_Int|) (<= |c_hhv__Block2_73_Int| 0)) is different from true [2019-03-21 20:00:42,841 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__Block1_4_73_Int|) (<= |c_hhv__Block1_4_73_Int| 0)) is different from false [2019-03-21 20:00:42,841 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv__Block1_4_73_Int|) (<= |c_hhv__Block1_4_73_Int| 0)) is different from true [2019-03-21 20:00:42,854 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_post_76_Int|) (<= |c_hhv_()>_post_76_Int| 0)) is different from false [2019-03-21 20:00:42,857 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_post_76_Int|) (<= |c_hhv_()>_post_76_Int| 0)) is different from true [2019-03-21 20:00:42,857 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_6_81_Int|) (<= |c_hhv_()>_Block0_6_81_Int| 0)) is different from false [2019-03-21 20:00:42,858 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_6_81_Int|) (<= |c_hhv_()>_Block0_6_81_Int| 0)) is different from true [2019-03-21 20:00:42,858 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_5_84_Int|) (<= |c_hhv_()>_Block0_5_84_Int| 0)) is different from false [2019-03-21 20:00:42,859 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_5_84_Int|) (<= |c_hhv_()>_Block0_5_84_Int| 0)) is different from true [2019-03-21 20:00:42,859 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_4_83_Int|) (<= |c_hhv_()>_Block0_4_83_Int| 0)) is different from false [2019-03-21 20:00:42,863 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_4_83_Int|) (<= |c_hhv_()>_Block0_4_83_Int| 0)) is different from true [2019-03-21 20:00:42,864 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_3_82_Int|) (<= |c_hhv_()>_Block0_3_82_Int| 0)) is different from false [2019-03-21 20:00:42,864 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_3_82_Int|) (<= |c_hhv_()>_Block0_3_82_Int| 0)) is different from true [2019-03-21 20:00:42,865 WARN L838 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_2_79_Int|) (<= |c_hhv_()>_Block0_2_79_Int| 0)) is different from false [2019-03-21 20:00:42,865 WARN L860 $PredicateComparison]: unable to prove that (and (<= 0 |c_hhv_()>_Block0_2_79_Int|) (<= |c_hhv_()>_Block0_2_79_Int| 0)) is different from true [2019-03-21 20:00:42,893 WARN L189 SmtUtils]: Removed 1 from assertion stack [2019-03-21 20:00:42,893 INFO L256 ToolchainWalker]: Toolchain cancelled while executing plugin de.uni_freiburg.informatik.ultimate.plugins.generator.treeautomizer. Reason: Timeout or Toolchain cancelled by user [2019-03-21 20:00:42,896 INFO L168 Benchmark]: Toolchain (without parser) took 147494.41 ms. Allocated memory was 578.8 MB in the beginning and 2.7 GB in the end (delta: 2.1 GB). Free memory was 399.8 MB in the beginning and 569.6 MB in the end (delta: -169.8 MB). Peak memory consumption was 1.9 GB. Max. memory is 7.1 GB. [2019-03-21 20:00:42,898 INFO L168 Benchmark]: SmtParser took 0.20 ms. Allocated memory is still 135.3 MB. Free memory is still 111.6 MB. There was no memory consumed. Max. memory is 7.1 GB. [2019-03-21 20:00:42,898 INFO L168 Benchmark]: TreeAutomizer took 147492.25 ms. Allocated memory was 578.8 MB in the beginning and 2.7 GB in the end (delta: 2.1 GB). Free memory was 399.8 MB in the beginning and 569.6 MB in the end (delta: -169.8 MB). Peak memory consumption was 1.9 GB. Max. memory is 7.1 GB. [2019-03-21 20:00:42,899 INFO L337 ainManager$Toolchain]: ####################### End [Toolchain 1] ####################### --- Results --- * Results from de.uni_freiburg.informatik.ultimate.core: - StatisticsResult: Toolchain Benchmarks Benchmark results are: * SmtParser took 0.20 ms. Allocated memory is still 135.3 MB. Free memory is still 111.6 MB. There was no memory consumed. Max. memory is 7.1 GB. * TreeAutomizer took 147492.25 ms. Allocated memory was 578.8 MB in the beginning and 2.7 GB in the end (delta: 2.1 GB). Free memory was 399.8 MB in the beginning and 569.6 MB in the end (delta: -169.8 MB). Peak memory consumption was 1.9 GB. Max. memory is 7.1 GB. * Results from de.uni_freiburg.informatik.ultimate.plugins.generator.treeautomizer: - TimeoutResult: Timeout (de.uni_freiburg.informatik.ultimate.plugins.generator.treeautomizer) Toolchain cancelled while SimplifyDDAWithTimeout was simplifying term of DAG size 1 for 3ms.. RESULT: Ultimate could not prove your program: Timeout Completed graceful shutdown