TSTP Solution File: KRS281+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : KRS281+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n012.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:26:36 EDT 2023
% Result : Unknown 32.61s 41.74s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.11 % Problem : KRS281+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.00/0.12 % Command : nanocop.sh %s %d
% 0.12/0.32 % Computer : n012.cluster.edu
% 0.12/0.32 % Model : x86_64 x86_64
% 0.12/0.32 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.32 % Memory : 8042.1875MB
% 0.12/0.32 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.32 % CPULimit : 300
% 0.12/0.32 % WCLimit : 300
% 0.12/0.32 % DateTime : Thu May 18 22:59:01 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.69/1.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.69/1.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.69/1.89 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.31/3.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.31/3.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.31/3.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.01/6.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.01/6.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.01/6.02 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.67/8.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.67/8.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.67/8.12 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.22/10.10 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.22/10.10 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.22/10.10 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.71/12.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.71/12.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.71/12.18 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.35/14.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.35/14.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.35/14.25 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.92/16.32 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.92/16.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.92/16.32 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.48/18.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.48/18.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.48/18.37 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.08/20.48 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.08/20.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.08/20.48 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.64/22.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.64/22.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.64/22.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.18/24.59 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.18/24.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.18/24.59 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.78/26.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.78/26.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.78/26.68 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.41/28.81 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.41/28.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.41/28.81 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.03/30.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.03/30.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.03/30.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.81/33.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.81/33.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.81/33.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.59/35.15 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.59/35.15 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.59/35.15 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.21/37.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.21/37.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.21/37.12 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.88/39.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.88/39.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.88/39.19 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.54/41.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.54/41.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.54/41.31 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.61/41.74 Timeout
%------------------------------------------------------------------------------