public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.7-5-g3e961ba Date: Tue, 15 Jul 2008 22:57:00 -0000 [thread overview] Message-ID: <20080715225733.4453.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via 3e961ba66a8250310a1ea67cddb52d92469a6d4b (commit) from cf74051352b34ad1242b4eeee5dacb0caa92b3a8 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 3e961ba66a8250310a1ea67cddb52d92469a6d4b Author: James Bottomley <James dot Bottomley at HansenPartnership dot com> Date: Mon Jul 14 16:49:00 2008 -0500 fix missing functions in caches Both the inline and non inline filtered function caches can lose functions. This happens because both of these caches are indexed by the entrypc. However, the vagaries of optimisation can actually cause us to end up with two functions with apparently the same entrypc (mainly because for inline functions, the entrypc has to be deduced from the range of addresses, which is nastily heuristic). A nice example of this is bsg_io_schedule. In my build of 2.6.26 it's a static function transformed to an inline by the compiler. The range deduction of its entrypc ends up being identical to that of bsg_release, so when I try to place a probe inside it, none of the function references actually refers to it. Since nothing ever actually makes use of this index, the fix is simple: don't use a map indexed on the entrypc, use a simple vector. Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 84 +++++++++++++++++++++++++++++++---------------------------- 1 files changed, 44 insertions(+), 40 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2008-07-15 22:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080715225733.4453.qmail@sourceware.org \ --to=fche@sourceware.org \ --cc=systemtap-cvs@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: linkBe 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).