Andrew Gallatin wrote:
>
> Daniel Eischen writes:
> > > > On further reflection, this DEFINITELY has to do with the work done on
> > > > npx(4)/signals/etc. in the past week. I _must_ be getting a GPF becau
se the
> > > > fpu state that it's attempting to restore is corrupt (i.e.: the contro
l word
> > > > is incorrect), so something is not being initialized somewhere that it
used
> > > > to be, or is being initialized incorrectly.
> > >
> > > The last few commits to machdep.c bother me, rev 1.539 in particular.
> > >
> > > If you are in a position to be able to quickly test it, it would be grea
t
> > > to know if backing out the last few changes fixes this, and which change
in
> > > particular.
> >
> > There have been two commits since 1.539; what version of machdep.c
> > is being used?
>
> 1.539 works. 1.540 crashes. The failure mode is:
My apologies, I meant 1.540 (really :-).
I suspect it might be time to give up and do the alternative sigtrap and
sigreturn.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message