[Bug general/4298] New: Unexplained "BlockedSignal" did not handle handleRemoval

["mark at klomp dot org" <sourceware-bugzilla at sourceware dot org>]

Mike Cvet reported the following in bug #3705:

{frysk.proc.LinuxPtraceTask@3967ceb5,pid=26079,tid=26079,state=blockedContinue} 
in state "BlockedSignal" did not handle handleRemoval

frysk.proc.State.unhandled(FryskGui)
frysk.proc.TaskState.handleRemoval(FryskGui)
frysk.proc.Task.performRemoval(FryskGui)
frysk.proc.LinuxPtraceProc.sendRefresh(FryskGui)
frysk.proc.LinuxPtraceHost.sendRefresh(FryskGui)
frysk.proc.LinuxPtraceHostState$1.handleRefresh(FryskGui)
frysk.proc.Host$1.execute(FryskGui)
frysk.event.EventLoop.runEventLoop(FryskGui)
frysk.event.EventLoop.run(FryskGui)
frysk.gui.Gui$3.run(FryskGui)
java.lang.Thread.run(libgcj.so.7rh)

This should not happen (tm).
This means a task got killed and disappeared while we thought it we got it
blocked. We only handle such a case if we are in the detached state.

-- 
           Summary: Unexplained "BlockedSignal" did not handle handleRemoval
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: mark at klomp dot org
                CC: mcvet at redhat dot com


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

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