TSTP Solution File: CSR087+3 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR087+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n004.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:04:27 EDT 2023

% Result   : Unknown 149.74s 149.98s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR087+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n004.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Fri May 19 00:18:54 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 11.18/10.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.18/10.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.18/10.91  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.55/22.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.55/22.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.55/22.70  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 33.31/33.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.31/33.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.31/33.53  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 44.33/44.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.33/44.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.33/44.21  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 48.68/49.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.68/49.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.68/49.21  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 60.05/61.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.05/61.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.05/61.01  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 71.13/72.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.13/72.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.13/72.30  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 81.62/83.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.62/83.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.62/83.10  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 96.00/97.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 96.00/97.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 96.00/97.25  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 149.73/149.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 149.73/149.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 149.73/149.42  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 149.74/149.98  Timeout
%------------------------------------------------------------------------------