TSTP Solution File: KRS287+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : KRS287+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n007.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 26.81s 41.89s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.14 % Problem : KRS287+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.03/0.14 % Command : nanocop.sh %s %d
% 0.11/0.36 % Computer : n007.cluster.edu
% 0.11/0.36 % Model : x86_64 x86_64
% 0.11/0.36 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.36 % Memory : 8042.1875MB
% 0.11/0.36 % OS : Linux 3.10.0-693.el7.x86_64
% 0.11/0.36 % CPULimit : 300
% 0.11/0.36 % WCLimit : 300
% 0.11/0.36 % DateTime : Thu May 18 22:51:38 EDT 2023
% 0.11/0.36 % CPUTime :
% 1.40/1.61 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.40/1.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.40/1.61 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.83/3.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.83/3.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.83/3.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.19/5.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.19/5.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.19/5.83 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.58/7.91 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.58/7.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.58/7.91 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.90/9.90 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.90/9.90 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.90/9.90 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.18/11.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.18/11.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.18/11.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.52/14.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.52/14.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.52/14.06 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.82/16.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.82/16.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.82/16.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.24/18.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.24/18.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.24/18.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.49/20.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.49/20.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.49/20.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.82/22.36 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.82/22.36 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.82/22.36 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.21/24.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.21/24.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.21/24.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.60/26.61 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.60/26.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.60/26.61 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.94/28.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.94/28.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.94/28.60 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.21/30.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.21/30.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.21/30.68 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.65/32.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.65/32.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.65/32.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.90/34.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.90/34.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.90/34.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.15/36.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.15/36.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.15/36.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.54/39.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.54/39.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.54/39.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.78/40.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.78/40.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.78/40.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.81/41.89 Timeout
%------------------------------------------------------------------------------