TSTP Solution File: ITP020+5 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : ITP020+5 : TPTP v8.1.2. Bugfixed v7.5.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n004.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:23:23 EDT 2023

% Result   : Unknown 84.51s 89.63s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.10  % Problem  : ITP020+5 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.00/0.11  % Command  : nanocop.sh %s %d
% 0.10/0.31  % Computer : n004.cluster.edu
% 0.10/0.31  % Model    : x86_64 x86_64
% 0.10/0.31  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.10/0.31  % Memory   : 8042.1875MB
% 0.10/0.31  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.10/0.31  % CPULimit : 300
% 0.10/0.32  % WCLimit  : 300
% 0.10/0.32  % DateTime : Thu May 18 21:15:55 EDT 2023
% 0.10/0.32  % CPUTime  : 
% 4.87/4.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.87/4.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.87/4.94  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 10.06/10.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.06/10.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.06/10.51  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 14.87/15.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.87/15.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.87/15.30  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 19.83/20.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.83/20.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.83/20.61  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 23.13/24.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.13/24.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.13/24.23  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 27.98/29.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.98/29.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.98/29.90  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 32.69/34.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.69/34.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.69/34.99  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 37.74/40.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.74/40.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.74/40.41  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 42.50/45.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.50/45.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.50/45.34  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 45.88/49.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.88/49.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.88/49.28  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 50.72/54.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.72/54.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.72/54.70  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 55.40/59.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.40/59.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.40/59.90  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 59.97/64.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.97/64.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.97/64.84  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 84.47/89.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 84.47/89.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 84.47/89.22  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 84.51/89.63  Timeout
%------------------------------------------------------------------------------