0.00/0.04	% Problem    : theBenchmark.p : TPTP v0.0.0. Released v0.0.0.
0.00/0.04	% Command    : nanocop_casc.sh %s %d
0.03/0.23	% Computer   : n002.star.cs.uiowa.edu
0.03/0.23	% Model      : x86_64 x86_64
0.03/0.23	% CPU        : Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
0.03/0.23	% Memory     : 32218.625MB
0.03/0.23	% OS         : Linux 3.10.0-693.2.2.el7.x86_64
0.03/0.23	% CPULimit   : 300
0.03/0.23	% DateTime   : Sat Jul 14 06:31:44 CDT 2018
0.03/0.23	% CPUTime    : 
8.90/8.98	*** Overflow of the global/trail stack in spite of garbage collection!
8.90/8.98	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
8.90/8.98	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
17.78/18.13	*** Overflow of the global/trail stack in spite of garbage collection!
17.78/18.13	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
17.78/18.13	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
26.77/27.33	*** Overflow of the global/trail stack in spite of garbage collection!
26.77/27.33	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
26.77/27.33	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
35.65/36.48	*** Overflow of the global/trail stack in spite of garbage collection!
35.65/36.48	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
35.65/36.48	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
44.54/45.65	*** Overflow of the global/trail stack in spite of garbage collection!
44.54/45.65	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
44.54/45.65	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
53.60/54.88	*** Overflow of the global/trail stack in spite of garbage collection!
53.60/54.88	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
53.60/54.88	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
62.51/64.02	*** Overflow of the global/trail stack in spite of garbage collection!
62.51/64.02	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
62.51/64.02	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
71.43/73.18	*** Overflow of the global/trail stack in spite of garbage collection!
71.43/73.18	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
71.43/73.18	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
80.31/82.35	*** Overflow of the global/trail stack in spite of garbage collection!
80.31/82.35	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
80.31/82.35	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
89.19/91.53	*** Overflow of the global/trail stack in spite of garbage collection!
89.19/91.53	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
89.19/91.53	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
98.21/100.68	*** Overflow of the global/trail stack in spite of garbage collection!
98.21/100.68	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
98.21/100.68	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
132.14/134.39	*** Overflow of the global/trail stack in spite of garbage collection!
132.14/134.39	You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
132.14/134.39	Peak sizes were: global stack 127048 kbytes, trail stack 4152 kbytes
132.22/134.83	EOF