public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, pr4225, created. release-0.7-31-g5e112f9
Date: Sun, 03 Aug 2008 04:33:00 -0000	[thread overview]
Message-ID: <20080803043321.15525.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, pr4225 has been created
        at  5e112f921fb7b05115f021319e18f90e68594a19 (commit)

- Log -----------------------------------------------------------------
commit 5e112f921fb7b05115f021319e18f90e68594a19
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Sat Aug 2 23:16:52 2008 -0400

    PR4225: use shared stap_uprobe[] pool in .bss

commit 48e685da27141914cff14dc6ea92aebbb74c5906
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Sat Aug 2 22:21:35 2008 -0400

    PR4225: it's alive, alive!

commit 6d0f3f0cc2931c2ad29b57f4fecdde3ccc210d8c
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Sat Aug 2 16:28:50 2008 -0400

    PR4225: signs of life

commit 1384b663414d5380e25b21457e71458078ded8d5
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Sat Aug 2 13:50:28 2008 -0400

    c code generation: assert C indentation/nesting cancels out at appropriate points

commit 67e704a6b1aa140d00d8fe4040fc6e76e7cac2fb
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Sat Aug 2 13:50:28 2008 -0400

    c code generation: assert C indentation/nesting cancels out at appropriate points

commit e014982dda6c78a278e92307b9121c5a0a77ed43
Merge: 5743764427a592fd9619afeff3881199e985cdc3 e6b9397b3e13a7c497368777006020f64560fa98
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Wed Jul 23 19:40:41 2008 -0400

    Merge commit 'e6b9397' into pr4225
    
    * commit 'e6b9397':
      changelog for entry-pc semantic error fix

commit 5743764427a592fd9619afeff3881199e985cdc3
Merge: 91af0778bb5082d46270ff38f33db4054cbee822 552fdd9f5a7eb3394888356301929c078173a22b
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Wed Jul 23 17:41:13 2008 -0400

    Merge commit '552fdd9f5a7eb3394888356301929c078173a22b' into pr4225
    
    * commit '552fdd9f5a7eb3394888356301929c078173a22b':
      fix semantic error: no entrypc found using probe .statement(*@file:line) constructs
      Fix sw 6752. Alter condtional to check for >= 2.6.26. This accounts and fixes false positives in kernel_v strings that return xx.xx.xx.xx over xx.xx.xx.

commit 91af0778bb5082d46270ff38f33db4054cbee822
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Wed Jul 23 11:33:26 2008 -0400

    PR4225: support intermingled process/kernel/module probes without screwing up module cache

commit 7a24d42223ae98598c99bfb21437a00f13397d6d
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Tue Jul 22 16:14:02 2008 -0400

    PR4225: parse process("path").function/statement probe points

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


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


                 reply	other threads:[~2008-08-03  4:33 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=20080803043321.15525.qmail@sourceware.org \
    --to=fche@sourceware.org \
    --cc=systemtap-cvs@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).