summaryrefslogtreecommitdiffstats
path: root/tapset-utrace.cxx
diff options
context:
space:
mode:
authorJosh Stone <jistone@redhat.com>2010-04-07 16:41:41 -0700
committerJosh Stone <jistone@redhat.com>2010-04-07 16:46:57 -0700
commit1af1e62d9f67237277dd771a0cb78fa6b069742d (patch)
tree7a168a6caf1649dfe2ea470d43972c65619a06ad /tapset-utrace.cxx
parentea1e477a78969d44aeea51cfc3cbd2e8ed96cfe4 (diff)
downloadsystemtap-steved-1af1e62d9f67237277dd771a0cb78fa6b069742d.tar.gz
systemtap-steved-1af1e62d9f67237277dd771a0cb78fa6b069742d.tar.xz
systemtap-steved-1af1e62d9f67237277dd771a0cb78fa6b069742d.zip
Clean up and clarify semantic_error chaining
I consolidated the copy-construction that every target_symbol::chain caller was doing. I also removed the comments that target_symbol errors might be chained due to function wildcards, because it's not true -- each derived instance gets a deep_copy of the probe body. However, @cast can still chain since it may try multiple modules to resolve the casting dereference.
Diffstat (limited to 'tapset-utrace.cxx')
-rw-r--r--tapset-utrace.cxx2
1 files changed, 1 insertions, 1 deletions
diff --git a/tapset-utrace.cxx b/tapset-utrace.cxx
index 25e0b15e..8e2573ab 100644
--- a/tapset-utrace.cxx
+++ b/tapset-utrace.cxx
@@ -601,7 +601,7 @@ utrace_var_expanding_visitor::visit_target_symbol (target_symbol* e)
}
catch (const semantic_error &er)
{
- e->chain (new semantic_error(er));
+ e->chain (er);
provide(e);
return;
}