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

View Problem - Process Solution

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

% Computer : n017.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.71s 41.70s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : PLA041+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n017.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Thu May 18 20:12:15 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 1.90/2.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.90/2.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.90/2.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.73/4.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.73/4.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.73/4.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.31/6.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.31/6.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.31/6.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.04/8.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.04/8.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.04/8.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.63/10.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.63/10.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.63/10.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.24/12.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.24/12.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.24/12.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.85/14.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.85/14.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.85/14.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.43/16.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.43/16.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.43/16.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.02/18.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.02/18.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.02/18.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.47/20.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.47/20.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.47/20.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.03/22.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.03/22.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.03/22.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.73/24.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.73/24.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.73/24.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.42/26.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.42/26.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.42/26.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.04/28.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.04/28.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.04/28.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.61/30.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.61/30.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.61/30.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.15/32.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.15/32.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.15/32.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.82/35.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.82/35.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.82/35.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.53/37.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.53/37.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.53/37.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.09/39.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.09/39.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.09/39.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.69/41.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.69/41.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.69/41.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.71/41.70  Timeout
%------------------------------------------------------------------------------