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

View Problem - Process Solution

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

% Computer : n005.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 100.47s 103.02s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : LAT329+4 : TPTP v8.1.2. Released v3.4.0.
% 0.14/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n005.cluster.edu
% 0.14/0.34  % Model    : x86_64 x86_64
% 0.14/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34  % Memory   : 8042.1875MB
% 0.14/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34  % CPULimit : 300
% 0.14/0.34  % WCLimit  : 300
% 0.14/0.34  % DateTime : Thu May 18 14:02:28 EDT 2023
% 0.14/0.34  % CPUTime  : 
% 6.08/6.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.08/6.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.08/6.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.20/12.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.20/12.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.20/12.42  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.18/18.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.18/18.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.18/18.51  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.00/24.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.00/24.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.00/24.65  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.09/29.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.09/29.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.09/29.18  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.08/35.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.08/35.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.08/35.14  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.99/41.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.99/41.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.99/41.34  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.84/47.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.84/47.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.84/47.47  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.49/53.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.49/53.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.49/53.53  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.24/57.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.24/57.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.24/57.93  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.65/64.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.65/64.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.65/64.57  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 74.22/76.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.22/76.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.22/76.75  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 100.41/102.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.41/102.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.41/102.43  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 100.47/103.02  Timeout
%------------------------------------------------------------------------------