Re: [Valgrind-users] time-stamp of memory allocation

[Robin R. <rob...@sa...>]

willpz <zielonca <at> gmail.com> writes:

> 
> > 
> > Thank you,
> > that fixed it!
> > 
> > Robin
> > 
> > 
----------------------------------------------------------------------------
--
> > Free Next-Gen Firewall Hardware Offer
> > Buy your Sophos next-gen firewall before the end March 2013 
> > and get the hardware for free! Learn more.
> > http://p.sf.net/sfu/sophos-d2d-feb
> > 
> 
> Hi,
> 
> Could you please tell how did you solve this issue (and eventually post 
the
> patch here)? 
> 
> Willian
> 
> Rehrmann, Robin <robin.rehrmann <at> sap.com> writes:
> 
> 
----------------------------------------------------------------------------
--
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/
ostg.clktrk
> 

Hi,
I have not done it via patch. I just used vgdb:

VALGRIND=`which valgrind`
OPT="-v --tool=memcheck --leak-check=full --error-limit=no --log-file=
$LOG_FILE --undef-value-errors=no --num-callers=32 --fullpath-after=src/ --
vgdb=yes --gen-suppressions=all"

$VALGRIND $OPT <prog> &
back_pid=$!
vgdb --pid=$back_pid leak_check full definiteleak >> $log_file

Regards, 

Robin