TSTP Solution File: HWV082+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV082+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n002.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 38.86s 41.83s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.13/0.14 % Problem : HWV082+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.13/0.14 % Command : nanocop.sh %s %d
% 0.14/0.36 % Computer : n002.cluster.edu
% 0.14/0.36 % Model : x86_64 x86_64
% 0.14/0.36 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.36 % Memory : 8042.1875MB
% 0.14/0.36 % OS : Linux 3.10.0-693.el7.x86_64
% 0.14/0.36 % CPULimit : 300
% 0.14/0.36 % WCLimit : 300
% 0.14/0.36 % DateTime : Fri May 19 03:55:34 EDT 2023
% 0.14/0.36 % CPUTime :
% 2.26/2.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.26/2.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.26/2.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.07/4.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.07/4.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.07/4.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.06/6.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.06/6.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.06/6.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.88/8.41 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.88/8.41 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.88/8.41 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.07/10.69 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.07/10.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.07/10.69 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.92/12.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.92/12.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.92/12.56 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.03/14.81 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.03/14.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.03/14.81 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.84/16.61 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.84/16.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.84/16.61 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.88/18.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.88/18.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.88/18.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.83/20.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.83/20.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.83/20.89 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.78/22.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.78/22.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.78/22.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.68/25.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.68/25.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.68/25.00 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.59/27.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.59/27.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.59/27.12 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.55/29.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.55/29.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.55/29.22 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.33/31.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.33/31.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.33/31.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.24/33.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.24/33.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.24/33.22 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.07/35.29 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.07/35.29 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.07/35.29 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.00/37.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.00/37.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.00/37.42 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.99/39.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 36.99/39.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.99/39.57 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.83/41.51 *** Overflow of the global/trail stack in spite of garbage collection!
% 38.83/41.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.83/41.51 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.86/41.83 Timeout
%------------------------------------------------------------------------------