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, master, updated. release-1.6-619-g4881684 Date: Mon, 19 Dec 2011 14:06:00 -0000 [thread overview] Message-ID: <20111219140643.18900.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 4881684f575de1ed2aa31d490c1a9b8bd74cdd9f (commit) from 8f54d98f98c01698d1cad77609b0a7898450559f (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 4881684f575de1ed2aa31d490c1a9b8bd74cdd9f Author: Frank Ch. Eigler <fche@redhat.com> Date: Mon Dec 19 09:03:58 2011 -0500 PR13489, the neverending kludge story. Resolve RHEL5's old utrace conflicts. RHEL5's old utrace uses utrace_native_view() instead of task_user_regset_view(), so we shouldn't be so stuck on trying to find it. To add insult to injury, any attempt to use kallsyms* to look up the latter results in an unloadable module since kallsyms* is not exported in these old kernels. * transport/transport.c (_stp_transport_init): Only look for task_user_regset_view for other than old rhel5 utrace. ----------------------------------------------------------------------- Summary of changes: runtime/transport/transport.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-19 14:06 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=20111219140643.18900.qmail@sourceware.org \ --to=fche@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).