TSTP Solution File: LAT363+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT363+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n002.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:59 EDT 2023
% Result : Unknown 160.62s 158.15s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : LAT363+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13 % Command : nanocop.sh %s %d
% 0.13/0.34 % Computer : n002.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:44:42 EDT 2023
% 0.13/0.34 % CPUTime :
% 11.91/11.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.91/11.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.91/11.67 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 23.98/23.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.98/23.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.98/23.34 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 35.80/35.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.80/35.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.80/35.64 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 47.54/47.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 47.54/47.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.54/47.89 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 54.53/54.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 54.53/54.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.53/54.79 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 66.36/66.69 *** Overflow of the global/trail stack in spite of garbage collection!
% 66.36/66.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.36/66.69 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 78.09/78.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 78.09/78.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.09/78.11 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 89.88/89.48 *** Overflow of the global/trail stack in spite of garbage collection!
% 89.88/89.48 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.88/89.48 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 106.59/105.69 *** Overflow of the global/trail stack in spite of garbage collection!
% 106.59/105.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 106.59/105.69 Peak sizes were: global stack 128536 kbytes, trail stack 4200 kbytes
% 160.57/158.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 160.57/158.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 160.57/158.05 Peak sizes were: global stack 128408 kbytes, trail stack 4200 kbytes
% 160.62/158.15 Timeout
%------------------------------------------------------------------------------