public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: bug: cygwin 2.0 doesn't work at all
Date: Tue, 28 Apr 2015 17:00:00 -0000	[thread overview]
Message-ID: <87r3r4qjcg.fsf@Rainer.invalid> (raw)
In-Reply-To: <trinity-fb583d65-b360-410c-bc6c-da381e290934-1430215078423@3capp-mailcom-lxa09>	(Leonid Mironov's message of "Tue, 28 Apr 2015 11:57:58 +0200")

Leonid Mironov writes:
> Upgrading cygwin package to 2.0 broke [almost] all programs using
> cygwin1.dll e.g. bash, they exit immediately after they've been
> started with the exit code 0xc0000005 and no screen messages or
> messages in windows logs.

That particular exit code is "Access is Denied" if I'm not mistaken, so
you might want to check the access rights in the Cygwin tree for
starters.

> The remainder of the setup fails too because
> cygwin programs invoked by the setup e.g. dash from autorebase start
> failing with the same symptoms. Rolling cygwin package back to 1.7.35
> resolved this issue. Windows 7 professional 32-bit, cygcheck output
> follows

Are you sure you didn't accidentally update while some Cygwin processes
were still running, still using the old Cygwin DLL?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

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

      parent reply	other threads:[~2015-04-28 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  9:58 Leonid Mironov
2015-04-28 10:55 ` Marco Atzeri
2015-04-28 14:32 ` Warren Young
2015-04-28 17:00 ` Achim Gratz [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=87r3r4qjcg.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).