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

View Problem - Process Solution

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

% Computer : n012.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:24 EDT 2023

% Result   : Unknown 103.03s 102.92s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12  % Problem  : GRP638+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n012.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:50:37 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.19/6.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.19/6.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.19/6.24  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 12.49/12.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.49/12.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.49/12.56  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 18.72/18.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.72/18.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.72/18.74  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 25.07/25.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.07/25.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.07/25.11  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 29.25/29.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.25/29.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.25/29.22  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.78/35.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.78/35.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.78/35.61  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 42.11/42.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.11/42.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.11/42.71  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 48.41/48.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.41/48.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.41/48.82  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 54.53/54.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.53/54.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.53/54.91  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 58.47/59.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.47/59.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.47/59.08  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 64.58/65.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.58/65.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.58/65.26  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 71.03/71.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.03/71.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.03/71.71  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 77.16/77.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.16/77.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.16/77.74  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 103.01/102.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.01/102.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.01/102.86  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 103.03/102.92  Timeout
%------------------------------------------------------------------------------