%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : CAT024+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n023.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 10:12:48 EDT 2023 % Result : Unknown 82.93s 89.65s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.11/0.12 % Problem : CAT024+4 : TPTP v8.1.2. Released v3.4.0. % 0.11/0.13 % Command : nanocop.sh %s %d % 0.12/0.34 % Computer : n023.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:32:18 EDT 2023 % 0.12/0.34 % CPUTime : % 4.93/4.94 *** Overflow of the global/trail stack in spite of garbage collection! % 4.93/4.94 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 4.93/4.94 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 9.52/9.96 *** Overflow of the global/trail stack in spite of garbage collection! % 9.52/9.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 9.52/9.96 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 14.07/15.08 *** Overflow of the global/trail stack in spite of garbage collection! % 14.07/15.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 14.07/15.08 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 18.82/20.46 *** Overflow of the global/trail stack in spite of garbage collection! % 18.82/20.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 18.82/20.46 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 22.36/24.50 *** Overflow of the global/trail stack in spite of garbage collection! % 22.36/24.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 22.36/24.50 Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes % 27.12/29.75 *** Overflow of the global/trail stack in spite of garbage collection! % 27.12/29.75 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 27.12/29.75 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 31.76/34.89 *** Overflow of the global/trail stack in spite of garbage collection! % 31.76/34.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 31.76/34.89 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 36.53/40.19 *** Overflow of the global/trail stack in spite of garbage collection! % 36.53/40.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 36.53/40.19 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 41.19/45.29 *** Overflow of the global/trail stack in spite of garbage collection! % 41.19/45.29 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 41.19/45.29 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 44.52/49.23 *** Overflow of the global/trail stack in spite of garbage collection! % 44.52/49.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 44.52/49.23 Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes % 49.17/54.59 *** Overflow of the global/trail stack in spite of garbage collection! % 49.17/54.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 49.17/54.59 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 53.77/59.77 *** Overflow of the global/trail stack in spite of garbage collection! % 53.77/59.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 53.77/59.77 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 58.55/65.16 *** Overflow of the global/trail stack in spite of garbage collection! % 58.55/65.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 58.55/65.16 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 82.88/89.06 *** Overflow of the global/trail stack in spite of garbage collection! % 82.88/89.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 82.88/89.06 Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes % 82.93/89.65 Timeout %------------------------------------------------------------------------------