TSTP Solution File: PLA040+1 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : PLA040+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n021.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 32.03s 41.88s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12  % Problem  : PLA040+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.04/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n021.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:42:42 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 1.70/1.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.70/1.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.70/1.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.57/4.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.57/4.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.57/4.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.20/6.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.20/6.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.20/6.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.87/8.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.87/8.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.87/8.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.34/10.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.34/10.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.34/10.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.90/12.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.90/12.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.90/12.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.44/14.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.44/14.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.44/14.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.91/16.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.91/16.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.91/16.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.61/18.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.61/18.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.61/18.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.26/20.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.26/20.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.26/20.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.77/22.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.77/22.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.77/22.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.25/24.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.25/24.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.25/24.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.79/26.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.79/26.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.79/26.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.35/28.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.35/28.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.35/28.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.86/30.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.86/30.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.86/30.86  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.46/33.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.46/33.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.46/33.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.10/35.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.10/35.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.10/35.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.73/37.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.73/37.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.73/37.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.44/39.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.44/39.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.44/39.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.99/41.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.99/41.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.99/41.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.03/41.88  Timeout
%------------------------------------------------------------------------------