TSTP Solution File: PLA042+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : PLA042+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n011.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:47:00 EDT 2023
% Result : Unknown 31.30s 41.87s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12 % Problem : PLA042+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.03/0.13 % Command : nanocop.sh %s %d
% 0.12/0.34 % Computer : n011.cluster.edu
% 0.12/0.34 % Model : x86_64 x86_64
% 0.12/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34 % Memory : 8042.1875MB
% 0.12/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34 % CPULimit : 300
% 0.12/0.34 % WCLimit : 300
% 0.12/0.34 % DateTime : Thu May 18 20:44:18 EDT 2023
% 0.12/0.34 % CPUTime :
% 1.77/1.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.77/1.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.77/1.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.35/3.91 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.35/3.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.35/3.91 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.96/6.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.96/6.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.96/6.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.51/8.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.51/8.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.51/8.07 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.77/9.81 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.77/9.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.77/9.81 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.37/12.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.37/12.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.37/12.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.89/14.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.89/14.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.89/14.28 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.55/16.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.55/16.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.55/16.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.11/18.44 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.11/18.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.11/18.44 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.32/20.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.32/20.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.32/20.19 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.96/22.62 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.96/22.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.96/22.62 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.57/24.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.57/24.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.57/24.72 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.12/26.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.12/26.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.12/26.74 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.80/28.92 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.80/28.92 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.80/28.92 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.37/30.88 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.37/30.88 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.37/30.88 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.97/33.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.97/33.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.97/33.00 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.50/35.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.50/35.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.50/35.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.13/37.15 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.13/37.15 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.13/37.15 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.70/39.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.70/39.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.70/39.19 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.26/41.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.26/41.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.26/41.31 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.30/41.87 Timeout
%------------------------------------------------------------------------------