TSTP Solution File: SYO589+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : SYO589+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n023.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:13 EDT 2023
% Result : Unknown 30.58s 42.72s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12 % Problem : SYO589+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.04/0.12 % Command : nanocop.sh %s %d
% 0.12/0.33 % Computer : n023.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:46:29 EDT 2023
% 0.12/0.33 % CPUTime :
% 1.55/1.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 1.55/1.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.55/1.74 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.96/3.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.96/3.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.96/3.70 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.41/5.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 4.41/5.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.41/5.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.71/7.83 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.71/7.83 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.71/7.83 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.13/9.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 7.13/9.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.13/9.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.54/11.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.54/11.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.54/11.97 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.92/14.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.92/14.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.92/14.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.33/16.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.33/16.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.33/16.18 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.69/18.17 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.69/18.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.69/18.17 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.20/20.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.20/20.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.20/20.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.52/22.29 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.52/22.29 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.52/22.29 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.95/24.42 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.95/24.42 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.95/24.42 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.34/26.49 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.34/26.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.34/26.49 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.71/28.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.71/28.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.71/28.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.16/30.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.16/30.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.16/30.58 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.88/33.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.88/33.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.88/33.06 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.71/35.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 24.71/35.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.71/35.18 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.64/37.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 26.64/37.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.64/37.34 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.73/39.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.73/39.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.73/39.64 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.53/42.30 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.53/42.30 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.53/42.30 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.58/42.72 Timeout
%------------------------------------------------------------------------------