TSTP Solution File: HWV062+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV062+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n016.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:05 EDT 2023
% Result : Unknown 38.79s 42.78s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.11 % Problem : HWV062+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.06/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n016.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 : Fri May 19 03:56:57 EDT 2023
% 0.12/0.33 % CPUTime :
% 2.04/2.23 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.04/2.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.04/2.23 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.85/4.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.85/4.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.85/4.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.70/6.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.70/6.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.70/6.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.65/8.38 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.65/8.38 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.65/8.38 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.50/10.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.50/10.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.50/10.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.43/12.63 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.43/12.63 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.43/12.63 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.49/14.66 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.49/14.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.49/14.66 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.42/16.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.42/16.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.42/16.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.17/18.63 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.17/18.63 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.17/18.63 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.95/20.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.95/20.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.95/20.64 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.84/22.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.84/22.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.84/22.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.76/24.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.76/24.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.76/24.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.66/27.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.66/27.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.66/27.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.76/29.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.76/29.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.76/29.20 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.73/31.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.73/31.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.73/31.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.72/33.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.72/33.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.72/33.31 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.73/35.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.73/35.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.73/35.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.94/37.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.94/37.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.94/37.64 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.89/40.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 36.89/40.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.89/40.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.75/42.46 *** Overflow of the global/trail stack in spite of garbage collection!
% 38.75/42.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.75/42.46 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.79/42.78 Timeout
%------------------------------------------------------------------------------