Mail Archives: cygwin/2006/02/24/09:45:10
On Fri, Feb 24, 2006 at 07:11:14AM -0700, Eric Blake wrote:
>> Exception: STATUS_ACCESS_VIOLATION at eip=00437B40
>> eax=00004000 ebx=00000004 ecx=610FCE28 edx=00000000 esi=0022EED9 edi=61102C1C
>> ebp=0022EEA8 esp=0022EC0C program=C:\cygwin\bin\bash.exe, pid 21516, thread main
>> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
>> Stack trace:
>> Frame Function Args
>> 0022EEA8 00437B40 (00000002, 004B01C0, 004B0090, 61010EAC)
>> 0022EF78 61005BC8 (0022EFD0, FFFFFFFF, 0022EFB3, 00246E40)
>> 0022FF88 61005EB3 (00000000, 00000000, 00000000, 00000000)
>> End of stack trace
>
>Next step - in the cmd.com window, run '.\bash' without arguments, to see
>if it is still crashing. If so, run 'strace -o strace.out bash', and post
>that somewhere where the list readers can see it (strace output tends to
>be large, so don't send it to the list if it is larger than, say 200k or
>so). That may give the cygwin1.dll developers an idea of what is causing
>the crash.
The above stack dump indicates that the crash is happening in bash, not
in cygwin.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -