On Feb 25, 2013, at 1:17 PM, David Smith <[email protected]> wrote: > This works great for thread creation probes (for instance), but not for > exit probes. When the exit callback happens, I call stopExecution(). > However, when stopExecution() returns, the process has already > terminated, so I can't call oneTimeCode().
Is there any way you can call the oneTimeCode directly from the callback? The thread should still be present, if wrapping itself up, when the callback is delivered. There is an inherent race condition if something else is continuing the entire process but it doesn't sound like that's happening here. Drew > For now we're just calling the systemtap exit probe from the mutator, so > it happens at the right time, but with the wrong context. > > Can anyone think of a way around this? > > Thanks for the help. > > -- > David Smith > [email protected] > Red Hat > http://www.redhat.com > 256.217.0141 (direct) > 256.837.0057 (fax) > _______________________________________________ > Dyninst-api mailing list > [email protected] > https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api -- Andrew Bernat Paradyn Project [email protected] http://www.cs.wisc.edu/~bernat
_______________________________________________ Dyninst-api mailing list [email protected] https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api
