TSTP Solution File: HWV056+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV056+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n008.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 31.23s 41.74s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12 % Problem : HWV056+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.11/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n008.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:43:39 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.68/1.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.68/1.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.68/1.82 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.26/3.91 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.26/3.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.26/3.91 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.72/5.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.72/5.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.72/5.92 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.22/8.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.22/8.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.22/8.00 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.73/10.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.73/10.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.73/10.02 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.19/12.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.19/12.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.19/12.12 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.79/14.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.79/14.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.79/14.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.29/16.35 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.29/16.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.29/16.35 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.80/18.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.80/18.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.80/18.31 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.33/20.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.33/20.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.33/20.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.76/22.46 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.76/22.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.76/22.46 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.17/24.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.17/24.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.17/24.45 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.77/26.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.77/26.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.77/26.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.27/28.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.27/28.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.27/28.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.61/30.62 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.61/30.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.61/30.62 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.29/32.98 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.29/32.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.29/32.98 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.12/35.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.12/35.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.12/35.22 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.74/37.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.74/37.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.74/37.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.49/39.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.49/39.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.49/39.25 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.15/41.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.15/41.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.15/41.31 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.23/41.74 Timeout
%------------------------------------------------------------------------------