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

View Problem - Process Solution

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

% Computer : n002.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:28 EDT 2023

% Result   : Unknown 110.29s 113.48s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : ITP025+4 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n002.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 22:00:51 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 7.09/7.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.09/7.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.09/7.01  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 13.84/14.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.84/14.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.84/14.10  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 20.67/21.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.67/21.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.67/21.40  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 27.50/28.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.50/28.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.50/28.74  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 32.42/34.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.42/34.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.42/34.10  Peak sizes were: global stack 129816 kbytes, trail stack 4200 kbytes
% 39.33/41.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.33/41.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.33/41.19  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 45.72/48.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.72/48.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.72/48.02  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 52.45/54.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.45/54.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.45/54.52  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 59.44/62.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.44/62.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.44/62.01  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 64.30/67.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.30/67.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.30/67.26  Peak sizes were: global stack 129816 kbytes, trail stack 4200 kbytes
% 71.23/74.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.23/74.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.23/74.47  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 110.25/112.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 110.25/112.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 110.25/112.49  Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 110.29/113.48  Timeout
%------------------------------------------------------------------------------