This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: BASH under B19
- To: gnu-win32 at cygnus dot com
- Subject: Re: BASH under B19
- From: cgf at cygnus dot com (Christopher G. Faylor)
- Date: 16 Apr 1998 22:14:49 GMT
- Newsgroups: cygnus.gnu-win32
- Organization: Cygnus Solutions
- References: <8B40B8756FA1D111BCB900A02495E24F36B421@neptune.xstor.com>, <3535BF6B.539DB456.cygnus.gnu-win32@tibco.com>
- Stamped: newsgate-cygnus
In article <3535BF6B.539DB456.cygnus.gnu-win32@tibco.com>,
Matt Stupple <matts@tibco.com> wrote:
>Bob McGowan wrote:
>>
>> I am a bit confused by the second paragraph. In the usual DOS
>> command.com and, I thought, in the cmd.exe of WinNT, a ^C is simply an
>> interrupt. Unlike UNIX, it cannot be changed, that I know of, by any
>> simple command interface. Regardless, it is just an interrupt and
>> should stop a running process. If the Cygwin stuff is supposed to
>> maintain some compatability with the MS environment, then I do not see
>> why it would be necessary or desireable to have new threads spawned by
>> this key sequence.
>>
>
>This is a straight copy from the MSVC help on the signal() function:
Actually, Cygwin32 does *not* start a new thread when ^C is hit. A ^C
should behave just like UNIX. It should either stop your process or,
in the case of a shell, it should intercept the signal and "do something".
MSVC does start a new thread when a ^C is hit. Cygwin32 doesn't.
--
cgf@cygnus.com "Everything has a boolean value, if you stand
http://www.cygnus.com/ far enough away from it." -- Galena Alyson Canada
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".