From: "ben at demerara dot io" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30427] New: abidiff segmentation fault with libpipewire-0.3.so
Date: Sun, 07 May 2023 09:45:56 +0000 [thread overview]
Message-ID: <bug-30427-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30427
Bug ID: 30427
Summary: abidiff segmentation fault with libpipewire-0.3.so
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: ben at demerara dot io
CC: libabigail at sourceware dot org
Target Milestone: ---
The resolution for https://sourceware.org/bugzilla/show_bug.cgi?id=30329
seemingly exposed a bug that results in a segmentation fault.
Command to reproduce:
abidiff --verbose --headers-dir1 old-image/usr/include --headers-dir2
new-image/usr/include --debug-info-dir1 old-image/usr/lib/debug
--debug-info-dir2 new-image/usr/lib/debug
old-image/usr/lib/x86_64-linux-gnu/libpipewire-0.3.so.0.369.0
new-image/usr/lib/x86_64-linux-gnu/libpipewire-0.3.so.0.370.0
--drop-private-types
Thread 1 "abidiff" received signal SIGSEGV, Segmentation fault.
0x00007ffff7a14fdd in __libdw_find_attr (die=die@entry=0x7fffff7ff400,
search_name=search_name@entry=3,
codep=codep@entry=0x7fffff7ff0b0, formp=formp@entry=0x7fffff7ff0b4)
at /usr/src/debug/elfutils/elfutils-0.189/libdw/libdwP.h:696
696 if (die->abbrev == NULL || readp != NULL)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-05-07 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 9:45 ben at demerara dot io [this message]
2023-05-07 10:07 ` [Bug default/30427] " ben at demerara dot io
2023-05-11 14:43 ` dodji at redhat dot com
2023-05-12 19:41 ` dodji at redhat dot com
2023-05-13 7:32 ` ben at demerara dot io
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-30427-9487@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).