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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CAT035+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n009.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 10:12:51 EDT 2023

% Result   : Unknown 121.35s 124.94s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CAT035+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n009.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 20:12:08 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 8.15/8.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.15/8.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.15/8.04  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 15.96/16.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.96/16.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.96/16.17  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 23.80/24.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.80/24.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.80/24.47  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 31.77/32.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.77/32.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.77/32.81  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 36.81/38.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.81/38.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.81/38.40  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 44.71/46.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.71/46.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.71/46.29  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 52.51/54.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.51/54.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.51/54.53  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 60.40/62.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.40/62.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.40/62.89  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 68.10/71.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.10/71.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.10/71.03  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 73.13/76.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.13/76.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.13/76.78  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 80.77/84.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.77/84.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.77/84.41  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 121.33/124.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 121.33/124.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 121.33/124.28  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 121.35/124.94  Timeout
%------------------------------------------------------------------------------