TSTP Solution File: HWV068+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV068+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n023.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 40.17s 44.89s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : HWV068+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.13 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n023.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:42:44 EDT 2023
% 0.12/0.34 % CPUTime :
% 2.28/2.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.28/2.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.28/2.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.22/4.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.22/4.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.22/4.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.09/6.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.09/6.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.09/6.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.02/8.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.02/8.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.02/8.42 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.87/10.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.87/10.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.87/10.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.93/12.66 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.93/12.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.93/12.66 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.86/14.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.86/14.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.86/14.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.85/16.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.85/16.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.85/16.73 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.98/19.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.98/19.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.98/19.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.90/21.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.90/21.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.90/21.83 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.89/23.98 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.89/23.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.89/23.98 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.91/26.09 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.91/26.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.91/26.09 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.68/27.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.68/27.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.68/27.93 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.78/30.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.78/30.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.78/30.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.75/32.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.75/32.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.75/32.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.61/34.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.61/34.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.61/34.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.65/36.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.65/36.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.65/36.57 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.86/38.69 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.86/38.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.86/38.69 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.11/41.81 *** Overflow of the global/trail stack in spite of garbage collection!
% 38.11/41.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.11/41.81 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.07/44.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 40.07/44.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.07/44.79 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.17/44.89 Timeout
%------------------------------------------------------------------------------