TSTP Solution File: KRS290+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : KRS290+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n020.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 24.49s 40.80s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12 % Problem : KRS290+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.06/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n020.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 23:02:17 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.38/1.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.38/1.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.38/1.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.60/3.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.60/3.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.60/3.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.83/5.66 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.83/5.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.83/5.66 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.86/7.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.86/7.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.86/7.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.06/8.69 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.06/8.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.06/8.69 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.23/10.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.23/10.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.23/10.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.47/12.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.47/12.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.47/12.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.68/14.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.68/14.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.68/14.92 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.87/17.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.87/17.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.87/17.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.20/19.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.20/19.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.20/19.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.42/21.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.42/21.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.42/21.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.63/23.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.63/23.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.63/23.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.78/25.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.78/25.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.78/25.33 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.02/27.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.02/27.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.02/27.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.28/29.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.28/29.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.28/29.47 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.47/31.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.47/31.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.47/31.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.73/33.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.73/33.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.73/33.64 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.92/35.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.92/35.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.92/35.72 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.15/37.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.15/37.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.15/37.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.37/39.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.37/39.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.37/39.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.49/40.80 Timeout
%------------------------------------------------------------------------------