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.6-339-g3b62d74
Date: Thu, 20 Oct 2011 18:46:00 -0000	[thread overview]
Message-ID: <20111020184647.31031.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  3b62d74b6a33a7c71c104d1b3e414044a5978cd5 (commit)
      from  cd4c71e97a1704bd830d0a8b1b743645b8a538a7 (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 3b62d74b6a33a7c71c104d1b3e414044a5978cd5
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Oct 20 20:42:34 2011 +0200

    Add runtime/autoconf-mm-context-vdso-base.c for vma.c vdso catching.
    
    Some architectures use an unsigned long vdso_base field in mm->context,
    instead of a void *vdso field. Detect either in _stp_vma_match_vdso().

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

Summary of changes:
 buildrun.cxx                                       |    1 +
 ...text-vdso.c => autoconf-mm-context-vdso-base.c} |    2 +-
 runtime/vma.c                                      |    9 ++++++++-
 3 files changed, 10 insertions(+), 2 deletions(-)
 copy runtime/{autoconf-mm-context-vdso.c => autoconf-mm-context-vdso-base.c} (61%)


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


                 reply	other threads:[~2011-10-20 18:46 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=20111020184647.31031.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).