Re: MinTTY requires gdiplus.dll ? (2)

[Houder <houder@xs4all.nl>]

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@entry=0x1802f91b0 
<strace::microseconds()::clock_monotonic>,
     clockid=clockid@entry=0, ts=ts@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