| Summary: | unblock a running process is not handled | ||
|---|---|---|---|
| Product: | frysk | Reporter: | Sami Wagiaalla <swagiaal> |
| Component: | general | Assignee: | Andrew Cagney <cagney> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P1 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
| Bug Depends on: | |||
| Bug Blocks: | 1553 | ||
Two potential bugs: - the task was running and was sent a redundant RequestUnblock - the task was in the running state, but should have been in the blocked state Index: frysk-core/frysk/proc/ChangeLog 2005-11-22 Andrew Cagney <cagney@redhat.com> * TaskState.java: In .running state, handle processRequestUnblock. * TestTaskObserverBlocked.java: Add testUnblockRunning. BTW, I wonder if the observer should be sent a message noteing that the operation is bogus (the blocked set is empty), ditto for case where the observer wasn't in the blocked set. |
Exception in thread "Thread-2" Reaped unknown child pid = 5938 java.lang.RuntimeException: Linux{frysk.proc.LinuxTask@132dcd0,id={TaskId,5620},proc={frysk.proc.LinuxProc@461f8,id={ProcId,5620},state=running},state=running} in state "running" did not handle RequestUnblock