TSTP Solution File: KRS282+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : KRS282+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n031.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 37.54s 41.72s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12 % Problem : KRS282+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.11/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n031.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 23:31:10 EDT 2023
% 0.12/0.33 % CPUTime :
% 2.00/2.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.00/2.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.00/2.18 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.93/4.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.93/4.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.93/4.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.82/6.29 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.82/6.29 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.82/6.29 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.68/8.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.68/8.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.68/8.37 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.29/10.16 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.29/10.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.29/10.16 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.27/12.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.27/12.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.27/12.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.11/14.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.11/14.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.11/14.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.98/16.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.98/16.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.98/16.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.85/18.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.85/18.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.85/18.68 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.52/20.52 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.52/20.52 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.52/20.52 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.39/22.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.39/22.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.39/22.83 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.40/25.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.40/25.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.40/25.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.33/27.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.33/27.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.33/27.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.23/29.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.23/29.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.23/29.07 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.18/31.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.18/31.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.18/31.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.09/33.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.09/33.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.09/33.20 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.90/35.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.90/35.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.90/35.18 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.81/37.35 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.81/37.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.81/37.35 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.63/39.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.63/39.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.63/39.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.43/41.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 37.43/41.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.43/41.47 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.54/41.72 Timeout
%------------------------------------------------------------------------------