TSTP Solution File: SYO598+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SYO598+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n006.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:15 EDT 2023
% Result : Unknown 30.19s 41.74s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.11 % Problem : SYO598+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n006.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:18:06 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.70/1.86 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.70/1.86 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.70/1.86 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.20/3.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.20/3.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.20/3.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.84/6.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.84/6.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.84/6.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.37/8.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.37/8.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.37/8.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.84/10.03 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.84/10.03 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.84/10.03 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.31/12.11 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.31/12.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.31/12.11 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.82/14.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 10.82/14.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.82/14.19 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.38/16.27 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.38/16.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.38/16.27 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.91/18.32 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.91/18.32 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.91/18.32 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.34/20.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.34/20.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.34/20.37 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.83/22.44 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.83/22.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.83/22.44 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.34/24.53 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.34/24.53 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.34/24.53 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.78/26.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.78/26.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.78/26.58 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.31/28.71 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.31/28.71 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.31/28.71 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.79/30.69 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.79/30.69 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.79/30.69 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.25/32.77 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.25/32.77 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.25/32.77 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.75/34.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 25.75/34.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.75/34.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.21/36.91 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.21/36.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.21/36.91 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.62/38.98 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.62/38.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.62/38.98 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.08/41.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.08/41.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.08/41.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.19/41.74 Timeout
%------------------------------------------------------------------------------