public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926)
Date: Sun, 02 Oct 2016 09:38:00 -0000	[thread overview]
Message-ID: <57F0D486.1060301@maxrnd.com> (raw)
In-Reply-To: <DM2PR0201MB079958F9EBD05C7DED300E16A7C30@DM2PR0201MB0799.namprd02.prod.outlook.com>

Tony Kelman wrote:
>> Could you paste a complete sample of the error message so we can
>> determine where in the Cygwin code it's coming from?
>
> Still a problem in 14936. Folks, this could be very bad. Anyone at all
> testing the insider builds, or are we going to be blindsided when an
> update goes out to everyone that breaks cygwin?
>
> Here's one:
>
>        1 [main] cp (6432) C:\cygwin64\bin\cp.exe: *** fatal error - cygheap base
          mismatch detected - 0x180302408/0xD92408.
> This problem is probably due to using incompatible versions of the cygwin DLL.
> Search for cygwin1.dll using the Windows Start->Find/Search facility
> and delete all but the most recent version.  The most recent version *should*
> reside in x:\cygwin\bin, where 'x' is the drive on which you have
> installed the cygwin distribution.  Rebooting is also suggested if you
> are unable to find another cygwin DLL.

OK, you're seeing two different problems. Solving the one above is critical. It 
might help solve the other problem shown below; we'll have to see.

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.

Then try running your build again.

>
>
> And another:
>
>        0 [main] cmake 10384 child_info_fork::abort: C:\cygwin64\bin\cygintl-8.dll:
          Loaded to different address: parent(0x3E3680000) != child(0x190000)

This is a garden-variety fork() failure due to the child having something in its 
address space at 0x3E3680000 such that Cygwin can't load cygintl-8.dll at that 
address where the parent has it. But since you've apparently got two Cygwin 
installations on your PATH, maybe that's complicating things. See if fixing the 
first problem above makes this problem go away too.

..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

  reply	other threads:[~2016-10-02  9:34 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 [this message]
2016-10-02  9:56           ` Tony Kelman
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=57F0D486.1060301@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).