%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : TOP042+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n026.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:09 EDT 2023 % Result : Unknown 100.03s 103.28s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.03/0.13 % Problem : TOP042+4 : TPTP v8.1.2. Released v3.4.0. % 0.03/0.14 % Command : nanocop.sh %s %d % 0.13/0.35 % Computer : n026.cluster.edu % 0.13/0.35 % Model : x86_64 x86_64 % 0.13/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.13/0.35 % Memory : 8042.1875MB % 0.13/0.35 % OS : Linux 3.10.0-693.el7.x86_64 % 0.13/0.35 % CPULimit : 300 % 0.13/0.35 % WCLimit : 300 % 0.13/0.35 % DateTime : Thu May 18 20:18:10 EDT 2023 % 0.13/0.35 % CPUTime : % 6.07/6.11 *** Overflow of the global/trail stack in spite of garbage collection! % 6.07/6.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 6.07/6.11 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 11.91/12.14 *** Overflow of the global/trail stack in spite of garbage collection! % 11.91/12.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 11.91/12.14 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 17.81/18.44 *** Overflow of the global/trail stack in spite of garbage collection! % 17.81/18.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 17.81/18.44 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 23.96/24.99 *** Overflow of the global/trail stack in spite of garbage collection! % 23.96/24.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 23.96/24.99 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 27.90/29.06 *** Overflow of the global/trail stack in spite of garbage collection! % 27.90/29.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 27.90/29.06 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 33.83/35.11 *** Overflow of the global/trail stack in spite of garbage collection! % 33.83/35.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 33.83/35.11 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 39.74/41.33 *** Overflow of the global/trail stack in spite of garbage collection! % 39.74/41.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 39.74/41.33 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 45.67/47.60 *** Overflow of the global/trail stack in spite of garbage collection! % 45.67/47.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 45.67/47.60 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 51.66/53.84 *** Overflow of the global/trail stack in spite of garbage collection! % 51.66/53.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 51.66/53.84 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 55.57/58.16 *** Overflow of the global/trail stack in spite of garbage collection! % 55.57/58.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 55.57/58.16 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes % 61.41/64.17 *** Overflow of the global/trail stack in spite of garbage collection! % 61.41/64.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 61.41/64.17 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 67.27/70.39 *** Overflow of the global/trail stack in spite of garbage collection! % 67.27/70.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 67.27/70.39 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 73.41/76.84 *** Overflow of the global/trail stack in spite of garbage collection! % 73.41/76.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 73.41/76.84 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 100.02/102.70 *** Overflow of the global/trail stack in spite of garbage collection! % 100.02/102.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 100.02/102.70 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes % 100.03/103.28 Timeout %------------------------------------------------------------------------------