TSTP Solution File: HWV076+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV076+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n009.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:07 EDT 2023
% Result : Unknown 35.40s 41.90s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.13 % Problem : HWV076+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.11/0.13 % Command : nanocop.sh %s %d
% 0.12/0.35 % Computer : n009.cluster.edu
% 0.12/0.35 % Model : x86_64 x86_64
% 0.12/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.35 % Memory : 8042.1875MB
% 0.12/0.35 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.35 % CPULimit : 300
% 0.12/0.35 % WCLimit : 300
% 0.12/0.35 % DateTime : Fri May 19 03:21:03 EDT 2023
% 0.12/0.35 % CPUTime :
% 1.83/2.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.83/2.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.83/2.02 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.55/4.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.55/4.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.55/4.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.32/6.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.32/6.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.32/6.19 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.18/8.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.18/8.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.18/8.37 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.94/10.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.94/10.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.94/10.33 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.78/12.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.78/12.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.78/12.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.56/14.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.56/14.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.56/14.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.29/16.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.29/16.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.29/16.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.00/18.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.00/18.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.00/18.60 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.74/20.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.74/20.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.74/20.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.42/22.77 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.42/22.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.42/22.77 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.18/24.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.18/24.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.18/24.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.77/26.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.77/26.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.77/26.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.37/28.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.37/28.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.37/28.82 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.03/30.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.03/30.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.03/30.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.82/33.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.82/33.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.82/33.25 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.68/35.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.68/35.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.68/35.34 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.54/37.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.54/37.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.54/37.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.42/39.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.42/39.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.42/39.58 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.31/41.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.31/41.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.31/41.70 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.40/41.90 Timeout
%------------------------------------------------------------------------------