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=Rqu4xYlmHUvPqZaM D84UVCD4M7WjJa0C09DpaITUWDCNjfmQcju7URVpFLTb8P0yeCan/Zcq8Ho6bm0o c0ykjQ5PzJW8emlu8AdrjojGBydaALp31PV5BeWvws6MKS/5aTQB2d9uRHcJfLMY 3iAJCOeBhWGSpRhmY52drT0/R6g= 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=0BILc1PCl46mkz/w9vCY2/ YeZQw=; b=mDCuONbQwhWH0+tod3AaWiNfsKoDb5HHPMlIt9dnn4JV3JoirhxLlK WjOxByitm0EIofnXr/4EC6/7io5UJtgWEt8kHP4jyD3iy7UsetCWXqONRpjH97XJ ERibt3mJtJ1MN5DlwhQ12Rrd8hVGQgBtBKqZGsFafgmwBkz8/ddbM= 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: vms173025pub.verizon.net X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=Jp0M15MC 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=h1PgugrvaO0A:10 a=K8qnXWEmRwUbJaQLpOIA:9 a=pILNOxqGKmIA:10 Message-id: <556BBA7B.9020008@cygwin.com> Date: Sun, 31 May 2015 21:50:51 -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> In-reply-to: <3EC211E2982D40B9BB6AA77E3BD6214E@GatewayI5> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit 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