TSTP Solution File: PLA043+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : PLA043+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n029.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:01 EDT 2023
% Result : Unknown 34.57s 41.82s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.11 % Problem : PLA043+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.10/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n029.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 21:00:13 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.86/2.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.86/2.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.86/2.05 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.51/3.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.51/3.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.51/3.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.26/6.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.26/6.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.26/6.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.93/8.13 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.93/8.13 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.93/8.13 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.59/10.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.59/10.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.59/10.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.27/12.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.27/12.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.27/12.34 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.85/14.39 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.85/14.39 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.85/14.39 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.64/16.50 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.64/16.50 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.64/16.50 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.41/18.68 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.41/18.68 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.41/18.68 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.22/20.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.22/20.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.22/20.70 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.96/22.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.96/22.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.96/22.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.81/24.94 *** Overflow of the global/trail stack in spite of garbage collection!
% 20.81/24.94 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.81/24.94 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.53/26.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.53/26.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.53/26.89 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.25/28.91 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.25/28.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.25/28.91 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.90/30.98 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.90/30.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.90/30.98 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.63/33.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.63/33.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.63/33.12 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.40/35.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.40/35.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.40/35.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.03/37.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.03/37.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.03/37.18 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.78/39.32 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.78/39.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.78/39.32 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.54/41.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.54/41.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.54/41.45 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.57/41.82 Timeout
%------------------------------------------------------------------------------