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-235-gb049078
Date: Tue, 17 Nov 2009 15:17:00 -0000	[thread overview]
Message-ID: <20091117151735.708.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  b0490786a904cbd19fb04c3d66ac3c277bfc2c71 (commit)
      from  f685b2fea262d1e517d75d69c84ec0d1edea6cf0 (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 b0490786a904cbd19fb04c3d66ac3c277bfc2c71
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Nov 17 16:11:28 2009 +0100

    Use DW_AT_MIPS_linkage_name when available in vardie_from_symtable.
    
    If there is a DW_AT_MIPS_linkage_name it encodes the actual name of
    the variable as used in the symbol table.
    
    * dwflpp.cpp (vardie_from_symtable): Check whether there is a
      DW_AT_MIPS_linkage_name attribute and use its value if so.

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

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


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


                 reply	other threads:[~2009-11-17 15:17 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=20091117151735.708.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).