On Nov 29 23:11, Thomas Wolff wrote:
> Am 29.11.2018 um 20:58 schrieb Corinna Vinschen:
> > On Nov 29 19:41, Houder wrote:
> > > Hi,
> > > 
> > > As I wrote in the preceding post ...
> > > 
> > > Using Corinna's latest snapshot in a "Dos box" results in a
> > > prompt from bash.
> > > 
> > > Once in bash, I can launch MinTTY ( 64-@@ /usr/bin/mintty )
> > > 
> > > Placing strace in front of this call, results in:
> > > 
> > > 64-@@ strace /usr/bin/mintty
> > > --- Process 3112 created
> > > --- Process 3112 loaded C:\Windows\System32\ntdll.dll at 00000000777b0000
> > > ...
> > > --- Process 3112 loaded C:\Windows\winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_fa3b1e3d17594757\comc
> > > tl32.dll at 000007fefb9c0000
> > > --- Process 3112 loaded C:\Windows\System32\gdi32.dll at 000007fefdc10000
> > > ...
> > > --- Process 3112 loaded C:\Windows\winsxs\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.24280_none_145e10148b8de48e\GdiPlus.dll
> > > at 000007fefb440000
> > > ...
> > > --- Process 3112, exception c0000005 at 0000000180044bb3
> > > --- Process 3112 exited with status 0xc0000005
> > > Segmentation fault
> There's also another dll reported from winsxs rather than System32 in your
> log. Maybe some files got corrupted on your system?
> 
> > I can reproduce this but while it's clear *where* it happens, it's
> > unclear *when* and *why* it happens.
> Unclear to me what exactly can be reproduced. With today's snapshot
> cygwin1.dll, I can start mintty any way, also from Explorer, via shortcut,
> or directly from cmd.exe (skipping cygwin shell).
> Thomas

Are you running Windows 10?  If so, you won't see this problem.
It only occurs on pre-W10 systems.  I have a local workaround but
I want to debug this a bit more since I still don't understand *why*
this occurs in the first place.

Btw., a mintty-debuginfo package would be most helpful...


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer