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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : ITP020+4 : TPTP v8.1.2. Bugfixed v7.5.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:23:23 EDT 2023

% Result   : Unknown 106.58s 108.20s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : ITP020+4 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n017.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 : Thu May 18 21:13:02 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.81/6.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.81/6.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.81/6.78  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 13.52/14.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.52/14.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.52/14.01  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 19.78/20.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.78/20.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.78/20.89  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 26.74/27.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.74/27.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.74/27.73  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 31.39/32.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.39/32.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.39/32.74  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 37.67/39.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.67/39.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.67/39.57  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 43.89/45.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.89/45.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.89/45.68  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 50.17/51.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.17/51.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.17/51.96  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 56.48/58.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.48/58.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.48/58.22  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 61.07/62.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.07/62.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.07/62.77  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 68.17/70.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.17/70.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.17/70.40  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 74.47/76.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.47/76.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.47/76.89  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 80.81/83.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.81/83.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.81/83.13  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 106.57/107.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 106.57/107.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.57/107.98  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 106.58/108.20  Timeout
%------------------------------------------------------------------------------