On Dec  1 09:57, Houder wrote:
> On 2018-11-30 14:19, Corinna Vinschen wrote:
> [snip]
> 
> > I'm trying to avoid remote debugging so I rather try to reproduce this
> > @work.  However, if you're interested in debugging this, set a
> > breakpoint to clk_monotonic_t::now() and observe how the call to the
> > virtual init() method hangs or crashes.  If you find out why, I'd be
> > most grateful.
> 
> Below I included parts of the diff between 1126 and 1129. You have been
> refactoring the code related to "timing".
> 
> Above you state that the call to init() (clk_monotonic_t::init(), is my
> understanding) from clk_monotonic_t::now() makes the cygwin1.dll end up
> in "some mysterious loop" (my wording). At least on pre-W10 ...
> 
> Looking at the code (trying to understand it), it appears to me that it
> is NOT "Windows version" dependent ...
> 
> My question: why do you claim in
> 
>     https://cygwin.com/ml/cygwin/2018-11/msg00261.html
> 
> that Windows 10 is NOT affected? Does W10 run a different "thread" in
> the Cygwin codebase?

On W10, wincap.has_precise_interrupt_time () is true.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer