No, not intentionally, we don't touch threads. On Mar 21, 2013, at 7:45 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> Did you enable threadcomm? I better finish this work I started and get my > branch out there... > > > On Thu, Mar 21, 2013 at 6:42 PM, Mark F. Adams <mark.adams at columbia.edu> > wrote: > I'm getting segv in at the end of runs on the Cray XC30. in optimized builds > it segv with a stack like > > PetscFinalize > PetscViewerASCIIGetStdout > PetscCommDuplicate > PetscThreadCommGetRank > > In debug builds it does not segv but there are a bunch of un freeded memory > in ThreadComm stuff. > > Mark > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130321/1a059396/attachment.html>
