From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: MinTTY requires gdiplus.dll ? (2)
Date: Sat, 01 Dec 2018 09:49:00 -0000 [thread overview]
Message-ID: <20181201094853.GL30649@calimero.vinschen.de> (raw)
In-Reply-To: <fb45509f322f95b57ae075c05260383a@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-12-01 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 18:42 Houder
2018-11-29 19:58 ` Corinna Vinschen
2018-11-29 22:11 ` Thomas Wolff
2018-11-29 22:40 ` Houder
2018-11-29 23:35 ` Houder
2018-11-30 12:17 ` Corinna Vinschen
2018-11-30 12:42 ` Houder
2018-11-30 13:19 ` Corinna Vinschen
2018-11-30 14:06 ` Houder
2018-12-01 8:57 ` Houder
2018-12-01 9:49 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181201094853.GL30649@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).