TSTP Solution File: HWV074+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV074+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n022.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:07 EDT 2023
% Result : Unknown 34.17s 42.02s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.22 % Problem : HWV074+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.11/0.23 % Command : nanocop.sh %s %d
% 0.12/0.49 % Computer : n022.cluster.edu
% 0.12/0.49 % Model : x86_64 x86_64
% 0.12/0.49 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.49 % Memory : 8042.1875MB
% 0.12/0.49 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.49 % CPULimit : 300
% 0.12/0.50 % WCLimit : 300
% 0.12/0.50 % DateTime : Fri May 19 03:43:47 EDT 2023
% 0.12/0.50 % CPUTime :
% 1.82/2.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.82/2.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.82/2.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.40/4.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.40/4.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.40/4.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.05/6.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.05/6.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.05/6.20 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.70/8.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.70/8.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.70/8.31 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.25/10.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.25/10.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.25/10.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.02/12.59 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.02/12.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.02/12.59 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.75/14.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.75/14.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.75/14.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.40/16.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.40/16.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.40/16.64 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.06/18.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.06/18.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.06/18.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.85/20.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.85/20.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.85/20.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.53/22.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.53/22.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.53/22.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.31/25.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.31/25.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.31/25.05 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.03/27.08 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.03/27.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.03/27.08 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.80/29.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.80/29.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.80/29.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.61/31.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.61/31.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.61/31.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.32/33.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.32/33.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.32/33.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.92/35.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.92/35.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.92/35.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.70/37.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.70/37.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.70/37.45 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.49/39.59 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.49/39.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.49/39.59 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.09/41.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.09/41.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.09/41.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.17/42.02 Timeout
%------------------------------------------------------------------------------