TSTP Solution File: HWV083+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV083+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n004.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:08 EDT 2023
% Result : Unknown 33.10s 41.96s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12 % Problem : HWV083+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.03/0.13 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n004.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:31:09 EDT 2023
% 0.12/0.34 % CPUTime :
% 1.68/1.81 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.68/1.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.68/1.81 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.22/3.94 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.22/3.94 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.22/3.94 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.04/6.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.04/6.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.04/6.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.94/8.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.94/8.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.94/8.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.46/10.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.46/10.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.46/10.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.32/12.49 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.32/12.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.32/12.49 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.92/14.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.92/14.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.92/14.33 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.64/16.48 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.64/16.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.64/16.48 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.34/18.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.34/18.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.34/18.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.02/20.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.02/20.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.02/20.56 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.62/22.63 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.62/22.63 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.62/22.63 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.35/24.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.35/24.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.35/24.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.87/26.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.87/26.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.87/26.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.55/29.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.55/29.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.55/29.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.16/30.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.16/30.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.16/30.89 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.67/32.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.67/32.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.67/32.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.27/35.09 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.27/35.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.27/35.09 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.82/37.16 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.82/37.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.82/37.16 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.46/39.36 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.46/39.36 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.46/39.36 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.07/41.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.07/41.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.07/41.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.10/41.96 Timeout
%------------------------------------------------------------------------------