Cygwin: vim causes bash to die

Larry Hall (Cygwin)
Mon Jun 1 01:51:00 GMT 2015

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.



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:
Unsubscribe info:

More information about the Cygwin mailing list