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

[Leif W. <lei...@gm...>]

I like --leak-check=full --track-origins=yes and sometimes --db-attach=yes
if I want to jump in with gdb when the error hits.


On Tue, Jan 14, 2014 at 11:04 AM, David Faure <fa...@kd...> wrote:

> 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
>
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>



-- 
Cheers,
Leif