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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : LAT302+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 11:28:43 EDT 2023

% Result   : Unknown 99.41s 103.97s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.11  % Problem  : LAT302+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n031.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 14:46:59 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.53/6.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.53/6.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.53/6.57  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 13.14/13.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.14/13.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.14/13.84  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 19.54/21.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.54/21.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.54/21.02  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 25.34/26.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.34/26.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.34/26.62  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.98/30.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.98/30.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.98/30.75  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.42/36.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.42/36.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.42/36.63  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 40.05/43.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.05/43.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.05/43.05  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.97/49.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.97/49.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.97/49.44  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.90/55.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.90/55.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.90/55.76  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.94/60.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.94/60.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.94/60.07  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.90/66.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.90/66.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.90/66.14  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 68.02/72.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.02/72.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.02/72.54  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 74.05/78.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.05/78.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.05/78.66  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.36/103.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.36/103.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.36/103.35  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.41/103.97  Timeout
%------------------------------------------------------------------------------