In jython, once upon a time this would 'influence' all running threads:
def crash(): crash()
And this, too:
a =3D 'asdf' * 1024
print len(a) # optional
a =3D a + a
I don't know whether it has already been taken care of.
The problem was that jython does a java.lang.System.exit()
when it ran out of memory.
On Thursday 05 September 2002 05:58, Steve Yegge wrote:
> Yep, this is exactly what was happening. Good catch. Now
> that I realize this is the issue, it's trivial to fix.
> Thanks very much!
> Delaney, Timothy writes:
> > > From: Steve Yegge [mailto:stevey@...]
> > >
> > > I *really* need for all the errors to be thrown up to the
> > > caller. Can someone tell me:
> > >
> > > - is there some setting I can use to force this behavior?
> > >
> > > - if not, would someone kindly point me to the code I
> > > can tweak (in core/Py.java?) to hack it for myself?
> > Are you by any chance using threads? An exception thrown on a thread
> > will not propagate to the location where the thread was created (or
> > started) - it must be handled in the code in that thread.
> > Tim Delaney