Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Termination signals are delayed #35

Closed
GoogleCodeExporter opened this issue Apr 27, 2015 · 4 comments
Closed

Termination signals are delayed #35

GoogleCodeExporter opened this issue Apr 27, 2015 · 4 comments
Labels
auto-migrated Difficulty-Medium Milestone-0.3.4 Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

When sending one of the process terminating signals (TERM, KILL, HUP, INT)
to MinTTY, it will not exit immediately, waiting for the next keypress instead.

The reason for that is that Win32 functions are not interruptible by
signals in Cygwin and MinTTY spends most of its time in
MsgWaitForMultipleObjects().

Original issue reported on code.google.com by andy.koppe on 11 Jan 2009 at 9:06
@GoogleCodeExporter
Copy link
Author 

Issue 36 has been merged into this issue.

Original comment by andy.koppe on 11 Jan 2009 at 9:07

@GoogleCodeExporter
Copy link
Author 

Fixed in r106 on 0.3 branch. Thanks to Christopher Faylor for the correct 
solution: a
separate thread waiting for signals using sigwait().

Original comment by andy.koppe on 11 Jan 2009 at 10:27

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author 

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Original comment by andy.koppe on 14 Jan 2009 at 7:41

  • Changed state: Verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Difficulty-Medium Milestone-0.3.4 Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter