On Fri, 25 Oct 2002 03:43:03 -0700
Juli Mallett <[EMAIL PROTECTED]> wrote:
> FWIW, this fixes every reproducable hang I've had with X and related.
AOL
Bye,
Alexander.
--
The dark ages were caused by the Y1K problem.
http://www.Leidinger.net Alexander @ Leidin
I can also confirm that my X server has been rock solid since applying the
patch.
I think Bruce deserves a lollipop.
Juli Mallett <[EMAIL PROTECTED]> wrote:
>
> * De: Bruce Evans <[EMAIL PROTECTED]> [ Data: 2002-10-24 ]
> [ Subjecte: Re: Floating point problems ]
&g
* De: Bruce Evans <[EMAIL PROTECTED]> [ Data: 2002-10-24 ]
[ Subjecte: Re: Floating point problems ]
> Thanks. This makes the main bug clear. The PCB_NPXINITDONE bit in the
> state was not being restored. This was confusing to debug because gdb
> doesn't understand
Well, that's certainly fixed the problems my test app had.
As for X:
I was regularly able to hurt X by clicking randomly on the "transfers"
window in Opera, and switching between it and other internal frames:
symptoms included SEGVs, minute-long hangs, etc. Invoking such rain-dances
failed to pro
On Thu, 24 Oct 2002, Peter Edwards wrote:
> There was some discussion about issues with interactions between the floating
> point context and signal handling in a thread a week or so ago, and a suggestion
> that someone try and get a simple test that would fail. I was surprised how
> easy it was:
Hi,
There was some discussion about issues with interactions between the floating
point context and signal handling in a thread a week or so ago, and a suggestion
that someone try and get a simple test that would fail. I was surprised how
easy it was: The following program just spins calculating
On 8 Jul, Bruce Evans wrote:
> Compilng libc with gcc3 -O2 does this.
>
> PR: 40209
Thanks, after recompiling libc{,_r} it works as expected.
Bye,
Alexander.
--
The best things in life are free, but the
expensive ones are still worth a look.
http://w
On Sun, 7 Jul 2002, Alexander Leidinger wrote:
> I've updated to todays current from a -current as of May 1 and I get the
> following error from my mailer (tkrat 2.0.3, written in tcl/tk):
> ---snip---
> expected floating-point number but got "0.0<45132"
> expected floating-point number but got "
Hi,
I've updated to todays current from a -current as of May 1 and I get the
following error from my mailer (tkrat 2.0.3, written in tcl/tk):
---snip---
expected floating-point number but got "0.0<45132"
expected floating-point number but got "0.0<45132"
while executing
".f1.t.messlist.scroll
