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

View Problem - Process Solution

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

% Computer : n017.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:41 EDT 2023

% Result   : Unknown 136.69s 139.36s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR107+7 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n017.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 23:49:45 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 9.96/9.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.96/9.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.96/9.83  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.90/20.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.90/20.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.90/20.15  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.59/30.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.59/30.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.59/30.44  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 39.21/40.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.21/40.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.21/40.73  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 42.62/43.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.62/43.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.62/43.97  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 52.49/54.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.49/54.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.49/54.44  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 62.33/64.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.33/64.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.33/64.69  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 72.15/75.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.15/75.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.15/75.11  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 81.61/85.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.61/85.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.61/85.14  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 84.94/88.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 84.94/88.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 84.94/88.56  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 94.60/98.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.60/98.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.60/98.83  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 136.67/139.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 136.67/139.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 136.67/139.25  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 136.69/139.36  Timeout
%------------------------------------------------------------------------------