TSTP Solution File: PLA044+1 by leanCoP---2.2

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : PLA044+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm  : none
% Format   : tptp:raw
% Command  : leancop_casc.sh %s %d

% Computer : n026.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  : 600s
% DateTime : Mon Jul 18 17:25:48 EDT 2022

% Result   : Unknown 52.44s 62.50s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.11  % Problem  : PLA044+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.06/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n026.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  : 600
% 0.12/0.33  % DateTime : Tue May 31 20:02:56 EDT 2022
% 0.12/0.33  % CPUTime  : 
% 1.92/2.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.92/2.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.92/2.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.75/4.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.75/4.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.75/4.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.62/6.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.62/6.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.62/6.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.31/8.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.31/8.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.31/8.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.07/10.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.07/10.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.07/10.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.84/12.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.84/12.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.84/12.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.58/14.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.58/14.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.58/14.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.29/16.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.29/16.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.29/16.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.01/18.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.01/18.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.01/18.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.77/20.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.77/20.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.77/20.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.51/22.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.51/22.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.51/22.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.25/24.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.25/24.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.25/24.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.02/26.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.02/26.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.02/26.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.72/28.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.72/28.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.72/28.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.61/31.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.61/31.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.61/31.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.59/33.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.59/33.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.59/33.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.40/35.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.40/35.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.40/35.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.73/36.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.73/36.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.73/36.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.13/38.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.13/38.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.13/38.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.86/41.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.86/41.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.86/41.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.64/43.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.64/43.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.64/43.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.38/45.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.38/45.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.38/45.49  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.17/47.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.17/47.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.17/47.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.92/49.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.92/49.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.92/49.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.68/51.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.68/51.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.68/51.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.33/53.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.33/53.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.33/53.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.16/55.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.16/55.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.16/55.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.88/57.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.88/57.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.88/57.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.64/60.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.64/60.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.64/60.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.33/62.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.33/62.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.33/62.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------