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

View Problem - Process Solution

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

% Result   : Unknown 43.30s 62.65s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : SYO584+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.34  % Computer : n023.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 600
% 0.12/0.34  % DateTime : Sat Jul  9 10:25:40 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.62/1.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.62/1.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.62/1.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.18/4.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.18/4.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.18/4.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.63/5.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.63/5.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.63/5.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.13/8.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.13/8.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.13/8.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.55/10.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.55/10.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.55/10.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.05/12.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.05/12.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.05/12.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.62/14.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.62/14.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.62/14.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.07/16.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.07/16.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.07/16.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.50/18.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.50/18.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.50/18.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.90/20.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.90/20.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.90/20.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.31/22.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.31/22.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.31/22.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.72/24.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.72/24.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.72/24.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.14/26.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.14/26.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.14/26.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.53/28.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.53/28.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.53/28.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.11/30.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.11/30.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.11/30.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.46/33.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.46/33.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.46/33.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.89/34.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.89/34.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.89/34.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.23/36.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.23/36.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.23/36.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.64/39.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.64/39.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.64/39.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.10/41.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.10/41.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.10/41.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.47/43.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.47/43.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.47/43.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.91/45.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.91/45.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.91/45.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.33/47.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.33/47.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.33/47.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.73/49.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.73/49.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.73/49.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.15/51.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.15/51.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.15/51.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.56/53.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.56/53.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.56/53.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.98/55.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.98/55.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.98/55.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.37/57.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.37/57.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.37/57.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.85/59.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.85/59.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.85/59.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.23/61.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.23/61.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.23/61.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------