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

View Problem - Process Solution

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

% Computer : n010.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:41 EDT 2023

% Result   : Unknown 99.53s 102.96s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.12  % Problem  : LAT293+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n010.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 14:21:31 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 6.12/6.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.12/6.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.12/6.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.08/12.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.08/12.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.08/12.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.07/18.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.07/18.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.07/18.53  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.01/24.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.01/24.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.01/24.69  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.05/29.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.05/29.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.05/29.21  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.01/35.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.01/35.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.01/35.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.96/41.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.96/41.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.96/41.23  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.79/47.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.79/47.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.79/47.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.60/53.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.60/53.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.60/53.58  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.56/58.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.56/58.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.56/58.04  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.30/63.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.30/63.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.30/63.87  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.96/70.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.96/70.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.96/70.01  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.50/102.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.50/102.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.50/102.06  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.53/102.96  Timeout
%------------------------------------------------------------------------------