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-1.6-241-g1d381a0
Date: Wed, 21 Sep 2011 10:51:00 -0000	[thread overview]
Message-ID: <20110921105111.21554.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  1d381a0d947061c10eb0209a49aaf8af8873726d (commit)
      from  d0d7bd5fd8ebe136c7afca43e157f04c1abed243 (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 1d381a0d947061c10eb0209a49aaf8af8873726d
Author: Timo Juhani Lindfors <timo dot lindfors at iki dot fi>
Date:   Wed Sep 21 12:19:01 2011 +0300

    Tell the user if UTS_VERSION does not match running kernel
    
    The test is done before looking at build-id since build-id error
    messages like
    
    ERROR: Build-id mismatch: "kernel" vs. "vmlinux-2.6.32-5-amd64" byte 0 (0x5e vs 0xff)
    Pass 5: run failed.  Try again with another '--vp 00001' option.
    
    are not very user-friendly.

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

Summary of changes:
 buildrun.cxx                         |    1 +
 runtime/autoconf-generated-compile.c |    4 ++++
 translate.cxx                        |   17 +++++++++++++++++
 3 files changed, 22 insertions(+), 0 deletions(-)
 create mode 100644 runtime/autoconf-generated-compile.c


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


                 reply	other threads:[~2011-09-21 10:51 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=20110921105111.21554.qmail@sourceware.org \
    --to=fche@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).