Skip to content

bash Access Violations in Cygwin

April 12, 2010

One day, for no discernible reason at all and due not at all to any action on your part, bash may start stackdumping under cygwin and producing very ominous errors like:


Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
eax=00D84278 ebx=61226E54 ecx=751D783F edx=002E41B8 esi=00000000 edi=0022FA04
ebp=610209C0 esp=0022C7D4 program=C:\cygwin\bin\bash.exe, pid 3136, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
End of stack trace

Don’t panic. The solution seems to be to downgrade to bash 3.2.49-22.

Advertisements

From → tips

2 Comments
  1. DaveK permalink

    If it really happens for seemingly no reason at all, the most likely thing is that your security software has updated itself overnight and become BLODA:

    http://cygwin.com/faq/faq.using.html#faq.using.bloda

    Did you ever try reporting this to the mailing list? I had a look but you didn’t seem to use the wanderer99 handle if you did.

  2. No, I didn’t. I assumed this was a well-known problem. I turned up a few hits on the mailing list when I googled it.

    I’m not using any of the programs in that list, I don’t think.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: