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

View Problem - Process Solution

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

% Computer : n012.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:51 EDT 2023

% Result   : Unknown 98.38s 102.03s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.11  % Problem  : LAT334+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n012.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:33:06 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.07/6.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.07/6.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.07/6.08  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.99/12.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.99/12.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.99/12.24  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.97/18.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.97/18.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.97/18.47  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.78/24.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.78/24.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.78/24.56  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.82/29.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.82/29.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.82/29.09  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.62/34.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.62/34.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.62/34.91  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.42/41.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.42/41.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.42/41.11  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.31/47.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.31/47.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.31/47.42  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.20/53.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.20/53.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.20/53.63  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.19/58.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.19/58.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.19/58.02  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.07/64.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.07/64.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.07/64.01  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.03/70.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.03/70.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.03/70.22  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.99/76.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.99/76.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.99/76.51  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.33/101.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 98.33/101.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 98.33/101.39  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.38/102.03  Timeout
%------------------------------------------------------------------------------