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-0.9.9-315-g86598eb
Date: Wed, 16 Sep 2009 10:25:00 -0000	[thread overview]
Message-ID: <20090916102534.24053.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  86598ebfa13479b4ba3b6b7a9de25c3e497ff57e (commit)
      from  e3e5c5563d361c206fba99b98b0f9f8a135089ce (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 86598ebfa13479b4ba3b6b7a9de25c3e497ff57e
Author: Mark Wielaard <mjw@redhat.com>
Date:   Wed Sep 16 12:22:04 2009 +0200

    Clean up dwflpp::translate_location workaround for DW_AT_data_member_location.
    
    Do the same workaround as loc2c-test.c does. Just treat a constant member
    location offset as a DW_OP_plus_uconst and call c_translate_location for it.
    Also Remove c_translate_add_offset.
    
    * dwflpp.cxx (dwflpp::translate_location): Check elfutils version and only
      do workaround for elfutils < 0.142.
    * loc2c.h (c_translate_add_offset): Removed.
    * loc2c.c (c_translate_add_offset): Likewise.

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

Summary of changes:
 dwflpp.cxx |   23 +++++++++++------------
 loc2c.c    |   34 ----------------------------------
 loc2c.h    |    7 -------
 3 files changed, 11 insertions(+), 53 deletions(-)


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


                 reply	other threads:[~2009-09-16 10:25 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=20090916102534.24053.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).