public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29932] abidiff coredump at abg-dwarf-reader.cc:lookup_fn_type_from_die_repr_per_tu when read libc.so from glibc
Date: Mon, 26 Dec 2022 13:04:04 +0000	[thread overview]
Message-ID: <bug-29932-9487-1bCINXx4B7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29932-9487@http.sourceware.org/bugzilla/>

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

dodji at redhat dot com changed:

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

--- Comment #1 from dodji at redhat dot com ---
This should be fixed by commit
https://sourceware.org/git/?p=libabigail.git;a=commit;h=de45f1e69b96a1f7511c94837e1793136b384407
in the master branch of the Git repository.

The fix should be available in the coming 2.3 version of libabigail.

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

  parent reply	other threads:[~2022-12-26 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22  7:52 [Bug default/29932] New: abidiff coredump at abg-ir.cc:hash_as_canonical_type_or_constant " hexiaole1994 at 126 dot com
2022-12-22  9:35 ` [Bug default/29932] abidiff coredump at abg-dwarf-reader.cc:lookup_fn_type_from_die_repr_per_tu " hexiaole1994 at 126 dot com
2022-12-24 14:44 ` dodji at redhat dot com
2022-12-26 13:04 ` dodji at redhat dot com [this message]
2022-12-27 14:49 ` hexiaole1994 at 126 dot com
2022-12-27 16:02 ` dodji at redhat 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-29932-9487-1bCINXx4B7@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@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).