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/StringCompare03_jayhorn-tmp_1.smt2 -------------------------------------------------------------------------------- This is Ultimate 0.1.24-1d12a10 [2019-03-21 17:31:40,996 INFO L170 SettingsManager]: Resetting all preferences to default values... [2019-03-21 17:31:40,998 INFO L174 SettingsManager]: Resetting UltimateCore preferences to default values [2019-03-21 17:31:41,009 INFO L177 SettingsManager]: Ultimate Commandline Interface provides no preferences, ignoring... [2019-03-21 17:31:41,010 INFO L174 SettingsManager]: Resetting Boogie Preprocessor preferences to default values [2019-03-21 17:31:41,011 INFO L174 SettingsManager]: Resetting Boogie Procedure Inliner preferences to default values [2019-03-21 17:31:41,012 INFO L174 SettingsManager]: Resetting Abstract Interpretation preferences to default values [2019-03-21 17:31:41,014 INFO L174 SettingsManager]: Resetting LassoRanker preferences to default values [2019-03-21 17:31:41,016 INFO L174 SettingsManager]: Resetting Reaching Definitions preferences to default values [2019-03-21 17:31:41,017 INFO L174 SettingsManager]: Resetting SyntaxChecker preferences to default values [2019-03-21 17:31:41,018 INFO L177 SettingsManager]: Büchi Program Product provides no preferences, ignoring... [2019-03-21 17:31:41,018 INFO L174 SettingsManager]: Resetting LTL2Aut preferences to default values [2019-03-21 17:31:41,019 INFO L174 SettingsManager]: Resetting PEA to Boogie preferences to default values [2019-03-21 17:31:41,020 INFO L174 SettingsManager]: Resetting BlockEncodingV2 preferences to default values [2019-03-21 17:31:41,022 INFO L174 SettingsManager]: Resetting ChcToBoogie preferences to default values [2019-03-21 17:31:41,022 INFO L174 SettingsManager]: Resetting AutomataScriptInterpreter preferences to default values [2019-03-21 17:31:41,023 INFO L174 SettingsManager]: Resetting BuchiAutomizer preferences to default values [2019-03-21 17:31:41,025 INFO L174 SettingsManager]: Resetting CACSL2BoogieTranslator preferences to default values [2019-03-21 17:31:41,027 INFO L174 SettingsManager]: Resetting CodeCheck preferences to default values [2019-03-21 17:31:41,029 INFO L174 SettingsManager]: Resetting InvariantSynthesis preferences to default values [2019-03-21 17:31:41,030 INFO L174 SettingsManager]: Resetting RCFGBuilder preferences to default values [2019-03-21 17:31:41,031 INFO L174 SettingsManager]: Resetting TraceAbstraction preferences to default values [2019-03-21 17:31:41,034 INFO L177 SettingsManager]: TraceAbstractionConcurrent provides no preferences, ignoring... [2019-03-21 17:31:41,034 INFO L177 SettingsManager]: TraceAbstractionWithAFAs provides no preferences, ignoring... [2019-03-21 17:31:41,035 INFO L174 SettingsManager]: Resetting TreeAutomizer preferences to default values [2019-03-21 17:31:41,036 INFO L174 SettingsManager]: Resetting IcfgToChc preferences to default values [2019-03-21 17:31:41,036 INFO L174 SettingsManager]: Resetting IcfgTransformer preferences to default values [2019-03-21 17:31:41,037 INFO L177 SettingsManager]: ReqToTest provides no preferences, ignoring... [2019-03-21 17:31:41,037 INFO L174 SettingsManager]: Resetting Boogie Printer preferences to default values [2019-03-21 17:31:41,038 INFO L174 SettingsManager]: Resetting ChcSmtPrinter preferences to default values [2019-03-21 17:31:41,039 INFO L174 SettingsManager]: Resetting ReqPrinter preferences to default values [2019-03-21 17:31:41,040 INFO L174 SettingsManager]: Resetting Witness Printer preferences to default values [2019-03-21 17:31:41,041 INFO L177 SettingsManager]: Boogie PL CUP Parser provides no preferences, ignoring... [2019-03-21 17:31:41,041 INFO L174 SettingsManager]: Resetting CDTParser preferences to default values [2019-03-21 17:31:41,042 INFO L177 SettingsManager]: AutomataScriptParser provides no preferences, ignoring... [2019-03-21 17:31:41,042 INFO L177 SettingsManager]: ReqParser provides no preferences, ignoring... [2019-03-21 17:31:41,043 INFO L174 SettingsManager]: Resetting SmtParser preferences to default values [2019-03-21 17:31:41,044 INFO L174 SettingsManager]: Resetting Witness Parser preferences to default values [2019-03-21 17:31:41,045 INFO L181 SettingsManager]: Finished resetting all preferences to default values... [2019-03-21 17:31:41,045 INFO L98 SettingsManager]: Beginning loading settings from /storage/repos/ultimate/releaseScripts/default/UAutomizer-linux/../../../trunk/examples/settings/chc/TreeAutomizer/TreeAutomizerStandardSettings.epf [2019-03-21 17:31:41,052 INFO L110 SettingsManager]: Loading preferences was successful [2019-03-21 17:31:41,053 INFO L112 SettingsManager]: Preferences different from defaults after loading the file: [2019-03-21 17:31:41,055 INFO L131 SettingsManager]: Preferences of TreeAutomizer differ from their defaults: [2019-03-21 17:31:41,055 INFO L133 SettingsManager]: * SMT solver=Internal_SMTInterpol [2019-03-21 17:31:41,056 INFO L131 SettingsManager]: Preferences of SmtParser differ from their defaults: [2019-03-21 17:31:41,057 INFO L133 SettingsManager]: * Use TreeAutomizer as solver for the given file (assumes the file contains Horn clauses only).=true [2019-03-21 17:31:41,096 INFO L81 nceAwareModelManager]: Repository-Root is: /tmp [2019-03-21 17:31:41,109 INFO L259 ainManager$Toolchain]: [Toolchain 1]: Applicable parser(s) successfully (re)initialized [2019-03-21 17:31:41,112 INFO L215 ainManager$Toolchain]: [Toolchain 1]: Toolchain selected. [2019-03-21 17:31:41,114 INFO L271 PluginConnector]: Initializing SmtParser... [2019-03-21 17:31:41,114 INFO L276 PluginConnector]: SmtParser initialized [2019-03-21 17:31:41,115 INFO L430 ainManager$Toolchain]: [Toolchain 1]: Parsing single file: /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringCompare03_jayhorn-tmp_1.smt2 [2019-03-21 17:31:41,191 INFO L210 SmtParser]: Parsing .smt2 file as a set of Horn Clauses unknown [2019-03-21 17:31:42,738 INFO L251 SmtParser]: Succesfully executed SMT file /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringCompare03_jayhorn-tmp_1.smt2 [2019-03-21 17:31:42,743 INFO L297 ainManager$Toolchain]: ####################### [Toolchain 1] ####################### [2019-03-21 17:31:42,745 INFO L131 ToolchainWalker]: Walking toolchain with 1 elements. [2019-03-21 17:31:42,745 INFO L113 PluginConnector]: ------------------------TreeAutomizer---------------------------- [2019-03-21 17:31:42,746 INFO L271 PluginConnector]: Initializing TreeAutomizer... [2019-03-21 17:31:42,748 INFO L276 PluginConnector]: TreeAutomizer initialized [2019-03-21 17:31:42,749 INFO L185 PluginConnector]: Executing the observer TreeAutomizerObserver from plugin TreeAutomizer for "de.uni_freiburg.informatik.ultimate.source.smtparser OTHER 21.03 05:31:42" (1/1) ... [2019-03-21 17:31:42,775 INFO L144 PredicateUnifier]: Initialized classic predicate unifier Received shutdown request... [2019-03-21 17:33:35,623 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,624 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,624 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,625 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,625 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,626 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,626 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,627 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,627 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,628 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,628 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,628 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,629 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,629 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,630 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,630 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,630 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,631 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,631 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,635 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,635 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,636 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,636 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,637 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,637 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,638 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,638 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,639 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,639 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,639 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,640 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,640 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,641 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,641 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,642 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,642 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,642 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,643 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,643 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,644 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,644 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,645 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,645 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,646 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,646 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,647 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,647 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,647 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,648 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,648 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,649 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,649 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,650 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,650 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,650 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,651 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,651 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,652 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,652 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,653 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,653 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,654 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,654 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,655 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,655 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,655 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,656 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,657 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,657 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,657 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:33:35,687 WARN L189 SmtUtils]: Removed 1 from assertion stack [2019-03-21 17:33:35,688 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 17:33:35,690 INFO L168 Benchmark]: Toolchain (without parser) took 112946.46 ms. Allocated memory was 248.5 MB in the beginning and 2.9 GB in the end (delta: 2.7 GB). Free memory was 210.2 MB in the beginning and 982.2 MB in the end (delta: -772.0 MB). Peak memory consumption was 1.9 GB. Max. memory is 7.1 GB. [2019-03-21 17:33:35,692 INFO L168 Benchmark]: SmtParser took 0.20 ms. Allocated memory is still 131.1 MB. Free memory is still 109.9 MB. There was no memory consumed. Max. memory is 7.1 GB. [2019-03-21 17:33:35,692 INFO L168 Benchmark]: TreeAutomizer took 112943.76 ms. Allocated memory was 248.5 MB in the beginning and 2.9 GB in the end (delta: 2.7 GB). Free memory was 210.2 MB in the beginning and 982.2 MB in the end (delta: -772.0 MB). Peak memory consumption was 1.9 GB. Max. memory is 7.1 GB. [2019-03-21 17:33:35,694 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 131.1 MB. Free memory is still 109.9 MB. There was no memory consumed. Max. memory is 7.1 GB. * TreeAutomizer took 112943.76 ms. Allocated memory was 248.5 MB in the beginning and 2.9 GB in the end (delta: 2.7 GB). Free memory was 210.2 MB in the beginning and 982.2 MB in the end (delta: -772.0 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 0ms.. RESULT: Ultimate could not prove your program: Timeout Completed graceful shutdown