This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Valgrinding ld.so
- From: Guillaume Berard <berardgui at gmail dot com>
- To: "Carlos O'Donell" <carlos at systemhalted dot org>
- Cc: "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Mon, 9 Sep 2013 21:53:41 +0200
- Subject: Re: Valgrinding ld.so
- Authentication-results: sourceware.org; auth=none
- References: <CAJ3=_kiQePCM8TP_W9GL-KjVZo936m1TjiXEzw8gxLhPpc5wGA at mail dot gmail dot com> <CAE2sS1hv5oGsWMfn6HXwpMP0=4k3z0n2x60E4OgcQ71k0Z_m+A at mail dot gmail dot com>
Worked like a charm.
Thanks a lot.
On Mon, Sep 9, 2013 at 9:48 PM, Carlos O'Donell <carlos@systemhalted.org> wrote:
> On Mon, Sep 9, 2013 at 3:36 PM, Guillaume Berard <berardgui@gmail.com> wrote:
>> I was wondering if there is a way to valgrind ld.so.
>> I cloned glibc source and built my own ld.so with a leak (one malloc,
>> no free) with --dynamic-linker, but valgrind does not show any
>> errors... Does someone know if there is particular settings to give to
>> valgrind to profile ld.so code?
>
> It should work to run it directly on the dynamic loader? Does it?
>
> e.g. valgrind /path/to/build/elf/ld.so --library-path
> /path/to/build:/path/to/build/elf ./application
>
> Cheers,
> Carlos.