Bug 1526 - frysk.proc.TaskObserver.Attached doesn't work
Summary: frysk.proc.TaskObserver.Attached doesn't work
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on: 1376 1426
Blocks: 1553 1364
  Show dependency tree / graph
 
Reported: 2005-10-22 18:48 UTC by Andrew Cagney
Modified: 2006-11-22 17:04 UTC (History)
2 users (show)

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 Andrew Cagney 2005-10-22 18:48:55 UTC 
Currently not defined, called when a task is first started, needed because a
task needs to transition through a number of states the tasks contents can be
accessed.
Comment 1 Andrew Cagney 2005-10-22 19:45:15 UTC 
The name .Started has been changed to .Attached; the observer is fired both when
a new task is initialized, and when an existing task is attatched.  In both
cases the task is ready and able to be queried (fetch memory et.al.)

A better name is needed.

2005-10-22  Andrew Cagney  <cagney@redhat.com>

        * Proc.java: Delete .taskDiscovered.
        * TaskObservable.java: Delete, merged into Proc.java.
        * TaskObserver.java: Add .Attached.
        * TaskState.java: Replace Proc .taskDiscovered, with Task
        .notifyAttached.
        * Task.java: Update; add .notifyAttached.
Comment 2 Andrew Cagney 2005-10-26 22:02:16 UTC 
Index: frysk-core/frysk/proc/ChangeLog
2005-10-26  Andrew Cagney  <cagney@redhat.com>

        * TestTaskObserver.java: New.
        * TaskState.java: Handle .processRequestAddObserver in "running"
        state.

but it still needs a better name :-)