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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : GRP645+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:26 EDT 2023

% Result   : Unknown 105.37s 105.30s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : GRP645+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.11/0.33  % Computer : n010.cluster.edu
% 0.11/0.33  % Model    : x86_64 x86_64
% 0.11/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.33  % Memory   : 8042.1875MB
% 0.11/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.33  % CPULimit : 300
% 0.11/0.33  % WCLimit  : 300
% 0.11/0.33  % DateTime : Fri May 19 01:40:34 EDT 2023
% 0.11/0.33  % CPUTime  : 
% 7.41/7.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.41/7.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.41/7.40  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 14.72/14.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.72/14.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.72/14.66  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 20.71/20.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.71/20.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.71/20.57  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 26.78/26.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.78/26.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.78/26.86  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 30.96/31.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.96/31.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.96/31.27  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 37.26/37.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.26/37.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.26/37.43  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 43.34/43.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.34/43.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.34/43.42  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 49.53/49.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.53/49.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.53/49.83  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 55.85/56.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.85/56.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.85/56.09  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.07/60.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.07/60.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.07/60.33  Peak sizes were: global stack 127384 kbytes, trail stack 4200 kbytes
% 66.31/66.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.31/66.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.31/66.34  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 72.58/72.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.58/72.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.58/72.62  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 105.29/104.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.29/104.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.29/104.30  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 105.37/105.30  Timeout
%------------------------------------------------------------------------------