Re: [BProc] another 3.2.0 oops

[<er...@he...>]

On Wed, Oct 23, 2002 at 02:17:57PM -0400, Nicholas Henke wrote:
> On Wed, 23 Oct 2002 13:32:42 -0400
> er...@he... wrote:
> 
> > On Mon, Oct 21, 2002 at 10:06:44AM -0400, Nicholas Henke wrote:
> > > Hrm -- I seems to be breaking things again. The following oops
> > > occurred running my 'noop' script again -- the ps script is that
> > > script, just remove the bpsh $node ps line. I have seen this oops
> > > twice so far -- the Code: was the same in both. If the trace is
> > > bogus, I would _really_ appreciate any pointers you could give me to
> > > get better traces for you. 
> > 
> > Ok, here we go again.  I saw an oops.  It might be the oops you saw.
> > I think the odds are decent that it's the same one.  I fixed it (I
> > think) and the slave nodes that were crashing with your script don't
> > seem to be crashing anymore.  So give this one a whirl and let me know
> > how it goes.
> > 
> > You can either try the patch (for kernel/slave.c) included in this
> > email (in addition to all the other ones).  Or just grab BProc 3.2.2
> > which I just threw up on SourceForge.  Oh, and I fixed that silly
> > VERSION:= build problem.
> 
> Sounds good -- btw, do you have any updated docs for the bproc_* C api?
> I am working on a python wrapper for the newer calls.

I'm afraid not.  Feel free to ask questions if the examples in things
like bpsh and mpirun are insufficient.

- Erik