<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Carolina,<div><br></div><div>SegFaults don't always mean you're running out of memory, just trying to access it incorrectly. Fortunately they are usually easy to debug. I'd suggest compiling FLASH in debug mode (by adding '-debug' to your setup line, assuming appropriate debug flags are set in the Makefile.h for your site). If the compiler doesn't catch anything, running the debug-compiled code usually does. You could also use a debugger such as gdb. If that doesn't work, I recommend going with a software called valgrind. It will find EVERY memory error in the code (there should be none...). It may already be installed on the cluster you're using.</div><div><br></div><div>Best,</div><div>Sean<br><div apple-content-edited="true">
<span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; border-collapse: separate; border-spacing: 0px; -webkit-text-decorations-in-effect: none; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br class="Apple-interchange-newline">--------------------------------------------------------</div><div>Sean M. Couch, Ph.D.</div><div>Hubble Fellow</div><div>Flash Center for Computational Science</div><div>Department of Astronomy & Astrophysics</div><div>The University of Chicago</div><div>5747 S Ellis Ave, Jo 315</div><div>Chicago, IL 60637</div><div>(773) 702-3899</div><div><a href="http://www.flash.uchicago.edu/~smc">www.flash.uchicago.edu/~smc</a></div><div><br></div></div></span></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Apr 25, 2013, at 4:36 PM, Carolina Pepe <<a href="mailto:carolina.pepe@gmail.com">carolina.pepe@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div><div><div><div>Hello all,<br><br></div>I've been working with a 1d spherical configuration of FLASH.<br></div>Now, I'm trying to read some tabulated values from a .dat file and change how certain variables are calculated. This reading is done in Driver_sourceTerms and Gravity_accelOneRow.<br>
<br></div>Besides this reading, no major changes have been done (just some little algebra with the read values).<br><br></div>However, i get this error:<br><br>mpirun noticed that process rank 0 with PID 3141 on node blackhole exited on signal 11 (Segmentation fault).<br>
<br></div>right after the first evolution step. The strangest thing of all is that it runs for certain combination of parameters (in the .par) but I get this error for some other combination. From what I've found around, it is usually related to memory issues, but since I'm running it on a powerful cluster, this shouldn't be an issue.<br>
<br></div>Should I have extra precautions when reading a file from FLASH?<br><br></div>Thanks in advance for any kind of help :)<br><br></div>Carolina<br><br></div>p.s. I added an error flag to check the opening of the file, and it opens correctly. <br>
<div><br><br></div></div>
</blockquote></div><br></div></body></html>