public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24251] Allocatable section after non-allocatable ones
Date: Thu, 17 Sep 2020 15:51:02 +0000	[thread overview]
Message-ID: <bug-24251-11298-EH8ewRvLU7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24251-11298@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24251

--- Comment #14 from Mark Wielaard <mark at klomp dot org> ---
Created attachment 12847
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12847&action=edit
boottime-debug

(In reply to Tom de Vries from comment #13)
> (In reply to Jan Kratochvil from comment #10)
> > FYI even dwz-0.13 which already contains this patch still shows:
> > 
> > dwz: Allocatable section in
> > ./usr/bin/boottime-0-0.3.20200615git15668db.fc33.x86_64.debug after
> > non-allocatable ones
> > 
> > in many packages, such as:
> > 
> > https://kojipkgs.fedoraproject.org//packages/sysutil/0/0.3.
> > 20200615git15668db.fc33/data/logs/x86_64/build.log
> > https://koji.fedoraproject.org/koji/
> > rpmlist?buildrootID=21879423&type=component
> >  = dwz-0.13-2.fc32.x86_64.rpm
> 
> Can you file a PR with a reproducer?

Got one, extracted from
https://koji.fedoraproject.org/koji/buildinfo?buildID=1570316
sysutil-debuginfo-0-0.3.20200615git15668db.fc33.x86_64.rpm

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-09-17 15:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 [Bug default/24251] New: " vries at gcc dot gnu.org
2019-01-01  0:00 ` [Bug default/24251] " vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2020-09-06 19:28 ` jan.kratochvil at redhat dot com
2020-09-07  7:53 ` mark at klomp dot org
2020-09-07  8:01 ` jan.kratochvil at redhat dot com
2020-09-08 13:27 ` vries at gcc dot gnu.org
2020-09-17 15:51 ` mark at klomp dot org [this message]
2020-09-24 22:18 ` mark at klomp dot org
2020-09-25  7:56 ` jan.kratochvil at redhat dot com
2020-09-25  8:03 ` jakub at redhat dot com
2020-09-25  9:44 ` mark at klomp dot org
2020-09-25  9:52 ` jan.kratochvil at redhat dot com
2020-09-25 18:49 ` mark at klomp dot org
2021-02-13 23:05 ` mark at klomp dot org

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=bug-24251-11298-EH8ewRvLU7@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=dwz@sourceware.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).