TSTP Solution File: HWV058+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV058+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:04 EDT 2023
% Result : Unknown 28.01s 41.80s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : HWV058+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n002.cluster.edu
% 0.12/0.33 % Model : x86_64 x86_64
% 0.12/0.33 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33 % Memory : 8042.1875MB
% 0.12/0.33 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33 % CPULimit : 300
% 0.12/0.33 % WCLimit : 300
% 0.12/0.33 % DateTime : Fri May 19 03:56:34 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.55/1.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.55/1.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.55/1.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.94/3.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.94/3.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.94/3.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.40/5.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.40/5.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.40/5.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.74/7.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.74/7.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.74/7.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.11/9.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.11/9.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.11/9.92 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.45/12.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.45/12.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.45/12.00 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.80/14.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.80/14.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.80/14.07 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.14/16.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.14/16.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.14/16.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.57/18.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.57/18.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.57/18.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.99/20.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.99/20.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.99/20.28 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.32/22.36 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.32/22.36 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.32/22.36 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.71/24.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.71/24.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.71/24.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.25/26.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.25/26.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.25/26.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.66/28.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.66/28.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.66/28.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.98/30.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.98/30.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.98/30.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.37/32.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.37/32.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.37/32.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.77/34.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.77/34.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.77/34.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.14/36.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.14/36.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.14/36.89 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.53/38.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.53/38.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.53/38.93 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.92/41.09 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.92/41.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.92/41.09 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.01/41.80 Timeout
%------------------------------------------------------------------------------