From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26771] abidw crashes reading /lib64/libclang-cpp.so.10
Date: Fri, 23 Oct 2020 20:24:02 +0000 [thread overview]
Message-ID: <bug-26771-9487-NwWIXfnUfh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26771-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26771
--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
The problem reproduces with the current trunk of libabigail as of
247f50dbf3761ca0fc842abba753cbf52bf4291c
The following libraries continue to exhibit the problem.
/lib64/libmedfwrap.so.11.0.1 from med-4.1.0-1.fc33.x86_64
/lib64/libmedC.so.11.0.1 from med-4.1.0-1.fc33.x86_64
/lib64/libGLU.so.1.3.1 from mesa-libGLU-9.0.1-3.fc33.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-23 20:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 6:05 [Bug default/26771] New: " woodard at redhat dot com
2020-10-23 20:24 ` woodard at redhat dot com [this message]
2020-10-23 21:18 ` [Bug default/26771] " woodard at redhat dot com
2020-10-29 8:40 ` dodji at redhat dot com
2020-10-29 12:18 ` maennich at android dot com
2020-11-10 18:11 ` gprocida+abigail at google dot com
2020-11-10 18:12 ` maennich at android dot com
2020-11-10 18:12 ` maennich at android dot com
2020-11-10 18:30 ` gprocida+abigail at google dot com
2020-11-10 18:40 ` gprocida+abigail at google dot com
2020-11-11 9:06 ` dodji at redhat dot com
2020-11-11 9:31 ` gprocida+abigail at google dot com
2020-11-11 9:54 ` gprocida+abigail at google dot com
2020-11-11 14:09 ` gprocida+abigail at google dot com
2020-11-12 17:15 ` woodard at redhat dot com
2020-11-12 19:04 ` woodard 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-26771-9487-NwWIXfnUfh@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).