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

View Problem - Process Solution

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

% Computer : n023.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 38.94s 44.91s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : PLA044+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n023.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:01:44 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 1.82/1.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.82/1.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.82/1.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.04/3.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.04/3.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.04/3.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.53/5.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.53/5.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.53/5.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.09/7.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.09/7.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.09/7.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.51/9.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.51/9.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.51/9.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.17/12.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.17/12.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.17/12.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.69/14.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.69/14.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.69/14.22  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.41/16.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.41/16.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.41/16.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.47/18.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.47/18.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.47/18.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.95/21.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.95/21.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.95/21.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.09/24.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.09/24.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.09/24.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.00/26.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.00/26.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.00/26.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.84/29.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.84/29.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.84/29.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.75/31.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.75/31.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.75/31.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.63/33.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.63/33.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.63/33.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.70/35.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.70/35.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.70/35.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.79/37.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.79/37.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.79/37.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.84/40.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.84/40.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.84/40.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.92/42.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.92/42.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.92/42.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.84/44.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.84/44.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.84/44.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.94/44.91  Timeout
%------------------------------------------------------------------------------