From: Tony Kelman <tony@kelman.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926)
Date: Sun, 02 Oct 2016 09:56:00 -0000 [thread overview]
Message-ID: <DM2PR0201MB07991C4D55AD240A54BA9E65A7C30@DM2PR0201MB0799.namprd02.prod.outlook.com> (raw)
In-Reply-To: <57F0D486.1060301@maxrnd.com>
> You've got two different cygwin1.dll somewhere on your PATH. As your builds
> proceed, they likely start out using the correct cygwin1.dll but sometimes load
> the wrong cygwin1.dll along the way. The error message tells you how to solve
> the problem. But I usually use this method:
> - open a Command Prompt running as Administrator
> - cd c:\ or wherever the root of your Cygwin installation drive is
> - dir /S cygwin1.dll
> You might see multiple listings of the same cygwin1.dll due to the crazy WoW
> support but these will all have the same date and size. You want to find the
> cygwin1.dll that has a different date (probably older) and size. That's the
> problematic one; rename it or delete it.
And if not?
C:\>dir /S cygwin1.dll
Volume in drive C is Windows
Volume Serial Number is C225-5FBC
Directory of C:\cygwin64\bin
08/31/2016 05:32 AM 3,306,962 cygwin1.dll
1 File(s) 3,306,962 bytes
Total Files Listed:
1 File(s) 3,306,962 bytes
0 Dir(s) 58,480,676,864 bytes free
C:\>
--
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-02 9:38 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 [this message]
2016-10-02 10:00 ` Tony Kelman
2016-10-03 6:57 ` Mark Geisert
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=DM2PR0201MB07991C4D55AD240A54BA9E65A7C30@DM2PR0201MB0799.namprd02.prod.outlook.com \
--to=tony@kelman.net \
--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).