TSTP Solution File: KRS285+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : KRS285+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n009.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 26.45s 41.96s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.11 % Problem : KRS285+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.03/0.12 % Command : nanocop.sh %s %d
% 0.11/0.33 % Computer : n009.cluster.edu
% 0.11/0.33 % Model : x86_64 x86_64
% 0.11/0.33 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.33 % Memory : 8042.1875MB
% 0.11/0.33 % OS : Linux 3.10.0-693.el7.x86_64
% 0.11/0.33 % CPULimit : 300
% 0.11/0.33 % WCLimit : 300
% 0.11/0.33 % DateTime : Thu May 18 23:03:17 EDT 2023
% 0.11/0.33 % CPUTime :
% 1.64/1.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.64/1.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.64/1.79 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.92/3.66 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.92/3.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.92/3.66 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.25/5.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.25/5.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.25/5.73 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.51/7.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.51/7.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.51/7.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.91/9.98 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.91/9.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.91/9.98 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.29/12.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.29/12.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.29/12.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.62/14.08 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.62/14.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.62/14.08 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.07/16.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.07/16.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.07/16.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.43/18.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.43/18.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.43/18.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.72/20.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.72/20.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.72/20.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.07/22.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.07/22.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.07/22.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.38/24.50 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.38/24.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.38/24.50 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.72/26.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.72/26.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.72/26.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.97/28.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.97/28.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.97/28.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.25/30.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.25/30.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.25/30.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.50/32.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.50/32.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.50/32.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.73/34.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.73/34.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.73/34.79 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.91/36.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.91/36.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.91/36.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.16/38.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.16/38.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.16/38.93 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.44/41.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.44/41.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.44/41.02 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.45/41.96 Timeout
%------------------------------------------------------------------------------