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

View Problem - Process Solution

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

% Computer : n014.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:37 EDT 2022

% Result   : Unknown 51.01s 62.44s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.13  % Problem  : SYO587+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.12/0.14  % Command  : leancop_casc.sh %s %d
% 0.15/0.35  % Computer : n014.cluster.edu
% 0.15/0.35  % Model    : x86_64 x86_64
% 0.15/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.15/0.35  % Memory   : 8042.1875MB
% 0.15/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.15/0.35  % CPULimit : 300
% 0.15/0.35  % WCLimit  : 600
% 0.15/0.35  % DateTime : Sat Jul  9 01:03:06 EDT 2022
% 0.15/0.36  % CPUTime  : 
% 2.28/2.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.28/2.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.28/2.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.15/4.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.15/4.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.15/4.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.05/6.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.05/6.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.05/6.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.91/8.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.91/8.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.91/8.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.76/10.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.76/10.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.76/10.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.77/12.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.77/12.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.77/12.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.77/14.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.77/14.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.77/14.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.61/16.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.61/16.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.61/16.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.50/18.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.50/18.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.50/18.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.56/21.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.56/21.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.56/21.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.36/22.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.36/22.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.36/22.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.16/24.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.16/24.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.16/24.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.82/26.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.82/26.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.82/26.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.51/28.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.51/28.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.51/28.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.17/30.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.17/30.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.17/30.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.67/32.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.67/32.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.67/32.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.23/35.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.23/35.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.23/35.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.56/36.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.56/36.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.56/36.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.99/39.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.99/39.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.99/39.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.55/41.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.55/41.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.55/41.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.09/43.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.09/43.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.09/43.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.65/45.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.65/45.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.65/45.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.13/47.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.13/47.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.13/47.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.77/49.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.77/49.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.77/49.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.35/51.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.35/51.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.35/51.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.86/53.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.86/53.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.86/53.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.37/55.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.37/55.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.37/55.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.94/57.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.94/57.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.94/57.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.41/59.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.41/59.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.41/59.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.96/61.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.96/61.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.96/61.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------