TSTP Solution File: LCL680+1.020 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LCL680+1.020 : TPTP v8.1.2. Released v4.0.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n028.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:49 EDT 2023
% Result : Unknown 33.88s 41.79s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : LCL680+1.020 : TPTP v8.1.2. Released v4.0.0.
% 0.07/0.14 % Command : nanocop.sh %s %d
% 0.14/0.35 % Computer : n028.cluster.edu
% 0.14/0.35 % Model : x86_64 x86_64
% 0.14/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35 % Memory : 8042.1875MB
% 0.14/0.35 % OS : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35 % CPULimit : 300
% 0.14/0.35 % WCLimit : 300
% 0.14/0.35 % DateTime : Thu May 18 16:42:33 EDT 2023
% 0.14/0.35 % CPUTime :
% 1.85/2.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.85/2.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.85/2.03 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 3.48/4.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.48/4.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.48/4.00 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 5.16/6.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.16/6.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.16/6.13 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 6.92/8.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.92/8.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.92/8.17 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 8.49/10.16 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.49/10.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.49/10.16 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 10.25/12.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.25/12.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.25/12.43 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 12.03/14.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.03/14.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.03/14.45 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 13.68/16.44 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.68/16.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.68/16.44 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 15.31/18.52 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.31/18.52 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.31/18.52 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 17.06/20.61 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.06/20.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.06/20.61 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 18.64/22.66 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.64/22.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.64/22.66 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 20.40/24.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.40/24.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.40/24.74 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 22.09/26.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.09/26.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.09/26.82 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 23.73/28.88 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.73/28.88 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.73/28.88 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 25.46/31.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.46/31.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.46/31.07 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 27.13/33.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.13/33.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.13/33.01 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 28.83/35.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.83/35.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.83/35.07 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 30.41/37.16 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.41/37.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.41/37.16 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 32.17/39.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.17/39.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.17/39.24 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 33.86/41.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.86/41.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.86/41.31 Peak sizes were: global stack 130848 kbytes, trail stack 4192 kbytes
% 33.88/41.78 Timeout
%------------------------------------------------------------------------------