When firing up mintty, I get the following output. Sometimes I
eventually get a prompt, but sometimes it just hangs. It's not mintty
related though, as this happens when I ssh in from other hosts.
2 [main] bash 5048 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
1014 [main] bash 5048 open_stackdumpfile: Dumping stack trace to
bash.exe.sta ckdump
2 [main] bash 3628 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
724 [main] bash 3628 open_stackdumpfile: Dumping stack trace to
bash.exe.sta ckdump
2 [main] bash 2620 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
739 [main] bash 2620 open_stackdumpfile: Dumping stack trace to
bash.exe.sta ckdump
0 [main] bash 5052 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
320 [main] bash 5052 open_stackdumpfile: Dumping stack trace to
bash.exe.sta ckdump
0 [main] bash 2864 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
361 [main] bash 2864 open_stackdumpfile: Dumping stack trace to
bash.exe.sta ckdump
2 [main] -bash 2828 child_copy: linked dll data write copy
failed, 0x33D00 0..0x3414A4,
done 0, windows pid 3108, Win32 error 487
1131084 [main] -bash 228 child_copy: linked dll data write copy failed,
0x33D000 ..0x3414A4, done 0,
windows pid 228, Win32 error 487
2142200 [main] bash 5080 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
2142565 [main] bash 5080 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
2207657 [main] bash 2836 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
2208007 [main] bash 2836 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
2398524 [main] bash 5792 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
2399088 [main] bash 5792 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
2525536 [main] bash 1088 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
2525848 [main] bash 1088 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
2977764 [main] bash 1888 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
2978099 [main] bash 1888 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
3069194 [main] -bash 2828 child_copy: linked dll data write copy failed,
0x33D000..0x3414A4, done 0, windows pid 3108, Win32 error 487
4176819 [main] bash 2860 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
4177524 [main] bash 2860 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
4547675 [main] bash 756 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
4548091 [main] bash 756 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
pwohl...@h1n1 ~
$
pwohl...@h1n1 ~
$ cat bash.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=61020137
eax=00DC1898 ebx=6123C374 ecx=75550D06 edx=003441B8 esi=00000000
edi=0028F9E8
ebp=61020890 esp=0028C7B8 program=D:\apps\cygwin\bin\bash.exe, pid 6104,
thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
End of stack trace
pwohl...@h1n1 ~
$ bash --version
bash --version
GNU bash, version 3.2.51(24)-release (i686-pc-cygwin)
Copyright (C) 2007 Free Software Foundation, Inc.
pwohl...@h1n1 ~
$ uname -a
uname -a
CYGWIN_NT-6.1-WOW64 h1n1 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin
Any thoughts on how to rectify?
Thanks,
Peter Wohlers
--
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
