TSTP Solution File: HWV064+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV064+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n010.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 47.92s 60.45s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.11 % Problem : HWV064+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.13/0.12 % Command : nanocop.sh %s %d
% 0.14/0.33 % Computer : n010.cluster.edu
% 0.14/0.33 % Model : x86_64 x86_64
% 0.14/0.33 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.33 % Memory : 8042.1875MB
% 0.14/0.33 % OS : Linux 3.10.0-693.el7.x86_64
% 0.14/0.33 % CPULimit : 300
% 0.14/0.33 % WCLimit : 300
% 0.14/0.33 % DateTime : Fri May 19 03:20:41 EDT 2023
% 0.14/0.33 % CPUTime :
% 2.52/2.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.52/2.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.52/2.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.96/5.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.96/5.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.96/5.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.50/9.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.50/9.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.50/9.02 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.88/11.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.88/11.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.88/11.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.81/14.62 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.81/14.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.81/14.62 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.27/17.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.27/17.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.27/17.18 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.61/20.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.61/20.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.61/20.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.93/23.23 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.93/23.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.93/23.23 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.37/26.52 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.37/26.52 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.37/26.52 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.29/29.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.29/29.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.29/29.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.53/31.49 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.53/31.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.53/31.49 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.08/34.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.08/34.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.08/34.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.81/38.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.81/38.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.81/38.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.23/41.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.23/41.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.23/41.00 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.82/44.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.82/44.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.82/44.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.34/47.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 38.34/47.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.34/47.33 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.78/50.36 *** Overflow of the global/trail stack in spite of garbage collection!
% 40.78/50.36 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.78/50.36 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.25/53.44 *** Overflow of the global/trail stack in spite of garbage collection!
% 43.25/53.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.25/53.44 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.58/56.46 *** Overflow of the global/trail stack in spite of garbage collection!
% 45.58/56.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.58/56.46 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.83/59.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 47.83/59.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.83/59.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.92/60.45 Timeout
%------------------------------------------------------------------------------