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

View Problem - Process Solution

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

% Computer : n012.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:18 EDT 2023

% Result   : Unknown 70.30s 74.98s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12  % Problem  : ITP015+5 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.10/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n012.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:41:18 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 3.85/3.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.85/3.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.85/3.92  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 7.78/8.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.78/8.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.78/8.29  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 11.65/12.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.65/12.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.65/12.33  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 15.44/16.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.44/16.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.44/16.44  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 18.27/19.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.27/19.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.27/19.61  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 22.23/23.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.23/23.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.23/23.83  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 25.98/27.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.98/27.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.98/27.78  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 29.82/32.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.82/32.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.82/32.00  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 33.77/36.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.77/36.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.77/36.26  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 36.63/39.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.63/39.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.63/39.40  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 40.40/43.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.40/43.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.40/43.37  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 43.81/47.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.81/47.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.81/47.12  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 47.19/51.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.19/51.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.19/51.27  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 70.25/74.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.25/74.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.25/74.24  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 70.30/74.98  Timeout
%------------------------------------------------------------------------------