> > ------------------------------ > > Message: 5 > Date: Thu, 14 Mar 2013 11:49:06 -0700 > From: Randall Mackie <rlmackie862 at gmail.com> > To: PETSc users list <petsc-users at mcs.anl.gov> > Subject: Re: [petsc-users] possible error > Message-ID: <BE1D9C27-B333-423F-BB61-7519A7F7910D at gmail.com> > Content-Type: text/plain; charset=us-ascii > > Nachiket, > > I've run into a similar situation before, where my code ran fine in debug > mode, bombed out with segmentation violation > in optimize mode, and yet I couldn't find anything in valgrind. In my case, I > eventually tracked it down to some variable > not being broadcast to all processors, and so that variable would often take > some weird value on some processor. > I tracked it down by putting in a goto statement (that would go to the end of > the code and PetscFinalize) early in my code, > and if it ran fine, then I'd move the goto statement down further in the > code, and then keep moving it > until the program bombed, and this helped me track it down the issue. Also, > if you run on just 1 processor do you see the same > behavior? > > Randy M.
Hi Randy, Thanks for your message. I see the same behavior on one processor. I'm upgrading gcc right now; if that does not fix it - I will try to track it down using your method. -Nachiket
