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/StringMiscellaneous03_jayhorn-tmp_13.smt2 -------------------------------------------------------------------------------- This is Ultimate 0.1.24-1d12a10 [2019-03-21 18:38:49,691 INFO L170 SettingsManager]: Resetting all preferences to default values... [2019-03-21 18:38:49,693 INFO L174 SettingsManager]: Resetting UltimateCore preferences to default values [2019-03-21 18:38:49,705 INFO L177 SettingsManager]: Ultimate Commandline Interface provides no preferences, ignoring... [2019-03-21 18:38:49,705 INFO L174 SettingsManager]: Resetting Boogie Preprocessor preferences to default values [2019-03-21 18:38:49,707 INFO L174 SettingsManager]: Resetting Boogie Procedure Inliner preferences to default values [2019-03-21 18:38:49,708 INFO L174 SettingsManager]: Resetting Abstract Interpretation preferences to default values [2019-03-21 18:38:49,710 INFO L174 SettingsManager]: Resetting LassoRanker preferences to default values [2019-03-21 18:38:49,712 INFO L174 SettingsManager]: Resetting Reaching Definitions preferences to default values [2019-03-21 18:38:49,712 INFO L174 SettingsManager]: Resetting SyntaxChecker preferences to default values [2019-03-21 18:38:49,713 INFO L177 SettingsManager]: Büchi Program Product provides no preferences, ignoring... [2019-03-21 18:38:49,714 INFO L174 SettingsManager]: Resetting LTL2Aut preferences to default values [2019-03-21 18:38:49,715 INFO L174 SettingsManager]: Resetting PEA to Boogie preferences to default values [2019-03-21 18:38:49,716 INFO L174 SettingsManager]: Resetting BlockEncodingV2 preferences to default values [2019-03-21 18:38:49,717 INFO L174 SettingsManager]: Resetting ChcToBoogie preferences to default values [2019-03-21 18:38:49,718 INFO L174 SettingsManager]: Resetting AutomataScriptInterpreter preferences to default values [2019-03-21 18:38:49,719 INFO L174 SettingsManager]: Resetting BuchiAutomizer preferences to default values [2019-03-21 18:38:49,720 INFO L174 SettingsManager]: Resetting CACSL2BoogieTranslator preferences to default values [2019-03-21 18:38:49,723 INFO L174 SettingsManager]: Resetting CodeCheck preferences to default values [2019-03-21 18:38:49,724 INFO L174 SettingsManager]: Resetting InvariantSynthesis preferences to default values [2019-03-21 18:38:49,725 INFO L174 SettingsManager]: Resetting RCFGBuilder preferences to default values [2019-03-21 18:38:49,727 INFO L174 SettingsManager]: Resetting TraceAbstraction preferences to default values [2019-03-21 18:38:49,729 INFO L177 SettingsManager]: TraceAbstractionConcurrent provides no preferences, ignoring... [2019-03-21 18:38:49,730 INFO L177 SettingsManager]: TraceAbstractionWithAFAs provides no preferences, ignoring... [2019-03-21 18:38:49,730 INFO L174 SettingsManager]: Resetting TreeAutomizer preferences to default values [2019-03-21 18:38:49,731 INFO L174 SettingsManager]: Resetting IcfgToChc preferences to default values [2019-03-21 18:38:49,732 INFO L174 SettingsManager]: Resetting IcfgTransformer preferences to default values [2019-03-21 18:38:49,733 INFO L177 SettingsManager]: ReqToTest provides no preferences, ignoring... [2019-03-21 18:38:49,733 INFO L174 SettingsManager]: Resetting Boogie Printer preferences to default values [2019-03-21 18:38:49,734 INFO L174 SettingsManager]: Resetting ChcSmtPrinter preferences to default values [2019-03-21 18:38:49,735 INFO L174 SettingsManager]: Resetting ReqPrinter preferences to default values [2019-03-21 18:38:49,736 INFO L174 SettingsManager]: Resetting Witness Printer preferences to default values [2019-03-21 18:38:49,737 INFO L177 SettingsManager]: Boogie PL CUP Parser provides no preferences, ignoring... [2019-03-21 18:38:49,737 INFO L174 SettingsManager]: Resetting CDTParser preferences to default values [2019-03-21 18:38:49,738 INFO L177 SettingsManager]: AutomataScriptParser provides no preferences, ignoring... [2019-03-21 18:38:49,738 INFO L177 SettingsManager]: ReqParser provides no preferences, ignoring... [2019-03-21 18:38:49,738 INFO L174 SettingsManager]: Resetting SmtParser preferences to default values [2019-03-21 18:38:49,739 INFO L174 SettingsManager]: Resetting Witness Parser preferences to default values [2019-03-21 18:38:49,740 INFO L181 SettingsManager]: Finished resetting all preferences to default values... [2019-03-21 18:38:49,740 INFO L98 SettingsManager]: Beginning loading settings from /storage/repos/ultimate/releaseScripts/default/UAutomizer-linux/../../../trunk/examples/settings/chc/TreeAutomizer/TreeAutomizerStandardSettings.epf [2019-03-21 18:38:49,748 INFO L110 SettingsManager]: Loading preferences was successful [2019-03-21 18:38:49,748 INFO L112 SettingsManager]: Preferences different from defaults after loading the file: [2019-03-21 18:38:49,750 INFO L131 SettingsManager]: Preferences of TreeAutomizer differ from their defaults: [2019-03-21 18:38:49,750 INFO L133 SettingsManager]: * SMT solver=Internal_SMTInterpol [2019-03-21 18:38:49,751 INFO L131 SettingsManager]: Preferences of SmtParser differ from their defaults: [2019-03-21 18:38:49,752 INFO L133 SettingsManager]: * Use TreeAutomizer as solver for the given file (assumes the file contains Horn clauses only).=true [2019-03-21 18:38:49,790 INFO L81 nceAwareModelManager]: Repository-Root is: /tmp [2019-03-21 18:38:49,808 INFO L259 ainManager$Toolchain]: [Toolchain 1]: Applicable parser(s) successfully (re)initialized [2019-03-21 18:38:49,814 INFO L215 ainManager$Toolchain]: [Toolchain 1]: Toolchain selected. [2019-03-21 18:38:49,816 INFO L271 PluginConnector]: Initializing SmtParser... [2019-03-21 18:38:49,816 INFO L276 PluginConnector]: SmtParser initialized [2019-03-21 18:38:49,817 INFO L430 ainManager$Toolchain]: [Toolchain 1]: Parsing single file: /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringMiscellaneous03_jayhorn-tmp_13.smt2 [2019-03-21 18:38:49,899 INFO L210 SmtParser]: Parsing .smt2 file as a set of Horn Clauses unknown [2019-03-21 18:39:06,690 INFO L251 SmtParser]: Succesfully executed SMT file /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringMiscellaneous03_jayhorn-tmp_13.smt2 [2019-03-21 18:39:06,695 INFO L297 ainManager$Toolchain]: ####################### [Toolchain 1] ####################### [2019-03-21 18:39:06,696 INFO L131 ToolchainWalker]: Walking toolchain with 1 elements. [2019-03-21 18:39:06,697 INFO L113 PluginConnector]: ------------------------TreeAutomizer---------------------------- [2019-03-21 18:39:06,697 INFO L271 PluginConnector]: Initializing TreeAutomizer... [2019-03-21 18:39:06,700 INFO L276 PluginConnector]: TreeAutomizer initialized [2019-03-21 18:39:06,701 INFO L185 PluginConnector]: Executing the observer TreeAutomizerObserver from plugin TreeAutomizer for "de.uni_freiburg.informatik.ultimate.source.smtparser OTHER 21.03 06:39:06" (1/1) ... [2019-03-21 18:39:06,723 INFO L144 PredicateUnifier]: Initialized classic predicate unifier Received shutdown request... [2019-03-21 18:41:29,860 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,863 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,869 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,875 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,886 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,890 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,890 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,892 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,894 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,896 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,898 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,900 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,903 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,904 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,906 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,908 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,910 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,912 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,913 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,914 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,917 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,918 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,920 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,924 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,926 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,928 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,929 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,931 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,933 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,935 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,938 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,940 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,942 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,944 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,946 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,948 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,951 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,953 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,955 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,957 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,959 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,959 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,961 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,963 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,965 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,967 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,969 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,971 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,972 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,974 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,976 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,978 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,980 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,980 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,982 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,984 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,986 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,988 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,991 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,991 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,993 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,995 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,997 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:29,999 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,001 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,002 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,004 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,008 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,010 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,012 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,014 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,014 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,016 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,018 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,020 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,022 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,025 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,027 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,028 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,030 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,032 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,034 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,036 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,039 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,042 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,044 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,046 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,047 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 18:41:30,572 WARN L838 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_5_237_Int|)) is different from false [2019-03-21 18:41:30,573 WARN L860 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_5_237_Int|)) is different from true [2019-03-21 18:41:30,574 WARN L838 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_4_237_Int|)) is different from false [2019-03-21 18:41:30,575 WARN L860 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_4_237_Int|)) is different from true [2019-03-21 18:41:30,576 WARN L838 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_3_237_Int|)) is different from false [2019-03-21 18:41:30,576 WARN L860 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_3_237_Int|)) is different from true [2019-03-21 18:41:30,577 WARN L838 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_2_237_Int|)) is different from false [2019-03-21 18:41:30,577 WARN L860 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_2_237_Int|)) is different from true [2019-03-21 18:41:30,579 WARN L838 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_1_237_Int|)) is different from false [2019-03-21 18:41:30,579 WARN L860 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_1_237_Int|)) is different from true [2019-03-21 18:41:30,580 WARN L838 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_237_Int|)) is different from false [2019-03-21 18:41:30,581 WARN L860 $PredicateComparison]: unable to prove that (not (= 5 |c_hhv_()>_Block0_237_Int|)) is different from true [2019-03-21 18:41:30,582 WARN L838 $PredicateComparison]: unable to prove that (ite (= |c_hhv_()>_pre_0_Int| 5) (<= |c_hhv_()>_pre_0_Int| 2) (not (= 5 |c_hhv_()>_pre_0_Int|))) is different from false [2019-03-21 18:41:30,582 WARN L860 $PredicateComparison]: unable to prove that (ite (= |c_hhv_()>_pre_0_Int| 5) (<= |c_hhv_()>_pre_0_Int| 2) (not (= 5 |c_hhv_()>_pre_0_Int|))) is different from true [2019-03-21 18:41:30,646 WARN L189 SmtUtils]: Removed 1 from assertion stack [2019-03-21 18:41:30,646 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 18:41:30,649 INFO L168 Benchmark]: Toolchain (without parser) took 143953.61 ms. Allocated memory was 1.3 GB in the beginning and 2.2 GB in the end (delta: 911.2 MB). Free memory was 208.3 MB in the beginning and 1.6 GB in the end (delta: -1.4 GB). There was no memory consumed. Max. memory is 7.1 GB. [2019-03-21 18:41:30,650 INFO L168 Benchmark]: SmtParser took 0.20 ms. Allocated memory is still 131.6 MB. Free memory is still 109.2 MB. There was no memory consumed. Max. memory is 7.1 GB. [2019-03-21 18:41:30,651 INFO L168 Benchmark]: TreeAutomizer took 143951.01 ms. Allocated memory was 1.3 GB in the beginning and 2.2 GB in the end (delta: 911.2 MB). Free memory was 208.3 MB in the beginning and 1.6 GB in the end (delta: -1.4 GB). There was no memory consumed. Max. memory is 7.1 GB. [2019-03-21 18:41:30,652 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.6 MB. Free memory is still 109.2 MB. There was no memory consumed. Max. memory is 7.1 GB. * TreeAutomizer took 143951.01 ms. Allocated memory was 1.3 GB in the beginning and 2.2 GB in the end (delta: 911.2 MB). Free memory was 208.3 MB in the beginning and 1.6 GB in the end (delta: -1.4 GB). There was no memory consumed. 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 2ms.. RESULT: Ultimate could not prove your program: Timeout Completed graceful shutdown