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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : GRP634+4 : TPTP v8.1.2. Released v3.4.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:16:22 EDT 2023

% Result   : Unknown 98.64s 100.91s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : GRP634+4 : TPTP v8.1.2. Released v3.4.0.
% 0.13/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n017.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:16:38 EDT 2023
% 0.13/0.33  % CPUTime  : 
% 5.38/5.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.38/5.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.38/5.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 10.82/10.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.82/10.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.82/10.70  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 16.34/16.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.34/16.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.34/16.98  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 21.72/23.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.72/23.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.72/23.14  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.03/28.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.03/28.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.03/28.28  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 35.61/33.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.61/33.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.61/33.60  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 41.14/39.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.14/39.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.14/39.78  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 46.67/46.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.67/46.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.67/46.08  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 52.39/52.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.39/52.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.39/52.42  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 56.12/56.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.12/56.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.12/56.78  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 61.92/62.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.92/62.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.92/62.88  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 67.76/69.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.76/69.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.76/69.11  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 73.62/75.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.62/75.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.62/75.45  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.59/99.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 98.59/99.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 98.59/99.91  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 98.64/100.91  Timeout
%------------------------------------------------------------------------------