From: "Houder" <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Update: mintty 2.1.2
Date: Fri, 24 Jul 2015 07:50:00 -0000 [thread overview]
Message-ID: <63a08c60771faffa23bc1c029235301d.squirrel@oude-webmail.xs4all.nl> (raw)
In-Reply-To: <announce.55B1677D.5080303@towo.net>
> mintty 2.1.2 is an update in response to a number of crash reports under
> unclear circumstances;
> mintty only detaches from the caller's terminal if the option -D is given
Thank you, Thomas!
I extracted mintty.exe (and named it mintty-v212.exe) from mintty-2.1.2-0.tar.xz, and
placed it in <Windows Cygwin root>/bin (i.e. I did not install through setup.exe)
From winmain.c (v212),
// if started from console, try to detach from caller's terminal (~daemonize)
// in order to not suppress signals
// (indicated by isatty if linked with -mwindows)
if (daemonize && !isatty(0)) { // boolean daemonize is set to true if -D is specified
if (fork() > 0) exit(0);
setsid();
}
I gather, that v212 has the "old behaviour" if -D is not specified on the command line.
Test v212:
- started from the explorer: works
- using a dos console (in which mintty-v212 is started): works
- using a dos console (in which bash is started), followed by invocation of mintty-v212: works
- using a dos console (in which cmd is started), followed by invocation of mintty-v212: works
Of course, SIGINT is ignored in the third case (old behaviour).
Invocation of 'mintty-v212 -D' in the third case, makes "mintty" crash again ...
(hint: source code of setsid.c -- util-linux package)
(... and I ask myself whether or not the condition '!isatty' is the "correct condition" to
go "daemon")
Henri
--
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
next prev parent reply other threads:[~2015-07-24 7:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 22:41 Thomas Wolff
2015-07-24 7:50 ` Houder [this message]
2015-07-24 11:40 ` Thomas Wolff
2015-07-24 13:18 ` Houder
2015-07-24 13:25 ` Houder
2015-07-24 13:34 ` Corinna Vinschen
2015-07-24 22:03 ` Thomas Wolff
2015-07-25 17:03 ` Houder
2015-07-25 20:15 ` Houder
2015-07-26 11:09 ` Houder
2015-07-26 11:58 ` Houder
2015-07-26 16:53 ` Thomas Wolff
2015-07-26 22:59 ` Houder
2015-07-27 10:54 ` Houder
2015-07-27 15:58 ` Houder
2015-07-27 17:44 ` Thomas Wolff
2015-07-27 19:29 ` Corinna Vinschen
2015-07-27 20:44 ` Houder
2015-07-27 20:58 ` Houder
2015-07-27 20:59 ` Corinna Vinschen
2015-07-27 21:14 ` Houder
2015-07-27 7:17 ` Csaba Raduly
2015-07-27 8:50 ` Houder
2015-07-24 13:25 ` Corinna Vinschen
2015-07-27 18:08 ` Buchbinder, Barry (NIH/NIAID) [E]
2015-07-27 22:01 ` Thomas Wolff
2015-07-30 12:00 ` Kptain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63a08c60771faffa23bc1c029235301d.squirrel@oude-webmail.xs4all.nl \
--to=houder@xs4all.nl \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).