TSTP Solution File: HWV083+1 by leanCoP---2.2

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : HWV083+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm  : none
% Format   : tptp:raw
% Command  : leancop_casc.sh %s %d

% Computer : n027.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  : 600s
% DateTime : Sat Jul 16 18:17:00 EDT 2022

% Result   : Unknown 57.77s 70.88s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.12  % Problem  : HWV083+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.08/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n027.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  : 600
% 0.12/0.33  % DateTime : Fri Jun 17 03:29:06 EDT 2022
% 0.12/0.33  % CPUTime  : 
% 1.63/1.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.63/1.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.63/1.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.12/3.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.12/3.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.12/3.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.62/5.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.62/5.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.62/5.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.09/8.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.09/8.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.09/8.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.56/10.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.56/10.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.56/10.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.04/12.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.04/12.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.04/12.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.37/14.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.37/14.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.37/14.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.43/16.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.43/16.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.43/16.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.02/21.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.02/21.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.02/21.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.34/24.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.34/24.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.34/24.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.73/27.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.73/27.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.73/27.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.04/30.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.04/30.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.04/30.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.46/33.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.46/33.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.46/33.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.84/36.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.84/36.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.84/36.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.19/39.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.19/39.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.19/39.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.67/54.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.67/54.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.67/54.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.05/56.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.05/56.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.05/56.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.45/58.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.45/58.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.45/58.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.88/60.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.88/60.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.88/60.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 51.43/62.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.43/62.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.43/62.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 53.27/65.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.27/65.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.27/65.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 57.70/69.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.70/69.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.70/69.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------