public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29048] Symbols DW_SECT_INFO, DW_SECT_ABBREV, DW_SECT_STR_OFFSETS aren't defined
Date: Wed, 13 Apr 2022 16:10:56 +0000	[thread overview]
Message-ID: <bug-29048-10460-If6e6Rs1Ex@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29048-10460@http.sourceware.org/bugzilla/>

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
Added just the constants:

commit 399b55a75830f1854c8da9f29282810e82f270b6
Author: Mark Wielaard <mark@klomp.org>
Date:   Wed Apr 13 17:23:57 2022 +0200

    libdw: Add DWARF5 package file section identifiers, DW_SECT_*

    This only adds the constants. There is no handling of DWARF
    package file (dwp) files for now.

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

    Signed-off-by: Mark Wielaard <mark@klomp.org>

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

  parent reply	other threads:[~2022-04-13 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 22:47 [Bug general/29048] New: " yuri at tsoft dot com
2022-04-13 15:03 ` [Bug general/29048] " mark at klomp dot org
2022-04-13 15:15 ` yuri at tsoft dot com
2022-04-13 16:10 ` mark at klomp dot org [this message]
2022-04-18 17:39 ` yuri at tsoft dot com
2022-04-19  8:20 ` mark at klomp dot org
2022-04-19 16:24 ` yuri at tsoft dot com

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-29048-10460-If6e6Rs1Ex@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@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).