TSTP Solution File: PLA038+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : PLA038+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 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:47:00 EDT 2023
% Result : Unknown 34.64s 44.82s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.13 % Problem : PLA038+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.14/0.13 % Command : nanocop.sh %s %d
% 0.14/0.35 % Computer : n019.cluster.edu
% 0.14/0.35 % Model : x86_64 x86_64
% 0.14/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35 % Memory : 8042.1875MB
% 0.14/0.35 % OS : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35 % CPULimit : 300
% 0.14/0.35 % WCLimit : 300
% 0.14/0.35 % DateTime : Thu May 18 20:45:27 EDT 2023
% 0.21/0.35 % CPUTime :
% 1.78/1.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.78/1.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.78/1.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.44/3.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.44/3.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.44/3.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.94/5.98 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.94/5.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.94/5.98 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.56/8.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.56/8.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.56/8.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.91/9.91 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.91/9.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.91/9.91 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.52/12.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.52/12.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.52/12.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.13/14.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.13/14.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.13/14.28 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.70/16.38 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.70/16.38 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.70/16.38 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.26/18.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.26/18.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.26/18.37 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.65/20.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.65/20.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.65/20.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.19/22.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.19/22.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.19/22.57 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.85/24.61 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.85/24.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.85/24.61 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.36/26.63 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.36/26.63 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.36/26.63 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.94/28.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.94/28.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.94/28.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.54/30.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 23.54/30.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.54/30.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.38/33.16 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.38/33.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.38/33.16 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.27/35.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.27/35.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.27/35.28 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.74/37.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.74/37.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.74/37.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.26/41.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.26/41.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.26/41.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.57/43.94 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.57/43.94 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.57/43.94 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.64/44.82 Timeout
%------------------------------------------------------------------------------