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-222-g7b8548e
- From: jistone at sourceware dot org
- To: systemtap-cvs at sourceware dot org
- Date: 7 Jun 2010 20:40:30 -0000
- Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-222-g7b8548e
- 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 7b8548ee9fa40d47438f1dfe945b451b3749aa5c (commit)
via 58701b785126dfe1fa75049a11b68ec6ac07b55d (commit)
via 60bebf58e032c417fff238d200f81964d10d1cc6 (commit)
via 015f9b165a84e6be84f2e56c8ccb970210b27083 (commit)
via 3c03b01b666b8d395038b993a02fd7c65efd6075 (commit)
from edc3c5b1d4a69fbf8714249c93f4964187acf449 (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 7b8548ee9fa40d47438f1dfe945b451b3749aa5c
Author: Josh Stone <jistone@redhat.com>
Date: Mon Jun 7 13:28:58 2010 -0700
Guard embeddedcode_info_pass from failures
We should not run this pass if there were previous errors, as
functioncall_traversing_visitor require referents on all calls. Fixes
a segfault in semko/five.stp after an arg-count mismatch, as well as the
new semko/nofunc.stp with a completely missing function.
* elaborate.cxx (semantic_pass): Only do embeddedcode_info_pass if !rc.
* testsuite/semko/nofunc.stp: New, as I couldn't find such a test.
commit 58701b785126dfe1fa75049a11b68ec6ac07b55d
Author: Josh Stone <jistone@redhat.com>
Date: Mon Jun 7 13:14:37 2010 -0700
Improve identification of arity-mismatch errors
Instead of pointing at the declaration site, we now finger the use which
is trying to set a bad arity, and also mention who originally set the
arity if possible. For example, semok/six.stp now says:
semantic error: inconsistent arity (1 vs. 2): identifier 'bar' at ../testsuite/semko/six.stp:6:3
source: bar[1, 2] = 3; # inconsistent array dimensions
^
semantic error: arity 1 first inferred here: identifier 'bar' at :5:3
source: bar[1] = 2;
^
* staptree.cxx (vardecl::set_arity): Require a token from the caller,
and report the original caller's token as well.
* elaborate.cxx (symresolution_info::visit_symbol): Pass the token.
(symresolution_info::find_var): Ditto.
* parse.cxx (parser::parse_global): Ditto.
* tapset-mark.cxx (mark_derived_probe::mark_derived_probe): Ditto.
* tapset-utrace.cxx
(utrace_var_expanding_visitor::visit_target_symbol_cached): Ditto.
* tapsets.cxx (tracepoint_derived_probe::tracepoint_derived_probe):
Ditto.
commit 60bebf58e032c417fff238d200f81964d10d1cc6
Author: Josh Stone <jistone@redhat.com>
Date: Mon Jun 7 12:58:00 2010 -0700
Never permit homonymous vars with different arity
It was previously possible to generate a global array and local scalar
having the same name, because find_var was glossing over globals that
didn't have compatible_arity.
Fixes semko/nine, and improves semko/six to an arity-mismatch error
rather than a local-array error.
* elaborate.cxx (symresolution_info::find_var): Use set_arity without
checking compatibile_arity, so that compatibility gets asserted.
(symresolution_info::visit_foreach_loop): Add "missing global" hint.
(symresolution_info::visit_arrayindex): Don't create local arrays.
commit 015f9b165a84e6be84f2e56c8ccb970210b27083
Author: Josh Stone <jistone@redhat.com>
Date: Mon Jun 7 12:02:43 2010 -0700
Fork semko/two.stp into distinct errors
Now two.stp checks the failure of integer+string, and twotwo.stp checks
that stats can't be a function arg. Both need -u to defeat optimization.
commit 3c03b01b666b8d395038b993a02fd7c65efd6075
Author: Josh Stone <jistone@redhat.com>
Date: Mon Jun 7 11:53:12 2010 -0700
Use real probepoints in semko/two-ten
These tests were using non-existent probepoints (foo,p1,p2), leading to
an error that masks the real failure we're trying to test.
(A few were actually broken -- commits to follow...)
-----------------------------------------------------------------------
Summary of changes:
elaborate.cxx | 52 ++++++++++++------------------
parse.cxx | 2 +-
staptree.cxx | 17 ++++++++--
staptree.h | 3 +-
tapset-mark.cxx | 2 +-
tapset-utrace.cxx | 2 +-
tapsets.cxx | 2 +-
testsuite/semko/eight.stp | 3 +-
testsuite/semko/five.stp | 2 +-
testsuite/semko/four.stp | 2 +-
testsuite/semko/nine.stp | 2 +-
testsuite/semko/nofunc.stp | 5 +++
testsuite/semko/seven.stp | 2 +-
testsuite/semko/six.stp | 2 +-
testsuite/semko/ten.stp | 4 +-
testsuite/semko/three.stp | 2 +-
testsuite/semko/two.stp | 7 +---
testsuite/semko/{two.stp => twotwo.stp} | 6 ++--
18 files changed, 61 insertions(+), 56 deletions(-)
create mode 100755 testsuite/semko/nofunc.stp
copy testsuite/semko/{two.stp => twotwo.stp} (51%)
hooks/post-receive
--
systemtap: system-wide probe/trace tool