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

View Problem - Process Solution

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

% Computer : n010.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:28 EDT 2023

% Result   : Unknown 105.90s 107.03s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12  % Problem  : GRP653+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n010.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:38:05 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.53/6.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.53/6.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.53/6.51  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 12.83/12.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.83/12.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.83/12.68  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 19.16/18.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.16/18.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.16/18.86  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 25.39/24.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.39/24.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.39/24.95  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 29.40/29.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.40/29.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.40/29.05  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.47/35.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.47/35.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.47/35.12  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 44.07/43.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.07/43.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.07/43.90  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 50.76/51.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.76/51.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.76/51.20  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 56.83/57.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.83/57.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.83/57.91  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.58/61.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.58/61.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.58/61.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 66.68/68.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.68/68.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.68/68.24  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 72.97/74.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.97/74.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.97/74.73  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 78.99/80.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.99/80.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.99/80.67  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 105.88/106.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.88/106.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.88/106.91  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 105.90/107.03  Timeout
%------------------------------------------------------------------------------