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

View Problem - Process Solution

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

% Computer : n016.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 109.03s 113.34s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT328+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n016.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 14:55:31 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.79/6.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.79/6.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.79/6.78  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 13.20/13.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.20/13.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.20/13.77  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 19.81/20.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.81/20.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.81/20.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 26.80/27.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.80/27.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.80/27.83  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 31.63/32.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.63/32.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.63/32.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 38.57/40.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.57/40.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.57/40.14  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.42/47.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.42/47.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.42/47.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.99/54.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.99/54.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.99/54.26  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.92/61.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.92/61.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.92/61.92  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 63.85/67.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.85/67.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.85/67.25  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 71.49/75.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.49/75.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.49/75.07  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 77.24/81.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.24/81.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.24/81.50  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 83.36/88.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.36/88.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.36/88.11  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 109.00/113.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 109.00/113.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 109.00/113.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 109.03/113.34  Timeout
%------------------------------------------------------------------------------