Subject: Re: Signal catching changes broke Matlab
To: None <firstname.lastname@example.org>
From: Nathan J. Williams <email@example.com>
Date: 09/27/2004 18:20:04
Thor Lancelot Simon <firstname.lastname@example.org> writes:
> On Mon, Sep 27, 2004 at 08:30:31PM +0200, Jaromir Dolecek wrote:
> > Christos Zoulas wrote:
> > > It is not the masking of SIGSEGV... It is a more subtle thing,
> > > because linux behaves the same way. Anyway the change should
> > > not be backed out because it will make SEGV processes spin again,
> > > but we should investigate why side-effect it is causing.
> > The spinning is not a severe problem - such app can easily be killed
> > manually. Since the change broke some real-world apps and we want
> The spinning may break real-world apps. I can think of a certain
> commercial LISP interpreter that catches SEGV... will reverting this
> change break PVS et. al again to fix Matlab? Six of one, half a dozen
> of the other!
The spinning occurred when a process that had SEGV masked generated
another SEGV. I don't believe that just catching SEGV was affected.