TSTP Solution File: LAT379+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT379+4 : TPTP v8.1.2. Released v3.4.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 11:29:03 EDT 2023
% Result : Unknown 165.38s 162.31s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12 % Problem : LAT379+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.13 % Command : nanocop.sh %s %d
% 0.13/0.34 % Computer : n021.cluster.edu
% 0.13/0.34 % Model : x86_64 x86_64
% 0.13/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34 % Memory : 8042.1875MB
% 0.13/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34 % CPULimit : 300
% 0.13/0.34 % WCLimit : 300
% 0.13/0.34 % DateTime : Thu May 18 14:12:05 EDT 2023
% 0.13/0.34 % CPUTime :
% 11.91/11.69 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.91/11.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.91/11.69 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.42/22.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.42/22.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.42/22.84 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.28/34.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.28/34.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.28/34.53 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 47.07/45.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 47.07/45.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.07/45.92 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 53.71/52.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 53.71/52.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.71/52.42 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 65.00/64.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 65.00/64.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.00/64.14 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 78.95/78.16 *** Overflow of the global/trail stack in spite of garbage collection!
% 78.95/78.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.95/78.16 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 93.25/91.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 93.25/91.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.25/91.87 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 111.31/110.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 111.31/110.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 111.31/110.20 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 165.34/162.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 165.34/162.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 165.34/162.26 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 165.38/162.31 Timeout
%------------------------------------------------------------------------------