0.12/0.12	% Problem    : theBenchmark.p : TPTP v0.0.0. Released v0.0.0.
0.12/0.12	% Command    : nanocop_casc.sh %s %d
0.12/0.33	% Computer   : n007.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   : 180
0.12/0.33	% DateTime   : Thu Aug 29 17:23:12 EDT 2019
0.12/0.33	% CPUTime    : 
6.14/6.11	*** Overflow of the global/trail stack in spite of garbage collection!
6.14/6.11	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
6.14/6.11	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
12.05/12.26	*** Overflow of the global/trail stack in spite of garbage collection!
12.05/12.26	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
12.05/12.26	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
18.00/18.51	*** Overflow of the global/trail stack in spite of garbage collection!
18.00/18.51	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
18.00/18.51	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
23.89/24.67	*** Overflow of the global/trail stack in spite of garbage collection!
23.89/24.67	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
23.89/24.67	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
29.83/30.98	*** Overflow of the global/trail stack in spite of garbage collection!
29.83/30.98	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
29.83/30.98	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
35.83/37.21	*** Overflow of the global/trail stack in spite of garbage collection!
35.83/37.21	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
35.83/37.21	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
41.56/43.19	*** Overflow of the global/trail stack in spite of garbage collection!
41.56/43.19	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
41.56/43.19	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
86.42/86.93	*** Overflow of the global/trail stack in spite of garbage collection!
86.42/86.93	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
86.42/86.93	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
86.46/87.64	EOF