0.00/0.03 % Problem : theBenchmark.p : TPTP v0.0.0. Released v0.0.0. 0.00/0.04 % Command : nanocop_casc.sh %s %d 0.03/0.23 % Computer : n009.star.cs.uiowa.edu 0.03/0.23 % Model : x86_64 x86_64 0.03/0.23 % CPU : Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz 0.03/0.23 % Memory : 32218.625MB 0.03/0.23 % OS : Linux 3.10.0-693.2.2.el7.x86_64 0.03/0.23 % CPULimit : 300 0.03/0.23 % DateTime : Sat Jul 14 05:06:41 CDT 2018 0.03/0.23 % CPUTime : 2.24/2.41 *** Overflow of the global/trail stack in spite of garbage collection! 2.24/2.41 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 2.24/2.41 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 4.50/5.48 *** Overflow of the global/trail stack in spite of garbage collection! 4.50/5.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 4.50/5.48 Peak sizes were: global stack 121032 kbytes, trail stack 10040 kbytes 6.71/8.54 *** Overflow of the global/trail stack in spite of garbage collection! 6.71/8.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 6.71/8.54 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 8.89/11.58 *** Overflow of the global/trail stack in spite of garbage collection! 8.89/11.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 8.89/11.58 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 11.17/14.68 *** Overflow of the global/trail stack in spite of garbage collection! 11.17/14.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 11.17/14.68 Peak sizes were: global stack 121032 kbytes, trail stack 10040 kbytes 13.49/17.72 *** Overflow of the global/trail stack in spite of garbage collection! 13.49/17.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 13.49/17.72 Peak sizes were: global stack 121032 kbytes, trail stack 10040 kbytes 15.67/20.76 *** Overflow of the global/trail stack in spite of garbage collection! 15.67/20.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 15.67/20.76 Peak sizes were: global stack 121032 kbytes, trail stack 10040 kbytes 17.94/23.81 *** Overflow of the global/trail stack in spite of garbage collection! 17.94/23.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 17.94/23.81 Peak sizes were: global stack 121032 kbytes, trail stack 10040 kbytes 20.09/26.89 *** Overflow of the global/trail stack in spite of garbage collection! 20.09/26.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 20.09/26.89 Peak sizes were: global stack 121032 kbytes, trail stack 10040 kbytes 22.39/29.99 *** Overflow of the global/trail stack in spite of garbage collection! 22.39/29.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 22.39/29.99 Peak sizes were: global stack 121032 kbytes, trail stack 10040 kbytes 24.68/33.02 *** Overflow of the global/trail stack in spite of garbage collection! 24.68/33.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 24.68/33.02 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 26.84/36.07 *** Overflow of the global/trail stack in spite of garbage collection! 26.84/36.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 26.84/36.07 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 29.11/39.13 *** Overflow of the global/trail stack in spite of garbage collection! 29.11/39.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 29.11/39.13 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 31.36/42.19 *** Overflow of the global/trail stack in spite of garbage collection! 31.36/42.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 31.36/42.19 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 33.52/45.25 *** Overflow of the global/trail stack in spite of garbage collection! 33.52/45.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 33.52/45.25 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 35.80/48.32 *** Overflow of the global/trail stack in spite of garbage collection! 35.80/48.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 35.80/48.32 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 37.98/51.38 *** Overflow of the global/trail stack in spite of garbage collection! 37.98/51.38 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 37.98/51.38 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 40.23/54.45 *** Overflow of the global/trail stack in spite of garbage collection! 40.23/54.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 40.23/54.45 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 42.52/57.50 *** Overflow of the global/trail stack in spite of garbage collection! 42.52/57.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 42.52/57.50 Peak sizes were: global stack 121160 kbytes, trail stack 10040 kbytes 44.68/60.57 *** Overflow of the global/trail stack in spite of garbage collection! 44.68/60.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. 44.68/60.57 Peak sizes were: global stack 121032 kbytes, trail stack 10040 kbytes 44.77/61.47 EOF