Summary: | A rapidly exec'ing process on attach causes stack trace | ||
---|---|---|---|
Product: | frysk | Reporter: | Phil Muldoon <pmuldoon> |
Component: | general | Assignee: | Andrew Cagney <cagney> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | swagiaal |
Priority: | P1 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Bug Depends on: | 1500, 1988 | ||
Bug Blocks: | 1586, 1654 | ||
Attachments: | Very Simple Exec bomb |
Description
Phil Muldoon
2005-10-04 21:43:26 UTC
Created attachment 684 [details]
Very Simple Exec bomb
It seems that this just occurs at any time. The rapid Exec exposes it more rapidly than in normal usage. But in the sceanrio where an observer is added to "normal" process (ie ones that do not magnify troubling behaviour on a larger scale) these stack traces occur then too. Currently there does not have to be an exec observer attached to the PID for this to occur now (it occurs just on startup) Exception in thread "Thread-2" java.lang.RuntimeException: Linux{frysk.proc.LinuxTask@5b63c60,id={TaskId,9455},proc={frysk.proc.LinuxProc@5b2c820,id={ProcId,9455},state=running},state=unattached} in state "unattached" did not handle PerformExeced at frysk.proc.State.unhandled(java.lang.Object, java.lang.String) (/home/pmuldoon/workspace/frysk-gui/frysk/proc/State.java:70) at frysk.proc.TaskState.processPerformExeced(frysk.proc.Task) (/home/pmuldoon/workspace/frysk-gui/frysk/proc/TaskState.java:106) at frysk.proc.Task$19.execute() (/home/pmuldoon/workspace/frysk-gui/frysk/proc/Task.java:442) at frysk.event.EventLoop.runEventLoop(boolean) (/home/pmuldoon/workspace/frysk-gui/frysk/event/EventLoop.java:290) at frysk.event.EventLoop.run() (/home/pmuldoon/workspace/frysk-gui/frysk/event/EventLoop.java:384) at frysk.gui.FryskGui$3.run() (/home/pmuldoon/workspace/frysk-gui/frysk/gui/FryskGui.java:189) at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0) *** Bug 1500 has been marked as a duplicate of this bug. *** *** Bug 1988 has been marked as a duplicate of this bug. *** The exec observer now works okay. Changed Proc.java. |