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

View Problem - Process Solution

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

% Computer : n032.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 106.32s 111.50s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.07  % Problem  : LAT331+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.08  % Command  : nanocop.sh %s %d
% 0.07/0.26  % Computer : n032.cluster.edu
% 0.07/0.26  % Model    : x86_64 x86_64
% 0.07/0.26  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.07/0.26  % Memory   : 8042.1875MB
% 0.07/0.26  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.07/0.26  % CPULimit : 300
% 0.07/0.26  % WCLimit  : 300
% 0.07/0.26  % DateTime : Thu May 18 14:11:09 EDT 2023
% 0.07/0.26  % CPUTime  : 
% 6.36/6.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.36/6.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.36/6.42  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.67/13.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.67/13.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.67/13.51  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.95/19.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.95/19.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.95/19.74  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 26.69/27.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.69/27.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.69/27.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 31.92/33.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.92/33.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.92/33.18  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 39.02/41.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.02/41.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.02/41.01  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 46.03/48.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.03/48.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.03/48.20  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 53.08/55.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.08/55.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.08/55.50  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 59.87/62.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.87/62.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.87/62.46  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 64.50/67.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.50/67.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.50/67.51  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 70.01/73.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.01/73.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.01/73.58  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 75.58/79.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 75.58/79.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 75.58/79.76  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 81.25/86.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.25/86.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.25/86.01  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 106.29/110.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 106.29/110.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.29/110.92  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 106.32/111.50  Timeout
%------------------------------------------------------------------------------