From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926)
Date: Mon, 03 Oct 2016 06:57:00 -0000 [thread overview]
Message-ID: <57F1FD3E.80601@maxrnd.com> (raw)
In-Reply-To: <DM2PR0201MB0799F93894D9F5E334A69789A7C30@DM2PR0201MB0799.namprd02.prod.outlook.com>
Tony Kelman wrote:
>> You've got two different cygwin1.dll somewhere on your PATH.
>
> For more information, I have one cygwin64 installation on C:, one
> cygwin32 installation on E:, and they're never both on my path at
> the same time. I'm not sure where that orphan registry entry that was
> showing up in cygcheck.out came from, but I removed it and it made no
> difference.
With only one Cygwin installation on C: I can only come up with wild guesses.
Are you somehow alternating between the C: and E: Cygwin versions, or running
them simultaneously from separate windows, or accidentally running 32-bit Cygwin
commands from a 64-bit Cygwin terminal window? Unusual stuff like that?
One sure-fire way to make sure your 32-bit E: installation is not causing havoc
with your 64-bit C: installation is to temporarily rename E:\cygwin32 to
E:\somethingelse and retry your build. This should not be necessary but I don't
know what else to suggest.
I have in the past run 32-bit and 64-bit Cygwin installations simultaneously on
the same machine, in order to build 32-bit and 64-bit Cygwin DLLs at the same
time. Never had a problem. But that was Windows 7 so probably not applicable.
> This is absolutely due to a change in Windows itself. 3 updates in
> a row now, 14926, 14931, and now 14936, it's 100% reproducible just
> from updating Windows. Downgrading to build 14915 gets everything back
> working again, but that build is now expired so the only way for me to
> get back to a supported build of Windows where cygwin works properly
> is by totally reinstalling Windows. I haven't done that yet, but if
> we can't identify the problem and a solution soon, I will have to.
I see what you've been saying about different insider builds of Windows 10 but I
don't think anybody here is beating up on these releases.
..mark
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-10-03 6:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:51 Tony Kelman
2016-09-24 13:49 ` Tony Kelman
2016-09-25 8:20 ` Mark Geisert
2016-09-27 10:58 ` Tony Kelman
2016-10-02 6:58 ` Tony Kelman
2016-10-02 9:38 ` Mark Geisert
2016-10-02 9:56 ` Tony Kelman
2016-10-02 10:00 ` Tony Kelman
2016-10-03 6:57 ` Mark Geisert [this message]
2016-10-03 12:09 ` Tim Prince
2016-10-02 15:09 ` Achim Gratz
2016-10-03 3:58 ` Tony Kelman
2016-10-03 6:40 ` Achim Gratz
2016-10-03 9:10 ` Tony Kelman
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=57F1FD3E.80601@maxrnd.com \
--to=mark@maxrnd.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).