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-340-gb100897 Date: Fri, 21 Oct 2011 11:37:00 -0000 [thread overview] Message-ID: <20111021113715.9100.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 b100897fdb986b1338099351e6b60a187572ce47 (commit) from 3b62d74b6a33a7c71c104d1b3e414044a5978cd5 (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 b100897fdb986b1338099351e6b60a187572ce47 Author: Mark Wielaard <mjw@redhat.com> Date: Fri Oct 21 13:34:21 2011 +0200 Extend vma_map entry vm_end range when additional segments are mapped. Once registered, we may want to extend an earlier registered region. A segment might be mapped with different flags for different offsets. If so we want to record the extended range so we can address more precisely to module names and symbols. * runtime/task_finder_vma.c (__stp_tf_get_vma_map_entry_end_internal): New function. (stap_extend_vma_map_info): Likewise. * runtime/vma.c (_stp_vma_mmap_cb): Call stap_extend_vma_map_info(). ----------------------------------------------------------------------- Summary of changes: runtime/task_finder_vma.c | 48 +++++++++++++++++++++++++++++++++++++++++++++ runtime/vma.c | 18 +++++++++++++++- 2 files changed, 64 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-10-21 11:37 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=20111021113715.9100.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).