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

View Problem - Process Solution

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

% Computer : n005.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:44 EDT 2023

% Result   : Unknown 97.62s 102.05s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.11  % Problem  : LAT303+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.11/0.33  % Computer : n005.cluster.edu
% 0.11/0.33  % Model    : x86_64 x86_64
% 0.11/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.33  % Memory   : 8042.1875MB
% 0.11/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.33  % CPULimit : 300
% 0.11/0.33  % WCLimit  : 300
% 0.11/0.33  % DateTime : Thu May 18 14:26:43 EDT 2023
% 0.11/0.33  % CPUTime  : 
% 5.84/5.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.84/5.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.84/5.81  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.39/11.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.39/11.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.39/11.91  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 16.95/18.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.95/18.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.95/18.04  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 22.46/24.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.46/24.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.46/24.26  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 26.34/28.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.34/28.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.34/28.96  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 32.34/35.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.34/35.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.34/35.07  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 38.31/41.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.31/41.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.31/41.30  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 44.33/47.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.33/47.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.33/47.59  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 50.36/53.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.36/53.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.36/53.81  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.32/58.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.32/58.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.32/58.03  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.21/64.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.21/64.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.21/64.06  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.26/70.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.26/70.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.26/70.47  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.19/76.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.19/76.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.19/76.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.58/101.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.58/101.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.58/101.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.62/102.05  Timeout
%------------------------------------------------------------------------------