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

View Problem - Process Solution

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

% Computer : n021.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:45 EDT 2023

% Result   : Unknown 98.67s 102.33s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.13  % Problem  : LAT307+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.35  % Computer : n021.cluster.edu
% 0.14/0.35  % Model    : x86_64 x86_64
% 0.14/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35  % Memory   : 8042.1875MB
% 0.14/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35  % CPULimit : 300
% 0.14/0.35  % WCLimit  : 300
% 0.14/0.35  % DateTime : Thu May 18 14:16:31 EDT 2023
% 0.14/0.35  % CPUTime  : 
% 6.04/6.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.04/6.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.04/6.06  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.86/12.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.86/12.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.86/12.17  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.78/18.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.78/18.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.78/18.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.51/24.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.51/24.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.51/24.56  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.53/29.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.53/29.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.53/29.12  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.42/35.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.42/35.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.42/35.17  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.14/41.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.14/41.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.14/41.17  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.20/47.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.20/47.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.20/47.73  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.11/53.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.11/53.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.11/53.86  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.10/58.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.10/58.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.10/58.29  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.07/64.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.07/64.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.07/64.33  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.98/70.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.98/70.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.98/70.53  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.23/77.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.23/77.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.23/77.11  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.64/101.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 98.64/101.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 98.64/101.72  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.67/102.33  Timeout
%------------------------------------------------------------------------------