public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
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: Tue, 18 Aug 2009 21:41:00 -0000	[thread overview]
Message-ID: <20090818214127.6535.qmail@sourceware.org> (raw)
In-Reply-To: <20090812145803.10512.mjw@redhat.com>


------- Additional Comments From mjw at redhat dot com  2009-08-18 21:41 -------
Although this doesn't fix the general comdat section issue, it does fix the
issue at hand:

commit 08b22cd52aad1023c91341a1fd9bdb821cf4c90f
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Aug 18 23:03:00 2009 +0200

    PR10512 STAP_PROBES don't work in c++ constructors/destructors testcase.
    
    * testsuite/systemtap.base/cxxclass.exp: New file.
    * testsuite/systemtap.base/cxxclass.stp: Likewise.
    * testsuite/systemtap.base/cxxclass.cxx: Likewise.

commit a80a54cb804d0df40e064a72bd8c6bf7c1258e02
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Aug 18 22:08:51 2009 +0200

    PR10512 Referencing computed goto labels in c++ constructors does work.
    
    PR10533 inlined vars are not always found was fixed which means we
    no longer need to prevent inlining of the STAP_PROBE macros.
    
    * includes/sys/sdt.h (STAP_UNINLINE_LABEL): Removed.
      (STAP_PROBE[1-9]_): Remove label: and STAP_UNINLINE_LABEL.

When we find other c++ related issues we should open a new bug.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


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.

      parent reply	other threads:[~2009-08-18 21:41 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
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 [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=20090818214127.6535.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).