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

View Problem - Process Solution

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

% Computer : n031.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:04 EDT 2023

% Result   : Unknown 107.52s 111.10s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.09  % Problem  : TOP023+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.10  % Command  : nanocop.sh %s %d
% 0.09/0.29  % Computer : n031.cluster.edu
% 0.09/0.29  % Model    : x86_64 x86_64
% 0.09/0.29  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.09/0.29  % Memory   : 8042.1875MB
% 0.09/0.29  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.09/0.29  % CPULimit : 300
% 0.09/0.29  % WCLimit  : 300
% 0.09/0.29  % DateTime : Thu May 18 20:30:15 EDT 2023
% 0.09/0.29  % CPUTime  : 
% 8.95/8.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.95/8.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.95/8.93  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 16.08/16.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.08/16.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.08/16.45  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 22.94/23.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.94/23.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.94/23.34  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 29.71/30.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.71/30.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.71/30.61  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 34.87/36.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.87/36.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.87/36.34  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 41.85/43.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.85/43.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.85/43.23  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 48.63/50.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.63/50.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.63/50.15  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.38/56.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.38/56.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.38/56.49  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 60.12/62.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.12/62.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.12/62.65  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 64.02/67.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.02/67.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.02/67.15  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 69.92/73.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.92/73.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.92/73.24  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 76.16/79.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.16/79.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.16/79.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 82.07/85.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.07/85.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.07/85.66  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 107.41/110.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 107.41/110.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 107.41/110.55  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 107.52/111.10  Timeout
%------------------------------------------------------------------------------