%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : TOP040+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n001.cluster.edu % Model : x86_64 x86_64 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 2.10GHz % Memory : 8042.1875MB % OS : Linux 3.10.0-693.el7.x86_64 % CPULimit : 300s % WCLimit : 300s % DateTime : Fri May 19 12:39:08 EDT 2023 % Result : Unknown 98.35s 102.02s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.06/0.12 % Problem : TOP040+4 : TPTP v8.1.2. Released v3.4.0. % 0.06/0.12 % Command : nanocop.sh %s %d % 0.12/0.33 % Computer : n001.cluster.edu % 0.12/0.33 % Model : x86_64 x86_64 % 0.12/0.33 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.12/0.33 % Memory : 8042.1875MB % 0.12/0.33 % OS : Linux 3.10.0-693.el7.x86_64 % 0.12/0.33 % CPULimit : 300 % 0.12/0.33 % WCLimit : 300 % 0.12/0.33 % DateTime : Thu May 18 20:32:39 EDT 2023 % 0.12/0.33 % CPUTime : % 5.93/5.95 *** Overflow of the global/trail stack in spite of garbage collection! % 5.93/5.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 5.93/5.95 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 11.72/12.07 *** Overflow of the global/trail stack in spite of garbage collection! % 11.72/12.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 11.72/12.07 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 17.72/18.51 *** Overflow of the global/trail stack in spite of garbage collection! % 17.72/18.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 17.72/18.51 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 23.60/24.68 *** Overflow of the global/trail stack in spite of garbage collection! % 23.60/24.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 23.60/24.68 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 27.62/29.05 *** Overflow of the global/trail stack in spite of garbage collection! % 27.62/29.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 27.62/29.05 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 33.66/35.18 *** Overflow of the global/trail stack in spite of garbage collection! % 33.66/35.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 33.66/35.18 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 39.50/41.24 *** Overflow of the global/trail stack in spite of garbage collection! % 39.50/41.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 39.50/41.24 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 45.38/47.45 *** Overflow of the global/trail stack in spite of garbage collection! % 45.38/47.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 45.38/47.45 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 51.29/53.70 *** Overflow of the global/trail stack in spite of garbage collection! % 51.29/53.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 51.29/53.70 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 55.34/58.22 *** Overflow of the global/trail stack in spite of garbage collection! % 55.34/58.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 55.34/58.22 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 61.20/63.97 *** Overflow of the global/trail stack in spite of garbage collection! % 61.20/63.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 61.20/63.97 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 67.05/70.24 *** Overflow of the global/trail stack in spite of garbage collection! % 67.05/70.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 67.05/70.24 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 72.95/76.56 *** Overflow of the global/trail stack in spite of garbage collection! % 72.95/76.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 72.95/76.56 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 98.32/101.41 *** Overflow of the global/trail stack in spite of garbage collection! % 98.32/101.41 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 98.32/101.41 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 98.35/102.02 Timeout %------------------------------------------------------------------------------