This is the mail archive of the
systemtap-cvs@sourceware.org
mailing list for the systemtap project.
[SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-117-gf3b5366
- From: jistone at sourceware dot org
- To: systemtap-cvs at sourceware dot org
- Date: 6 May 2010 03:25:12 -0000
- Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-117-gf3b5366
- Reply-to: systemtap at sourceware dot org
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 f3b5366d0a5d6c746eaf5e7596e3c439c48c2f51 (commit)
via 6ce303b8edeb90514f7423bebc95fcee21414ce0 (commit)
from 2adaeba8931bf46916f1d3529fefd35b716a31ff (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 f3b5366d0a5d6c746eaf5e7596e3c439c48c2f51
Author: Josh Stone <jistone@redhat.com>
Date: Wed May 5 16:47:19 2010 -0700
PR11556: Support array indexing on @cast pointers
It's a bit of a special case, because we don't have a pointer DIE for
the named type in @cast expressions. However, we can read the element
size manually and still simulate an array access.
* loc2c.c (pointer_stride): New, factored out of array_stride.
(c_translate_array_pointer): New, performs the pointer math based on
the element size of the pointee type.
* dwflpp.cxx (dwflpp::translate_components): Take a starting component.
(dwflpp::literal_stmt_for_pointer): If the initial type is not already
a pointer or array, we can fake an array access on the input pointer.
* testsuite/semok/cast.stp: Add an array access test on a @cast.
* testsuite/systemtap.base/cast.stp: Ditto.
* testsuite/systemtap.base/cast.exp: Ditto.
commit 6ce303b8edeb90514f7423bebc95fcee21414ce0
Author: Josh Stone <jistone@redhat.com>
Date: Wed May 5 15:52:55 2010 -0700
Straighten out die/attr use in dwflpp translation
It was confusing (to me) what was the expected state of each die_mem and
attr_mem passed around in dwflpp translation. I've changed it now so
that we pass just a vardie and typedie, which I think is clearer. This
is also nicer for @cast where we don't have any attr for the initial
type.
* dwflpp.cxx (dwarf_die_type): Helper to get the type, throw on error.
(dwflpp::translate_components): Just update a vardie and typedie.
(dwflpp::translate_final_fetch_or_store): Use a vardie and typedie.
(dwflpp::resolve_unqualified_inner_typedie): Update dies, not attrs.
(dwflpp::literal_stmt_for_local): Update calls to above.
(dwflpp::literal_stmt_for_return): Ditto.
(dwflpp::literal_stmt_for_pointer): Ditto.
-----------------------------------------------------------------------
Summary of changes:
dwflpp.cxx | 236 +++++++++++++++++--------------------
dwflpp.h | 26 ++--
loc2c.c | 83 +++++++++----
loc2c.h | 6 +
testsuite/semok/cast.stp | 3 +
testsuite/systemtap.base/cast.exp | 1 +
testsuite/systemtap.base/cast.stp | 7 +
7 files changed, 198 insertions(+), 164 deletions(-)
hooks/post-receive
--
systemtap: system-wide probe/trace tool