From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/10512] STAP_PROBES don't work in c++ constructors/destructors
Date: Mon, 17 Aug 2009 14:03:00 -0000 [thread overview]
Message-ID: <20090817140248.12800.qmail@sourceware.org> (raw)
In-Reply-To: <20090812145803.10512.mjw@redhat.com>
------- Additional Comments From mjw at redhat dot com 2009-08-17 14:02 -------
There are two more gcc bugs associated with this issue now.
The following contains a small example of the issue with using labelrefs in C++
class constructors: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41090
"Using static label reference in c++ class constructor produces wrong code"
And while working on a partial workaround putting everything in their own
section through variable attributes I came across a section conflict when doing
that from a c and a c++ context: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41091
"Using section attribute in c and c++ function causes section type conflict"
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10512
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-08-17 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 14:58 [Bug runtime/10512] New: " mjw at redhat dot com
2009-08-12 15:00 ` [Bug runtime/10512] " mjw at redhat dot com
2009-08-12 18:29 ` jistone at redhat dot com
2009-08-14 9:05 ` mjw at redhat dot com
2009-08-14 9:40 ` mjw at redhat dot com
2009-08-14 10:07 ` mjw at redhat dot com
2009-08-17 10:26 ` mjw at redhat dot com
2009-08-17 12:09 ` mjw at redhat dot com
2009-08-17 14:03 ` mjw at redhat dot com [this message]
2009-08-17 22:25 ` mjw at redhat dot com
2009-08-18 10:54 ` mjw at redhat dot com
2009-08-18 10:55 ` mjw at redhat dot com
2009-08-18 21:41 ` mjw 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=20090817140248.12800.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).