| Summary: | Selecting certain processes under 'debug process' in druid throws errors | ||
|---|---|---|---|
| Product: | frysk | Reporter: | Mike Cvet <mcvet> |
| Component: | general | Assignee: | Phil Muldoon <pmuldoon> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | ajocksch, cagney |
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
| Bug Depends on: | |||
| Bug Blocks: | 1553 | ||
I'll look into the gui disappearing (I suspect though a SIGSEGV). The trace looks like an unhandled core state. Mike, as of 08/23 this no longer happens. Can you confirm? Haven't seen these symptoms in over a month - closing! |
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)