From: "seppo.yliolli at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28301] libabigail asserts with older versions of gcc / glibc
Date: Mon, 28 Mar 2022 18:59:56 +0000 [thread overview]
Message-ID: <bug-28301-9487-XeJEOpaEB6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28301-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28301
--- Comment #9 from Seppo Yli-Olli <seppo.yliolli at gmail dot com> ---
It's still this same case I was talking on IRC about except as said, it turns
out this it's a lot more subtle and can be triggered with smaller differences
of glibc. Same asserts going on. It appears libabigail itself (at least in our
case) is affected by the glibc it's built against which makes it impossible to
for abidw'ing another glibc. Something perhaps worth mentioning is we're using
the separate debugedit project, not RPM debugedit.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-28 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 12:52 [Bug default/28301] New: " jjardon at gnome dot org
2021-09-02 12:55 ` [Bug default/28301] " gprocida at google dot com
2021-09-02 14:06 ` jjardon at gnome dot org
2021-10-01 20:37 ` seppo.yliolli at gmail dot com
2021-10-04 7:55 ` dodji at redhat dot com
2021-10-04 8:08 ` seppo.yliolli at gmail dot com
2021-10-04 11:20 ` seppo.yliolli at gmail dot com
2021-10-07 7:51 ` dodji at redhat dot com
2021-10-07 8:44 ` seppo.yliolli at gmail dot com
2022-03-28 18:59 ` seppo.yliolli at gmail dot com [this message]
2023-04-24 14:49 ` ben at demerara dot io
2023-04-26 14:13 ` 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-28301-9487-XeJEOpaEB6@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).