public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "prasad at linux dot vnet dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/7030] signal tapset may be referring to inline functions.
Date: Tue, 18 Nov 2008 09:52:00 -0000	[thread overview]
Message-ID: <20081118095105.5838.qmail@sourceware.org> (raw)
In-Reply-To: <20081113083330.7030.srikar@linux.vnet.ibm.com>


------- Additional Comments From prasad at linux dot vnet dot ibm dot com  2008-11-18 09:51 -------
The behaviour described below can be attributed to the fact that probe 
_signal.send.part1 and probe _signal.send.part4 which respectively point to the 
kernel functions __group_send_sig_info() and specific_send_sig_info() have been 
inlined.

The sudden inlining of these funtions could be the result of changes made to 
these functions through commit 4cd4b6d4e0372075f846feb85aea016cbdbfec4c that 
made them a mere wrapper over send_signal(). Following this change, and due to 
the fact that the wrapper functions are being inlined by the compiler, we shall 
point these probe aliases directly to send_signal() with the appropriate names 
and function parameters. The probe aliases are restricted to kernel versions 
newer than 2.6.25.

On application of the attached patch, the script sig_by_pid.stp is found to 
work fine on the Fedora kernel 2.6.27.5-101.fc10.i686. It is pending testing on 
a kernel older than 2.6.25 though. Requesting comments, if any.


-- 


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

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

      parent reply	other threads:[~2008-11-18  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13  8:34 [Bug tapsets/7030] New: " srikar at linux dot vnet dot ibm dot com
2008-11-13 10:15 ` [Bug tapsets/7030] " mjw at redhat dot com
2008-11-18  9:52 ` prasad at linux dot vnet dot ibm 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=20081118095105.5838.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).