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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : ITP023+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:26 EDT 2023

% Result   : Unknown 83.49s 87.42s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.11  % Problem  : ITP023+5 : TPTP v8.1.2. Bugfixed v7.5.0.
% 0.11/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:31:33 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 4.77/4.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.77/4.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.77/4.82  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 9.40/9.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.40/9.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.40/9.96  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 14.14/15.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.14/15.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.14/15.26  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 18.87/20.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.87/20.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.87/20.32  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 21.87/23.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.87/23.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.87/23.98  Peak sizes were: global stack 128664 kbytes, trail stack 4200 kbytes
% 26.48/28.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.48/28.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.48/28.57  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 31.43/34.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.43/34.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.43/34.02  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 36.34/39.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.34/39.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.34/39.20  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 41.19/44.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.19/44.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.19/44.37  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 44.36/47.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.36/47.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.36/47.91  Peak sizes were: global stack 128664 kbytes, trail stack 4200 kbytes
% 49.29/52.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.29/52.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.29/52.73  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 54.25/57.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.25/57.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.25/57.91  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 59.02/62.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.02/62.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.02/62.99  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 83.37/86.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.37/86.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.37/86.90  Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 83.49/87.42  Timeout
%------------------------------------------------------------------------------