DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=HanQV9S2cOMtpoYkhbWKG0hFhzyMAfpQJptuhNAk+tX
	zXyFJZP0EmH0vtYHcsBYIiWrOkowEzgu/dy3piTP0sqkaTQU2lXrGDINJvjvtS57
	NqUZGh0Ht9FuTRQfi6RjZ1uKaAUCcbjVr7GpzQroCI+2qJHxAUbnkAO2wy01peTc
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: "John Marsh" <jmarsh61 AT gmail DOT com>
To: <cygwin AT cygwin DOT com>
References: <3EC211E2982D40B9BB6AA77E3BD6214E AT GatewayI5> <556BBA7B DOT 9020008 AT cygwin DOT com>
In-Reply-To: <556BBA7B.9020008@cygwin.com>
Subject: RE: Cygwin: vim causes bash to die
Date: Mon, 1 Jun 2015 09:30:49 -0700
Message-ID: <FD88D2F47383431E940B5B938866A30A@GatewayI5>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Thanks for looking into this Larry.

You have to run vim several times in the same terminal for the fault to
occur.  I launch bash from a desktop shortcut, and it appears to be using
the conhost process.  My bash terminal is configured with white background
and black text, and vim is configured with a light background.  I've been
using cygwin since it first came out, and I've always launched bash and vim
this way, and never seen this problem before.  In fact I have another
Windows 7 computer with an older version of cygwin that works fine.  So it
seems that a bug has been introduced along the line.  I'm wondering if it
has something to to with the ongoing terminal issues I've seen discussed in
the mailing list.

I would like to submit a detailed problem report.  How is this done?

Thanks again,
John

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of
Larry Hall (Cygwin)
Sent: Sunday, May 31, 2015 6:51 PM
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin: vim causes bash to die

On 05/31/2015 02:32 PM, John Marsh wrote:
>
> Issue: vim causes bash to die
>
> Windows Event Viewer (Application Error)
>
> Faulting application name: conhost.exe, version: 6.1.7601.18839, time
stamp:
> 0x553e7baa
> Faulting module name: conhost.exe, version: 6.1.7601.18839, time stamp:
> 0x553e7baa
> Exception code: 0xc0000005
> Fault offset: 0x00000000000234df
> Faulting process id: 0x2254
> Faulting application start time: 0x01d09bc9f5b48b51 Faulting 
> application path: C:\Windows\system32\conhost.exe Faulting module 
> path: C:\Windows\system32\conhost.exe Report Id: 
> 50014a1e-07be-11e5-b4f2-fc1aad7fabda
>
> Is there a fix for this?

Sorry, I can't reproduce this from a bash started in cmd.exe or mintty.exe.
Based on the Windows Event Viewer information above, it's actually the
Windows console (conhost) that's crashing.  Perhaps it would better for you
if you ran it from mintty?  If you want to submit a complete problem report
that describes the steps to reproduce the problem, that may throw some light
on the problem.  With the exception of me running on Windows 8 and you
Windows 7, I don't see a significant difference in configuration.


--
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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


--
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