TSTP Solution File: HWV086+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV086+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n008.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:08 EDT 2023
% Result : Unknown 34.07s 41.86s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.13 % Problem : HWV086+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.03/0.14 % Command : nanocop.sh %s %d
% 0.13/0.35 % Computer : n008.cluster.edu
% 0.13/0.35 % Model : x86_64 x86_64
% 0.13/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35 % Memory : 8042.1875MB
% 0.13/0.35 % OS : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35 % CPULimit : 300
% 0.13/0.35 % WCLimit : 300
% 0.13/0.35 % DateTime : Fri May 19 03:47:09 EDT 2023
% 0.13/0.35 % CPUTime :
% 1.95/2.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.95/2.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.95/2.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.70/4.08 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.70/4.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.70/4.08 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.34/6.09 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.34/6.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.34/6.09 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.22/8.38 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.22/8.38 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.22/8.38 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.71/10.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.71/10.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.71/10.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.57/12.48 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.57/12.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.57/12.48 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.31/14.46 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.31/14.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.31/14.46 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.14/16.61 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.14/16.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.14/16.61 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.01/18.77 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.01/18.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.01/18.77 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.74/20.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.74/20.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.74/20.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.55/22.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.55/22.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.55/22.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.21/24.75 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.21/24.75 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.21/24.75 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.83/26.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.83/26.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.83/26.82 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.51/28.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.51/28.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.51/28.93 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.06/30.95 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.06/30.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.06/30.95 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.60/32.95 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.60/32.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.60/32.95 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.24/35.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.24/35.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.24/35.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.93/37.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.93/37.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.93/37.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.39/39.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.39/39.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.39/39.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.03/41.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.03/41.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.03/41.37 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.07/41.86 Timeout
%------------------------------------------------------------------------------