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

View Problem - Process Solution

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

% Computer : n013.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 11:28:43 EDT 2023

% Result   : Unknown 105.52s 108.23s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.13  % Problem  : LAT300+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n013.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Thu May 18 13:57:26 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 7.38/7.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.38/7.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.38/7.35  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 14.23/14.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.23/14.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.23/14.20  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 21.08/21.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.08/21.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.08/21.51  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.08/28.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.08/28.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.08/28.84  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 32.69/33.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.69/33.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.69/33.84  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 39.06/40.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.06/40.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.06/40.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 44.73/46.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.73/46.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.73/46.21  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 50.18/52.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.18/52.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.18/52.23  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.83/58.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.83/58.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.83/58.64  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 60.02/63.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.02/63.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.02/63.50  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 66.21/69.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.21/69.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.21/69.56  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 105.50/107.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.50/107.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.50/107.66  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 105.52/108.23  Timeout
%------------------------------------------------------------------------------