%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : TOP044+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n018.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 172.66s 160.30s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.00/0.12 % Problem : TOP044+4 : TPTP v8.1.2. Released v3.4.0. % 0.11/0.12 % Command : nanocop.sh %s %d % 0.11/0.32 % Computer : n018.cluster.edu % 0.11/0.32 % Model : x86_64 x86_64 % 0.11/0.32 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.11/0.32 % Memory : 8042.1875MB % 0.11/0.32 % OS : Linux 3.10.0-693.el7.x86_64 % 0.11/0.32 % CPULimit : 300 % 0.11/0.32 % WCLimit : 300 % 0.11/0.32 % DateTime : Thu May 18 20:16:41 EDT 2023 % 0.11/0.32 % CPUTime : % 12.97/12.76 *** Overflow of the global/trail stack in spite of garbage collection! % 12.97/12.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 12.97/12.76 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 26.42/26.68 *** Overflow of the global/trail stack in spite of garbage collection! % 26.42/26.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 26.42/26.68 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 38.90/39.23 *** Overflow of the global/trail stack in spite of garbage collection! % 38.90/39.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 38.90/39.23 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 50.20/50.69 *** Overflow of the global/trail stack in spite of garbage collection! % 50.20/50.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 50.20/50.69 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 67.33/57.21 *** Overflow of the global/trail stack in spite of garbage collection! % 67.33/57.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 67.33/57.21 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 78.69/68.30 *** Overflow of the global/trail stack in spite of garbage collection! % 78.69/68.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 78.69/68.30 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 90.59/80.25 *** Overflow of the global/trail stack in spite of garbage collection! % 90.59/80.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 90.59/80.25 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 102.16/91.33 *** Overflow of the global/trail stack in spite of garbage collection! % 102.16/91.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 102.16/91.33 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 118.78/107.60 *** Overflow of the global/trail stack in spite of garbage collection! % 118.78/107.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 118.78/107.60 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 172.62/159.95 *** Overflow of the global/trail stack in spite of garbage collection! % 172.62/159.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 172.62/159.95 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 172.66/160.30 Timeout %------------------------------------------------------------------------------