%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : TOP045+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n012.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 163.67s 162.19s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.10/0.11 % Problem : TOP045+4 : TPTP v8.1.2. Released v3.4.0. % 0.10/0.12 % Command : nanocop.sh %s %d % 0.11/0.33 % Computer : n012.cluster.edu % 0.11/0.33 % Model : x86_64 x86_64 % 0.11/0.33 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.11/0.33 % Memory : 8042.1875MB % 0.11/0.33 % OS : Linux 3.10.0-693.el7.x86_64 % 0.11/0.33 % CPULimit : 300 % 0.11/0.33 % WCLimit : 300 % 0.11/0.33 % DateTime : Thu May 18 19:59:54 EDT 2023 % 0.11/0.33 % CPUTime : % 12.43/12.20 *** Overflow of the global/trail stack in spite of garbage collection! % 12.43/12.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 12.43/12.20 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 25.61/25.37 *** Overflow of the global/trail stack in spite of garbage collection! % 25.61/25.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 25.61/25.37 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 38.20/38.49 *** Overflow of the global/trail stack in spite of garbage collection! % 38.20/38.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 38.20/38.49 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 52.88/52.87 *** Overflow of the global/trail stack in spite of garbage collection! % 52.88/52.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 52.88/52.87 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 59.38/59.49 *** Overflow of the global/trail stack in spite of garbage collection! % 59.38/59.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 59.38/59.49 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 70.77/70.48 *** Overflow of the global/trail stack in spite of garbage collection! % 70.77/70.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 70.77/70.48 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 82.35/82.03 *** Overflow of the global/trail stack in spite of garbage collection! % 82.35/82.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 82.35/82.03 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 93.80/93.32 *** Overflow of the global/trail stack in spite of garbage collection! % 93.80/93.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 93.80/93.32 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 110.08/109.35 *** Overflow of the global/trail stack in spite of garbage collection! % 110.08/109.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 110.08/109.35 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 163.60/161.65 *** Overflow of the global/trail stack in spite of garbage collection! % 163.60/161.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 163.60/161.65 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 163.67/162.19 Timeout %------------------------------------------------------------------------------