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, mjw/backtrace, updated. release-1.5-160-g2e4fe95
Date: Fri, 22 Jul 2011 09:53:00 -0000	[thread overview]
Message-ID: <20110722095347.13049.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, mjw/backtrace has been updated
       via  2e4fe9549eea14de8e88b1e0697fcfd870296d06 (commit)
      from  7e46daf103bea7dcc92e255629e8412e8f608215 (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 2e4fe9549eea14de8e88b1e0697fcfd870296d06
Author: Mark Wielaard <mjw@redhat.com>
Date:   Fri Jul 22 11:51:41 2011 +0200

    Remove stack-x64x.c specific fallback for _stp_stack_print_fallback().
    
    If the standard kernel based _stp_stack_print_fallback() isn't available
    don't try to be smart and guess at stack addresses ourselves. Just give
    up. Dwarf based unwinding is good enough now and the kernel dump_stack()
    does a much better job than we can at guessing stack values.

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

Summary of changes:
 runtime/stack-x86.c |   19 -------------------
 runtime/stack.c     |    7 ++++++-
 2 files changed, 6 insertions(+), 20 deletions(-)


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


                 reply	other threads:[~2011-07-22  9:53 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=20110722095347.13049.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).