Bug 1832 - unblock a running process is not handled
Summary: unblock a running process is not handled
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on:
Blocks: 1553
  Show dependency tree / graph
 
Reported: 2005-11-08 22:58 UTC by Sami Wagiaalla
Modified: 2006-11-22 17:04 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sami Wagiaalla 2005-11-08 22:58:12 UTC 
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
Comment 1 Andrew Cagney 2005-11-11 05:13:44 UTC 
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
Comment 2 Andrew Cagney 2005-11-23 03:06:51 UTC 
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.