TSTP Solution File: HWV065+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV065+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n021.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 30.73s 42.10s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.17 % Problem : HWV065+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.04/0.17 % Command : nanocop.sh %s %d
% 0.14/0.39 % Computer : n021.cluster.edu
% 0.14/0.39 % Model : x86_64 x86_64
% 0.14/0.39 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.39 % Memory : 8042.1875MB
% 0.14/0.39 % OS : Linux 3.10.0-693.el7.x86_64
% 0.14/0.39 % CPULimit : 300
% 0.14/0.39 % WCLimit : 300
% 0.14/0.39 % DateTime : Fri May 19 03:36:27 EDT 2023
% 0.14/0.39 % CPUTime :
% 1.76/1.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.76/1.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.76/1.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.35/3.94 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.35/3.94 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.35/3.94 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.83/6.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.83/6.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.83/6.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.44/8.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.44/8.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.44/8.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.91/10.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.91/10.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.91/10.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.56/12.35 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.56/12.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.56/12.35 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.09/14.32 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.09/14.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.09/14.32 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.62/16.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.62/16.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.62/16.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.18/18.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.18/18.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.18/18.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.67/20.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.67/20.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.67/20.57 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.26/22.69 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.26/22.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.26/22.69 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.76/24.75 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.76/24.75 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.76/24.75 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.22/26.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.22/26.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.22/26.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.83/28.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.83/28.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.83/28.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.28/30.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.28/30.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.28/30.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.75/33.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.75/33.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.75/33.05 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.20/35.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.20/35.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.20/35.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.68/37.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.68/37.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.68/37.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.18/39.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.18/39.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.18/39.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.70/41.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.70/41.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.70/41.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.73/42.10 Timeout
%------------------------------------------------------------------------------