TSTP Solution File: HWV067+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV067+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n006.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 49.32s 60.43s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.11 % Problem : HWV067+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n006.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:37:06 EDT 2023
% 0.12/0.33 % CPUTime :
% 2.62/2.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.62/2.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.62/2.72 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 5.10/5.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.10/5.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.10/5.87 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 7.58/8.90 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.58/8.90 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.58/8.90 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 10.16/12.10 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.16/12.10 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.16/12.10 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 12.00/14.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.00/14.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.00/14.57 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 14.47/17.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.47/17.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.47/17.20 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 17.11/20.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.11/20.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.11/20.42 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 19.61/23.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.61/23.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.61/23.45 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 22.02/26.50 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.02/26.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.02/26.50 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 23.97/29.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.97/29.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.97/29.12 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 26.58/31.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.58/31.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.58/31.89 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 29.25/35.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.25/35.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.25/35.00 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 32.04/38.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.04/38.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.04/38.25 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 34.47/41.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.47/41.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.47/41.05 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 36.95/44.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 36.95/44.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.95/44.07 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 39.36/47.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 39.36/47.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.36/47.19 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 41.78/50.29 *** Overflow of the global/trail stack in spite of garbage collection!
% 41.78/50.29 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.78/50.29 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 44.32/53.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 44.32/53.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.32/53.53 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 46.80/56.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 46.80/56.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.80/56.58 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 49.30/59.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 49.30/59.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.30/59.65 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 49.32/60.42 Timeout
%------------------------------------------------------------------------------