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

View Problem - Process Solution

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

% Computer : n023.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 44.79s 62.71s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12  % Problem  : SYO597+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.04/0.13  % Command  : leancop_casc.sh %s %d
% 0.12/0.34  % Computer : n023.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 600
% 0.12/0.34  % DateTime : Sat Jul  9 07:59:40 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.68/1.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.68/1.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.68/1.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.20/4.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.20/4.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.20/4.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.59/5.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.59/5.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.59/5.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.12/7.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.12/7.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.12/7.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.57/10.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.57/10.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.57/10.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.02/12.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.02/12.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.02/12.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.53/14.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.53/14.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.53/14.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.03/16.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.03/16.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.03/16.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.56/18.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.56/18.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.56/18.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.06/20.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.06/20.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.06/20.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.44/22.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.44/22.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.44/22.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.94/24.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.94/24.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.94/24.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.43/26.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.43/26.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.43/26.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.93/28.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.93/28.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.93/28.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.36/30.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.36/30.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.36/30.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.88/32.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.88/32.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.88/32.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.47/35.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.47/35.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.47/35.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.03/37.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.03/37.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.03/37.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.48/39.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.48/39.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.48/39.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.95/41.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.95/41.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.95/41.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.38/43.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.38/43.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.38/43.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.95/45.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.95/45.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.95/45.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.41/47.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.41/47.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.41/47.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.91/49.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.91/49.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.91/49.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.36/51.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.36/51.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.36/51.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.77/53.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.77/53.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.77/53.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.26/55.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.26/55.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.26/55.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.73/57.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.73/57.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.73/57.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.21/59.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.21/59.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.21/59.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.66/61.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.66/61.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.66/61.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------