From: Pavel Roskin <proski@gnu.org>
To: Lubomir Kundrak <lkundrak@redhat.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix for linker build ID in Fedora 8
Date: Mon, 26 Nov 2007 08:06:27 -0500 [thread overview]
Message-ID: <1196082387.14380.6.camel@dv> (raw)
In-Reply-To: <1196081685.26555.25.camel@localhost.localdomain>
On Mon, 2007-11-26 at 13:54 +0100, Lubomir Kundrak wrote:
> On Mon, 2007-11-26 at 07:35 -0500, Pavel Roskin wrote:
> > The objcopy test exists to detect certain breakage in objcopy. I'm not
> > sure that testing it in the condition that it only copies .text is
> > sufficient to find the original problem. Surely, that will need some
> > software archeology. The test comes from GRUB 1. Anyway, I'll rather
> > test objcopy under conditions close to those used in the build process.
>
> To be honest, I'm not completely sure either.
OK, I understand that you also want the test to pass on native x86_64.
I'll try to find more information about the original objcopy problem and
make a fix that addresses both the build ID issue and the x86_64 issue.
> > And what's the build ID for? Why do we want to keep it?
>
> It basically makes it possible to match an executable or library with
> its core dump and sources it was compiled for. The latter is achieved by
> placing the sources to build-specific directory.
Fair enough. I've been helped by Fedora's debuginfo more than once.
I understand it's OK to strip build ID from anything that is used in the
real boot (whether it's affected by the new objcopy bug or not), as we
want space saving and we cannot debug it in gdb.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-11-26 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 3:07 [PATCH] Fix for linker build ID in Fedora 8 Pavel Roskin
2007-11-25 22:26 ` Lubomir Kundrak
2007-11-26 10:28 ` Lubomir Kundrak
2007-11-26 12:35 ` Pavel Roskin
2007-11-26 12:54 ` Lubomir Kundrak
2007-11-26 13:06 ` Pavel Roskin [this message]
2007-12-12 15:45 ` Robert Millan
2007-12-14 4:33 ` Pavel Roskin
2007-12-14 5:45 ` Pavel Roskin
2007-12-14 6:10 ` Bean
2007-12-14 6:47 ` Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 7:39 Pavel Roskin
2007-11-18 6:50 ` Robert Millan
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=1196082387.14380.6.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.org \
--cc=lkundrak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.