Yes- and memcheck can be noisy by producing alot of unwanted warnings. The debugger is really the best place to start. 


On Mon, May 9, 2011 at 7:54 PM, Axel Kohlmeyer <> wrote:
On Mon, May 9, 2011 at 7:49 PM, Timothy Sirk <> wrote:
> Axel is right, the debugger is really an essential tool. valgrind's memcheck
> will also catch many memory problems, with minimum effort.

good point, however, also valgrind is dependent on compiling with -g
to be able to tell exactly where the memory access violation happened.


Dr. Axel Kohlmeyer

Institute for Computational Molecular Science
Temple University, Philadelphia PA, USA.

Timothy Sirk
Army Research Laboratory
Materials & Manufacturing Science Division
Macromolecular Science & Technology Branch
RDRL-WMM-G, Bldg. 4600
Aberdeen Proving Ground, MD  21005-5069