TSTP Solution File: SEV435+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SEV435+1 : TPTP v8.1.2. Released v6.3.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n021.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:07:38 EDT 2023
% Result : Unknown 213.67s 210.29s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12 % Problem : SEV435+1 : TPTP v8.1.2. Released v6.3.0.
% 0.11/0.13 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n021.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:52:08 EDT 2023
% 0.12/0.34 % CPUTime :
% 19.20/18.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.20/18.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.20/18.67 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 37.82/36.90 *** Overflow of the global/trail stack in spite of garbage collection!
% 37.82/36.90 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.82/36.90 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 56.24/55.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 56.24/55.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.24/55.47 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 81.53/80.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 81.53/80.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.53/80.56 Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 100.02/99.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 100.02/99.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.02/99.12 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 119.13/118.50 *** Overflow of the global/trail stack in spite of garbage collection!
% 119.13/118.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 119.13/118.50 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 153.73/152.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 153.73/152.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 153.73/152.00 Peak sizes were: global stack 129688 kbytes, trail stack 4200 kbytes
% 213.62/209.48 *** Overflow of the global/trail stack in spite of garbage collection!
% 213.62/209.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 213.62/209.48 Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 213.67/210.29 Timeout
%------------------------------------------------------------------------------