TSTP Solution File: CSR088+7 by nanoCoP---2.0

View Problem - Process Solution

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

% Computer : n016.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:28 EDT 2023

% Result   : Unknown 134.51s 132.55s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR088+7 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n016.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Fri May 19 01:12:27 EDT 2023
% 0.13/0.33  % CPUTime  : 
% 9.51/9.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.51/9.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.51/9.40  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 18.98/18.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.98/18.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.98/18.74  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 28.41/28.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.41/28.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.41/28.00  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 37.90/37.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.90/37.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.90/37.44  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 41.12/40.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.12/40.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.12/40.89  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 50.93/50.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.93/50.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.93/50.31  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 60.62/60.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.62/60.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.62/60.58  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 70.30/69.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.30/69.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.30/69.96  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 79.61/79.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.61/79.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.61/79.04  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 82.63/82.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.63/82.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.63/82.37  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 92.16/91.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 92.16/91.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 92.16/91.63  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 134.50/132.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 134.50/132.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 134.50/132.49  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 134.51/132.55  Timeout
%------------------------------------------------------------------------------