TSTP Solution File: CSR100+6 by nanoCoP---2.0

View Problem - Process Solution

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

% Computer : n027.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:36 EDT 2023

% Result   : Unknown 134.49s 134.08s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.11  % Problem  : CSR100+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.06/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n027.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 : Fri May 19 00:05:50 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 9.70/9.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.70/9.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.70/9.59  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.16/18.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.16/18.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.16/18.75  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 28.19/27.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.19/27.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.19/27.71  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 37.97/37.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.97/37.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.97/37.61  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 40.94/41.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.94/41.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.94/41.49  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 50.49/50.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.49/50.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.49/50.98  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 60.46/60.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.46/60.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.46/60.63  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 70.24/70.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.24/70.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.24/70.81  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 79.93/81.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.93/81.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.93/81.13  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 83.13/84.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.13/84.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.13/84.26  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 92.43/93.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 92.43/93.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 92.43/93.23  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 134.49/134.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 134.49/134.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 134.49/134.04  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 134.49/134.08  Timeout
%------------------------------------------------------------------------------