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

View Problem - Process Solution

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

% Computer : n012.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:38 EDT 2023

% Result   : Unknown 138.33s 139.48s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : CSR103+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n012.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:38:46 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 9.80/9.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.80/9.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.80/9.69  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 20.42/20.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.42/20.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.42/20.84  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 30.89/31.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.89/31.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.89/31.21  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 40.58/40.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.58/40.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.58/40.74  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 44.03/45.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.03/45.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.03/45.05  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 53.88/55.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.88/55.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.88/55.34  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 63.56/65.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.56/65.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.56/65.64  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 73.51/76.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.51/76.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.51/76.09  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 83.11/86.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.11/86.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.11/86.35  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 86.31/89.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 86.31/89.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 86.31/89.55  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 138.33/139.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 138.33/139.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 138.33/139.42  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 138.33/139.48  Timeout
%------------------------------------------------------------------------------