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-111-g207d2da
Date: Wed, 17 Aug 2011 12:28:00 -0000	[thread overview]
Message-ID: <20110817122856.16504.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  207d2da9298e751279039ddd8aac11fd6678e301 (commit)
      from  5da8feffae62c98343630e87d2d7cc120415166c (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 207d2da9298e751279039ddd8aac11fd6678e301
Author: Mark Wielaard <mjw@redhat.com>
Date:   Wed Aug 17 13:46:48 2011 +0200

    PR6961 - backtrace from non-pt_regs probe context
    
    When printing a kernel backtrace use the kernel dump_trace if available.
    If the kernel is compiled with frame pointers we can guess the stack
    pionter pretty reliably, otherwise let dump_stack figure it out and
    skip some of the framework stack frames before starting the print the
    remaining stack.

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

Summary of changes:
 runtime/stack-x86.c                       |    3 +-
 runtime/stack.c                           |   55 +++++++++++++++++++++--------
 testsuite/systemtap.context/backtrace.stp |    4 ++-
 3 files changed, 45 insertions(+), 17 deletions(-)


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


                 reply	other threads:[~2011-08-17 12:28 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=20110817122856.16504.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).