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-424-g2d7232c
Date: Wed, 16 Nov 2011 13:28:00 -0000	[thread overview]
Message-ID: <20111116132810.32010.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  2d7232ca34eee7f244949fa4d05dcf039f558709 (commit)
      from  8c6bb2894a95b9035e7469adf339fb6402749b0f (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 2d7232ca34eee7f244949fa4d05dcf039f558709
Author: Mark Wielaard <mjw@redhat.com>
Date:   Wed Nov 16 13:33:26 2011 +0100

    Don't use dwfl_module bias in either emit_address() and vardie_from_symtable().
    
    dwflpp::emit_address() is called by loc2c for emitting DW_OP_addr.
    DW_OP_addr could come from the actual dwarf location description or
    could be synthetically generated from through vardie_from_symtable().
    vardie_from_symtable() would keep the dwfl module bias (if there was one),
    but the DW_OP_addr from real dwarf debuginfo would not have it.
    Now we are consistently not having the module bias added.
    
    Add some variants of the externalvar.exp testcase, which previously
    failed with older GCC versions (where we would pick up the DW_OP_addr
    from the dwarf location description), while newer GCCs emit dwarf DIEs
    for these variables that only have the external flag set. The new
    testcase variants use static vars, which will have DW_OP_addr emitted
    in both old and new GCC versions.

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

Summary of changes:
 dwflpp.cxx                                 |   53 +++++++++------------------
 testsuite/systemtap.base/externalvar.c     |    9 +++++
 testsuite/systemtap.base/externalvar.exp   |   16 ++++++++-
 testsuite/systemtap.base/externalvar.stp   |   34 ++++++++++++++++++
 testsuite/systemtap.base/externalvar_lib.c |    5 +++
 5 files changed, 81 insertions(+), 36 deletions(-)


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


                 reply	other threads:[~2011-11-16 13: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=20111116132810.32010.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).