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

View Problem - Process Solution

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

% Computer : n001.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 146.75s 145.71s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR100+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n001.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 01:18:36 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 10.78/10.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.78/10.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.78/10.58  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 21.22/20.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.22/20.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.22/20.79  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 31.74/31.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.74/31.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.74/31.22  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 42.76/41.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.76/41.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.76/41.98  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 46.71/46.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.71/46.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.71/46.62  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 57.76/57.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.76/57.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.76/57.62  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 68.69/68.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.69/68.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.69/68.92  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 79.23/80.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.23/80.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.23/80.06  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 93.11/93.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.11/93.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.11/93.56  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 146.72/145.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 146.72/145.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 146.72/145.05  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 146.75/145.71  Timeout
%------------------------------------------------------------------------------