TSTP Solution File: KRS286+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : KRS286+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n010.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 24.36s 41.78s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12 % Problem : KRS286+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.03/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n010.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 22:55:27 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.41/1.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.41/1.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.41/1.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.64/3.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.64/3.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.64/3.64 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.89/5.62 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.89/5.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.89/5.62 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.04/7.63 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.04/7.63 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.04/7.63 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.13/9.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.13/9.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.13/9.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.30/11.77 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.30/11.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.30/11.77 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.52/13.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.52/13.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.52/13.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.76/15.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.76/15.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.76/15.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.96/18.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.96/18.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.96/18.05 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.10/20.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.10/20.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.10/20.05 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.34/22.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.34/22.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.34/22.18 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.58/24.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.58/24.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.58/24.25 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.80/26.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.80/26.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.80/26.31 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.10/28.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.10/28.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.10/28.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.31/30.44 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.31/30.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.31/30.44 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.53/32.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.53/32.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.53/32.56 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.72/34.59 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.72/34.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.72/34.59 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.95/36.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.95/36.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.95/36.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.09/38.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.09/38.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.09/38.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.30/40.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.30/40.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.30/40.83 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.36/41.78 Timeout
%------------------------------------------------------------------------------