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

View Problem - Process Solution

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

% Computer : n013.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:21 EDT 2023

% Result   : Unknown 93.31s 94.63s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : GRP630+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n013.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Fri May 19 01:57:11 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 5.43/5.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.43/5.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.43/5.44  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 10.62/10.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.62/10.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.62/10.55  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 15.93/15.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.93/15.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.93/15.79  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 21.19/20.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.19/20.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.19/20.98  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 24.66/24.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.66/24.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.66/24.39  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 30.20/30.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.20/30.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.20/30.40  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 35.29/36.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.29/36.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.29/36.36  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 40.70/41.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.70/41.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.70/41.79  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 45.99/47.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.99/47.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.99/47.82  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 49.48/51.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.48/51.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.48/51.35  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.68/57.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.68/57.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.68/57.14  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 59.99/62.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.99/62.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.99/62.39  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 65.33/67.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.33/67.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.33/67.62  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 93.28/94.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.28/94.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.28/94.58  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 93.31/94.63  Timeout
%------------------------------------------------------------------------------