TSTP Solution File: KRS280+1 by leanCoP---2.2
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : leanCoP---2.2
% Problem : KRS280+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : leancop_casc.sh %s %d
% Computer : n018.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 : Sun Jul 17 03:14:09 EDT 2022
% Result : Unknown 50.11s 62.44s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : KRS280+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.12 % Command : leancop_casc.sh %s %d
% 0.13/0.33 % Computer : n018.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 : 600
% 0.13/0.33 % DateTime : Tue Jun 7 07:41:50 EDT 2022
% 0.13/0.33 % CPUTime :
% 1.84/1.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.84/1.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.84/1.99 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.58/4.09 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.58/4.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.58/4.09 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.12/6.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.12/6.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.12/6.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.99/8.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.99/8.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.99/8.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.79/10.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.79/10.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.79/10.37 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.61/12.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.61/12.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.61/12.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.30/14.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.30/14.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.30/14.40 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.08/16.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.08/16.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.08/16.58 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.89/18.65 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.89/18.65 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.89/18.65 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.64/20.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.64/20.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.64/20.72 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.45/22.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.45/22.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.45/22.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.27/24.90 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.27/24.90 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.27/24.90 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.88/26.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.88/26.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.88/26.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.61/28.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.61/28.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.61/28.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.41/31.10 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.41/31.10 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.41/31.10 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.23/33.15 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.23/33.15 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.23/33.15 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.85/35.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.85/35.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.85/35.07 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.40/37.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 31.40/37.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.40/37.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.86/39.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.86/39.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.86/39.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.42/41.16 *** Overflow of the global/trail stack in spite of garbage collection!
% 34.42/41.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.42/41.16 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.05/43.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 36.05/43.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.05/43.34 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.70/45.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 37.70/45.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.70/45.45 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.27/47.36 *** Overflow of the global/trail stack in spite of garbage collection!
% 39.27/47.36 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.27/47.36 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.77/49.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 40.77/49.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.77/49.45 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.31/51.51 *** Overflow of the global/trail stack in spite of garbage collection!
% 42.31/51.51 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.31/51.51 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.91/53.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 43.91/53.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.91/53.57 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.39/55.56 *** Overflow of the global/trail stack in spite of garbage collection!
% 45.39/55.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.39/55.56 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.01/57.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 47.01/57.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.01/57.76 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.53/59.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 48.53/59.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.53/59.74 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.01/61.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 50.01/61.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.01/61.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------