public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "ananth at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/9816] functioncallcount.stp causes system crash
Date: Tue, 10 Feb 2009 10:19:00 -0000	[thread overview]
Message-ID: <20090210101725.32605.qmail@sourceware.org> (raw)
In-Reply-To: <20090204113414.9816.ananth@in.ibm.com>


------- Additional Comments From ananth at in dot ibm dot com  2009-02-10 10:17 -------
Our observations so far:
a. Powerpc instruction emulation had a bug. Patch submitted to fix it
(http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068062.html)
b. functioncallcount.stp as it exists probes calls and inlines. That is a
problem -- at least on powerpc with the upstream kernel, set/clear/*_bit (part
of arch/powerpc/include/asm/bitops.h) shouldn't be probed. Its not clear how to
add a set of inline functions in a header file in the blacklist in one go.
c. Maybe its best not to allow routines in bitops.h to be traced?
d. The functioncallcount.stp needs to be modified to just probe .call and not
inlines.

Comments?

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9816

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2009-02-10 10:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 14:58 [Bug translator/9816] New: " ananth at in dot ibm dot com
2009-02-04 15:01 ` [Bug translator/9816] " mjw at redhat dot com
2009-02-04 18:52 ` fche at redhat dot com
2009-02-04 23:42 ` mhiramat at redhat dot com
2009-02-04 23:48 ` mhiramat at redhat dot com
2009-02-05  5:07 ` mhiramat at redhat dot com
2009-02-05 12:47 ` ananth at in dot ibm dot com
2009-02-05 16:49 ` mahesh at linux dot vnet dot ibm dot com
2009-02-05 18:43 ` mhiramat at redhat dot com
2009-02-05 20:27 ` fche at redhat dot com
2009-02-05 23:58 ` mhiramat at redhat dot com
2009-02-06  2:05 ` ananth at in dot ibm dot com
2009-02-06  3:42 ` ananth at in dot ibm dot com
2009-02-10 10:19 ` ananth at in dot ibm dot com [this message]
2009-02-10 17:31 ` ananth at in dot ibm dot com
2009-02-10 19:58 ` fche at redhat dot com
2009-02-11  7:14 ` ananth at in dot ibm dot com
2009-02-11  7:18 ` ananth at in dot ibm dot com
2009-02-12 15:03 ` ananth at in dot ibm 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=20090210101725.32605.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).