0.03/0.12	% Problem    : theBenchmark.p : TPTP v0.0.0. Released v0.0.0.
0.03/0.12	% Command    : nanocop_casc.sh %s %d
0.12/0.33	% Computer   : n019.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 16:10:28 EDT 2019
0.12/0.33	% CPUTime    : 
5.92/5.91	*** Overflow of the global/trail stack in spite of garbage collection!
5.92/5.91	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
5.92/5.91	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
11.90/12.30	*** Overflow of the global/trail stack in spite of garbage collection!
11.90/12.30	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
11.90/12.30	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
17.87/18.51	*** Overflow of the global/trail stack in spite of garbage collection!
17.87/18.51	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
17.87/18.51	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
23.80/24.70	*** Overflow of the global/trail stack in spite of garbage collection!
23.80/24.70	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
23.80/24.70	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
29.82/31.01	*** Overflow of the global/trail stack in spite of garbage collection!
29.82/31.01	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
29.82/31.01	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
35.80/37.17	*** Overflow of the global/trail stack in spite of garbage collection!
35.80/37.17	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
35.80/37.17	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
41.69/43.35	*** Overflow of the global/trail stack in spite of garbage collection!
41.69/43.35	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
41.69/43.35	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
86.59/86.95	*** Overflow of the global/trail stack in spite of garbage collection!
86.59/86.95	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
86.59/86.95	Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
86.69/87.61	EOF