TSTP Solution File: LAT319+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT319+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n010.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:48 EDT 2023
% Result : Unknown 106.32s 111.12s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12 % Problem : LAT319+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12 % Command : nanocop.sh %s %d
% 0.12/0.35 % Computer : n010.cluster.edu
% 0.12/0.35 % Model : x86_64 x86_64
% 0.12/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.35 % Memory : 8042.1875MB
% 0.12/0.35 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.35 % CPULimit : 300
% 0.12/0.35 % WCLimit : 300
% 0.12/0.35 % DateTime : Thu May 18 14:23:46 EDT 2023
% 0.12/0.35 % CPUTime :
% 6.58/6.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.58/6.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.58/6.58 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 13.26/14.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.26/14.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.26/14.00 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 20.09/21.36 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.09/21.36 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.09/21.36 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 25.71/27.48 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.71/27.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.71/27.48 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 29.47/31.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.47/31.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.47/31.93 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.96/37.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.96/37.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.96/37.71 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 41.52/44.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 41.52/44.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.52/44.96 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 49.65/53.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 49.65/53.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.65/53.71 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 56.73/61.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 56.73/61.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.73/61.02 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 61.32/65.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 61.32/65.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.32/65.83 Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 68.27/73.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 68.27/73.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.27/73.24 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 106.29/110.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 106.29/110.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.29/110.39 Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 106.32/111.12 Timeout
%------------------------------------------------------------------------------