public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-457-gd19a9a8 Date: Fri, 09 Jul 2010 00:26:00 -0000 [thread overview] Message-ID: <20100709002622.2496.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 d19a9a82f1a527eadd78f66b0e1dc8575ed7b3b2 (commit) via e1704764eedc1399535598d843aea1a06fa20807 (commit) from 059867ed1227f5d0b327e17895272b3b87701637 (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 d19a9a82f1a527eadd78f66b0e1dc8575ed7b3b2 Author: Josh Stone <jistone@redhat.com> Date: Thu Jul 8 17:09:20 2010 -0700 PR11785: Fix pretty-printing for tracepoint base types We need slightly special code to deal with tracepoint base types, which should not be dereferenced at all, but just used as-is. * tapsets.cxx (dwarf_pretty_print): Add deref_p, which is usually true, but is false for tracepoints if "pointer" is really a direct value. (dwarf_pretty_print::deref): Copy the value directly if !deref_p. (dwarf_pretty_print::recurse_pointer): Detect void pointees more reliably, e.g. in case of a const node with no type -> const void. (dwarf_cast_query::handle_query_module): @cast always has deref_p. (tracepoint_var_expanding_visitor::visit_target_symbol_arg): Permit pretty-printing on !isptr args, and use that to set deref_p. (tracepoint_derived_probe::resolve_tracepoint_arg_type): Check pointers more carefully for a pointee type, again for const void. commit e1704764eedc1399535598d843aea1a06fa20807 Author: Josh Stone <jistone@redhat.com> Date: Thu Jul 8 17:07:58 2010 -0700 Include session::compatible in the script hash Now that the compatibility version has runtime-level effects, we need to include it in the script hash. * hash.cxx (find_script_hash): Add session::compatible. ----------------------------------------------------------------------- Summary of changes: hash.cxx | 1 + tapsets.cxx | 56 ++++++++++++++++++++++++++++++++++++++++++++------------ 2 files changed, 45 insertions(+), 12 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-07-09 0:26 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=20100709002622.2496.qmail@sourceware.org \ --to=jistone@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).