Re: [Valgrind-users] Best valgrind options for finding corrupt memory

[David F. <fa...@kd...>]

On Tuesday 14 January 2014 08:03:14 Samuel Quiring wrote:
> Greetings,
> 
> I suspect my program is corrupting (overwriting) memory, e.g., malloc'ing 16
> bytes for a string that is 17 bytes when you count the nul, then copying 17
> bytes into the 16 byte area.  What are the best valgrind options for
> detecting memory corruption?

The default options :-)

(memcheck tool)

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5