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-195-gfafeaf8
Date: Sun, 08 Nov 2009 21:07:00 -0000	[thread overview]
Message-ID: <20091108210743.386.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  fafeaf8e5874e6855343421b5dd91403fc49c991 (commit)
      from  e29b2f5a9c72fa413af00023384a39d4b667f17a (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 fafeaf8e5874e6855343421b5dd91403fc49c991
Author: Mark Wielaard <mark@hermans.wildebeest.org>
Date:   Sun Nov 8 22:03:31 2009 +0100

    PR10923 Handle AT_frame_base given by DW_OP_call_frame_cfa in .debug_frame.
    
    dwarf_cfi_addrframe should not be called with pc adjusted to the bias
    of the dwfl_module_dwarf_cfi or dwfl_module_eh_cfi. This just happened to
    work in the .eh_frame case because bias was always zero.
    
    * dwflpp.cxx (get_cfa_ops): Don't adjust pc for bias.

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

Summary of changes:
 dwflpp.cxx |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


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


                 reply	other threads:[~2009-11-08 21:07 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=20091108210743.386.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).