TSTP Solution File: TOP028+4 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : TOP028+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n022.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:39:05 EDT 2023

% Result   : Unknown 103.23s 106.32s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : TOP028+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n022.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  : 300
% 0.12/0.34  % DateTime : Thu May 18 20:02:06 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 5.98/6.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.98/6.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.98/6.03  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.67/12.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.67/12.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.67/12.01  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.43/18.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.43/18.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.43/18.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.10/24.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.10/24.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.10/24.43  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.22/29.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.22/29.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.22/29.27  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 33.39/35.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.39/35.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.39/35.38  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.99/41.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.99/41.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.99/41.99  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 46.01/48.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.01/48.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.01/48.76  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 52.25/55.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.25/55.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.25/55.15  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 56.71/59.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.71/59.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.71/59.75  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 65.06/68.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.06/68.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.06/68.64  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 103.18/105.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.18/105.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.18/105.62  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 103.23/106.32  Timeout
%------------------------------------------------------------------------------