TSTP Solution File: LAT346+4 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : LAT346+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n019.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:54 EDT 2023
% Result : Unknown 142.16s 142.61s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : LAT346+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n019.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:22:35 EDT 2023
% 0.12/0.33 % CPUTime :
% 9.68/9.59 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.68/9.59 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.68/9.59 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.63/19.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.63/19.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.63/19.22 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.10/29.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.10/29.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.10/29.05 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.30/38.23 *** Overflow of the global/trail stack in spite of garbage collection!
% 38.30/38.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.30/38.23 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 44.36/44.51 *** Overflow of the global/trail stack in spite of garbage collection!
% 44.36/44.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.36/44.51 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 54.18/54.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 54.18/54.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.18/54.33 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 64.01/64.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 64.01/64.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.01/64.71 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 73.96/75.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 73.96/75.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.96/75.17 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 89.83/91.36 *** Overflow of the global/trail stack in spite of garbage collection!
% 89.83/91.36 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.83/91.36 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 142.07/141.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 142.07/141.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 142.07/141.79 Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 142.16/142.61 Timeout
%------------------------------------------------------------------------------