Bug 2970 - frysk.proc.LinuxTask in state "BlockedSignal" did not handle handleDeleteObserver
Summary: frysk.proc.LinuxTask in state "BlockedSignal" did not handle handleDeleteObse...
Status: WAITING
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 1552
  Show dependency tree / graph
 
Reported: 2006-07-27 20:40 UTC by Mike Cvet
Modified: 2007-07-10 09:42 UTC (History)
2 users (show)

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 Mike Cvet 2006-07-27 20:40:20 UTC 
If you have the "show memory" and "show registers" actions attached to a process
on an event and these windows come up; x-ing these two windows brings up this
error; when the process that they are both observing should become unblocked and
continue.

{frysk.proc.LinuxTask@1087e40,pid=11431,tid=11431,state=BlockedSignal,sig=0} in
state "BlockedSignal" did not handle handleDeleteObserver

frysk.proc.State.unhandled(FryskGui)
frysk.proc.TaskState.handleDeleteObserver(FryskGui)
frysk.proc.Task.handleDeleteObserver(FryskGui)
frysk.proc.TaskObservation.handleDelete(FryskGui)
frysk.proc.ProcState$3.handleDeleteObservation(FryskGui)
frysk.proc.Proc$8.execute(FryskGui)
frysk.event.EventLoop.runEventLoop(FryskGui)
frysk.event.EventLoop.run(FryskGui)
frysk.gui.Gui$4.run(FryskGui)
java.lang.Thread.run(libgcj.so.7)
Comment 1 Mark Wielaard 2007-07-10 09:42:57 UTC 
This should have been fixed a long time ago when bug #3571 was fixed:

2006-12-06  Mark Wielaard  <mark@klomp.org>

        Fixes bug #3571
        * frysk-core/frysk/proc/TestTaskObserverInstruction.java: Don't
        explicitly unblock before deletion of observer.
        * LinuxPtraceTaskState.java (BlockedSignal.handleDeleteObservation):
        Explicitly unblock observer.