public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-157-gf407254
Date: Tue, 07 Aug 2012 19:28:00 -0000	[thread overview]
Message-ID: <> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]

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  f407254234d44a3123f223521518f2db9d63ce79 (commit)
       via  6ea5debde76070c17c004a85119f90ef8c0fbc41 (commit)
      from  ffe4e8c4317c026ce1beab204912c3f16d6854fe (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 f407254234d44a3123f223521518f2db9d63ce79
Author: Josh Stone <>
Date:   Tue Aug 7 12:24:18 2012 -0700

    parse: Fix a -Werror=delete-non-virtual-dtor
      CXX    stap-parse.o
    ../parse.cxx: In destructor ‘parser::pp1_activation::~pp1_activation()’:
    ../parse.cxx:421:16: error: deleting object of polymorphic class type
    ‘parser::pp_macrodecl’ which has non-virtual destructor might cause
    undefined behaviour [-Werror=delete-non-virtual-dtor]
    cc1plus: all warnings being treated as errors
    We need virtual ~macrodecl to destroy the inherited pp_macrodecl.

commit 6ea5debde76070c17c004a85119f90ef8c0fbc41
Author: Josh Stone <>
Date:   Tue Aug 7 12:10:59 2012 -0700

    spec: Configure the rpm verrel into the build


Summary of changes:
 parse.h        |    2 +-
 systemtap.spec |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-08-07 19: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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).