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

View Problem - Process Solution

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

% Computer : n015.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:06 EDT 2023

% Result   : Unknown 101.99s 106.17s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.09  % Problem  : TOP031+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.10  % Command  : nanocop.sh %s %d
% 0.08/0.29  % Computer : n015.cluster.edu
% 0.08/0.29  % Model    : x86_64 x86_64
% 0.08/0.29  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.08/0.29  % Memory   : 8042.1875MB
% 0.08/0.29  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.29  % CPULimit : 300
% 0.12/0.29  % WCLimit  : 300
% 0.12/0.29  % DateTime : Thu May 18 20:17:42 EDT 2023
% 0.12/0.29  % CPUTime  : 
% 7.48/7.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.48/7.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.48/7.43  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 14.15/13.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.15/13.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.15/13.97  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 20.05/20.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.05/20.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.05/20.53  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 25.57/26.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.57/26.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.57/26.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 29.69/31.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.69/31.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.69/31.20  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 35.06/36.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.06/36.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.06/36.66  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 40.61/42.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.61/42.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.61/42.88  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 47.07/50.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.07/50.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.07/50.08  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 53.53/56.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.53/56.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.53/56.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 57.51/61.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.51/61.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.51/61.15  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 63.49/67.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.49/67.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.49/67.19  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 69.52/73.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.52/73.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.52/73.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 75.76/79.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 75.76/79.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 75.76/79.96  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 101.94/105.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 101.94/105.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 101.94/105.36  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 101.99/106.17  Timeout
%------------------------------------------------------------------------------