TSTP Solution File: SYO596+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SYO596+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n024.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 34.14s 41.93s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.13 % Problem : SYO596+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.11/0.14 % Command : nanocop.sh %s %d
% 0.14/0.35 % Computer : n024.cluster.edu
% 0.14/0.35 % Model : x86_64 x86_64
% 0.14/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35 % Memory : 8042.1875MB
% 0.14/0.35 % OS : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35 % CPULimit : 300
% 0.14/0.35 % WCLimit : 300
% 0.14/0.35 % DateTime : Thu May 18 18:36:51 EDT 2023
% 0.14/0.35 % CPUTime :
% 1.89/2.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.89/2.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.89/2.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.63/4.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.63/4.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.63/4.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.41/6.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.41/6.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.41/6.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.16/8.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.16/8.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.16/8.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.65/10.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.65/10.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.65/10.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.45/12.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.45/12.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.45/12.42 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.31/14.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.31/14.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.31/14.60 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.21/16.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.21/16.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.21/16.72 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.95/18.63 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.95/18.63 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.95/18.63 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.40/20.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.40/20.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.40/20.45 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.15/22.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.15/22.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.15/22.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.80/24.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.80/24.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.80/24.79 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.47/26.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.47/26.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.47/26.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.09/28.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.09/28.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.09/28.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.79/31.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.79/31.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.79/31.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.47/33.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.47/33.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.47/33.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.09/35.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.09/35.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.09/35.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.74/37.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.74/37.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.74/37.25 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.38/39.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.38/39.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.38/39.34 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.04/41.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.04/41.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.04/41.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.14/41.92 Timeout
%------------------------------------------------------------------------------