TSTP Solution File: GRP618+4 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : GRP618+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n007.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:16:18 EDT 2023

% Result   : Unknown 100.79s 106.03s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : GRP618+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n007.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:31:28 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.43/5.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.43/5.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.43/5.49  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 10.66/10.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.66/10.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.66/10.55  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 18.31/18.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.31/18.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.31/18.03  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 24.82/25.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.82/25.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.82/25.24  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 29.27/30.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.27/30.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.27/30.45  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 35.69/37.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.69/37.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.69/37.65  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 42.46/45.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.46/45.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.46/45.19  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 48.81/52.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.81/52.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.81/52.07  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 54.96/58.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.96/58.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.96/58.03  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 58.78/62.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.78/62.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.78/62.07  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 64.27/67.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.27/67.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.27/67.73  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 69.90/73.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.90/73.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.90/73.98  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 75.55/80.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 75.55/80.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 75.55/80.26  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 100.72/105.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.72/105.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.72/105.23  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 100.79/106.03  Timeout
%------------------------------------------------------------------------------