public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/28728] Unknown DWARF DW_FORM_0x25 (DW_FORM_strx)
Date: Wed, 15 May 2024 11:29:28 +0000	[thread overview]
Message-ID: <bug-28728-13298-XcZUdBLxh3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28728-13298@http.sourceware.org/bugzilla/>

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

--- Comment #11 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Vitaly Chikunov from comment #10)
> Thanks the fix! But, since LLVM 18 is started to produce DWARF 5 by default,
> maybe you can draft a release with it?

I found some other bugs that cause issues with strx. Will post them soon.
Current work in progress here:
https://code.wildebeest.org/git/user/mjw/debugedit/log/?h=strx
Then do a new release after those get integrated.

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

      parent reply	other threads:[~2024-05-15 11:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27  7:23 [Bug debugedit/28728] New: Unknown DWARF DW_FORM_0x25 vt at altlinux dot org
2021-12-27  7:30 ` [Bug debugedit/28728] " vt at altlinux dot org
2021-12-27 10:40 ` [Bug debugedit/28728] Unknown DWARF DW_FORM_0x25 (DW_FORM_strx) mark at klomp dot org
2022-02-18  7:41 ` telans at posteo dot de
2022-02-18  7:47 ` telans at posteo dot de
2022-11-09  6:58 ` sam at gentoo dot org
2022-11-11  5:06 ` sam at gentoo dot org
2023-09-24 18:10 ` seppo.yliolli at gmail dot com
2023-12-06 14:39 ` mark at klomp dot org
2023-12-11 14:02 ` mark at klomp dot org
2024-04-27 11:50 ` vt at altlinux dot org
2024-05-15 11:29 ` mark at klomp dot org [this message]

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-28728-13298-XcZUdBLxh3@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=debugedit@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).