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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : SYO588+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 47.14s 62.74s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : SYO588+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.11/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n019.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 600
% 0.13/0.34  % DateTime : Sat Jul  9 13:53:38 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.67/1.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.67/1.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.67/1.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.17/3.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.17/3.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.17/3.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.88/6.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.88/6.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.88/6.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.22/7.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.22/7.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.22/7.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.90/10.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.90/10.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.90/10.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.52/12.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.52/12.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.52/12.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.02/14.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.02/14.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.02/14.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.65/16.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.65/16.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.65/16.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.24/18.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.24/18.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.24/18.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.93/20.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.93/20.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.93/20.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.53/22.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.53/22.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.53/22.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.21/24.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.21/24.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.21/24.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.93/26.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.93/26.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.93/26.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.54/28.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.54/28.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.54/28.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.15/31.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.15/31.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.15/31.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.86/33.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.86/33.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.86/33.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.36/35.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.36/35.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.36/35.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.89/37.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.89/37.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.89/37.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.51/39.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.51/39.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.51/39.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.12/41.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.12/41.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.12/41.38  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.62/43.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.62/43.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.62/43.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.14/45.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.14/45.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.14/45.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.72/47.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.72/47.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.72/47.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.25/49.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.25/49.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.25/49.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.67/51.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.67/51.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.67/51.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.10/53.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.10/53.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.10/53.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.62/55.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.62/55.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.62/55.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.11/57.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.11/57.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.11/57.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.55/59.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.55/59.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.55/59.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.96/61.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.96/61.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.96/61.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------