This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

20060521 snapshot, Ctrl-C, and Windows processes


Noticed a problem today: if you start a Windows process in bash and press
Ctrl-C, the Ctrl-C will be delivered to the process, but then bash (or the
Cygwin wrapper that waits for the Windows process) will simply hang until
the Windows process terminates.  If the process does not terminate (e.g.,
"ping -t"), bash will hang until Ctrl-C is pressed 10 times (the delays
between the consecutive Ctrl-Cs don't seem to matter).

Steps to reproduce:

In bash, type "ping -t", then, after a couple of ping results,
press Ctrl-C.  The process will hang (here's the screenshot):

$ ping -t

Pinging [] with 32 bytes of data:

Reply from bytes=32 time=82ms TTL=46
Reply from bytes=32 time=83ms TTL=46

Ping statistics for
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 82ms, Maximum = 83ms, Average = 82ms

Pressing Ctrl-C 10 times at this point returns to the bash prompt.
This is with the latest (20060521) snapshot, as well as with my own CVS
builds.  The output of "cygcheck -svr" is attached.
      |\      _,,,---,,_ |
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

Attachment: cygcheck-20060521.out
Description: Text document

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]