TSTP Solution File: PLA034+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : PLA034+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n032.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:46:59 EDT 2023
% Result : Unknown 30.00s 41.55s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.09 % Problem : PLA034+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.00/0.09 % Command : nanocop.sh %s %d
% 0.09/0.28 % Computer : n032.cluster.edu
% 0.09/0.28 % Model : x86_64 x86_64
% 0.09/0.28 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.09/0.28 % Memory : 8042.1875MB
% 0.09/0.28 % OS : Linux 3.10.0-693.el7.x86_64
% 0.09/0.28 % CPULimit : 300
% 0.09/0.28 % WCLimit : 300
% 0.09/0.28 % DateTime : Thu May 18 20:45:34 EDT 2023
% 0.09/0.28 % CPUTime :
% 1.69/1.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.69/1.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.69/1.85 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.23/3.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.23/3.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.23/3.82 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.62/5.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.62/5.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.62/5.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.07/7.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.07/7.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.07/7.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.66/9.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.66/9.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.66/9.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.11/11.98 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.11/11.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.11/11.98 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.53/14.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.53/14.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.53/14.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.08/16.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.08/16.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.08/16.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.57/18.21 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.57/18.21 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.57/18.21 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.01/20.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.01/20.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.01/20.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.39/22.28 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.39/22.28 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.39/22.28 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.08/24.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.08/24.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.08/24.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.51/26.46 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.51/26.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.51/26.46 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.03/28.49 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.03/28.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.03/28.49 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.54/30.62 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.54/30.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.54/30.62 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.01/32.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.01/32.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.01/32.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.53/34.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.53/34.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.53/34.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.02/36.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.02/36.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.02/36.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.54/38.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.54/38.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.54/38.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.90/40.80 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.90/40.80 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.90/40.80 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.00/41.55 Timeout
%------------------------------------------------------------------------------