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

View Problem - Process Solution

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

% Computer : n024.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:48 EDT 2023

% Result   : Unknown 97.81s 102.09s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT322+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n024.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Thu May 18 14:38:11 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 6.08/6.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.08/6.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.08/6.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.02/12.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.02/12.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.02/12.24  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.09/18.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.09/18.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.09/18.61  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.11/24.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.11/24.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.11/24.81  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.03/28.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.03/28.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.03/28.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.86/35.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.86/35.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.86/35.00  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.62/41.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.62/41.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.62/41.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.08/47.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.08/47.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.08/47.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 50.63/53.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.63/53.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.63/53.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.45/57.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.45/57.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.45/57.97  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.39/64.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.39/64.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.39/64.14  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.35/70.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.35/70.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.35/70.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.33/76.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.33/76.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.33/76.65  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.78/101.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.78/101.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.78/101.46  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.81/102.09  Timeout
%------------------------------------------------------------------------------