TSTP Solution File: SYO597+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SYO597+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n010.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 12:38:14 EDT 2023
% Result : Unknown 30.13s 41.77s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12 % Problem : SYO597+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.10/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n010.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 18:23:27 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.67/1.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.67/1.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.67/1.82 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.18/3.89 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.18/3.89 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.18/3.89 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.75/5.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.75/5.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.75/5.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.25/7.96 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.25/7.96 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.25/7.96 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.81/10.10 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.81/10.10 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.81/10.10 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.30/12.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.30/12.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.30/12.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.80/14.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.80/14.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.80/14.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.25/16.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.25/16.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.25/16.25 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.75/18.31 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.75/18.31 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.75/18.31 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.15/20.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.15/20.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.15/20.37 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.83/22.62 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.83/22.62 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.83/22.62 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.32/24.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.32/24.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.32/24.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.83/26.61 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.83/26.61 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.83/26.61 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.25/28.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.25/28.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.25/28.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.75/30.72 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.75/30.72 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.75/30.72 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.15/32.78 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.15/32.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.15/32.78 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.61/34.87 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.61/34.87 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.61/34.87 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.19/37.02 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.19/37.02 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.19/37.02 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.60/39.00 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.60/39.00 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.60/39.00 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.07/41.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.07/41.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.07/41.07 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.13/41.77 Timeout
%------------------------------------------------------------------------------