%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : LAT367+4 : TPTP v8.1.2. Released v3.4.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n003.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 11:29:00 EDT 2023 % Result : Unknown 161.84s 161.21s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.12/0.12 % Problem : LAT367+4 : TPTP v8.1.2. Released v3.4.0. % 0.12/0.12 % Command : nanocop.sh %s %d % 0.12/0.33 % Computer : n003.cluster.edu % 0.12/0.33 % Model : x86_64 x86_64 % 0.12/0.33 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.12/0.33 % Memory : 8042.1875MB % 0.12/0.33 % OS : Linux 3.10.0-693.el7.x86_64 % 0.12/0.33 % CPULimit : 300 % 0.12/0.33 % WCLimit : 300 % 0.12/0.33 % DateTime : Thu May 18 14:33:23 EDT 2023 % 0.19/0.33 % CPUTime : % 11.91/11.69 *** Overflow of the global/trail stack in spite of garbage collection! % 11.91/11.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 11.91/11.69 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 23.89/23.19 *** Overflow of the global/trail stack in spite of garbage collection! % 23.89/23.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 23.89/23.19 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 35.89/35.73 *** Overflow of the global/trail stack in spite of garbage collection! % 35.89/35.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 35.89/35.73 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 47.84/48.10 *** Overflow of the global/trail stack in spite of garbage collection! % 47.84/48.10 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 47.84/48.10 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 54.64/55.71 *** Overflow of the global/trail stack in spite of garbage collection! % 54.64/55.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 54.64/55.71 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes % 66.39/67.61 *** Overflow of the global/trail stack in spite of garbage collection! % 66.39/67.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 66.39/67.61 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 78.17/79.20 *** Overflow of the global/trail stack in spite of garbage collection! % 78.17/79.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 78.17/79.20 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 90.05/91.55 *** Overflow of the global/trail stack in spite of garbage collection! % 90.05/91.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 90.05/91.55 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 106.74/107.69 *** Overflow of the global/trail stack in spite of garbage collection! % 106.74/107.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 106.74/107.69 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes % 161.78/161.06 *** Overflow of the global/trail stack in spite of garbage collection! % 161.78/161.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 161.78/161.06 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes % 161.84/161.21 Timeout %------------------------------------------------------------------------------