[Bug dyninst/15049] stapdyn mishandling interrupts

[jistone at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=15049

--- Comment #2 from Josh Stone <jistone at redhat dot com> ---
Commits 6d27dcff and 63f4648b have improved the situation somewhat.  The
no-command case will now wait around for a signal or script exit(), just as
kernel mode does.  With a command, it should be a little better, but there's an
issue that Dyninst is squashing SIGINTs to mutatees.

https://lists.cs.wisc.edu/archive/dyninst-api/2013/msg00113.shtml

I've tested a patch so that PCEventHandler::shouldStopForSignal() doesn't count
SIGINT, and that seems to be much better.  I'll send that with justification to
dyninst-api and see what they think, and then this bug may be resolved.

-- 
You are receiving this mail because:
You are the assignee for the bug.