TSTP Solution File: SYO586+1 by leanCoP---2.2

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : SYO586+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm  : none
% Format   : tptp:raw
% Command  : leancop_casc.sh %s %d

% Computer : n023.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  : 600s
% DateTime : Thu Jul 21 17:29:37 EDT 2022

% Result   : Unknown 50.19s 62.91s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.14  % Problem  : SYO586+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.03/0.15  % Command  : leancop_casc.sh %s %d
% 0.15/0.36  % Computer : n023.cluster.edu
% 0.15/0.36  % Model    : x86_64 x86_64
% 0.15/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.15/0.36  % Memory   : 8042.1875MB
% 0.15/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.15/0.36  % CPULimit : 300
% 0.15/0.36  % WCLimit  : 600
% 0.15/0.36  % DateTime : Fri Jul  8 23:16:11 EDT 2022
% 0.15/0.37  % CPUTime  : 
% 1.80/1.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.80/1.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.80/1.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.39/3.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.39/3.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.39/3.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.98/6.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.98/6.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.98/6.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.64/8.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.64/8.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.64/8.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.26/10.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.26/10.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.26/10.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.94/12.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.94/12.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.94/12.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.51/14.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.51/14.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.51/14.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.13/16.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.13/16.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.13/16.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.84/18.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.84/18.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.84/18.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.44/20.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.44/20.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.44/20.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.71/22.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.71/22.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.71/22.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.24/24.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.24/24.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.24/24.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.95/26.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.95/26.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.95/26.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.65/29.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.65/29.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.65/29.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.27/31.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.27/31.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.27/31.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.98/33.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.98/33.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.98/33.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.56/35.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.56/35.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.56/35.22  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.06/37.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.06/37.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.06/37.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.55/39.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.55/39.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.55/39.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.26/41.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.26/41.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.26/41.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.88/43.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.88/43.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.88/43.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.48/45.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.48/45.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.48/45.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.03/47.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.03/47.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.03/47.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.60/49.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.60/49.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.60/49.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.17/51.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.17/51.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.17/51.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.78/54.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.78/54.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.78/54.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.28/56.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.28/56.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.28/56.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.93/58.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.93/58.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.93/58.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.56/60.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.56/60.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.56/60.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.04/62.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.04/62.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.04/62.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------