From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Update: mintty 2.1.2
Date: Fri, 24 Jul 2015 13:34:00 -0000 [thread overview]
Message-ID: <20150724133408.GB7535@calimero.vinschen.de> (raw)
In-Reply-To: <d9ef810e0ad325a9b51f641a10a06f0b.squirrel@oude-webmail.xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]
On Jul 24 15:18, Houder wrote:
> Hi Thomas,
>
> >>> mintty 2.1.2 is an update in response to a number of crash reports under
> >>> unclear circumstances;
> > To resolve this discomforting issue which I still cannot reproduce,
> > could please those who experience a crash report some details about
> > their calling environment?
> > Could the issue be related to the occasional fork() resource problems in
> > cygwin?
>
> ... euh, I do not believe so (in my case) ... I installed v211 using setup, which as
> you know, does a full "rebase" ...
>
> Also using 'setsid mintty' (in case of v113, v203) does not fail ...
>
> > How much free memory do you have?
>
> - my computer has lots of free memory (using less than 2 Gb of 8 Gb)
> - my environment: using Cygwin (only the traditional tools)
> - plus: Explorer (and most of the time: Process Explorer from SysInternals)
>
> I am really surprised, that you (and others?) do not experience crashes (v211, v212
> if -D is specfied). Failure occurs consistent on my side.
>
> > Maybe setsid() should not be called if fork() fails...
> > Could you try this please:
> > if (daemonize && !isatty(0)) {
> > int pid = fork();
> > if (pid > 0) exit(0); // exit parent process
> > if (pid == 0) setsid(); // detach child process
> > if (pid < 0) {
> > error("could not detach from caller");
> > exit(9);
> > }
> > }
>
> 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")
> > I wanted to check ttyname() for "/cons" but surprisingly ttyname() was
> > null when started from cygwin console;
>
> ... I expect ttyname() to return NULL, as mintty is a GUI application ... (and it did, using
> a "small GUI test program"; however it returned /dev/pty0 when executing it from a dos console
> in which mintty had been started). Yes, I am confused).
>
> As I wrote 'and I asked myself', I was wondering about something like: 'getpid() != 1'
Guys, the Cygwin DLL is as much open source as the other stuff we're
talking about here. It's a user space DLL, not a kernel driver or
rocket science. Give debugging a chance. Ideally build your own Cygwin
DLL with CFLAGS=-g to avoid optimization. Please don't let me do this
alone and just give up if I don't.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-24 13:34 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
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 [this message]
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=20150724133408.GB7535@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).