0.08/0.14	% Problem    : theBenchmark.p : TPTP v0.0.0. Released v0.0.0.
0.08/0.14	% Command    : nanocop_casc.sh %s %d
0.15/0.35	% Computer   : n009.cluster.edu
0.15/0.35	% Model      : x86_64 x86_64
0.15/0.35	% CPU        : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
0.15/0.35	% Memory     : 8042.1875MB
0.15/0.35	% OS         : Linux 3.10.0-693.el7.x86_64
0.15/0.36	% CPULimit   : 180
0.15/0.36	% DateTime   : Thu Aug 29 17:36:32 EDT 2019
0.15/0.36	% CPUTime    : 
6.53/6.57	*** Overflow of the global/trail stack in spite of garbage collection!
6.53/6.57	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
6.53/6.57	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
12.91/12.71	*** Overflow of the global/trail stack in spite of garbage collection!
12.91/12.71	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
12.91/12.71	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
19.06/18.71	*** Overflow of the global/trail stack in spite of garbage collection!
19.06/18.71	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
19.06/18.71	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
25.20/24.96	*** Overflow of the global/trail stack in spite of garbage collection!
25.20/24.96	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
25.20/24.96	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
31.64/31.47	*** Overflow of the global/trail stack in spite of garbage collection!
31.64/31.47	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
31.64/31.47	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
38.02/37.62	*** Overflow of the global/trail stack in spite of garbage collection!
38.02/37.62	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
38.02/37.62	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
44.48/43.94	*** Overflow of the global/trail stack in spite of garbage collection!
44.48/43.94	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
44.48/43.94	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
89.34/87.02	*** Overflow of the global/trail stack in spite of garbage collection!
89.34/87.02	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
89.34/87.02	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
89.48/87.70	EOF