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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : SYO599+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:44 EDT 2022

% Result   : Unknown 50.53s 62.61s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : SYO599+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.06/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n019.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  : 600
% 0.12/0.33  % DateTime : Sat Jul  9 13:49:08 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.72/1.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.72/1.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.72/1.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.32/3.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.32/3.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.32/3.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.97/6.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.97/6.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.97/6.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.60/8.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.60/8.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.60/8.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.19/10.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.19/10.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.19/10.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.04/12.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.04/12.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.04/12.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.74/14.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.74/14.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.74/14.38  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.31/16.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.31/16.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.31/16.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.94/18.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.94/18.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.94/18.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.72/20.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.72/20.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.72/20.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.56/22.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.56/22.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.56/22.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.31/24.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.31/24.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.31/24.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.97/26.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.97/26.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.97/26.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.66/29.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.66/29.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.66/29.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.42/31.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.42/31.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.42/31.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.11/33.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.11/33.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.11/33.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.68/35.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.68/35.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.68/35.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.13/37.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.13/37.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.13/37.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.63/39.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.63/39.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.63/39.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.31/41.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.31/41.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.31/41.38  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.94/43.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.94/43.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.94/43.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.59/45.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.59/45.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.59/45.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.33/47.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.33/47.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.33/47.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.00/49.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.00/49.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.00/49.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.78/51.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.78/51.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.78/51.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.51/53.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.51/53.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.51/53.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.30/56.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.30/56.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.30/56.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.05/58.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.05/58.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.05/58.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.77/60.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.77/60.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.77/60.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.52/62.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.52/62.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.52/62.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------