[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: WINDOWS32 "Signal 127" due to a path in quotes bug [Ooops]
From: |
Eli Zaretskii |
Subject: |
Re: WINDOWS32 "Signal 127" due to a path in quotes bug [Ooops] |
Date: |
Sun, 07 Aug 2005 06:42:51 +0300 |
> Date: Sun, 07 Aug 2005 02:39:03 +0200
> From: address@hidden
>
> > In general, Ctrl-C is documented on Windows to be passed to all the
> > programs that are attached to the console which has the focus when
> > Ctrl-C is hit.
>
> I dunno if this is the case, IME if the parent has registered a
> Ctrl-C handler it may need to set CREATE_DEFAULT_ERROR_MODE in
> the "process creation flags" in the call to CreateProcess.
The Microsoft documentation seems to indicate this flag is not
relevant to Ctrl-C. If you know otherwise, please point me to the
place in the documentation that says so, or give an example of a test
program and a session that demonstrates that this is needed.
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, (continued)
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, J. Grant, 2005/08/03
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Eli Zaretskii, 2005/08/04
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Eli Zaretskii, 2005/08/06
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Paul D. Smith, 2005/08/06
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Eli Zaretskii, 2005/08/06
Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Eli Zaretskii, 2005/08/06
Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Alessandro Vesely, 2005/08/07