From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69607 invoked by alias); 24 Jul 2015 13:18:48 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 69598 invoked by uid 89); 24 Jul 2015 13:18:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: lb2-smtp-cloud6.xs4all.net Received: from lb2-smtp-cloud6.xs4all.net (HELO lb2-smtp-cloud6.xs4all.net) (194.109.24.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 24 Jul 2015 13:18:46 +0000 Received: from oude-webmail.xs4all.nl ([194.109.26.18]) by smtp-cloud6.xs4all.net with ESMTP id wDJi1q00M0PS7C201DJikM; Fri, 24 Jul 2015 15:18:42 +0200 Received: from 83.162.234.136 (SquirrelMail authenticated user incog) by oude-webmail.xs4all.nl with HTTP; Fri, 24 Jul 2015 15:18:42 +0200 Message-ID: In-Reply-To: <55B22422.6000601@towo.net> References: <63a08c60771faffa23bc1c029235301d.squirrel@oude-webmail.xs4all.nl> <55B22422.6000601@towo.net> Date: Fri, 24 Jul 2015 13:18:00 -0000 Subject: Re: [ANNOUNCEMENT] Update: mintty 2.1.2 From: "Houder" To: cygwin@cygwin.com User-Agent: SquirrelMail/1.4.22 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2015-07/txt/msg00374.txt.bz2 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' 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