TSTP Solution File: HWV061+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV061+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n023.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 55.08s 61.50s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12 % Problem : HWV061+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.03/0.13 % Command : nanocop.sh %s %d
% 0.13/0.34 % Computer : n023.cluster.edu
% 0.13/0.34 % Model : x86_64 x86_64
% 0.13/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34 % Memory : 8042.1875MB
% 0.13/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34 % CPULimit : 300
% 0.13/0.34 % WCLimit : 300
% 0.13/0.34 % DateTime : Fri May 19 03:46:43 EDT 2023
% 0.13/0.34 % CPUTime :
% 3.05/3.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.05/3.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.05/3.13 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 5.90/6.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.90/6.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.90/6.26 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 8.91/9.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.91/9.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.91/9.40 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 11.86/12.51 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.86/12.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.86/12.51 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 13.98/14.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.98/14.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.98/14.85 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 16.83/17.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.83/17.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.83/17.65 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 19.68/20.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.68/20.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.68/20.67 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 22.72/24.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.72/24.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.72/24.05 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 25.72/27.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.72/27.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.72/27.02 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 27.85/29.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.85/29.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.85/29.39 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 30.76/33.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.76/33.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.76/33.19 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 33.75/36.35 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.75/36.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.75/36.35 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 36.59/39.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 36.59/39.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.59/39.40 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 39.52/42.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 39.52/42.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.52/42.54 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 42.16/45.32 *** Overflow of the global/trail stack in spite of garbage collection!
% 42.16/45.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.16/45.32 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 44.73/48.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 44.73/48.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.73/48.47 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 47.37/51.51 *** Overflow of the global/trail stack in spite of garbage collection!
% 47.37/51.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.37/51.51 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 49.89/54.63 *** Overflow of the global/trail stack in spite of garbage collection!
% 49.89/54.63 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.89/54.63 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 52.49/57.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 52.49/57.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.49/57.78 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 55.07/60.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 55.07/60.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.07/60.80 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 55.08/61.50 Timeout
%------------------------------------------------------------------------------