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-509-g7721a4d Date: Tue, 29 Nov 2011 11:57:00 -0000 [thread overview] Message-ID: <20111129115727.16878.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 7721a4d6d29c5fbcd151a0995796cb1a4feabb32 (commit) via b6a3ff43a2d56ffab2bb7bf26c8dffc48d06aeeb (commit) from 5d88da2782aeb45ccf072deb8a58cf0082f69674 (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 7721a4d6d29c5fbcd151a0995796cb1a4feabb32 Author: Mark Wielaard <mjw@redhat.com> Date: Tue Nov 29 12:32:05 2011 +0100 Support fallback kernel dump_stack() with or without bp argument. There has been some flip-flopping in the kernel whether or not dump_stack() takes a bp argument. We now support either with or without. See linux commits v2.6.36-9872-g9c0729d and v2.6.38-793-ge8e999c. commit b6a3ff43a2d56ffab2bb7bf26c8dffc48d06aeeb Author: Mark Wielaard <mjw@redhat.com> Date: Tue Nov 29 12:24:07 2011 +0100 PR10739 kfail on non-x86 architectures, no dump_trace available. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 2 ++ runtime/stack.c | 12 +++++++++--- testsuite/systemtap.base/backtrace.exp | 4 ++++ 3 files changed, 15 insertions(+), 3 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-29 11:57 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=20111129115727.16878.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).