public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Scott Mitchell <scott.kevin.mitchell@gmail.com>
To: cygwin@cygwin.com
Subject: Re: launching sh/bash from windows console (cmd) results in application Segmentation Faults
Date: Wed, 26 Mar 2014 20:50:00 -0000	[thread overview]
Message-ID: <CAFjYYd6GnwhGsxicfsLjnyyK5QiyrC6X30dx8VK0XDfVWpbMvQ@mail.gmail.com> (raw)

Do you have the same problem with Cygwin 32 bits?  How about with
the current Cygwin package (1.7.28) with either 32 bits or 64?
I had no problem running this on 32-bits from W7 x64 with 1.7.28.

___________________

I still have the same problem when updating to cygwin64 to 1.7.28:
CYGWIN_NT-6.1 1.7.28(0.271/5/3) 2014-02-09 21:06 x86_64 Cygwin

I just installed cygwin32 and it works as expected (I have not seen
any problems yet)
CYGWIN_NT-6.1-WOW64 1.7.28(0.271/5/3) 2014-02-09 21:06 i686 Cygwin

I am not sure if the is relevant but the "C:\Windows\System32\cmd.exe"
I have been using is a 32 bit executable as reported by cygwin:
$ file cmd.exe
cmd.exe: PE32 executable (console) Intel 80386, for MS Windows

I am not sure if this is an alternative and I don't have any
alternatives other than "C:\Windows\SysWOW64\cmd.exe" which is also
reported as 32 bit.

Any ideas or suggestions?

--
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:[~2014-03-26 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 20:50 Scott Mitchell [this message]
2014-03-26 22:04 ` Maximus5
  -- strict thread matches above, loose matches on Subject: below --
2014-03-26 22:53 Scott Mitchell
2014-03-26 18:39 Scott Mitchell
2014-03-26 19:50 ` Larry Hall (Cygwin)

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=CAFjYYd6GnwhGsxicfsLjnyyK5QiyrC6X30dx8VK0XDfVWpbMvQ@mail.gmail.com \
    --to=scott.kevin.mitchell@gmail.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).