<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">No, not intentionally, we don't touch threads.<div><br><div><div>On Mar 21, 2013, at 7:45 PM, Jed Brown <<a href="mailto:jedbrown@mcs.anl.gov">jedbrown@mcs.anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Did you enable threadcomm? I better finish this work I started and get my branch out there...</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 21, 2013 at 6:42 PM, Mark F. Adams <span dir="ltr"><<a href="mailto:mark.adams@columbia.edu" target="_blank">mark.adams@columbia.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm getting segv in at the end of runs on the Cray XC30. in optimized builds it segv with a stack like<br>
<br>
PetscFinalize<br>
PetscViewerASCIIGetStdout<br>
PetscCommDuplicate<br>
PetscThreadCommGetRank<br>
<br>
In debug builds it does not segv but there are a bunch of un freeded memory in ThreadComm stuff.<br>
<span class="HOEnZb"><font color="#888888"><br>
Mark</font></span></blockquote></div><br></div>
</blockquote></div><br></div></body></html>