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-113-g766cee5 Date: Wed, 17 Aug 2011 17:17:00 -0000 [thread overview] Message-ID: <20110817171700.2699.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 766cee5f52531d2599134b889c6e258a70026b42 (commit) from d70b339b103b5cc6496f41836324da7e06e7328d (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 766cee5f52531d2599134b889c6e258a70026b42 Author: Mark Wielaard <mjw@redhat.com> Date: Wed Aug 17 19:13:24 2011 +0200 Really old kprobes didn't have a symbol_name field, autoconf it. kprobes on addresses do just work and can now be build. symbol_named kprobes now get a registration warning if the symbol_name field isn't available. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 1 + runtime/autoconf-kprobe-symbol-name.c | 6 ++++++ tapsets.cxx | 8 ++++++++ 3 files changed, 15 insertions(+), 0 deletions(-) create mode 100644 runtime/autoconf-kprobe-symbol-name.c hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-08-17 17: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=20110817171700.2699.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: linkBe 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).