public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "doko at debian dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24756] New: dwz fails to process i386 pocl binaries (Unknown debugging section .debug_addr)
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <bug-24756-11298@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 24756
           Summary: dwz fails to process i386 pocl binaries (Unknown
                    debugging section .debug_addr)
           Product: dwz
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: nobody at sourceware dot org
          Reporter: doko at debian dot org
                CC: dwz at sourceware dot org
  Target Milestone: ---

seen with 0.12, and trunk 20190702 on i686-linux-gnu:

$ dwz -mlibpocl2.debug -Mlibpocl2.debug -- libpocl.so.2.2.0 libllvmopencl.so
dwz: libpocl.so.2.2.0: Unknown debugging section .debug_addr
dwz: libllvmopencl.so: Unknown debugging section .debug_addr
dwz: Too few files for multifile optimization

test case at
https://people.debian.org/~doko/tmp/dwz-tst-i386.tar.xz

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

             reply	other threads:[~2019-07-02 10:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 doko at debian dot org [this message]
2019-01-01  0:00 ` [Bug default/24756] Unknown debugging section .debug_addr vries at gcc dot gnu.org
2019-01-01  0:00 ` [Bug default/24756] Unknown debugging section .debug_addr (-gsplit-dwarf) 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-24756-11298@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).