This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION




Kris Thielemans-2 wrote:
> 
> Hi
> 
> I'm running (up-to-date) Cygwin 1.7.9-1 on Windows7 sp1 64-bit.
> 
> I recently am getting lots of errors like this
> 
> bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> 
> The messages do not happen all the time (for example, from bash (in minty)
> I
> do a few times ls. After about 4, I get 1-2 of these messages). They seem
> to
> mention only bash or sh. Here's an example of the stackdump
> 
> 
> Exception: STATUS_ACCESS_VIOLATION at eip=6102048B
> eax=00F70598 ebx=612454AC ecx=74C00F81 edx=003451F8 esi=00000000
> edi=0028F9F4
> ebp=61020C00 esp=0028C7C4 program=C:\cygwin\bin\bash.exe, pid 6236, thread
> main
> cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
> Stack trace:
> Frame     Function  Args
> End of stack trace
> 
> This seems to happen with pretty much all Cygwin programs (I've tried
> rsync,
> ls, cat, vi, gcc). The strange thing is of course that the exception
> mentioned is always in bash or sh, but that the actual program is just
> running fine. (Just as a sanity check I set PS1=\$, but still the same).
> 
> Up to recently, everything was fine on my system. It might have started
> after I did a rebaseall but I am unfortunately not sure.
> 
> What can I do to debug this?
> 
> Thanks
> 
> Kris
> 
> 
>  
> --
> 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
> 



> STATUS_ACCESS_VIOLATION at eip=6102048B 
I have debugged that, see
http://old.nabble.com/STATUS_ACCESS_VIOLATION-to32557806.html.

I do not know the direct cause. The post above contains a modification to
tamper the problem.
Without anything else, 
cat /proc/*/maps | egrep '^[01]' | egrep -v cygdrive | egrep -v .exe$
might reveal troubled dlls. Does it help to rebase them manually ?


Please, if you need again help with workarround or solution, ask a new
question to the folks on this forum. 



-- 
View this message in context: http://old.nabble.com/bash-2112-exception%3A%3Ahandle%3A-Exception%3A-STATUS_ACCESS_VIOLATION-tp32566047p32587500.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]