TSTP Solution File: HWV055+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV055+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n005.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:04 EDT 2023
% Result : Unknown 31.16s 41.79s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.13 % Problem : HWV055+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.14 % Command : nanocop.sh %s %d
% 0.13/0.35 % Computer : n005.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:26:23 EDT 2023
% 0.13/0.35 % CPUTime :
% 1.63/1.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.63/1.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.63/1.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.89/3.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.89/3.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.89/3.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.28/5.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.28/5.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.28/5.82 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.70/7.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.70/7.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.70/7.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.16/9.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.16/9.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.16/9.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.49/12.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.49/12.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.49/12.00 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.93/14.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.93/14.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.93/14.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.40/16.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.40/16.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.40/16.22 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.15/18.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.15/18.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.15/18.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.75/20.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.75/20.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.75/20.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.34/22.52 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.34/22.52 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.34/22.52 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.05/24.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.05/24.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.05/24.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.69/26.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.69/26.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.69/26.74 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.37/28.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.37/28.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.37/28.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.01/30.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.01/30.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.01/30.92 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.68/32.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.68/32.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.68/32.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.22/35.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.22/35.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.22/35.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.87/37.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.87/37.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.87/37.06 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.45/39.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.45/39.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.45/39.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.11/41.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.11/41.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.11/41.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.16/41.79 Timeout
%------------------------------------------------------------------------------