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.3-165-g7712327 Date: Wed, 29 Sep 2010 16:59:00 -0000 [thread overview] Message-ID: <20100929165908.17490.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 7712327519f2c24e779e42a54315ad50f5db8ba7 (commit) via 71fa1fe39faa153cf6ede620c4855e508059aa39 (commit) from 994aac0e5744703fa58eb3dabcd858eca1306e10 (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 7712327519f2c24e779e42a54315ad50f5db8ba7 Author: Frank Ch. Eigler <fche@elastic.org> Date: Wed Sep 29 12:53:37 2010 -0400 PR10812: undo +20 build-id address offsetting With the new relocation code, this does occasionally cause addresses to spill over into the next section, leading to unexpected relocation bases. * runtime/sym.c (_stp_module_check): Remove the build_id_len subtraction. Provide diagnostics on unexpected addresses/names. * translate.cxx (dump_unwindsyms): Likewise. commit 71fa1fe39faa153cf6ede620c4855e508059aa39 Author: Tony Jones <tonyj@suse.de> Date: Wed Sep 29 12:47:52 2010 -0400 PR10812: relocate module build-id Relocate the build_id_vaddr obtained from dwfl_module_build_id. Failure to do this was causing ppc64 systems to fail the build-id check for cases such as: probe module("libata").function("*").call { printf ("%s\n", probefunc()) } Signed-off-by: Tony Jones <tonyj@suse.de> ----------------------------------------------------------------------- Summary of changes: runtime/sym.c | 12 +++++------- translate.cxx | 29 +++++++++++++++++++++++++---- 2 files changed, 30 insertions(+), 11 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-09-29 16:59 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=20100929165908.17490.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).