TSTP Solution File: SEU411+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SEU411+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n011.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:27 EDT 2023
% Result : Unknown 192.89s 186.04s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12 % Problem : SEU411+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n011.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 13:19:44 EDT 2023
% 0.12/0.33 % CPUTime :
% 14.85/14.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.85/14.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.85/14.53 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 30.09/29.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.09/29.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.09/29.45 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 45.55/45.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 45.55/45.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.55/45.25 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 69.09/68.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 69.09/68.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.09/68.56 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 84.05/83.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 84.05/83.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 84.05/83.24 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 99.08/97.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 99.08/97.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.08/97.73 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 114.14/112.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 114.14/112.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 114.14/112.27 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 132.11/129.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 132.11/129.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 132.11/129.56 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 192.83/185.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 192.83/185.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 192.83/185.33 Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 192.89/186.04 Timeout
%------------------------------------------------------------------------------