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

View Problem - Process Solution

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

% Computer : n022.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:50 EDT 2023

% Result   : Unknown 101.99s 105.12s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.13  % Problem  : LAT330+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.35  % Computer : n022.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:01:36 EDT 2023
% 0.14/0.35  % CPUTime  : 
% 6.04/6.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.04/6.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.04/6.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.13/12.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.13/12.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.13/12.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.07/18.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.07/18.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.07/18.54  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.06/24.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.06/24.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.06/24.76  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.94/28.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.94/28.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.94/28.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.74/34.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.74/34.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.74/34.97  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.40/41.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.40/41.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.40/41.05  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.54/47.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.54/47.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.54/47.74  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 52.13/54.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.13/54.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.13/54.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 56.55/59.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.55/59.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.55/59.55  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 62.73/66.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.73/66.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.73/66.54  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 101.95/104.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 101.95/104.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 101.95/104.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 101.99/105.12  Timeout
%------------------------------------------------------------------------------