public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: Re: [BUG]: 3.1.4: cmd -> bash -> mintty yields Windows exception
Date: Fri, 21 Feb 2020 19:05:00 -0000	[thread overview]
Message-ID: <774a407a-66df-42e3-ce34-d7b084fadf46@acm.org> (raw)
In-Reply-To: <fdcd5fd3-09f5-3dff-9c6c-3c7b601f315b@t-online.de>

On 2/21/2020 10:33 AM, Hans-Bernhard Bröker wrote:
> Am 21.02.2020 um 18:22 schrieb David Rothenberger:
>> With cygwin 3.1.4, I get an "exception c0000005" when I perform the
>> following actions:
>>
>> 1. Use the Windows run box to start a cmd shell
>> 2. From there, run "bash". (I'm sure it is the Cygwin bash.)
> 
> How did you make sure of that?

Because I know my environment, and because I gave an explicit path to Cygwin's bash when I started it from cmd.

> But let's assume I did actually start Cygwin bash.
> 
>> 3. From there, run "mintty"
> 
> C:\Users\hbbro>\cygwin64\bin\bash
> 
> hbbro@NB5 /cygdrive/c/Users/hbbro
> $ mintty
> bash: mintty: command not found

I have Cygwin's paths in my Windows PATH variable, which is why it works for me. It would probably work for you if you ran "bash -li" from the cmd shell. 

-- 
David Rothenberger  ----  daveroth@acm.org

"Out of register space (ugh)"
                -- vi

--
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:[~2020-02-21 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 17:22 David Rothenberger
2020-02-21 17:46 ` Marco Atzeri
2020-02-21 18:33 ` Hans-Bernhard Bröker
2020-02-21 19:05   ` David Rothenberger [this message]
2020-02-21 18:41 ` Takashi Yano

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=774a407a-66df-42e3-ce34-d7b084fadf46@acm.org \
    --to=daveroth@acm.org \
    --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).