TSTP Solution File: LAT320+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT320+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n003.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:28:48 EDT 2023
% Result : Unknown 104.18s 106.20s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12 % Problem : LAT320+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.12 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n003.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 14:41:49 EDT 2023
% 0.12/0.34 % CPUTime :
% 6.23/6.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.23/6.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.23/6.20 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.26/12.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.26/12.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.26/12.37 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.15/18.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.15/18.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.15/18.47 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.06/24.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.06/24.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.06/24.67 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.10/29.15 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.10/29.15 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.10/29.15 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.22/35.23 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.22/35.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.22/35.23 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 40.00/41.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 40.00/41.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.00/41.17 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.94/47.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 45.94/47.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.94/47.56 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.64/53.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 51.64/53.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.64/53.54 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.51/58.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 55.51/58.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.51/58.03 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 64.47/67.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 64.47/67.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.47/67.11 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 104.12/105.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 104.12/105.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 104.12/105.87 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 104.18/106.20 Timeout
%------------------------------------------------------------------------------