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

View Problem - Process Solution

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

% Computer : n005.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 86.77s 88.54s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.13  % Problem  : ITP022+5 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n005.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Thu May 18 21:31:55 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 5.45/5.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.45/5.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.45/5.49  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 10.79/10.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.79/10.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.79/10.67  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 16.15/15.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.15/15.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.15/15.90  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 21.45/20.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.45/20.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.45/20.98  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 25.09/24.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.09/24.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.09/24.59  Peak sizes were: global stack 128664 kbytes, trail stack 4200 kbytes
% 30.33/30.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.33/30.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.33/30.33  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.74/35.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.74/35.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.74/35.61  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 40.42/40.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.42/40.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.42/40.10  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 45.26/45.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.26/45.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.26/45.49  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 48.35/48.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.35/48.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.35/48.99  Peak sizes were: global stack 128664 kbytes, trail stack 4200 kbytes
% 53.21/53.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.21/53.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.21/53.73  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 58.08/58.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.08/58.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.08/58.99  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 62.79/63.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.79/63.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.79/63.99  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 86.73/87.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 86.73/87.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 86.73/87.62  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 86.77/88.54  Timeout
%------------------------------------------------------------------------------