TSTP Solution File: LAT373+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT373+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n006.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 157.54s 155.84s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12 % Problem : LAT373+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n006.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:32:00 EDT 2023
% 0.12/0.34 % CPUTime :
% 11.68/11.46 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.68/11.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.68/11.46 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.17/22.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.17/22.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.17/22.83 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 34.74/34.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.74/34.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.74/34.21 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 46.12/45.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 46.12/45.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.12/45.47 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 53.03/52.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 53.03/52.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.03/52.54 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 64.37/64.14 *** Overflow of the global/trail stack in spite of garbage collection!
% 64.37/64.14 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.37/64.14 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 76.05/75.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 76.05/75.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.05/75.76 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 87.42/86.94 *** Overflow of the global/trail stack in spite of garbage collection!
% 87.42/86.94 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 87.42/86.94 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 104.10/103.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 104.10/103.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 104.10/103.42 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 157.48/155.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 157.48/155.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 157.48/155.22 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 157.54/155.84 Timeout
%------------------------------------------------------------------------------