TSTP Solution File: SEU438+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SEU438+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n010.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:04:38 EDT 2023
% Result : Unknown 207.97s 202.63s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12 % Problem : SEU438+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.13 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n010.cluster.edu
% 0.12/0.34 % Model : x86_64 x86_64
% 0.12/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34 % Memory : 8042.1875MB
% 0.12/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34 % CPULimit : 300
% 0.12/0.34 % WCLimit : 300
% 0.12/0.34 % DateTime : Thu May 18 13:00:22 EDT 2023
% 0.12/0.34 % CPUTime :
% 17.96/17.48 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.96/17.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.96/17.48 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 36.03/35.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 36.03/35.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.03/35.34 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 53.72/52.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 53.72/52.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.72/52.65 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 78.23/76.75 *** Overflow of the global/trail stack in spite of garbage collection!
% 78.23/76.75 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.23/76.75 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 95.34/93.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 95.34/93.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.34/93.57 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 113.21/110.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 113.21/110.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 113.21/110.89 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 147.77/144.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 147.77/144.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 147.77/144.47 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 207.86/202.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 207.86/202.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 207.86/202.17 Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 207.97/202.63 Timeout
%------------------------------------------------------------------------------