TSTP Solution File: HWV075+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV075+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n007.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:07 EDT 2023
% Result : Unknown 28.21s 41.81s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12 % Problem : HWV075+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.04/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n007.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:17:53 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.50/1.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.50/1.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.50/1.68 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.91/3.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.91/3.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.91/3.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.22/5.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.22/5.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.22/5.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.58/7.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.58/7.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.58/7.83 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.96/9.91 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.96/9.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.96/9.91 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.33/11.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.33/11.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.33/11.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.77/14.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.77/14.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.77/14.14 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.21/16.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.21/16.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.21/16.20 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.49/18.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.49/18.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.49/18.19 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.83/20.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.83/20.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.83/20.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.29/22.38 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.29/22.38 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.29/22.38 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.73/24.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.73/24.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.73/24.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.23/26.66 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.23/26.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.23/26.66 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.63/28.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.63/28.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.63/28.68 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.17/30.77 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.17/30.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.17/30.77 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.62/32.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.62/32.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.62/32.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.01/34.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.01/34.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.01/34.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.46/36.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.46/36.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.46/36.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.79/38.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.79/38.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.79/38.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.19/41.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.19/41.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.19/41.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.21/41.81 Timeout
%------------------------------------------------------------------------------