From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30123] bitfield.exp fails with fresh kernels
Date: Thu, 09 Mar 2023 22:09:34 +0000 [thread overview]
Message-ID: <bug-30123-6586-tw9INxmmJ0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30123-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30123
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |29037
Status|NEW |RESOLVED
Resolution|--- |FIXED
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
commit aeb35e508eaa completes the work begun back in bug #29037.
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=29037
[Bug 29037] Systemtap unable to find struct bitfield members for gcc11 compiled
code
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-03-09 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 14:01 [Bug runtime/30123] New: " mcermak at redhat dot com
2023-02-14 19:26 ` [Bug runtime/30123] " wcohen at redhat dot com
2023-03-09 22:09 ` fche at redhat dot com [this message]
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-30123-6586-tw9INxmmJ0@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).