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

View Problem - Process Solution

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

% Computer : n019.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:38 EDT 2022

% Result   : Unknown 45.71s 62.63s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : SYO589+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.03/0.12  % Command  : leancop_casc.sh %s %d
% 0.13/0.33  % Computer : n019.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 600
% 0.13/0.33  % DateTime : Sat Jul  9 04:36:38 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.70/1.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.70/1.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.70/1.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.16/3.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.16/3.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.16/3.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.68/5.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.68/5.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.68/5.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.16/7.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.16/7.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.16/7.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.60/10.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.60/10.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.60/10.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.10/12.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.10/12.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.10/12.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.66/14.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.66/14.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.66/14.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.13/16.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.13/16.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.13/16.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.62/18.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.62/18.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.62/18.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.09/20.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.09/20.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.09/20.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.65/22.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.65/22.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.65/22.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.16/24.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.16/24.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.16/24.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.72/26.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.72/26.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.72/26.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.23/28.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.23/28.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.23/28.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.67/30.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.67/30.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.67/30.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.21/32.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.21/32.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.21/32.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.72/35.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.72/35.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.72/35.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.13/37.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.13/37.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.13/37.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.55/39.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.55/39.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.55/39.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.08/41.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.08/41.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.08/41.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.60/43.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.60/43.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.60/43.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.05/45.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.05/45.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.05/45.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.61/47.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.61/47.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.61/47.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.13/49.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.13/49.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.13/49.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.68/51.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.68/51.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.68/51.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.19/53.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.19/53.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.19/53.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.83/55.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.83/55.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.83/55.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.41/57.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.41/57.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.41/57.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.11/60.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.11/60.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.11/60.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.70/61.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.70/61.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.70/61.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------