From c3add01f692e698995a62c13e154bab35d9212df Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Mon, 9 Mar 2009 17:23:05 -0700 Subject: Update location of c->probe_point reset The probe_point clear was nested in the overload processing code, I believe accidentally. This just makes it always cleared on probe exit. --- tapsets.cxx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tapsets.cxx b/tapsets.cxx index d99eebe2..18bd75f5 100644 --- a/tapsets.cxx +++ b/tapsets.cxx @@ -300,7 +300,6 @@ common_probe_entryfn_epilogue (translator_output* o, o->newline() << "c->cycles_base = cycles_atend;"; o->newline() << "c->cycles_sum = 0;"; - o->newline() << "c->probe_point = 0;"; // vacated o->newline(-1) << "}"; o->newline(-1) << "}"; o->newline() << "#endif"; @@ -309,6 +308,7 @@ common_probe_entryfn_epilogue (translator_output* o, o->newline(-1) << "}"; o->newline() << "#endif"; + o->newline() << "c->probe_point = 0;"; // vacated o->newline() << "if (unlikely (c->last_error && c->last_error[0])) {"; o->newline(1) << "if (c->last_stmt != NULL)"; o->newline(1) << "_stp_softerror (\"%s near %s\", c->last_error, c->last_stmt);"; -- cgit