Re: [Valgrind-users] Any way to see the memory address of leaked elements?

[Rainer G. <rge...@gm...>]

sorry for bringing up this old thread again. I am once more stuck with
a situation where I would need to know the memory address of the
leaked item. I have just looked at the valgrind code, but have not
found where exactly the "loss record" message (in text case) is being
generated. I would deeply appreciate if someone could point me what I
need to change in order to have valgrind display the address.

Thanks,
Rainer

On Wed, Dec 1, 2010 at 7:44 PM, Michael Smith <ms...@xi...> wrote:
> As far as I know, there's no way to do that.
>
> Last time I wanted this, I hacked it into my local copy of valgrind
> (actually just tracking a single address, and printing out one - even
> when multiple copies were leaked). Unfortunately, I've since lost that
> patch. Fortunately, it was really simple - so doing something like
> that yourself shouldn't be hard.
>
> Mike
>
>
> On Wed, Dec 1, 2010 at 6:56 AM, Rainer Gerhards <rge...@gm...> wrote:
>> Hi all,
>>
>> I am trying to find a well-hidden memory leak. To do so, it would be
>> immensely useful to know the memory addresses of the leaked objects.
>> Is there any way I can tell valgrind to show the addresses in its
>> memory leak output (just like it does e.g. on access violations)?
>>
>> Thanks,
>> Rainer
>>
>> ------------------------------------------------------------------------------
>> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
>> Tap into the largest installed PC base & get more eyes on your game by
>> optimizing for Intel(R) Graphics Technology. Get started today with the
>> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
>> http://p.sf.net/sfu/intelisp-dev2dev
>> _______________________________________________
>> Valgrind-users mailing list
>> Val...@li...
>> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>>
>