TSTP Solution File: SYO586+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SYO586+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n018.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 12:38:13 EDT 2023
% Result : Unknown 29.53s 41.78s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12 % Problem : SYO586+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.10/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n018.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 18:25:42 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.67/1.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.67/1.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.67/1.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.05/3.77 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.05/3.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.05/3.77 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.51/5.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.51/5.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.51/5.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.97/7.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.97/7.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.97/7.92 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.32/9.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.32/9.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.32/9.93 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.76/12.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.76/12.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.76/12.06 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.23/14.15 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.23/14.15 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.23/14.15 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.75/16.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.75/16.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.75/16.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.21/18.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.21/18.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.21/18.28 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.55/20.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.55/20.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.55/20.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.01/22.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.01/22.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.01/22.42 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.65/24.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.65/24.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.65/24.74 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.29/26.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.29/26.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.29/26.73 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.84/28.81 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.84/28.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.84/28.81 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.35/30.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.35/30.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.35/30.74 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.81/32.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.81/32.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.81/32.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.32/34.88 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.32/34.88 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.32/34.88 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.70/36.88 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.70/36.88 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.70/36.88 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.05/38.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.05/38.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.05/38.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.47/41.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.47/41.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.47/41.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.53/41.78 Timeout
%------------------------------------------------------------------------------