TSTP Solution File: LAT301+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT301+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:43 EDT 2023
% Result : Unknown 105.03s 111.21s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12 % Problem : LAT301+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/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:17:34 EDT 2023
% 0.12/0.34 % CPUTime :
% 7.02/7.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.02/7.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.02/7.01 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 14.08/14.35 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.08/14.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.08/14.35 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 21.09/21.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.09/21.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.09/21.60 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.13/28.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.13/28.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.13/28.85 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 33.05/34.10 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.05/34.10 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.05/34.10 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 39.56/40.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 39.56/40.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.56/40.78 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.31/47.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 45.31/47.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.31/47.21 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 50.87/53.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 50.87/53.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.87/53.33 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 56.54/59.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 56.54/59.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.54/59.65 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 60.33/64.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 60.33/64.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.33/64.06 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 65.89/69.94 *** Overflow of the global/trail stack in spite of garbage collection!
% 65.89/69.94 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.89/69.94 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 71.41/76.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 71.41/76.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.41/76.13 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 76.97/82.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 76.97/82.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.97/82.30 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 104.95/110.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 104.95/110.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 104.95/110.17 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 105.03/111.21 Timeout
%------------------------------------------------------------------------------