Bug 2806 - Selecting certain processes under 'debug process' in druid throws errors
Summary: Selecting certain processes under 'debug process' in druid throws errors
Status: RESOLVED WORKSFORME
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Phil Muldoon
URL:
Keywords:
Depends on:
Blocks: 1553
  Show dependency tree / graph
 
Reported: 2006-06-19 18:40 UTC by Mike Cvet
Modified: 2006-08-24 00:11 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-06-19 18:40:34 UTC 
After selecting 'debug process' from the druid main window, depending on what
process it is (it appears random... race condition?) Frysk will either exit
without any notification, or display an error similar to the following.
Subsequent debug attempts after receiving an error result in similar behaviour.

{frysk.proc.LinuxTask@f26360,pid=30718,tid=30718,state=blockedContinue} in state
"BlockedSignal" did not handle handleDetach

frysk.proc.State.unhandled(FryskGui)
frysk.proc.TaskState.handleDetach(FryskGui)
frysk.proc.Task.performDetach(FryskGui)
frysk.proc.ProcState$Detaching.<init>(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 Phil Muldoon 2006-06-19 18:47:50 UTC 
I'll look into the gui disappearing (I suspect though a SIGSEGV). The trace
looks like an unhandled core state.
Comment 2 Phil Muldoon 2006-08-24 00:01:14 UTC 
Mike, as of 08/23 this no longer happens. Can you confirm?
Comment 3 Mike Cvet 2006-08-24 00:11:55 UTC 
Haven't seen these symptoms in over a month - closing!