This is the mail archive of the
frysk@sourceware.org
mailing list for the frysk project.
Re: Corefile Actions and ProcBlockActions
- From: Nurdin Premji <npremji at redhat dot com>
- To: frysk <frysk at sources dot redhat dot com>
- Date: Thu, 07 Jun 2007 10:53:40 -0400
- Subject: Re: Corefile Actions and ProcBlockActions
- References: <46659D34.5020606@redhat.com>
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.