X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=sr9IbUgu4L730RqKbLG/
	onh9VTdvRlPls8v0xy2uF3ZixYy1fgK4VhWvOKck6rjdT0YSxx5T8N+CV9Jd4Saw
	74ACRhcMgU7Iypqdp53xeeRuVkC1L/pr0s4svIKbzoMZvsF/FrrDXhTZxNpH3pz+
	dcgsT/uiKTyvqXD3yA1krv0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; s=default; bh=tzeYs3F+YrTHfuTzidl7W3T9ZF
	Y=; b=LasbJ/Fwtyy8FePvWAU+dsgrVB6J6tTcBmwfWVLqYLXrvQ//S5I0OBy6og
	nEny7oaZNq+3RKVhEgfKuQu5Hm70JKpT3FVq4cGeD07VvOaUY+clhYLbqqllL+5F
	xZDGHawh9gAfmpLOuTugrB91G7ENn1RXRU+f2/0etvG5gS0UE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-7.6 required=5.0 tests=BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=instructed, entered, D*entry
X-HELO: lb2-smtp-cloud7.xs4all.net
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 30 Nov 2018 15:05:56 +0100
From: Houder <houder AT xs4all DOT nl>
To: cygwin AT cygwin DOT com
Subject: Re: MinTTY requires gdiplus.dll ? (2)
In-Reply-To: <20181130131918.GI30649@calimero.vinschen.de>
References: <1953c30851fd83b67ee9b162b29f4195 AT xs4all DOT nl> <20181129195845 DOT GE30649 AT calimero DOT vinschen DOT de> <4286450150901731f39f9514b8044ded AT xs4all DOT nl> <20181130131918 DOT GI30649 AT calimero DOT vinschen DOT de>
Message-ID: <4607f540cb6271db6e372d9e11138159@xs4all.nl>
X-Sender: houder AT xs4all DOT nl
User-Agent: XS4ALL Webmail
X-IsSubscribed: yes

On 2018-11-30 14:19, Corinna Vinschen wrote:
> On Nov 30 13:42, Houder wrote:
>> On 2018-11-29 20:58, Corinna Vinschen wrote:
>> > On Nov 29 19:41, Houder wrote:
>> [snip]
>> 
>> > > --- Process 3112 loaded C:\Windows\System32\winmm.dll at
>> > > 000007fefa040000
>> > > --- Process 3112 loaded C:\Windows\System32\winspool.drv at
>> > > 000007fef9f10000
>> > > --- Process 3112, exception c0000005 at 0000000180044bb3
>> > > --- Process 3112 exited with status 0xc0000005
>> > > Segmentation fault
>> >
>> > I can reproduce this but while it's clear *where* it happens, it's
>> > unclear *when* and *why* it happens.
>> >
>> > It only occurs if mintty is the first process in a process tree.  I.e.,
>> > when starting mintty from a shell running in a DOS window, the problem
>> > disappears.
>> >
>> > Worse, the problem also disappears when running mintty under gdb.
>> 
>> (I do not understand _exactly_ what you say here)
>> 
>> Uhm, if I invoke "gdb /usr/bin/mintty" (so, from the "Dos box") the 
>> problem
>> does NOT disappear.
>> 
>> That is:
>> 
>>     2 threads are created ... and that is it; no MinTTY window showing 
>> up!
> 
> I'm trying to avoid remote debugging so I rather try to reproduce this
> @work.  However, if you're interested in debugging this, set a
> breakpoint to clk_monotonic_t::now() and observe how the call to the
> virtual init() method hangs or crashes.  If you find out why, I'd be
> most grateful.

Sorry Corinna, your request is way over my head. I can only confirm, 
that gdb
does not return in clock.c

I set a breakpoint as you instructed. Subsequently I entered "run":

Thread 1 hit Breakpoint 1, clk_monotonic_t::now (
     this=this AT entry=0x1802f91b0 
<strace::microseconds()::clock_monotonic>,
     clockid=clockid AT entry=0, ts=ts AT entry=0xffffc7c0)
     at 
/ext/build/mknetrel/src/cygwin-snapshot-20181129-1/winsup/cygwin/clock.cc

Then I "stepped" through winsup/cygwin/clock.cc

169     in 
/ext/build/mknetrel/src/cygwin-snapshot-20181129-1/winsup/cygwin/cloc
k.cc
(gdb)

Here "I lost control" ...

Using https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git, I can 
see that
it is "close" to the call of init() in clk_monotonic_t::now().

That is it for the moment. Still curious what Thomas W. has to report 
about his
system.

Regards,

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