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

View Problem - Process Solution

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

% Computer : n009.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:35 EDT 2022

% Result   : Unknown 50.90s 62.62s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : SYO583+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.12  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n009.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 16:07:52 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.79/1.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.79/1.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.79/1.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.67/4.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.67/4.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.67/4.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.48/6.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.48/6.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.48/6.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.26/8.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.26/8.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.26/8.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.05/10.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.05/10.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.05/10.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.70/12.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.70/12.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.70/12.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.35/14.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.35/14.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.35/14.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.16/16.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.16/16.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.16/16.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.85/18.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.85/18.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.85/18.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.65/20.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.65/20.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.65/20.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.24/22.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.24/22.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.24/22.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.91/24.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.91/24.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.91/24.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.67/26.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.67/26.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.67/26.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.53/29.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.53/29.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.53/29.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.11/30.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.11/30.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.11/30.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.81/33.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.81/33.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.81/33.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.45/35.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.45/35.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.45/35.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.13/37.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.13/37.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.13/37.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.82/39.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.82/39.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.82/39.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.40/41.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.40/41.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.40/41.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.06/43.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.06/43.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.06/43.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.72/45.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.72/45.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.72/45.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.28/47.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.28/47.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.28/47.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.06/49.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.06/49.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.06/49.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.71/51.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.71/51.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.71/51.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.36/53.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.36/53.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.36/53.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.99/55.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.99/55.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.99/55.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.56/57.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.56/57.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.56/57.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.22/59.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.22/59.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.22/59.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.89/62.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.89/62.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.89/62.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------