[Bug dyninst/15049] stapdyn mishandling interrupts

["jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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

Josh Stone <jistone at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jistone at redhat dot com

--- Comment #1 from Josh Stone <jistone at redhat dot com> 2013-01-22 17:12:42 UTC ---
True, this needs more work, but bug 14665 is still open.

(In reply to comment #0)
> In the above case, stapdyn exits immediately. Let's give stapdyn something to
> run so it will hang around:

Yes, that should get fixed too.  That's part of why I was trying to get the
dyninst notification FD working (currently #if 0 in mutator::run) so we could
have a proper wait loop and break out in different ways, but it was failing for
me.

> Notice that even though I only interrupted stapdyn once, it complained of
> multiple interrupts and exited with a non-zero exit value (which might be
> related to bug #15029).

I was trying to be clever and give it a way out when truly stuck.  Like:
- 1st signal: pass the signal to the app and try to wait for it.
- 2nd signal: forget about the app, it's stuck, so just cleanup and quit.
- more signals: we must be stuck too, _exit().

But what happens here is the terminal CTRL-C gets sent to the whole process
group, including stap and stapdyn.  Then stap sends a signal to stapdyn too, so
now it has seen two.

So, this probably needs to be more clever.  Or less clever.  Suggestions
welcome.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.