TSTP Solution File: HWV066+1 by leanCoP---2.2
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : leanCoP---2.2
% Problem : HWV066+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : leancop_casc.sh %s %d
% Computer : n026.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:16:52 EDT 2022
% Result : Unknown 49.01s 62.53s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.11 % Problem : HWV066+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.03/0.12 % Command : leancop_casc.sh %s %d
% 0.12/0.33 % Computer : n026.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 09:37:23 EDT 2022
% 0.12/0.33 % CPUTime :
% 1.76/1.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.76/1.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.76/1.92 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.39/3.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.39/3.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.39/3.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.93/5.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.93/5.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.93/5.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.64/8.15 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.64/8.15 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.64/8.15 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.23/10.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.23/10.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.23/10.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.92/12.32 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.92/12.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.92/12.32 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.55/14.38 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.55/14.38 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.55/14.38 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.24/16.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.24/16.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.24/16.42 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.92/18.52 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.92/18.52 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.92/18.52 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.54/20.59 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.54/20.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.54/20.59 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.23/22.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.23/22.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.23/22.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.95/24.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.95/24.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.95/24.72 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.66/26.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.66/26.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.66/26.83 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.29/28.88 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.29/28.88 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.29/28.88 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.97/30.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.97/30.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.97/30.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.63/33.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.63/33.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.63/33.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.30/35.49 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.30/35.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.30/35.49 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.65/36.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.65/36.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.65/36.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.00/38.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.00/38.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.00/38.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.65/41.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.65/41.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.65/41.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.33/43.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.33/43.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.33/43.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.93/45.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.93/45.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.93/45.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.67/47.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 37.67/47.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.67/47.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.35/49.59 *** Overflow of the global/trail stack in spite of garbage collection!
% 39.35/49.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.35/49.59 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.96/51.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 40.96/51.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.96/51.68 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.56/53.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 42.56/53.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.56/53.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.21/55.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 44.21/55.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.21/55.72 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.75/57.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 45.75/57.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.75/57.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.32/59.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 47.32/59.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.32/59.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.92/61.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 48.92/61.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.92/61.93 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------