TSTP Solution File: LAT374+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT374+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n001.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 162.30s 160.08s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12 % Problem : LAT374+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n001.cluster.edu
% 0.12/0.33 % Model : x86_64 x86_64
% 0.12/0.33 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33 % Memory : 8042.1875MB
% 0.12/0.33 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33 % CPULimit : 300
% 0.12/0.33 % WCLimit : 300
% 0.12/0.33 % DateTime : Thu May 18 14:45:12 EDT 2023
% 0.12/0.34 % CPUTime :
% 11.95/11.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.95/11.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.95/11.70 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.71/23.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.71/23.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.71/23.11 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.56/34.52 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.56/34.52 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.56/34.52 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 47.42/46.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 47.42/46.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.42/46.04 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 54.44/53.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 54.44/53.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.44/53.70 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 66.18/65.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 66.18/65.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.18/65.58 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 77.60/76.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 77.60/76.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.60/76.74 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 91.33/90.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 91.33/90.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 91.33/90.37 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 109.14/107.77 *** Overflow of the global/trail stack in spite of garbage collection!
% 109.14/107.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 109.14/107.77 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 162.27/159.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 162.27/159.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 162.27/159.30 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 162.30/160.08 Timeout
%------------------------------------------------------------------------------