Bug 5800 - in state "destroyed" did not handle handleRemoval
Summary: in state "destroyed" did not handle handleRemoval
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 1582
  Show dependency tree / graph
 
Reported: 2008-02-28 14:46 UTC by Sami Wagiaalla
Modified: 2008-10-21 21:40 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sami Wagiaalla 2008-02-28 14:46:55 UTC 
start frysk gui and wait. Crash is much faster if there is a build running in
the background

{frysk.proc.live.LinuxPtraceProc@32b95245,pid=9641,state=destroyed} in state
"destroyed" did not handle handleRemoval

java.lang.RuntimeException:
{frysk.proc.live.LinuxPtraceProc@32b95245,pid=9641,state=destroyed} in state
"destroyed" did not handle handleRemoval
   at frysk.proc.live.State.unhandled(FryskGui)
   at frysk.proc.live.LinuxPtraceProcState.handleRemoval(FryskGui)
   at frysk.proc.live.LinuxPtraceProc$2.execute(FryskGui)
   at frysk.event.EventLoop.runEventLoop(FryskGui)
   at frysk.event.EventLoop.run(FryskGui)
   at frysk.gui.Gui$5.run(FryskGui)
   at java.lang.Thread.run(libgcj.so.8rh)
Comment 1 Mark Wielaard 2008-03-13 21:16:09 UTC 

*** This bug has been marked as a duplicate of 2621 ***
Comment 2 Andrew Cagney 2008-03-18 20:00:19 UTC 
Un-duping, just working on this case.