Summary: | LinuxPtraceTask aborts when trying to activate a new Proc from Source Window | ||
---|---|---|---|
Product: | frysk | Reporter: | Rick Moseley <rmoseley> |
Component: | general | Assignee: | Unassigned <frysk-bugzilla> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Bug Depends on: | |||
Bug Blocks: | 4193 |
Description
Rick Moseley
2007-04-11 18:02:52 UTC
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. |