Hi Francis,
On Nov 30 23:59, Francis ANDRE wrote:
> Hi
>
> The following set-x86.exe command in unattended mode crashes on Win7
>
> C:\Users\FrancisANDRE>c:\cygwin\bin\uname.exe -a
> CYGWIN_NT-6.1-WOW idefix 2.3.1(0.291/5/3) 2015-11-14 12:42 i686 Cygwin
>
> C:\Users\FrancisANDRE>c:\cygwin\setup
After upgrading to Windows 10 TH2 (ver 1511, build 10586), any attempt
to launch a cygwin64 process from 32bit native app (for example,
C:\windows\syswow64\cmd.exe) *always* results in a fork error.
To be precise, I can execute 64bit bash.exe from 32bit cmd.exe.
However, this bash process never su
cygcheck.out
Description: Binary data
--
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
On Mon, Nov 30, 2015 at 12:36:16PM -0600, David Blackstone wrote:
> Recently I found that the behavior of control-R in bash had changed.
> The key binding has been modified by the fzf-bash package to activate
> the fzf fuzzy search program. The first noticeable result is that
> pressing control-R
Hi Corinna
Le 01/12/2015 10:54, Corinna Vinschen a écrit :
Hi Francis,
On Nov 30 23:59, Francis ANDRE wrote:
Hi
The following set-x86.exe command in unattended mode crashes on Win7
C:\Users\FrancisANDRE>c:\cygwin\bin\uname.exe -a
CYGWIN_NT-6.1-WOW idefix 2.3.1(0.291/5/3) 2015-11-14 12:42 i68
On Dec 1 19:27, nu774 wrote:
> After upgrading to Windows 10 TH2 (ver 1511, build 10586), any attempt
> to launch a cygwin64 process from 32bit native app (for example,
> C:\windows\syswow64\cmd.exe) *always* results in a fork error.
>
> To be precise, I can execute 64bit bash.exe from 32bit cmd.
There must be a bug in the new CMD somewhere. But, anyway, I'll look
into it when I finally managed to update my W10 test machine.
No, cmd.exe is just an example. Any 32bit process can be an trigger.
I guess something has changed in TH2 kernel regarding process memory
management or something t
On Dec 1 12:18, Francis ANDRE wrote:
> Hi Corinna
>
> Le 01/12/2015 10:54, Corinna Vinschen a écrit :
> >Hi Francis,
> >
> >On Nov 30 23:59, Francis ANDRE wrote:
> >>Hi
> >>
> >>The following set-x86.exe command in unattended mode crashes on Win7
> >>
> >>C:\Users\FrancisANDRE>c:\cygwin\bin\uname
On Dec 1 21:07, nu774 wrote:
> >There must be a bug in the new CMD somewhere. But, anyway, I'll look
> >into it when I finally managed to update my W10 test machine.
>
> No, cmd.exe is just an example. Any 32bit process can be an trigger.
> I guess something has changed in TH2 kernel regarding p
On 1. 12. 2015 15:01, Corinna Vinschen wrote:
> On Dec 1 21:07, nu774 wrote:
>>> There must be a bug in the new CMD somewhere. But, anyway, I'll look
>>> into it when I finally managed to update my W10 test machine.
>>
>> No, cmd.exe is just an example. Any 32bit process can be an trigger.
>> I g
>From: Dave Kilroy [mailto:kilr...@googlemail.com]
>>On 23/10/2015 16:16, Matt Seitz (matseitz) wrote:
>> When I right click a folder in Windows Explorer and select "Bash
>> Prompt Here", a window opens briefly and then closes immediately.
> I suspect this may be due to the use of %DISPLAY% (
Op 1-12-2015 om 17:40 schreef David Macek:
> On 1. 12. 2015 15:01, Corinna Vinschen wrote:
>> On Dec 1 21:07, nu774 wrote:
There must be a bug in the new CMD somewhere. But, anyway, I'll look
into it when I finally managed to update my W10 test machine.
>>>
>>> No, cmd.exe is just an
On Mon, Nov 23, 2015 at 02:23:33PM -0700, Eric Blake wrote:
> On 11/23/2015 01:45 PM, Matt D. wrote:
> > Is there a reason why these produce different results?
> >
> > find . -exec cygpath -wa {} \;
> > find . -exec echo $(cygpath -wa {}) \;
>
> Incorrect quoting. You are invoking:
>
> find . -exe
On 12/01/2015 01:43 PM, Duncan Roe wrote:
>> Why not just:
>>
>> find . -exec cygpath -wa {} +
>>
>> since cygpath handles more than one file in an invocation (that is,
>> using '-exec {} +' rather than '-exec {} \;' is generally faster).
>>
> I would be using xargs. Especially under /cygdrive, th
On 1. 12. 2015 18:40, David Macek wrote:
> On 1. 12. 2015 15:01, Corinna Vinschen wrote:
>> On Dec 1 21:07, nu774 wrote:
There must be a bug in the new CMD somewhere. But, anyway, I'll look
into it when I finally managed to update my W10 test machine.
>>>
>>> No, cmd.exe is just an exam
Greetings, All!
I just got a hard case of stupidity...
Started Cygwin setup before checking if anything is running Cygwin.
Guess, what? It indeed did run. However, setup managed to uninstall mintty
before telling me that there's ssh-pageant running in the background.
I had to dig up and start shel
16 matches
Mail list logo
