From 36b155fa54b96e8f71b8c0997a4de76738de0338 Mon Sep 17 00:00:00 2001 From: "Frank Ch. Eigler" Date: Fri, 6 Nov 2009 20:57:55 -0500 Subject: expand comment on has_return=0 treatment of -L foo.return probes --- tapsets.cxx | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'tapsets.cxx') diff --git a/tapsets.cxx b/tapsets.cxx index 59598cf3..d20c0ab1 100644 --- a/tapsets.cxx +++ b/tapsets.cxx @@ -2901,9 +2901,13 @@ dwarf_derived_probe::saveargs(dwarf_query& q, Dwarf_Die* scope_die, dwarf_var_ex dwarf_type_name(&type_die, type_name)) args.insert("$return:"+type_name); - /* Pretend that we aren't in a .return for a moment, just so we can check - * whether variables are accessible. We don't want to all the entry-saving - * code generated during listing mode. */ + /* Pretend that we aren't in a .return for a moment, just so we can + * check whether variables are accessible. We don't want to all the + * entry-saving code generated during listing mode. This works + * because the set of $context variables available in a .return + * probe (apart from $return) is the same set as available for the + * corresponding .call probe, since we collect those variables at + * .call time. */ bool saved_has_return = has_return; q.has_return = has_return = false; -- cgit