Bug 3878 - {frysk.proc.LinuxPtraceTask@3b7cc42d,pid=21926,tid=21925,state=detached} in state "detached" did not handle handleStoppedEvent
Summary: {frysk.proc.LinuxPtraceTask@3b7cc42d,pid=21926,tid=21925,state=detached} in s...
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-17 13:58 UTC by Mike Cvet
Modified: 2008-04-17 21:42 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 Mike Cvet 2007-01-17 13:58:47 UTC 
Came across this one when directly instantiating the Source Window from the 
command line rather than from the session manager. Occurs when the window is 
attempting to block the process by adding an instruction observer.

{frysk.proc.LinuxPtraceTask@3b7cc42d,pid=21926,tid=21925,state=detached} in 
state "detached" did not handle handleStoppedEvent

frysk.proc.State.unhandled(FryskGui)
frysk.proc.TaskState.handleStoppedEvent(FryskGui)
frysk.proc.Task.processStoppedEvent(FryskGui)
frysk.proc.LinuxPtraceHost$PollWaitOnSigChld$5.stopped(FryskGui)
frysk.sys.Wait.waitAllNoHang(FryskGui)
frysk.proc.LinuxPtraceHost$PollWaitOnSigChld.execute(FryskGui)
frysk.event.EventLoop.runEventLoop(FryskGui)
frysk.event.EventLoop.run(FryskGui)
frysk.gui.Gui$5.run(FryskGui)
java.lang.Thread.run(libgcj.so.7rh)
Comment 1 Mark Wielaard 2007-01-17 14:10:35 UTC 
Mine
Comment 2 Andrew Cagney 2007-01-22 23:08:42 UTC 
I'm pretty sure this is a "can't happen", shouldn't have reached the detached state.
Comment 3 Mark Wielaard 2008-04-17 21:42:13 UTC 
This might or might not be related to bug #4059 where we are seeing spurious
stop events.