public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: MinTTY requires gdiplus.dll ? (2)
Date: Fri, 30 Nov 2018 12:42:00 -0000	[thread overview]
Message-ID: <4286450150901731f39f9514b8044ded@xs4all.nl> (raw)
In-Reply-To: <20181129195845.GE30649@calimero.vinschen.de>

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!

(hint: my system is a bit more peculiar than yours)

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

  parent reply	other threads:[~2018-11-30 12:42 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
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 [this message]
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=4286450150901731f39f9514b8044ded@xs4all.nl \
    --to=houder@xs4all.nl \
    --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).