This is the mail archive of the
mailing list for the Cygwin project.
Re: launching sh/bash from windows console (cmd) results in application Segmentation Faults
- From: Maximus5 <ConEmu dot Maximus5 at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 26 Mar 2014 20:38:47 +0000 (UTC)
- Subject: Re: launching sh/bash from windows console (cmd) results in application Segmentation Faults
- Authentication-results: sourceware.org; auth=none
- References: <CAFjYYd6GnwhGsxicfsLjnyyK5QiyrC6X30dx8VK0XDfVWpbMvQ at mail dot gmail dot com>
Scott Mitchell <scott.kevin.mitchell <at> gmail.com> writes:
> 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.
That is because of redirection in Windows x64.
When you need to access (or run) any 64-bit windows app in system folder
from any 32-bit app, you need to use "sysnative" alias.
$ file /c/windows/sysnative/cmd.exe
/c/windows/sysnative/cmd.exe: PE32+ executable (console) x86-64, for MS
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple