TSTP Solution File: HWV070+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV070+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n011.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 32.66s 41.84s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : HWV070+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.13 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n011.cluster.edu
% 0.12/0.34 % Model : x86_64 x86_64
% 0.12/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34 % Memory : 8042.1875MB
% 0.12/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34 % CPULimit : 300
% 0.12/0.34 % WCLimit : 300
% 0.12/0.34 % DateTime : Fri May 19 03:34:03 EDT 2023
% 0.12/0.34 % CPUTime :
% 1.84/2.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.84/2.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.84/2.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.51/4.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.51/4.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.51/4.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.17/6.08 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.17/6.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.17/6.08 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.78/8.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.78/8.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.78/8.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.42/10.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.42/10.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.42/10.19 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.10/12.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.10/12.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.10/12.28 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.66/14.36 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.66/14.36 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.66/14.36 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.35/16.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.35/16.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.35/16.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.90/18.50 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.90/18.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.90/18.50 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.63/20.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.63/20.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.63/20.60 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.32/22.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.32/22.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.32/22.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.98/24.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.98/24.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.98/24.73 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.59/26.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.59/26.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.59/26.79 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.18/28.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.18/28.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.18/28.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.83/30.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.83/30.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.83/30.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.46/33.08 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.46/33.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.46/33.08 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.97/34.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.97/34.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.97/34.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.51/37.09 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.51/37.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.51/37.09 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.05/39.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.05/39.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.05/39.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.59/41.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.59/41.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.59/41.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.66/41.84 Timeout
%------------------------------------------------------------------------------