From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30307] self compare problem with bpftrace
Date: Mon, 03 Apr 2023 17:48:21 +0000 [thread overview]
Message-ID: <bug-30307-9487-3ZDColWRTR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30307-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30307
Ben Woodard <woodard at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|arch specific self compare |self compare problem with
|problem with bpftrace |bpftrace
--- Comment #4 from Ben Woodard <woodard at redhat dot com> ---
Enblightenment seems to have a similar problem however it is not arch specific.
This calls into question whether the problem is more an arch specific problem
or if it is some sort of race condition in doing type canonicalization. When
doing the underlying abipkgdiff it seems to be the same kind of confusion of
typedef and a struct.
type of 'E_Zone* zone' changed:
in pointed to type 'typedef E_Zone' at e_zone.h:16:1:
underlying type 'struct _E_Zone' changed, as being reported
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-03 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 17:28 [Bug default/30307] New: arch specific " woodard at redhat dot com
2023-04-03 17:30 ` [Bug default/30307] " woodard at redhat dot com
2023-04-03 17:35 ` woodard at redhat dot com
2023-04-03 17:42 ` woodard at redhat dot com
2023-04-03 17:48 ` woodard at redhat dot com [this message]
2023-04-03 22:10 ` [Bug default/30307] " woodard at redhat dot com
2023-04-26 12:38 ` 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-30307-9487-3ZDColWRTR@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).