Hi Britton,<div><br></div><div>Can you get a traceback from the seg fault?  It would help to see the line number in the autogenerated QuadTree.c where the crash happens.  Autogenerated C files produced by cython<span></span> reproduce the original .pyx files line by line as comments so it&#39;s usually pretty easy to back out where the crash is happening in the original Pyrex file.</div>
<div><br></div><div>Nathan<br><br>On Thursday, February 27, 2014, Britton Smith &lt;<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi all,<div><br></div><div>I&#39;m trying to make projections of a rather large Enzo dataset and getting a segfault somewhere in Quadtree.so.  This dataset is ~230 GB in size with 27 levels of AMR.  As far as I can tell, the only hard coded limit I could find in QuadTree.pyx is for 80 levels, which I am clearly below.  Does anyone familiar with this part of the code have any idea if there are any other hard-coded limits in here that I might be exceeding?  If not, does anyone have any advice for how I might debug this?  I&#39;m seeing this behavior in both yt-2.x and yt-3.0, so it does seem to be something intrinsic to the quadtree code.</div>

<div><br></div><div>Thanks!</div><div>Britton</div></div>
</blockquote></div>