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

View Problem - Process Solution

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

% Computer : n021.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:45 EDT 2023

% Result   : Unknown 99.49s 103.32s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.13/0.14  % Problem  : LAT310+4 : TPTP v8.1.2. Released v3.4.0.
% 0.13/0.15  % Command  : nanocop.sh %s %d
% 0.16/0.36  % Computer : n021.cluster.edu
% 0.16/0.36  % Model    : x86_64 x86_64
% 0.16/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.16/0.36  % Memory   : 8042.1875MB
% 0.16/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.16/0.36  % CPULimit : 300
% 0.16/0.36  % WCLimit  : 300
% 0.16/0.36  % DateTime : Thu May 18 14:16:16 EDT 2023
% 0.16/0.37  % CPUTime  : 
% 7.02/7.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.02/7.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.02/7.03  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.87/13.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.87/13.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.87/13.17  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.77/19.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.77/19.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.77/19.50  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.74/25.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.74/25.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.74/25.84  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.68/30.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.68/30.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.68/30.09  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.54/36.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.54/36.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.54/36.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 40.41/42.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.41/42.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.41/42.37  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 46.27/48.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.27/48.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.27/48.57  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.98/54.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.98/54.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.98/54.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.85/59.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.85/59.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.85/59.18  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.78/65.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.78/65.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.78/65.25  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.82/71.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.82/71.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.82/71.63  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.78/77.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.78/77.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.78/77.82  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.47/102.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.47/102.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.47/102.87  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.49/103.32  Timeout
%------------------------------------------------------------------------------