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:49 PM, Timothy Sirk <firstname.lastname@example.org> wrote:good point, however, also valgrind is dependent on compiling with -g
> Axel is right, the debugger is really an essential tool. valgrind's memcheck
> will also catch many memory problems, with minimum effort.
to be able to tell exactly where the memory access violation happened.