TSTP Solution File: LCL662+1.020 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LCL662+1.020 : TPTP v8.1.2. Released v4.0.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n013.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:33:42 EDT 2023
% Result : Unknown 29.34s 42.78s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.13 % Problem : LCL662+1.020 : TPTP v8.1.2. Released v4.0.0.
% 0.03/0.14 % Command : nanocop.sh %s %d
% 0.15/0.35 % Computer : n013.cluster.edu
% 0.15/0.35 % Model : x86_64 x86_64
% 0.15/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.15/0.35 % Memory : 8042.1875MB
% 0.15/0.35 % OS : Linux 3.10.0-693.el7.x86_64
% 0.15/0.35 % CPULimit : 300
% 0.15/0.35 % WCLimit : 300
% 0.15/0.35 % DateTime : Thu May 18 15:54:06 EDT 2023
% 0.15/0.35 % CPUTime :
% 1.54/1.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.54/1.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.54/1.71 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 2.94/3.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.94/3.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.94/3.73 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 4.16/5.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.16/5.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.16/5.73 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 5.54/7.81 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.54/7.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.54/7.81 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 6.77/9.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.77/9.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.77/9.82 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 7.98/11.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.98/11.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.98/11.92 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 9.26/14.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.26/14.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.26/14.00 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 10.67/16.15 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.67/16.15 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.67/16.15 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 12.32/18.46 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.32/18.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.32/18.46 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 14.63/21.23 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.63/21.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.63/21.23 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 16.25/23.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.25/23.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.25/23.68 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 17.95/25.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.95/25.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.95/25.76 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 19.51/27.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.51/27.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.51/27.71 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 21.14/29.90 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.14/29.90 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.14/29.90 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 22.65/31.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.65/31.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.65/31.85 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 24.08/33.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.08/33.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.08/33.78 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 25.38/35.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.38/35.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.38/35.80 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 26.74/37.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.74/37.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.74/37.86 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 28.00/39.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.00/39.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.00/39.87 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 29.30/41.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.30/41.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.30/41.93 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 29.34/42.78 Timeout
%------------------------------------------------------------------------------