From: Tristan Gingold <gingold@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regression on prelinked-sepdebug-shlibs
Date: Mon, 04 Jan 2010 11:54:00 -0000 [thread overview]
Message-ID: <6B2A3106-D0C5-454A-AB03-C7A7D5F19475@adacore.com> (raw)
In-Reply-To: <20100104102317.GA27009@host0.dyn.jankratochvil.net>
On Jan 4, 2010, at 11:23 AM, Jan Kratochvil wrote:
> On Mon, 04 Jan 2010 10:50:49 +0100, Tristan Gingold wrote:
>> my understanding is that separate debug info and its binary file have the
>> same ordering of sections, or to be more precise, the separate debug info
>> only appends new debug sections to the binary file while making content
>> sections empty.
>
> $ rpm -V bash bash-debuginfo; rpm -qf /bin/bash /usr/lib/debug/bin/bash.debug
> bash-4.0.35-2.fc12.x86_64
> bash-debuginfo-4.0.35-2.fc12.x86_64
[...]
Ok, looks like we can't assume that they have identical sections: objcopy looks unable to keep
ELF specific sections.
>
>> Also, if you look at symfile.c:reread_separate_symbols (before my patch),
>> there was this code:
>
> OK, so reread_separate_symbols was wrong. This rereading code needs
> a rewrite - to unify it with the common loading code.
Unification is already done (was part of my patch).
>> BTW, where can I find prelink ? Looks like it is not available on RHEL S 5.2
>
> It has been always provided in RHELs, Fedoras etc.:
Thanks. /usr/sbin was not in my path.
>> The main drawback of addr-table is that is it much slower.
>
> IMO this kind of performance difference is negligible to be considered.
> It is some overhead per-section while now GDB has many overheads per-symbol.
Ok, maybe we can use addr-table instead. I am not a big fan of this approach but we may improve this later.
Thanks,
Tristan.
next prev parent reply other threads:[~2010-01-04 11:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 20:05 Jan Kratochvil
2010-01-04 9:50 ` Tristan Gingold
2010-01-04 10:24 ` Jan Kratochvil
2010-01-04 11:54 ` Tristan Gingold [this message]
2010-01-04 15:22 ` Tristan Gingold
2010-01-04 18:10 ` Jan Kratochvil
2010-01-05 11:02 ` Tristan Gingold
2010-01-05 16:15 ` Jan Kratochvil
2010-01-06 11:20 ` Tristan Gingold
2010-01-06 16:38 ` Tristan Gingold
2010-01-06 18:05 ` Jan Kratochvil
2010-01-06 19:16 ` Daniel Jacobowitz
2010-01-07 11:02 ` Tristan Gingold
2010-01-07 11:10 ` Jan Kratochvil
2010-01-07 11:18 ` Tristan Gingold
2010-01-07 13:42 ` Daniel Jacobowitz
2010-01-07 14:21 ` Tristan Gingold
2010-01-07 14:26 ` Daniel Jacobowitz
2010-01-07 14:37 ` Tristan Gingold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6B2A3106-D0C5-454A-AB03-C7A7D5F19475@adacore.com \
--to=gingold@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox