From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27588] dwz: libxul.so: loclistptr attribute, yet no .debug_loc section
Date: Mon, 17 May 2021 08:57:11 +0000 [thread overview]
Message-ID: <bug-27588-11298-5kDG7B7UcO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27588-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27588
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Martin Liska from comment #7)
> > FWIW, proposed a --devel-skip-producer option here (
> > https://sourceware.org/pipermail/dwz/2021q1/001121.html ). When used on
> > this example with "--devel-skip-producer NASM", dwz manages to finish.
>
> Good proposal, I like it!
This has been committed, but to clarify: this is a developer-only option for
experimentation purposes. There will be more work involved getting this
functionality into a release. See f.i. comment at
https://sourceware.org/pipermail/dwz/2021q1/001138.html .
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-17 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 9:17 [Bug default/27588] New: " mliska at suse dot cz
2021-03-16 10:08 ` [Bug default/27588] " vries at gcc dot gnu.org
2021-03-16 10:36 ` mliska at suse dot cz
2021-03-16 10:38 ` mliska at suse dot cz
2021-03-16 10:49 ` vries at gcc dot gnu.org
2021-03-16 11:12 ` mliska at suse dot cz
2021-03-16 14:21 ` vries at gcc dot gnu.org
2021-03-16 14:23 ` mliska at suse dot cz
2021-05-17 8:57 ` vries at gcc dot gnu.org [this message]
2023-01-16 10:14 ` mliska at suse dot cz
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-27588-11298-5kDG7B7UcO@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).