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-526-gaf3e4f8 Date: Thu, 01 Dec 2011 11:08:00 -0000 [thread overview] Message-ID: <20111201110823.31548.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 af3e4f8792bc0842e2d321afa978f2ae20d64cba (commit) from 8bf9072636b6cecfb674303ef10f701b587975f1 (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 af3e4f8792bc0842e2d321afa978f2ae20d64cba Author: Mark Wielaard <mjw@redhat.com> Date: Thu Dec 1 12:05:35 2011 +0100 Document some new features and improvements since systemtap 1.6. task_backtrace removed, MAXBACKTRACE documented, new probe_type() function, unwind and symbol data only processed when really necesessary, kernel backtraces for non-pt_regs probe context (timer and tracepoints), ubacktrace() from kernel probe points, s390x user space support, ppc, s390x and arm dwarf unwinder support, arm uprobes port. ----------------------------------------------------------------------- Summary of changes: NEWS | 36 ++++++++++++++++++++++++++++++++++++ 1 files changed, 36 insertions(+), 0 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-01 11:08 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=20111201110823.31548.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).