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

View Problem - Process Solution

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

% Computer : n022.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:42 EDT 2022

% Result   : Unknown 43.34s 62.49s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : SYO595+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.06/0.12  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n022.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 : Fri Jul  8 19:36:11 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.65/1.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.65/1.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.65/1.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.13/3.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.13/3.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.13/3.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.56/5.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.56/5.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.56/5.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.05/7.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.05/7.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.05/7.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.52/10.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.52/10.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.52/10.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.92/12.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.92/12.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.92/12.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.42/14.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.42/14.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.42/14.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.88/16.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.88/16.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.88/16.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.39/18.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.39/18.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.39/18.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.82/20.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.82/20.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.82/20.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.21/22.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.21/22.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.21/22.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.69/24.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.69/24.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.69/24.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.10/26.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.10/26.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.10/26.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.59/28.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.59/28.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.59/28.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.96/30.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.96/30.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.96/30.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.34/32.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.34/32.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.34/32.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.82/34.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.82/34.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.82/34.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.22/36.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.22/36.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.22/36.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.56/38.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.56/38.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.56/38.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.02/41.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.02/41.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.02/41.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.45/43.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.45/43.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.45/43.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.80/45.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.80/45.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.80/45.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.31/47.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.31/47.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.31/47.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.73/49.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.73/49.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.73/49.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.16/51.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.16/51.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.16/51.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.53/53.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.53/53.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.53/53.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.95/55.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.95/55.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.95/55.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.33/57.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.33/57.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.33/57.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.78/59.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.78/59.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.78/59.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.22/61.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.22/61.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.22/61.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------