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-278-ged9eb14 Date: Wed, 16 Jun 2010 01:41:00 -0000 [thread overview] Message-ID: <20100616014113.11353.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 ed9eb144b3063220f76586e4a7c126de696b6b50 (commit) via 7f6b80bd957c19ed6804cf66b255f9b4ed8c8f8b (commit) via 277c21bca6443dd55cc334d427169f45286f7c08 (commit) via bbee5bb8e68649b1bfe74896303342a82e0e8ac6 (commit) via 3a147004a8d4988df864ecc9ac133577838136a6 (commit) via f8809d54b6819b6778d02051d2834003c0899f1b (commit) from e51ccd5b174c06275b1ead786cea38ad8f13a720 (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 ed9eb144b3063220f76586e4a7c126de696b6b50 Author: Josh Stone <jistone@redhat.com> Date: Tue Jun 15 18:27:02 2010 -0700 unprivileged typo commit 7f6b80bd957c19ed6804cf66b255f9b4ed8c8f8b Author: Josh Stone <jistone@redhat.com> Date: Tue Jun 15 16:27:18 2010 -0700 Rename cast_op::type to type_name The existing name shadowed expression::type, and we can't have that... commit 277c21bca6443dd55cc334d427169f45286f7c08 Author: Josh Stone <jistone@redhat.com> Date: Tue Jun 15 15:46:47 2010 -0700 The Death of target_symbol::base_name Once upon a time, target_symbol was not a symbol, such shame. But lo! one fateful day, an new inheritance raised its game. Henceforth let target_symbol be known by its symbol::name. commit bbee5bb8e68649b1bfe74896303342a82e0e8ac6 Author: Josh Stone <jistone@redhat.com> Date: Tue Jun 15 15:17:39 2010 -0700 PR3672: Auto-stringify char* and char[] * tapsets.cxx (dwarf_pretty_print::print_chars): New, if the referenced type looks like a C-string, dereference it as such. (dwarf_pretty_print::recurse_array): Try print_chars first. (dwarf_pretty_print::recurse_pointer): Ditto. * tapset/conversions.stp (kernel_string2): New, with error string. commit 3a147004a8d4988df864ecc9ac133577838136a6 Author: Josh Stone <jistone@redhat.com> Date: Mon Jun 14 17:18:43 2010 -0700 PR3672: don't print "_vptr.foo" members The only use I can think for the vtable pointer is to try to identify an instance's subclass, but I don't think that's useful in the general case. We might want to think about how to expose that for power users though, because our syntax doesn't allow "$p->_vptr.foo". * tapsets.cxx (dwarf_pretty_print::recurse_struct_members): Filter out members which start with "_vptr.foo". commit f8809d54b6819b6778d02051d2834003c0899f1b Author: Josh Stone <jistone@redhat.com> Date: Tue Jun 15 15:00:08 2010 -0700 Ensure synthetic functions get symbol resolution When writing the pretty-print functions, I had trouble because the referents weren't being automatically filled in. Rather than assigning them manually, this change now adds synthetic functions to the session in a way that they will get symbol resolution later. * elaborate.cxx (semantic_pass_symbols): Process probes before functions, in case synthetic functions are added to the file. * staptree.cxx (functiondecl::join): New, add a synthetic function to the session functions, and append it to the file's functions for later symbol resolution. * tapsets.cxx (dwarf_pretty_print::expand): Use fdecl->join to add the function to the session, and leave referents as default for later. (dwarf_pretty_print::deref): Ditto. (dwarf_var_expanding_visitor::visit_target_symbol): Ditto. (dwarf_cast_query::handle_query_module): Ditto. (tracepoint_var_expanding_visitor::visit_target_symbol_arg): Ditto. (tracepoint_var_expanding_visitor::visit_target_symbol_context): Ditto. * tapset-procfs.cxx (procfs_var_expanding_visitor::visit_target_symbol): Ditto. ----------------------------------------------------------------------- Summary of changes: elaborate.cxx | 48 ++++++------ parse.cxx | 16 ++-- staptree.cxx | 25 ++++-- staptree.h | 4 +- tapset-mark.cxx | 22 +++--- tapset-procfs.cxx | 36 ++++---- tapset-utrace.cxx | 26 +++--- tapset/conversions.stp | 18 ++++- tapsets.cxx | 203 +++++++++++++++++++++++++++--------------------- 9 files changed, 224 insertions(+), 174 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-06-16 1:41 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=20100616014113.11353.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).