Specific session config = exception, defunct FryskGui process, hung bash processes I know the GUI is in a state of flux, but this bug seems especially noteworthy. If you create a new debug session though the Druid that results in a $HOME/.frysk/Sessions file that contains the data included in the attachment, the results are: 1) A dialog box with this exception: Frysk Core has reported the following errors null frysk.proc.LinuxTask.sendAttach (FryskGui) frysk.proc.TaskState$1.handleAttach (FryskGui) frysk.proc.Task.performAttach (FryskGui) frysk.proc.ProcState$Attaching.initialState (FryskGui) frysk.proc.ProcState$1.handleAddObservation (FryskGui) frysk.proc.Proc.handleAddObservation (FryskGui) frysk.proc.Proc$6.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) 2) The FryskGui process is defunct: ldimaggi 3418 3374 4 11:30 pts/1 00:00:03 [FryskGui] <defunct> 3) Any bash processes on the system are hung. (Note that bash is one of the processes being observed by the session object that we created.) Best of all - the bug was found by one of the - still incomplete - Dogtail tests (http://sources.redhat.com/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/test/dogtail_scripts/TestDruid.py?cvsroot=frysk)
Created attachment 1072 [details] The session config to cause the bug
This is because (I suspect) that Frysk UI is attaching Frysk UI and shooting itself in the proverbial foot. One should never attach to the Frysk UI that is running. Short term solution here is to filter our FryskGUI as an available attach in the Druid and also in the source window.