| Summary: | Adding syscallobserver twice to a process kills frysk with no error | ||
|---|---|---|---|
| Product: | frysk | Reporter: | Mike Cvet <mcvet> |
| Component: | general | Assignee: | Sami Wagiaalla <swagiaal> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
| Bug Depends on: | |||
| Bug Blocks: | 1582, 1632 | ||
Error no longer happens - and can no longer add multiple observers of the same
type through Phil's patch:
Log message:
2006-08-26 Phil Muldoon <pmuldoon@redhat.com>
* SessionProcDataModel.java (addTask): set parent GuiProc.
* GuiTask.java (setParent): New.
(getParent): New.
* ObserversMenu.java (addGuiObject): Remove post
observer check.
(setCurrentProc): Disable observers in menu
the the Proc already has.
(setCurrentTask): Disable observers in menu
the the Task *and* the Proc already has.
|
If, in the mainwindow, you add a syscallobserver to a process, an error pops up: {frysk.proc.LinuxTask@1227840,pid=29502,tid=29502,state=running} in state "running" did not handle handleAddSyscallObserver frysk.proc.State.unhandled(FryskGui) frysk.proc.TaskState.handleAddSyscallObserver(FryskGui) frysk.proc.Task.handleAddSyscallObserver(FryskGui) frysk.proc.TaskSyscallObservation.handleAdd(FryskGui) frysk.proc.ProcState$3.handleAddObservation(FryskGui) frysk.proc.Proc.handleAddObservation(FryskGui) frysk.proc.Proc$7.execute(FryskGui) frysk.event.EventLoop.runEventLoop(FryskGui) frysk.event.EventLoop.run(FryskGui) frysk.gui.Gui$3.run(FryskGui) java.lang.Thread.run(libgcj.so.7) But if you try adding the syscallobserver a second time to any process, Frysk quits with no error