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

View Problem - Process Solution

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

% Computer : n003.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 29.53s 41.68s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : PLA037+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n003.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 20:48:15 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 1.81/1.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.81/1.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.81/1.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.38/3.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.38/3.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.38/3.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.77/5.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.77/5.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.77/5.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.15/7.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.15/7.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.15/7.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.66/10.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.66/10.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.66/10.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.22/12.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.22/12.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.22/12.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.63/14.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.63/14.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.63/14.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.14/16.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.14/16.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.14/16.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.60/18.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.60/18.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.60/18.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.94/20.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.94/20.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.94/20.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.50/22.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.50/22.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.50/22.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.94/24.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.94/24.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.94/24.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.32/26.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.32/26.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.32/26.49  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.77/28.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.77/28.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.77/28.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.20/30.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.20/30.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.20/30.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.69/32.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.69/32.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.69/32.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.09/34.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.09/34.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.09/34.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.59/36.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.59/36.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.59/36.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.03/38.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.03/38.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.03/38.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.49/41.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.49/41.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.49/41.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.53/41.68  Timeout
%------------------------------------------------------------------------------