TSTP Solution File: KRS289+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : KRS289+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n015.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:37 EDT 2023
% Result : Unknown 27.73s 41.87s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.13/0.14 % Problem : KRS289+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.13/0.14 % Command : nanocop.sh %s %d
% 0.14/0.35 % Computer : n015.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.36 % WCLimit : 300
% 0.14/0.36 % DateTime : Thu May 18 23:14:37 EDT 2023
% 0.14/0.36 % CPUTime :
% 1.50/1.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.50/1.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.50/1.70 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.91/3.75 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.91/3.75 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.91/3.75 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.90/6.41 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.90/6.41 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.90/6.41 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.14/7.75 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.14/7.75 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.14/7.75 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.50/9.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.50/9.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.50/9.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.22/12.35 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.22/12.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.22/12.35 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.54/14.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.54/14.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.54/14.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.08/16.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.08/16.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.08/16.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.70/18.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.70/18.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.70/18.57 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.95/20.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.95/20.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.95/20.22 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.53/22.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.53/22.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.53/22.64 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.00/24.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.00/24.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.00/24.56 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.58/26.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.58/26.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.58/26.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.78/28.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.78/28.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.78/28.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.03/30.62 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.03/30.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.03/30.62 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.06/32.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.06/32.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.06/32.58 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.29/34.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.29/34.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.29/34.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.47/36.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.47/36.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.47/36.79 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.51/38.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.51/38.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.51/38.79 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.71/40.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.71/40.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.71/40.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.73/41.87 Timeout
%------------------------------------------------------------------------------