public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-233-g110a589
Date: Tue, 17 Nov 2009 08:27:00 -0000	[thread overview]
Message-ID: <20091117082705.11284.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  110a589704c72327ba80aaf75bff496a6b6334f6 (commit)
      from  e7c84665f79fd944371c2c49e57189ed1f6cee6d (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 110a589704c72327ba80aaf75bff496a6b6334f6
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Nov 17 09:24:41 2009 +0100

    Explain "cheat" comment in sym.c (_stp_tf_mmap_cb).
    
    We are abusing the "first" section address here to indicate where the
    module (actually first segment) is loaded (which is why we are ignoring
    the offset). It would be good to redesign the stp_module/stp_section
    data structures to better align with the actual memory mappings we are
    interested in (especially the "section" naming is slightly confusing
    since what we really seem to mean are elf segments (which can contain
    multiple elf sections).
    
    * runtime/sym.c (_stp_tf_mmap_cb): Add cheat comment.

-----------------------------------------------------------------------

Summary of changes:
 runtime/sym.c |   11 +++++++++++
 1 files changed, 11 insertions(+), 0 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2009-11-17  8:27 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=20091117082705.11284.qmail@sourceware.org \
    --to=mark@sourceware.org \
    --cc=systemtap-cvs@sourceware.org \
    --cc=systemtap@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: 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).