public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: bash (3312) C:\tools\cygwin\bin\bash.exe: *** fatal error - cygheap base mismatch detected - 0x180331408/0x18032D408.
Date: Sat, 19 Oct 2019 16:51:00 -0000	[thread overview]
Message-ID: <fafb01d6-d5c1-655a-e476-5ce14fcd4c9d@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAFHpkQF-eybPTW-wCSGVvkwhfsgbMtJFW7DRCWzoS244BcJgWw@mail.gmail.com>

On 2019-10-19 06:44, Ilʹja Šipicin wrote:
> sb, 19 okt. 2019 g. v 17:32, Biswapriyo Nath:
>> It seems to be issue in Travis CI. See this forum post:
>> https://travis-ci.community/t/cygwin-issue-cygheap-base-mismatch-detected/5359
>> If you are in hurry you can use Appveyor CI. I'm using it without any
>> issue. One has to just add `C:\cygwin64\bin` in PATH variable in YAML file.

> thank for another hint.
> I added 'get-childitem C:\cygwin64\bin'
> https://travis-ci.com/chipitsine/travis-cygwin/builds/132645696
> gci : Cannot find path 'C:\cygwin64\bin' because it does not exist.

He suggested adding the Cygwin bin to PATH: you have to find it; does not matter
where it exists, run:

	$ find /proc/cygdrive/?/ -name cygwin1.dll

or a global Windows search on My Computer/This PC/Cortana/etc.

> seems, it does not exist. no point to add it to PATH
> there's no hurry. I want to resolve it. My issue is the same as
> described on forum - builds used to work and accidentally stopped
> working (with the same error)

If you read the problem report, the issue is that the Travis provided
Git-for-Windows AKA Git-Bash AKA MSYS2/Cygwin Git/Bash/cygwin1.dll are installed
where its cygwin1.dll can be found via the path, but the shell child processes
are running using a different version of cygwin1.dll via the path, possibly
after installing new packages using a package manager like chocolatey or pacman.

Try running:

	$ which -a cygwin1.dll

and maybe:

	$ cygpath -alpw "$PATH"

to see what is active, and delete whichever installation is redundant.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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:[~2019-10-19 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-19  5:00 Илья Шипицин
2019-10-19  5:23 ` Brian Inglis
2019-10-19  9:52   ` Илья Шипицин
2019-10-19 10:02     ` Илья Шипицин
2019-10-19 12:32       ` Biswapriyo Nath
2019-10-19 12:44         ` Илья Шипицин
2019-10-19 16:51           ` Brian Inglis [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=fafb01d6-d5c1-655a-e476-5ce14fcd4c9d@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).