Corefile Actions and ProcBlockActions

Corefile Actions and ProcBlockActions

[Nurdin Premji]

I have created branch npremji-procblockaction-20070506-branch.
On this branch will be a refactoring of ProcBlockAction to take a 
ProcObserver interface with two methods existingTask() and 
allExistingTasksCompleted() (so maybe a ProcObserver.ProcAction 
extension to the interface) rather than an event. This will clear up 
some circular dependencies with trying to use the same StacktraceAction 
for a corefile proc and a live/ptrace proc. Additionally a 
ProcCoreAction with the same interface will be created.

This will mean that StacktraceAction will change from being an "is a" 
relation to a ProcBlockAction to ProcBlockAction having a "has a" 
relation with a ProcObserver(.ProcAction). Similar changes will be done 
to any class extending ProcBlockAction.

Re: Corefile Actions and ProcBlockActions

[Nurdin Premji]

Nurdin Premji wrote:
> I have created branch npremji-procblockaction-20070506-branch.
> On this branch will be a refactoring of ProcBlockAction to take a 
> ProcObserver interface with two methods existingTask() and 
> allExistingTasksCompleted() (so maybe a ProcObserver.ProcAction 
> extension to the interface) rather than an event. This will clear up 
> some circular dependencies with trying to use the same 
> StacktraceAction for a corefile proc and a live/ptrace proc. 
> Additionally a ProcCoreAction with the same interface will be created.
>
> This will mean that StacktraceAction will change from being an "is a" 
> relation to a ProcBlockAction to ProcBlockAction having a "has a" 
> relation with a ProcObserver(.ProcAction). Similar changes will be 
> done to any class extending ProcBlockAction.
Branch has been merged.
So now StacktraceAction and CoredumpAction are independent of the type 
of Proc they are running on (running ptrace Proc or dead corefile Proc). 
To actually get the action to run it must be added to the proc with one 
of ProcBlockAction or ProcCoreAction.