Re: [Libmesh-users] memory corruption errors.

2013-12-01 Thread Roy Stogner
On Sun, 1 Dec 2013, Subramanya Sadasiva wrote: > 1. Will using a devel build help? Definitely. dbg mode turns on the internal glibcxx checks, which range from extremely slow (bounds checking on std::vector) to glacial (some of the std::map checks change the asymptotic complexity IIRC). devel mo

Re: [Libmesh-users] memory corruption errors.

2013-12-01 Thread Subramanya Sadasiva
The problem is that the error, (which shows up as a random NaN, or a sudden jump in the residual, which does not s only occurs while running in parallel on fairly large systems, after a few timesteps. Running a debug case will be painfully slow. I’ve a couple of questions. 1. Will using a deve

Re: [Libmesh-users] memory corruption errors.

2013-12-01 Thread Roy Stogner
On Sat, 30 Nov 2013, Subramanya Sadasiva wrote: > Do you guys know of any free tools that help debug memory errors in > parallel code? Essentially a free version of total-view? If you can replicate the errors on a small problem, valgrind is usable in parallel. --- Roy --

[Libmesh-users] memory corruption errors.

2013-11-30 Thread Subramanya Sadasiva
Hi, Do you guys know of any free tools that help debug memory errors in parallel code? Essentially a free version of total-view? Thanks, Subramanya -- Rapidly troubleshoot problems before they affect your business. Mo