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

View Problem - Process Solution

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

% Computer : n028.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:38 EDT 2023

% Result   : Unknown 91.95s 94.72s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : LAT283+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n028.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:39:07 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.40/5.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.40/5.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.40/5.46  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 10.74/10.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.74/10.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.74/10.62  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 16.19/15.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.19/15.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.19/15.97  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 21.12/21.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.12/21.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.12/21.60  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 24.41/25.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.41/25.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.41/25.27  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 29.43/31.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.43/31.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.43/31.04  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 34.66/36.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.66/36.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.66/36.40  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 41.67/43.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.67/43.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.67/43.40  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 47.30/49.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.30/49.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.30/49.18  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 50.94/53.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.94/53.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.94/53.58  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 56.24/59.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.24/59.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.24/59.35  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 61.60/64.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.60/64.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.60/64.54  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 67.19/69.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.19/69.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.19/69.92  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 91.91/94.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 91.91/94.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 91.91/94.55  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 91.95/94.72  Timeout
%------------------------------------------------------------------------------