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

View Problem - Process Solution

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

% Computer : n022.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 91.01s 93.85s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : ITP025+5 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n022.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:53:48 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 5.43/5.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.43/5.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.43/5.49  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 10.67/10.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.67/10.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.67/10.51  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 16.11/15.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.11/15.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.11/15.92  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 21.40/22.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.40/22.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.40/22.07  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 24.99/25.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.99/25.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.99/25.53  Peak sizes were: global stack 128792 kbytes, trail stack 4200 kbytes
% 30.25/31.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.25/31.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.25/31.36  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 35.61/36.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.61/36.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.61/36.65  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 41.01/41.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.01/41.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.01/41.86  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 46.41/48.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.41/48.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.41/48.06  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 49.93/51.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.93/51.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.93/51.42  Peak sizes were: global stack 128792 kbytes, trail stack 4200 kbytes
% 55.44/57.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.44/57.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.44/57.47  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 60.85/63.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.85/63.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.85/63.69  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 66.16/69.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.16/69.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.16/69.82  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 90.91/93.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.91/93.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.91/93.71  Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 91.01/93.85  Timeout
%------------------------------------------------------------------------------