TSTP Solution File: HWV069+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV069+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n028.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:18:06 EDT 2023
% Result : Unknown 40.57s 42.80s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.16 % Problem : HWV069+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.03/0.17 % Command : nanocop.sh %s %d
% 0.12/0.38 % Computer : n028.cluster.edu
% 0.12/0.38 % Model : x86_64 x86_64
% 0.12/0.38 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.38 % Memory : 8042.1875MB
% 0.12/0.38 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.38 % CPULimit : 300
% 0.12/0.38 % WCLimit : 300
% 0.12/0.38 % DateTime : Fri May 19 03:45:03 EDT 2023
% 0.12/0.38 % CPUTime :
% 2.20/2.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.20/2.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.20/2.42 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 4.14/4.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.14/4.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.14/4.34 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 6.39/6.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.39/6.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.39/6.64 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 8.43/9.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.43/9.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.43/9.57 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 10.04/11.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.04/11.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.04/11.22 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 12.01/13.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.01/13.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.01/13.70 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 14.15/15.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.15/15.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.15/15.86 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 16.28/17.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.28/17.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.28/17.93 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 18.42/20.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.42/20.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.42/20.02 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 20.12/21.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.12/21.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.12/21.70 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 22.16/24.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.16/24.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.16/24.06 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 24.27/26.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.27/26.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.27/26.17 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 26.31/28.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.31/28.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.31/28.28 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 28.28/30.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.28/30.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.28/30.22 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 30.42/32.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.42/32.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.42/32.43 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 32.41/34.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.41/34.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.41/34.40 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 34.49/36.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.49/36.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.49/36.55 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 36.55/38.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 36.55/38.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.55/38.56 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 38.53/40.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 38.53/40.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.53/40.57 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 40.56/42.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 40.56/42.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.56/42.68 Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 40.57/42.79 Timeout
%------------------------------------------------------------------------------