From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26315] abidiff segfaults from 9a113ce but works in 1.7
Date: Thu, 10 Sep 2020 15:04:41 +0000 [thread overview]
Message-ID: <bug-26315-9487-ViwyrlKNrz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26315-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26315
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2020-09-10
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
--- Comment #5 from dodji at redhat dot com ---
Thank you for reporting this issue, and sorry for the inconvenience.
Looking at the backtrace it looks like libabigail the segmentation fault is
happening on this line:
··if·(*l.get_underlying_type()·!=·*r.get_underlying_type())$
basically, l and r are typdef types. Normally, {l,r}.get_underlying_type() can
never be NULL, because typedef always have underlying types.
So I am not sure what is happening there. It would be really helpful if I
could look at the binary itself to see what is happening, but I guess that is
not possible, is it?
Just for the record, the git hash I am looking at is this one:
fd8640dc09b99bee11745a4d5b176b2dee3400f4
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-10 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 15:35 [Bug default/26315] New: " sourceware at sgoth dot de
2020-07-29 16:01 ` [Bug default/26315] " gprocida+abigail at google dot com
2020-07-29 18:03 ` gprocida+abigail at google dot com
2020-07-29 18:13 ` sourceware at sgoth dot de
2020-07-29 18:23 ` sourceware at sgoth dot de
2020-09-10 15:04 ` dodji at redhat dot com [this message]
2020-09-27 9:23 ` sourceware at sgoth dot de
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-26315-9487-ViwyrlKNrz@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).