On Mar 26, 2013, at 10:16 AM, David Smith <[email protected]> wrote: > Andrew, > > Have you had a chance to take a look at this?
Thanks for the reminder. It looks like we have a conflict of desires going on inside of Dyninst. The "isStopped" method returns true if the user explicitly requests the process to be stopped, but false if it stopped for some other reason (e.g. handling a signal). As a quick fix, can you just comment out the isStopped check in BPatch_process::oneTimeCode? The ProcControl layer will handle things appropriately. Drew -- 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
