Bug 1500 - frysk crashes on a process exec'ing even though an exec observer is not applied
Summary: frysk crashes on a process exec'ing even though an exec observer is not applied
Status: RESOLVED DUPLICATE of bug 1418
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on:
Blocks: 1418
  Show dependency treegraph
 
Reported: 2005-10-19 14:18 UTC by Phil Muldoon
Modified: 2006-11-21 16:23 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Phil Muldoon 2005-10-19 14:18:57 UTC
Frysk crashes when an exec occurs in a process that it is attached to. Whether
an taskExec observer is applied does not matter. Whether any observer applied
does not matter. When that process execs, the following stack trace is dumped:

INFO: PID 4685 Host XXX Attached
Exception in thread "Thread-2" java.lang.RuntimeException: Linux{frysk.proc.Linu
xTask@6545450,id={TaskId,4685},proc={frysk.proc.LinuxProc@651a820,id={ProcId,468
5},state=running},state=unattached} in state "unattached" did not handle Perform
Execed
   at frysk.proc.State.unhandled(java.lang.Object, java.lang.String) (/home/pmul
doon/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/pro
c/Task.java:442)
   at frysk.event.EventLoop.runEventLoop(boolean) (/home/pmuldoon/workspace/frys
k-gui/frysk/event/EventLoop.java:290)
   at frysk.event.EventLoop.run() (/home/pmuldoon/workspace/frysk-gui/frysk/even
t/EventLoop.java:384)
   at frysk.gui.FryskGui$3.run() (/home/pmuldoon/workspace/frysk-gui/frysk/gui/F
ryskGui.java:189)
   at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0)
Comment 1 Andrew Cagney 2005-12-11 16:58:12 UTC
The bug here is that an attached task has got into the <<unattached>> state; not
that the <<unattached>> state can't handle an <<exec>> event.


*** This bug has been marked as a duplicate of 1418 ***