TSTP Solution File: KRS284+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : KRS284+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n016.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 23.89s 41.69s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : KRS284+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.13 % Command : nanocop.sh %s %d
% 0.13/0.34 % Computer : n016.cluster.edu
% 0.13/0.34 % Model : x86_64 x86_64
% 0.13/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34 % Memory : 8042.1875MB
% 0.13/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34 % CPULimit : 300
% 0.13/0.34 % WCLimit : 300
% 0.13/0.34 % DateTime : Thu May 18 23:26:27 EDT 2023
% 0.13/0.34 % CPUTime :
% 1.41/1.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.41/1.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.41/1.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.59/3.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.59/3.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.59/3.58 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.75/5.59 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.75/5.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.75/5.59 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.99/7.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.99/7.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.99/7.68 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.03/9.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.03/9.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.03/9.64 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.26/11.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.26/11.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.26/11.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.44/13.90 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.44/13.90 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.44/13.90 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.65/15.88 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.65/15.88 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.65/15.88 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.81/17.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.81/17.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.81/17.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.94/20.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.94/20.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.94/20.05 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.13/22.08 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.13/22.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.13/22.08 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.23/24.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.23/24.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.23/24.12 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.43/26.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.43/26.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.43/26.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.64/28.35 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.64/28.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.64/28.35 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.73/30.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.73/30.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.73/30.34 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.04/32.51 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.04/32.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.04/32.51 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.30/34.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.30/34.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.30/34.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.49/36.61 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.49/36.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.49/36.61 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.66/38.66 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.66/38.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.66/38.66 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.88/40.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.88/40.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.88/40.74 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.89/41.69 Timeout
%------------------------------------------------------------------------------