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

View Problem - Process Solution

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

% Computer : n003.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 105.63s 107.18s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : TOP030+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n003.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 20:07:05 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 6.03/6.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.03/6.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.03/6.02  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.91/12.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.91/12.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.91/12.20  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.82/18.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.82/18.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.82/18.46  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.07/25.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.07/25.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.07/25.00  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.86/29.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.86/29.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.86/29.92  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.02/36.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.02/36.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.02/36.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 41.22/42.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.22/42.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.22/42.59  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 47.44/48.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.44/48.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.44/48.90  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.12/55.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.12/55.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.12/55.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.71/60.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.71/60.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.71/60.77  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 67.92/70.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.92/70.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.92/70.50  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 105.60/107.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.60/107.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.60/107.16  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 105.63/107.18  Timeout
%------------------------------------------------------------------------------