X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=iqE3ov3EVk25yHEB z0PGjacnf9ii5Fjitbw7nfkxq1aL9w5BZe+NnbXX+VEKDPL56tPrFoylBIntvgfr 5gTOZK6y1hs0L0iFjOzKvQWusXURNXbc0UEYK7vjgtzx0dqjVInX1mi3o4mapGGU lRIFs44zaObZhtUdK6QOXvjC0ko= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=default; bh=hFoioTqc+JeWpf0LttjTjx n4l3w=; b=CUoXq46l/2Mx49xxAREmGKM5AGKQ8fRNl3nrd7XHXN2Oy+nHjsajFL RlUMZLoNg0bKDhL6TINcUm9b8FwWpAbAoS04N0jiVpLkJbGiqnEo1+bWdnlgc2qk pEsDzE7zN24TM5ejXhJWj/ZJIQD4KNnSl4XiQBx7i22sHDTBK8zjU= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.8 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 X-HELO: vms173021pub.verizon.net X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=S6gku9YP c=1 sm=1 tr=0 a=Z9UJdt/jcW91Hd6r4aN9qw==:117 a=vP6ySPhpAh4A:10 a=N659UExz7-8A:10 a=w_pzkKWiAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=XAFQembCKUMA:10 a=EhebF9AqHa1K2L5JBSwA:9 a=pILNOxqGKmIA:10 Message-id: <5571204B.4070008@cygwin.com> Date: Fri, 05 Jun 2015 00:06:35 -0400 From: "Larry Hall (Cygwin)" Reply-to: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin: vim causes bash to die References: <3EC211E2982D40B9BB6AA77E3BD6214E AT GatewayI5> <556BBA7B DOT 9020008 AT cygwin DOT com> In-reply-to: Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 06/01/2015 12:30 PM, John Marsh wrote: >> 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. > > 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 > I think what you've provided previously and with the description above is pretty complete now. The problem is I can't reproduce it (tried 10 times in a row from the Windows console) and it's apparently not a real common issue as yours is the first report we've seen. Here's some other suggestions for you to try to see if it helps you avoid the issue you're seeing: 1. Try running vim from mintty instead of the Windows console. 2. Try upgrading to the latest vim (a new one was just released). 3. Try running 'rebase-trigger all' and then re-running 'setup.exe'. See if that changes the vim behavior. -- 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