%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : TOP048+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n025.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:10 EDT 2023 % Result : Unknown 159.77s 157.07s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.11/0.12 % Problem : TOP048+4 : TPTP v8.1.2. Released v3.4.0. % 0.11/0.13 % Command : nanocop.sh %s %d % 0.12/0.34 % Computer : n025.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 20:15:57 EDT 2023 % 0.12/0.34 % CPUTime : % 11.77/11.61 *** Overflow of the global/trail stack in spite of garbage collection! % 11.77/11.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 11.77/11.61 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 23.37/22.89 *** Overflow of the global/trail stack in spite of garbage collection! % 23.37/22.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 23.37/22.89 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 35.19/34.49 *** Overflow of the global/trail stack in spite of garbage collection! % 35.19/34.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 35.19/34.49 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 47.12/46.02 *** Overflow of the global/trail stack in spite of garbage collection! % 47.12/46.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 47.12/46.02 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 53.99/53.66 *** Overflow of the global/trail stack in spite of garbage collection! % 53.99/53.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 53.99/53.66 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 65.84/65.62 *** Overflow of the global/trail stack in spite of garbage collection! % 65.84/65.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 65.84/65.62 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 77.50/76.95 *** Overflow of the global/trail stack in spite of garbage collection! % 77.50/76.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 77.50/76.95 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 88.97/88.21 *** Overflow of the global/trail stack in spite of garbage collection! % 88.97/88.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 88.97/88.21 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 105.77/104.57 *** Overflow of the global/trail stack in spite of garbage collection! % 105.77/104.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 105.77/104.57 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 159.72/156.95 *** Overflow of the global/trail stack in spite of garbage collection! % 159.72/156.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 159.72/156.95 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 159.77/157.07 Timeout %------------------------------------------------------------------------------