TSTP Solution File: SEU431+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SEU431+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n017.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 12:03:35 EDT 2023
% Result : Unknown 215.71s 211.86s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.09/0.12 % Problem : SEU431+4 : TPTP v8.1.2. Released v3.4.0.
% 0.09/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n017.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 : Thu May 18 12:32:55 EDT 2023
% 0.12/0.33 % CPUTime :
% 17.78/17.32 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.78/17.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.78/17.32 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 35.37/34.91 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.37/34.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.37/34.91 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 52.64/52.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 52.64/52.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.64/52.13 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 80.60/79.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 80.60/79.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.60/79.14 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 102.35/101.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 102.35/101.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.35/101.00 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 121.86/120.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 121.86/120.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 121.86/120.65 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 156.33/154.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 156.33/154.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 156.33/154.65 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 215.61/211.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 215.61/211.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 215.61/211.78 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 215.71/211.86 Timeout
%------------------------------------------------------------------------------