[gentoo-user] What does it take to get debug symbols from /lib/ld-2.9.so?

[gentoo-user] What does it take to get debug symbols from /lib/ld-2.9.so?

[Erik]

I have emerged glibc with "debug -glibc-omitfp" and restarted the
system. But when I execute "valgrind /usr/lib/mozilla-firefox/firefox" I
only see things like this:
Invalid read of size 4
   at 0x4018620: (within /lib/ld-2.9.so)

No filename:linenumber here. What does it take to get debug symbols from
/lib/ld-2.9.so?

[gentoo-user] Re: What does it take to get debug symbols from /lib/ld-2.9.so?

[Nikos Chantziaras]

On 09/06/2009 09:43 AM, Erik wrote:
> I have emerged glibc with "debug -glibc-omitfp" and restarted the
> system. But when I execute "valgrind /usr/lib/mozilla-firefox/firefox" I
> only see things like this:
> Invalid read of size 4
>     at 0x4018620: (within /lib/ld-2.9.so)
>
> No filename:linenumber here. What does it take to get debug symbols from
> /lib/ld-2.9.so?

Don't emerge with "debug -glibc-omitfp".  Emerge with "splitdebug" in 
FEATURES.

See http://www.gentoo.org/proj/en/qa/backtraces.xml (scroll down to 
where splitdebug is described).

Re: [gentoo-user] Re: What does it take to get debug symbols from /lib/ld-2.9.so?

[Graham Murray]

Nikos Chantziaras <realnc@arcor.de> writes:

> Don't emerge with "debug -glibc-omitfp".  Emerge with "splitdebug" in
> FEATURES.

And make sure you include a -g option (eg -ggdb) in CFLAGS

Re: [gentoo-user] Re: What does it take to get debug symbols from /lib/ld-2.9.so?

[Erik]

Nikos Chantziaras skrev:
> On 09/06/2009 09:43 AM, Erik wrote:
>> I have emerged glibc with "debug -glibc-omitfp" and restarted the
>> system. But when I execute "valgrind /usr/lib/mozilla-firefox/firefox" I
>> only see things like this:
>> Invalid read of size 4
>>     at 0x4018620: (within /lib/ld-2.9.so)
>>
>> No filename:linenumber here. What does it take to get debug symbols from
>> /lib/ld-2.9.so?
>
> Don't emerge with "debug -glibc-omitfp".  Emerge with "splitdebug" in
> FEATURES.
Done:
Conditional jump or move depends on uninitialised value(s)
   at 0x400C0AC: _dl_relocate_object (in /lib/ld-2.9.so)

Now it at least shows the function name. But still no
filename:linenumber. Maybe I need "debug" for that after all?

[gentoo-user] Re: What does it take to get debug symbols from /lib/ld-2.9.so?

[Nikos Chantziaras]

On 09/06/2009 11:22 AM, Erik wrote:
> Nikos Chantziaras skrev:
>> On 09/06/2009 09:43 AM, Erik wrote:
>>> I have emerged glibc with "debug -glibc-omitfp" and restarted the
>>> system. But when I execute "valgrind /usr/lib/mozilla-firefox/firefox" I
>>> only see things like this:
>>> Invalid read of size 4
>>>      at 0x4018620: (within /lib/ld-2.9.so)
>>>
>>> No filename:linenumber here. What does it take to get debug symbols from
>>> /lib/ld-2.9.so?
>>
>> Don't emerge with "debug -glibc-omitfp".  Emerge with "splitdebug" in
>> FEATURES.
> Done:
> Conditional jump or move depends on uninitialised value(s)
>     at 0x400C0AC: _dl_relocate_object (in /lib/ld-2.9.so)
>
> Now it at least shows the function name. But still no
> filename:linenumber. Maybe I need "debug" for that after all?

Just "-g" in CFLAGS.

Re: [gentoo-user] Re: What does it take to get debug symbols from /lib/ld-2.9.so?

[Erik]

Nikos Chantziaras skrev:
> On 09/06/2009 11:22 AM, Erik wrote:
>> Nikos Chantziaras skrev:
>>> On 09/06/2009 09:43 AM, Erik wrote:
>>>> I have emerged glibc with "debug -glibc-omitfp" and restarted the
>>>> system. But when I execute "valgrind
>>>> /usr/lib/mozilla-firefox/firefox" I
>>>> only see things like this:
>>>> Invalid read of size 4
>>>>      at 0x4018620: (within /lib/ld-2.9.so)
>>>>
>>>> No filename:linenumber here. What does it take to get debug symbols
>>>> from
>>>> /lib/ld-2.9.so?
>>>
>>> Don't emerge with "debug -glibc-omitfp".  Emerge with "splitdebug" in
>>> FEATURES.
>> Done:
>> Conditional jump or move depends on uninitialised value(s)
>>     at 0x400C0AC: _dl_relocate_object (in /lib/ld-2.9.so)
>>
>> Now it at least shows the function name. But still no
>> filename:linenumber. Maybe I need "debug" for that after all?
>
> Just "-g" in CFLAGS.

Ok, I added this to /etc/portage/env/sys-libs/glibc-2.9_p20081201-r2:
pre_pkg_setup() {
         if ! hasq -g $CFLAGS ; then
                  elog "Adding -g to CFLAGS for $PN-$PV to locate errors
reported by Valgrind."
                  CFLAGS="$CFLAGS -g"
         fi
}


Then I emerged glibc. It printed the elog message that I added and
included -g in the compile commands. Then I restarted the system. But
still no filename:linenumber in Valgrind.