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/StringContains01_jayhorn-tmp_1.smt2 -------------------------------------------------------------------------------- This is Ultimate 0.1.24-1d12a10 [2019-03-21 17:16:48,223 INFO L170 SettingsManager]: Resetting all preferences to default values... [2019-03-21 17:16:48,225 INFO L174 SettingsManager]: Resetting UltimateCore preferences to default values [2019-03-21 17:16:48,237 INFO L177 SettingsManager]: Ultimate Commandline Interface provides no preferences, ignoring... [2019-03-21 17:16:48,237 INFO L174 SettingsManager]: Resetting Boogie Preprocessor preferences to default values [2019-03-21 17:16:48,238 INFO L174 SettingsManager]: Resetting Boogie Procedure Inliner preferences to default values [2019-03-21 17:16:48,239 INFO L174 SettingsManager]: Resetting Abstract Interpretation preferences to default values [2019-03-21 17:16:48,241 INFO L174 SettingsManager]: Resetting LassoRanker preferences to default values [2019-03-21 17:16:48,243 INFO L174 SettingsManager]: Resetting Reaching Definitions preferences to default values [2019-03-21 17:16:48,243 INFO L174 SettingsManager]: Resetting SyntaxChecker preferences to default values [2019-03-21 17:16:48,244 INFO L177 SettingsManager]: Büchi Program Product provides no preferences, ignoring... [2019-03-21 17:16:48,245 INFO L174 SettingsManager]: Resetting LTL2Aut preferences to default values [2019-03-21 17:16:48,246 INFO L174 SettingsManager]: Resetting PEA to Boogie preferences to default values [2019-03-21 17:16:48,247 INFO L174 SettingsManager]: Resetting BlockEncodingV2 preferences to default values [2019-03-21 17:16:48,248 INFO L174 SettingsManager]: Resetting ChcToBoogie preferences to default values [2019-03-21 17:16:48,249 INFO L174 SettingsManager]: Resetting AutomataScriptInterpreter preferences to default values [2019-03-21 17:16:48,250 INFO L174 SettingsManager]: Resetting BuchiAutomizer preferences to default values [2019-03-21 17:16:48,251 INFO L174 SettingsManager]: Resetting CACSL2BoogieTranslator preferences to default values [2019-03-21 17:16:48,253 INFO L174 SettingsManager]: Resetting CodeCheck preferences to default values [2019-03-21 17:16:48,255 INFO L174 SettingsManager]: Resetting InvariantSynthesis preferences to default values [2019-03-21 17:16:48,256 INFO L174 SettingsManager]: Resetting RCFGBuilder preferences to default values [2019-03-21 17:16:48,257 INFO L174 SettingsManager]: Resetting TraceAbstraction preferences to default values [2019-03-21 17:16:48,260 INFO L177 SettingsManager]: TraceAbstractionConcurrent provides no preferences, ignoring... [2019-03-21 17:16:48,260 INFO L177 SettingsManager]: TraceAbstractionWithAFAs provides no preferences, ignoring... [2019-03-21 17:16:48,260 INFO L174 SettingsManager]: Resetting TreeAutomizer preferences to default values [2019-03-21 17:16:48,261 INFO L174 SettingsManager]: Resetting IcfgToChc preferences to default values [2019-03-21 17:16:48,262 INFO L174 SettingsManager]: Resetting IcfgTransformer preferences to default values [2019-03-21 17:16:48,263 INFO L177 SettingsManager]: ReqToTest provides no preferences, ignoring... [2019-03-21 17:16:48,263 INFO L174 SettingsManager]: Resetting Boogie Printer preferences to default values [2019-03-21 17:16:48,264 INFO L174 SettingsManager]: Resetting ChcSmtPrinter preferences to default values [2019-03-21 17:16:48,265 INFO L174 SettingsManager]: Resetting ReqPrinter preferences to default values [2019-03-21 17:16:48,265 INFO L174 SettingsManager]: Resetting Witness Printer preferences to default values [2019-03-21 17:16:48,267 INFO L177 SettingsManager]: Boogie PL CUP Parser provides no preferences, ignoring... [2019-03-21 17:16:48,267 INFO L174 SettingsManager]: Resetting CDTParser preferences to default values [2019-03-21 17:16:48,267 INFO L177 SettingsManager]: AutomataScriptParser provides no preferences, ignoring... [2019-03-21 17:16:48,268 INFO L177 SettingsManager]: ReqParser provides no preferences, ignoring... [2019-03-21 17:16:48,268 INFO L174 SettingsManager]: Resetting SmtParser preferences to default values [2019-03-21 17:16:48,269 INFO L174 SettingsManager]: Resetting Witness Parser preferences to default values [2019-03-21 17:16:48,270 INFO L181 SettingsManager]: Finished resetting all preferences to default values... [2019-03-21 17:16:48,270 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:16:48,278 INFO L110 SettingsManager]: Loading preferences was successful [2019-03-21 17:16:48,278 INFO L112 SettingsManager]: Preferences different from defaults after loading the file: [2019-03-21 17:16:48,281 INFO L131 SettingsManager]: Preferences of TreeAutomizer differ from their defaults: [2019-03-21 17:16:48,281 INFO L133 SettingsManager]: * SMT solver=Internal_SMTInterpol [2019-03-21 17:16:48,283 INFO L131 SettingsManager]: Preferences of SmtParser differ from their defaults: [2019-03-21 17:16:48,283 INFO L133 SettingsManager]: * Use TreeAutomizer as solver for the given file (assumes the file contains Horn clauses only).=true [2019-03-21 17:16:48,323 INFO L81 nceAwareModelManager]: Repository-Root is: /tmp [2019-03-21 17:16:48,336 INFO L259 ainManager$Toolchain]: [Toolchain 1]: Applicable parser(s) successfully (re)initialized [2019-03-21 17:16:48,342 INFO L215 ainManager$Toolchain]: [Toolchain 1]: Toolchain selected. [2019-03-21 17:16:48,343 INFO L271 PluginConnector]: Initializing SmtParser... [2019-03-21 17:16:48,344 INFO L276 PluginConnector]: SmtParser initialized [2019-03-21 17:16:48,345 INFO L430 ainManager$Toolchain]: [Toolchain 1]: Parsing single file: /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringContains01_jayhorn-tmp_1.smt2 [2019-03-21 17:16:48,427 INFO L210 SmtParser]: Parsing .smt2 file as a set of Horn Clauses unknown [2019-03-21 17:16:49,875 INFO L251 SmtParser]: Succesfully executed SMT file /storage/repos/jayhorn-chc-bench/sv-comp-2019/no-inlining/jbmc-regression/StringContains01_jayhorn-tmp_1.smt2 [2019-03-21 17:16:49,880 INFO L297 ainManager$Toolchain]: ####################### [Toolchain 1] ####################### [2019-03-21 17:16:49,882 INFO L131 ToolchainWalker]: Walking toolchain with 1 elements. [2019-03-21 17:16:49,882 INFO L113 PluginConnector]: ------------------------TreeAutomizer---------------------------- [2019-03-21 17:16:49,883 INFO L271 PluginConnector]: Initializing TreeAutomizer... [2019-03-21 17:16:49,885 INFO L276 PluginConnector]: TreeAutomizer initialized [2019-03-21 17:16:49,886 INFO L185 PluginConnector]: Executing the observer TreeAutomizerObserver from plugin TreeAutomizer for "de.uni_freiburg.informatik.ultimate.source.smtparser OTHER 21.03 05:16:49" (1/1) ... [2019-03-21 17:16:49,916 INFO L144 PredicateUnifier]: Initialized classic predicate unifier Received shutdown request... [2019-03-21 17:18:44,002 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,003 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,003 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,004 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,004 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,005 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,005 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,006 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,006 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,007 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,007 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,007 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,008 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,008 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,009 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,009 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,009 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,010 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,010 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,011 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,011 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,012 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,012 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,013 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,013 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,013 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,014 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,014 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,015 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,015 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,016 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,016 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,017 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,017 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,018 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,018 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,019 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,019 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,020 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,020 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,020 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,021 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,021 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,022 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,022 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,023 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,023 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,023 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,024 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,024 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,025 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,025 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,026 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,026 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,026 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,027 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,027 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,028 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,028 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,028 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,029 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,029 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,030 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,030 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,030 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,031 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,031 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,032 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,032 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,032 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,033 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,033 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,034 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,034 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,034 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,035 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,035 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,036 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,036 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,036 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,037 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,037 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,038 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,038 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,038 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,039 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,039 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,040 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,040 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,040 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,041 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,041 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,042 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,042 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,043 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,043 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,043 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,044 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,044 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,045 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,045 WARN L250 erpolLogProxyWrapper]: Unable to check validity of interpolant: cancelled [2019-03-21 17:18:44,064 WARN L189 SmtUtils]: Removed 1 from assertion stack [2019-03-21 17:18:44,064 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:18:44,069 INFO L168 Benchmark]: Toolchain (without parser) took 114187.96 ms. Allocated memory was 239.1 MB in the beginning and 3.0 GB in the end (delta: 2.7 GB). Free memory was 189.2 MB in the beginning and 1.4 GB in the end (delta: -1.2 GB). Peak memory consumption was 1.6 GB. Max. memory is 7.1 GB. [2019-03-21 17:18:44,070 INFO L168 Benchmark]: SmtParser took 0.21 ms. Allocated memory is still 141.6 MB. Free memory is still 111.4 MB. There was no memory consumed. Max. memory is 7.1 GB. [2019-03-21 17:18:44,070 INFO L168 Benchmark]: TreeAutomizer took 114185.54 ms. Allocated memory was 239.1 MB in the beginning and 3.0 GB in the end (delta: 2.7 GB). Free memory was 189.2 MB in the beginning and 1.4 GB in the end (delta: -1.2 GB). Peak memory consumption was 1.6 GB. Max. memory is 7.1 GB. [2019-03-21 17:18:44,072 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.21 ms. Allocated memory is still 141.6 MB. Free memory is still 111.4 MB. There was no memory consumed. Max. memory is 7.1 GB. * TreeAutomizer took 114185.54 ms. Allocated memory was 239.1 MB in the beginning and 3.0 GB in the end (delta: 2.7 GB). Free memory was 189.2 MB in the beginning and 1.4 GB in the end (delta: -1.2 GB). Peak memory consumption was 1.6 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 1ms.. RESULT: Ultimate could not prove your program: Timeout Completed graceful shutdown