When calling the "Manager.host.requestCreateAttachedProc(cmd, new AttachedObserver());" method from the SourceWindowFactory the Linux core generates an unhandled exception error as follows: {frysk.proc.LinuxPtraceTask@12f60e0,pid=9905,tid=9905,state=StartMainTask.wantToAttachContinue} in state "StartMainTask.wantToAttachContinue" did not handle handleTerminatedEvent java.lang.RuntimeException: {frysk.proc.LinuxPtraceTask@12f60e0,pid=9905,tid=9905,state=StartMainTask.wantToAttachContinue} in state "StartMainTask.wantToAttachContinue" did not handle handleTerminatedEvent at frysk.proc.State.unhandled(State.java:70) at frysk.proc.TaskState.handleTerminatedEvent(TaskState.java:70) at frysk.proc.Task.processTerminatedEvent(Task.java:414) at frysk.proc.LinuxPtraceWaitBuilder.terminated(LinuxPtraceWaitBuilder.java:217) at frysk.sys.Wait.waitAllNoHang(Wait.cxx:276) at frysk.event.PollEventLoop$1$PollWaitOnSigChild.execute(PollEventLoop.java:277) at frysk.event.PollEventLoop.runEventLoop(PollEventLoop.java:339) at frysk.event.EventLoop.run(EventLoop.java:178) at frysk.gui.Gui$4.run(Gui.java:367) at java.lang.Thread.run(libgcj.so.7)
This was actually a problem with the GUI passing a file path to execvp with a space on the front of it.
The core shouldn't panic when the exec path is invalid though :-)
Still seeing this randomly. Here is another stacktrace: {frysk.proc.LinuxPtraceTask@1143e00,pid=32052,tid=32052,state=detached} in state "detached" did not handle handleTerminatedEvent java.lang.RuntimeException: {frysk.proc.LinuxPtraceTask@1143e00,pid=32052,tid=32052,state=detached} in state "detached" did not handle handleTerminatedEvent at frysk.proc.State.unhandled(State.java:70) at frysk.proc.TaskState.handleTerminatedEvent(TaskState.java:70) at frysk.proc.Task.processTerminatedEvent(Task.java:414) at frysk.proc.LinuxPtraceWaitBuilder.terminated(LinuxPtraceWaitBuilder.java:218) at frysk.sys.Wait.wait(Wait.cxx:568) at frysk.sys.Wait.waitAll(Wait.java:106) at frysk.event.WaitEventLoop.block(WaitEventLoop.java:83) at frysk.event.EventLoop.runEventLoop(EventLoop.java:380) at frysk.event.EventLoop.run(EventLoop.java:485) at frysk.gui.Gui$4.run(Gui.java:367) at java.lang.Thread.run(libgcj.so.7) This pops up *sometimes* shorty after a source window has been brought up that has been attached to a running bash process.
I can no longer reproduce this. It appears to be fixed.