TSTP Solution File: SYO590+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SYO590+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n031.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:14 EDT 2023
% Result : Unknown 33.98s 41.71s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.12 % Problem : SYO590+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.08/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n031.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 19:05:55 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.84/2.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.84/2.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.84/2.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.42/3.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.42/3.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.42/3.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.10/6.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.10/6.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.10/6.06 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.83/8.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.83/8.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.83/8.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.55/10.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.55/10.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.55/10.22 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.29/12.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.29/12.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.29/12.34 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.94/14.32 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.94/14.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.94/14.32 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.52/16.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.52/16.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.52/16.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.27/18.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.27/18.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.27/18.56 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.99/20.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.99/20.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.99/20.56 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.74/22.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.74/22.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.74/22.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.33/24.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.33/24.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.33/24.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.11/26.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.11/26.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.11/26.89 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.81/28.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.81/28.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.81/28.89 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.50/30.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.50/30.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.50/30.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.24/33.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.24/33.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.24/33.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.00/35.10 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.00/35.10 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.00/35.10 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.59/37.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.59/37.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.59/37.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.29/39.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.29/39.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.29/39.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.96/41.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.96/41.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.96/41.22 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.98/41.71 Timeout
%------------------------------------------------------------------------------