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

View Problem - Process Solution

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

% Computer : n009.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:08 EDT 2023

% Result   : Unknown 103.57s 108.35s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : TOP038+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n009.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:22 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 5.96/5.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.96/5.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.96/5.99  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.84/12.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.84/12.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.84/12.14  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.48/18.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.48/18.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.48/18.19  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.10/24.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.10/24.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.10/24.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.19/29.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.19/29.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.19/29.20  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.06/35.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.06/35.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.06/35.96  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 41.28/43.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.28/43.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.28/43.61  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 49.32/51.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.32/51.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.32/51.75  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 56.28/58.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.28/58.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.28/58.93  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 61.39/64.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.39/64.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.39/64.41  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 67.04/70.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.04/70.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.04/70.15  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.65/76.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.65/76.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.65/76.33  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 78.18/82.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.18/82.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.18/82.43  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 103.54/107.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.54/107.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.54/107.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 103.57/108.35  Timeout
%------------------------------------------------------------------------------