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

View Problem - Process Solution

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

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

% Result   : Unknown 103.61s 105.17s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : ITP021+4 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n007.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:12:10 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 6.36/6.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.36/6.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.36/6.38  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 12.44/12.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.44/12.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.44/12.43  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 18.85/18.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.85/18.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.85/18.89  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 25.67/25.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.67/25.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.67/25.54  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 30.20/30.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.20/30.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.20/30.66  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 36.66/37.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.66/37.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.66/37.70  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 42.84/44.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.84/44.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.84/44.61  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 49.16/51.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.16/51.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.16/51.00  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 55.25/57.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.25/57.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.25/57.03  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 59.58/61.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.58/61.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.58/61.55  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 65.54/67.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.54/67.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.54/67.28  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 71.86/73.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.86/73.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.86/73.86  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 77.97/79.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.97/79.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.97/79.89  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 103.58/104.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.58/104.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.58/104.80  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 103.61/105.17  Timeout
%------------------------------------------------------------------------------