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

View Problem - Process Solution

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

% Computer : n008.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:39 EDT 2022

% Result   : Unknown 52.68s 64.64s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : SYO590+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.12  % Command  : leancop_casc.sh %s %d
% 0.13/0.33  % Computer : n008.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % 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 : Sat Jul  9 13:22:53 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.83/2.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.83/2.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.83/2.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.55/4.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.55/4.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.55/4.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.24/6.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.24/6.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.24/6.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.89/8.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.89/8.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.89/8.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.57/10.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.57/10.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.57/10.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.43/12.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.43/12.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.43/12.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.09/14.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.09/14.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.09/14.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.94/16.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.94/16.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.94/16.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.93/18.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.93/18.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.93/18.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.73/20.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.73/20.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.73/20.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.57/22.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.57/22.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.57/22.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.43/24.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.43/24.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.43/24.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.26/27.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.26/27.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.26/27.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.08/29.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.08/29.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.08/29.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.96/31.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.96/31.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.96/31.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.82/33.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.82/33.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.82/33.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.63/36.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.63/36.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.63/36.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.30/38.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.30/38.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.30/38.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.04/41.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.04/41.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.04/41.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.62/43.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.62/43.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.62/43.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.41/45.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.41/45.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.41/45.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.92/47.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.92/47.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.92/47.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.68/49.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.68/49.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.68/49.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.27/51.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.27/51.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.27/51.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.01/53.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.01/53.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.01/53.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.72/55.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.72/55.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.72/55.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.54/58.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.54/58.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.54/58.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.32/60.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.32/60.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.32/60.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.95/62.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.95/62.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.95/62.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.64/64.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.64/64.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.64/64.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------