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

View Problem - Process Solution

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

% Computer : n018.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:25 EDT 2023

% Result   : Unknown 110.83s 113.55s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : ITP022+4 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n018.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:36:59 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 7.02/6.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.02/6.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.02/6.98  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 13.89/14.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.89/14.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.89/14.14  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 20.64/21.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.64/21.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.64/21.42  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 27.50/28.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.50/28.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.50/28.67  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 32.45/34.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.45/34.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.45/34.19  Peak sizes were: global stack 129816 kbytes, trail stack 4200 kbytes
% 39.30/41.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.30/41.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.30/41.23  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 46.30/48.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.30/48.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.30/48.59  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 53.23/55.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.23/55.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.23/55.78  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 60.01/62.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.01/62.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.01/62.97  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 65.09/68.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.09/68.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.09/68.57  Peak sizes were: global stack 129816 kbytes, trail stack 4200 kbytes
% 71.93/75.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.93/75.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.93/75.47  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 110.79/113.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 110.79/113.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 110.79/113.47  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 110.83/113.55  Timeout
%------------------------------------------------------------------------------