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

View Problem - Process Solution

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

% Computer : n012.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:39 EDT 2023

% Result   : Unknown 94.32s 89.40s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.11  % Problem  : LAT287+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n012.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:31:21 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.43/5.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.43/5.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.43/5.45  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 10.61/10.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.61/10.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.61/10.53  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 15.79/15.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.79/15.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.79/15.73  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 21.15/20.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.15/20.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.15/20.94  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 24.50/24.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.50/24.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.50/24.20  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 29.72/30.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.72/30.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.72/30.24  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 35.03/35.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.03/35.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.03/35.51  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 40.28/40.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.28/40.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.28/40.53  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 45.43/45.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.43/45.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.43/45.63  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 49.05/49.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.05/49.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.05/49.37  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 54.20/55.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.20/55.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.20/55.01  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 64.44/60.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.44/60.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.44/60.18  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 69.57/65.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.57/65.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.57/65.29  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 94.29/89.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.29/89.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.29/89.30  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 94.32/89.39  Timeout
%------------------------------------------------------------------------------