public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] unstrip: Add --force to force combining files when ELF headers don't match.
Date: Tue, 03 Jun 2014 13:53:47 +0200	[thread overview]
Message-ID: <1401796427.4030.104.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 1401221101.4106.75.camel@bordewijk.wildebeest.org

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

On Tue, 2014-05-27 at 22:05 +0200, Mark Wielaard wrote:
> Updated patch attached.
>
> commit 22497096e8759b7c73233f2c2f9adff9d2db9ce7
> Author: Mark Wielaard <mjw@redhat.com>
> Date:   Mon May 26 21:28:05 2014 +0200
> 
>     unstrip: Add --force to force combining files when ELF headers don't match.
>     
>     Older versions of GNU binutils strip would drop some ELF header flags.
>     Causing the main ELF file and the separate .debug file to have mismatched
>     ELF header fields. Unfortunately some distros are still shipping such files.
>     eu-unstrip doesn't want to recombine such files. Add a more explicit
>     explanation which fields don't match and provide a --force, -F flag to
>     force combining such files anyway (producing a warning).
>     
>     https://bugzilla.redhat.com/show_bug.cgi?id=698005
>     https://bugzilla.redhat.com/show_bug.cgi?id=806474
>     
>     Signed-off-by: Mark Wielaard <mjw@redhat.com>

I pushed this variant to master.


             reply	other threads:[~2014-06-03 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 11:53 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-27 20:05 Mark Wielaard
2014-05-26 20:15 Mark Wielaard

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=1401796427.4030.104.camel@bordewijk.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).