%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : TOP024+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n010.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:04 EDT 2023 % Result : Unknown 98.67s 102.07s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.11/0.12 % Problem : TOP024+4 : TPTP v8.1.2. Released v3.4.0. % 0.11/0.13 % Command : nanocop.sh %s %d % 0.12/0.34 % Computer : n010.cluster.edu % 0.12/0.34 % Model : x86_64 x86_64 % 0.12/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.12/0.34 % Memory : 8042.1875MB % 0.12/0.34 % OS : Linux 3.10.0-693.el7.x86_64 % 0.12/0.34 % CPULimit : 300 % 0.12/0.34 % WCLimit : 300 % 0.12/0.34 % DateTime : Thu May 18 19:52:46 EDT 2023 % 0.12/0.34 % CPUTime : % 6.03/6.04 *** Overflow of the global/trail stack in spite of garbage collection! % 6.03/6.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 6.03/6.04 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 11.85/12.15 *** Overflow of the global/trail stack in spite of garbage collection! % 11.85/12.15 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 11.85/12.15 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 17.68/18.37 *** Overflow of the global/trail stack in spite of garbage collection! % 17.68/18.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 17.68/18.37 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 23.58/24.62 *** Overflow of the global/trail stack in spite of garbage collection! % 23.58/24.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 23.58/24.62 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 27.41/28.99 *** Overflow of the global/trail stack in spite of garbage collection! % 27.41/28.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 27.41/28.99 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 33.34/35.02 *** Overflow of the global/trail stack in spite of garbage collection! % 33.34/35.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 33.34/35.02 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 39.16/41.20 *** Overflow of the global/trail stack in spite of garbage collection! % 39.16/41.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 39.16/41.20 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 45.15/47.60 *** Overflow of the global/trail stack in spite of garbage collection! % 45.15/47.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 45.15/47.60 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 51.04/53.82 *** Overflow of the global/trail stack in spite of garbage collection! % 51.04/53.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 51.04/53.82 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 55.29/58.33 *** Overflow of the global/trail stack in spite of garbage collection! % 55.29/58.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 55.29/58.33 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 61.34/64.32 *** Overflow of the global/trail stack in spite of garbage collection! % 61.34/64.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 61.34/64.32 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 67.23/70.29 *** Overflow of the global/trail stack in spite of garbage collection! % 67.23/70.29 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 67.23/70.29 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 73.14/76.62 *** Overflow of the global/trail stack in spite of garbage collection! % 73.14/76.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 73.14/76.62 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 98.62/101.55 *** Overflow of the global/trail stack in spite of garbage collection! % 98.62/101.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 98.62/101.55 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 98.67/102.07 Timeout %------------------------------------------------------------------------------