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

View Problem - Process Solution

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

% Computer : n021.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:27 EDT 2023

% Result   : Unknown 119.11s 121.05s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : ITP024+4 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n021.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 21:57:44 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 7.09/7.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.09/7.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.09/7.06  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 14.18/14.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.18/14.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.18/14.42  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 22.17/22.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.17/22.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.17/22.54  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 29.93/30.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.93/30.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.93/30.63  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 35.83/37.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.83/37.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.83/37.27  Peak sizes were: global stack 129944 kbytes, trail stack 4200 kbytes
% 43.81/45.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.81/45.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.81/45.38  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 51.11/53.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.11/53.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.11/53.12  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 58.67/60.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.67/60.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.67/60.57  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 65.81/67.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.81/67.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.81/67.51  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 71.32/73.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.32/73.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.32/73.18  Peak sizes were: global stack 129944 kbytes, trail stack 4200 kbytes
% 79.12/81.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.12/81.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.12/81.57  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 119.03/120.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 119.03/120.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 119.03/120.78  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 119.11/121.05  Timeout
%------------------------------------------------------------------------------