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.2-365-g82ea0c9 Date: Tue, 29 Jun 2010 14:39:00 -0000 [thread overview] Message-ID: <20100629143910.12113.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 82ea0c96760eba1a1f521c007b9353e7e568906b (commit) from b3c857f19a8fab9067adee7374bd8a2c7377d160 (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 82ea0c96760eba1a1f521c007b9353e7e568906b Author: Mark Wielaard <mjw@redhat.com> Date: Tue Jun 29 16:16:02 2010 +0200 PR10599 Always print modname when available (and requested). * runtime/sym.c (_stp_umod_lookup): Also return vm_end if available. (_stp_kallsyms_lookup): Don't try to handle 32bit-on-64bit signedness, _stp_umod_lookup already does. If available return modname, size and offset. (_stp_print_addr): Always print modname when available (and requested). (_stp_symbol_snprint): Likewise. * runtime/unwind.c (unwind): Adjust _stp_umod_lookup call. * tapset/ucontext.stp (umodname): Likewise. ----------------------------------------------------------------------- Summary of changes: runtime/sym.c | 63 +++++++++++++++++++++++++++++++++++++------------- runtime/unwind.c | 2 +- tapset/ucontext.stp | 2 +- 3 files changed, 48 insertions(+), 19 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-06-29 14:39 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=20100629143910.12113.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).