TSTP Solution File: SYO588+1 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : SYO588+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n021.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  : 300s
% DateTime : Fri May 19 12:38:13 EDT 2023

% Result   : Unknown 29.31s 41.81s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.14  % Problem  : SYO588+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.12/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.36  % Computer : n021.cluster.edu
% 0.14/0.36  % Model    : x86_64 x86_64
% 0.14/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.36  % Memory   : 8042.1875MB
% 0.14/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.36  % CPULimit : 300
% 0.14/0.36  % WCLimit  : 300
% 0.14/0.36  % DateTime : Thu May 18 18:42:27 EDT 2023
% 0.14/0.36  % CPUTime  : 
% 1.74/1.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.74/1.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.74/1.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.44/4.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.44/4.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.44/4.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.01/6.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.01/6.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.01/6.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.60/8.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.60/8.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.60/8.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.13/10.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.13/10.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.13/10.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.81/12.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.81/12.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.81/12.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.31/14.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.31/14.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.31/14.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.66/16.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.66/16.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.66/16.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.03/18.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.03/18.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.03/18.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.54/20.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.54/20.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.54/20.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.90/22.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.90/22.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.90/22.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.26/24.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.26/24.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.26/24.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.59/26.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.59/26.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.59/26.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.99/28.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.99/28.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.99/28.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.37/30.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.37/30.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.37/30.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.70/32.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.70/32.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.70/32.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.17/34.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.17/34.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.17/34.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.54/36.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.54/36.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.54/36.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.92/38.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.92/38.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.92/38.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.27/41.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.27/41.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.27/41.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.31/41.80  Timeout
%------------------------------------------------------------------------------