[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] [lmi-commits] odd/eraseme_error 69d06e9 10/10: Attempt to find
From: |
Greg Chicares |
Subject: |
Re: [lmi] [lmi-commits] odd/eraseme_error 69d06e9 10/10: Attempt to find a problem |
Date: |
Wed, 7 Jul 2021 15:26:57 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 |
On 2021-07-07 13:20, Vadim Zeitlin wrote:
> On Wed, 7 Jul 2021 11:52:14 +0000 Greg Chicares <gchicares@sbcglobal.net>
> wrote:
>
> GC> On 2021-07-07 11:17, Vadim Zeitlin wrote:
> GC> > On Wed, 7 Jul 2021 06:22:15 -0400 (EDT) Greg Chicares
> <gchicares@sbcglobal.net> wrote:
> GC> >
> GC> > GC> branch: odd/eraseme_error
> GC> [...]
> GC> > GC> Attempt to find a problem
> GC> [...]
> GC> > Is this hang reproducible? If so, I could try debugging it.
> GC>
> GC> It's caused by a NaN.
>
> This is perfectly compatible with my almost superstitious fear of NaNs,
> but I wonder how is this possible then the commit message said that the
> function did return...
I don't yet know.
> GC> > Generally speaking, the best technique for debugging problems under
> Wine [...snip...]
> GC>
> GC> That never worked well for me.
>
> Would you be interested in describing this in more details, so that I
> could perhaps try to diagnose the problem?
I believe we've been down that road before. Effort would be
better spent on making the GUI test work under pc-linux-gnu,
so that 'wine' could be avoided more completely. But that
doesn't matter right now, because I've localized the problem
and know how to write a standalone (unit-)test case.