TSTP Solution File: LAT375+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT375+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n007.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:02 EDT 2023
% Result : Unknown 159.67s 157.08s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12 % Problem : LAT375+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n007.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:24:31 EDT 2023
% 0.12/0.34 % CPUTime :
% 11.78/11.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.78/11.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.78/11.55 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.78/23.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.78/23.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.78/23.25 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.56/35.52 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.56/35.52 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.56/35.52 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 47.38/47.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 47.38/47.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.38/47.00 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 54.13/53.50 *** Overflow of the global/trail stack in spite of garbage collection!
% 54.13/53.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.13/53.50 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 65.42/65.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 65.42/65.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.42/65.12 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 77.14/76.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 77.14/76.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.14/76.99 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 88.84/88.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 88.84/88.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.84/88.37 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 105.64/104.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 105.64/104.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.64/104.64 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 159.62/156.95 *** Overflow of the global/trail stack in spite of garbage collection!
% 159.62/156.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 159.62/156.95 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 159.67/157.08 Timeout
%------------------------------------------------------------------------------