This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Patch/Design communication (Re: frysk-core/frysk util/TestFStack.java util/Sta ...)
- From: Mark Wielaard <mark at klomp dot org>
- To: frysk at sourceware dot org
- Date: Mon, 18 Dec 2006 12:24:28 +0100
- Subject: Patch/Design communication (Re: frysk-core/frysk util/TestFStack.java util/Sta ...)
- References: <20061215205132.22259.qmail@sourceware.org>
Hi,
On Fri, 2006-12-15 at 20:51 +0000, npremji@sourceware.org wrote:
> Log message:
> frysk-core/frysk/bindir/CL
> * fcore.java: Reverted ProcException addition.
> * fstack.java: Ditto.
> frysk-core/frysk/util/CL
> * StacktraceAction.java: Revert ProcException.
> * CoredumpAction.java: Ditto.
> * TestFStack.java: Ditto.
> * TestFCore.java: Ditto.
> frysk-core/frysk/proc/CL
> * ProcException.java: Removed.
> * ProcBlockAction.java: Reverted ProcException.
> * TestProcForceDetach: Ditto.
> * TestProcStopped: Ditto.
What was the intention of the addition and subsequent removal of this?
If I understood the code correctly we could be handed a null proc or a
proc that we don't control/own. Where/How is this dealt with now?
This isn't specific to this patch btw. I hope that we can in general
discuss more of the design decisions on the main mailinglist. I try to
read all commit messages, but just going over each patch does not always
give me insight into the higher level debate that must have gone on for
some of the changed.
Cheers,
Mark