From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: MinTTY requires gdiplus.dll ? (2)
Date: Thu, 29 Nov 2018 22:11:00 -0000 [thread overview]
Message-ID: <773b9c80-a028-324b-1833-3bfea39aebe4@towo.net> (raw)
In-Reply-To: <20181129195845.GE30649@calimero.vinschen.de>
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
> 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.
>
>
> Corinna
--
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
next prev parent reply other threads:[~2018-11-29 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 18:42 Houder
2018-11-29 19:58 ` Corinna Vinschen
2018-11-29 22:11 ` Thomas Wolff [this message]
2018-11-29 22:40 ` Houder
2018-11-29 23:35 ` Houder
2018-11-30 12:17 ` Corinna Vinschen
2018-11-30 12:42 ` Houder
2018-11-30 13:19 ` Corinna Vinschen
2018-11-30 14:06 ` Houder
2018-12-01 8:57 ` Houder
2018-12-01 9:49 ` Corinna Vinschen
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=773b9c80-a028-324b-1833-3bfea39aebe4@towo.net \
--to=towo@towo.net \
--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).