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

View Problem - Process Solution

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

% Computer : n028.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:43 EDT 2022

% Result   : Unknown 46.66s 62.80s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.13  % Problem  : SYO598+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.08/0.14  % Command  : leancop_casc.sh %s %d
% 0.14/0.35  % Computer : n028.cluster.edu
% 0.14/0.35  % Model    : x86_64 x86_64
% 0.14/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35  % Memory   : 8042.1875MB
% 0.14/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35  % CPULimit : 300
% 0.14/0.35  % WCLimit  : 600
% 0.14/0.35  % DateTime : Sat Jul  9 00:37:25 EDT 2022
% 0.14/0.35  % CPUTime  : 
% 1.69/1.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.69/1.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.69/1.90  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 3.32/3.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.32/3.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.32/3.98  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 4.84/5.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.84/5.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.84/5.99  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 6.45/8.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.45/8.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.45/8.07  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 7.96/10.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.96/10.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.96/10.16  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 9.56/12.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.56/12.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.56/12.23  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 11.09/14.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.09/14.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.09/14.32  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 12.64/16.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.64/16.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.64/16.38  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 14.18/18.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.18/18.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.18/18.48  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 15.72/20.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.72/20.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.72/20.55  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 17.29/22.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.29/22.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.29/22.61  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 18.77/24.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.77/24.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.77/24.70  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 20.32/26.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.32/26.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.32/26.80  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 21.86/28.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.86/28.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.86/28.83  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 23.37/30.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.37/30.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.37/30.96  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 24.89/32.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.89/32.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.89/32.99  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 26.44/35.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.44/35.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.44/35.11  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 28.03/37.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.03/37.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.03/37.18  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 29.62/39.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.62/39.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.62/39.31  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 31.06/41.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.06/41.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.06/41.31  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 32.66/43.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.66/43.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.66/43.44  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 34.07/45.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.07/45.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.07/45.45  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 35.71/47.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.71/47.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.71/47.58  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 37.21/49.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.21/49.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.21/49.66  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 38.79/51.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.79/51.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.79/51.77  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 40.34/53.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.34/53.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.34/53.83  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 41.89/55.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.89/55.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.89/55.93  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 43.46/58.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.46/58.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.46/58.00  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 44.97/60.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.97/60.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.97/60.08  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 46.55/62.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.55/62.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.55/62.15  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
%------------------------------------------------------------------------------