|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
|
|
fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONRight after installing with nothing but the default packages and options,
when launching cygwin, bash flashes an error message for half a second and goes away. This is a first time install on vista 64 ultimate using 1.7 with setup version 2.637. I restarted, deleted cygwin directories and reinstalled with a different mirror and got the same result. I found the following in C:/cygwin/bash.exe.stackdump. When the error flashes, it shows different line numbers each time, like bash 1948. Oddly, I deleted the stackdump file, and it is never created again even when I have the error again afterwards. Exception: STATUS_ACCESS_VIOLATION at eip=08CE0000 eax=08CE0000 ebx=00000001 ecx=75F05709 edx=000000FE esi=73CBCAD4 edi=61157FEF ebp=0027CCA8 esp=0027CC9C program=C:\cygwin\bin\bash.exe, pid 2584, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args 0027CCA8 08CE0000 (6120B808, 6120C41C, 00FF87D2, 61020360) 0027CD78 61020293 (00000000, 0027CDB0, 610066C0, 7EFDE000) End of stack trace 848826 [main] bash 2584 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 870894 [main] bash 2584 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) - Ian Kelling -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONUpdate: This looks like the same error as Edward Lam posted on 7/2/2009 in
response to a bash update announcement. Attached is my cygcheck output. - Ian Kelling Cygwin Configuration Diagnostics Current System Time: Sat Jul 04 23:26:58 2009 Windows Vista Ultimate Ver 6.0 Build 6001 Service Pack 1 Running under WOW64 on AMD64 Path: C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem Output from C:\cygwin\bin\id.exe (nontsec) UID: 400(ian) GID: 401(mkpasswd) 401(mkpasswd) Output from C:\cygwin\bin\id.exe (ntsec) UID: 400(ian) GID: 401(mkpasswd) 401(mkpasswd) SysDir: C:\Windows\system32 WinDir: C:\Windows HOME = 'F:\a' Path = 'C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem' ALLUSERSPROFILE = 'C:\ProgramData' APPDATA = 'C:\Users\ian\AppData\Roaming' CommonProgramFiles = 'C:\Program Files (x86)\Common Files' CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files' CommonProgramW6432 = 'C:\Program Files\Common Files' COMPUTERNAME = 'VL' ComSpec = 'C:\Windows\system32\cmd.exe' FP_NO_HOST_CHECK = 'NO' HOMEDRIVE = 'C:' HOMEPATH = '\Users\ian' LOCALAPPDATA = 'C:\Users\ian\AppData\Local' LOGONSERVER = '\\VL' NUMBER_OF_PROCESSORS = '2' OS = 'Windows_NT' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' PROCESSOR_ARCHITECTURE = 'x86' PROCESSOR_ARCHITEW6432 = 'AMD64' PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 15 Stepping 13, GenuineIntel' PROCESSOR_LEVEL = '6' PROCESSOR_REVISION = '0f0d' ProgramData = 'C:\ProgramData' ProgramFiles = 'C:\Program Files (x86)' ProgramFiles(x86) = 'C:\Program Files (x86)' ProgramW6432 = 'C:\Program Files' PROMPT = '$P$G' PUBLIC = 'C:\Users\Public' SESSIONNAME = 'Console' SystemDrive = 'C:' SystemRoot = 'C:\Windows' TEMP = 'C:\Users\ian\AppData\Local\Temp' TMP = 'C:\Users\ian\AppData\Local\Temp' USERDOMAIN = 'vl' USERNAME = 'ian' USERPROFILE = 'C:\Users\ian' windir = 'C:\Windows' HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygwin\setup HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.gov%2fpub%2fcygwin%2f HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.gov%2fpub%2fcygwin%2f\OpenWithList HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu\Programs\Cygwin (default) = (unsupported type) HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'C:\cygwin' HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygnus Solutions\Cygwin\mounts v2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\setup (default) = 'C:\cygwin' obcaseinsensitive set to 1 c: hd NTFS 102399Mb 35% CP CS UN PA FC d: hd NTFS 3999Mb 2% CP CS UN PA FC e: hd NTFS 119Mb 12% CP CS UN PA FC f: hd NTFS 370416Mb 62% CP CS UN PA FC C:\cygwin / system binary,auto C:\cygwin\bin /usr/bin system binary,auto C:\cygwin\lib /usr/lib system binary,auto cygdrive prefix /cygdrive user binary,auto Not Found: awk Not Found: bash Not Found: cat Not Found: cp Not Found: cpp (good!) Not Found: crontab Found: C:\Windows\system32\find.exe Not Found: gcc Not Found: gdb Not Found: grep Not Found: kill Not Found: ld Not Found: ls Not Found: make Not Found: mv Not Found: patch Not Found: perl Not Found: rm Not Found: sed Not Found: ssh Not Found: sh Not Found: tar Not Found: test Not Found: vi Not Found: vim 61k 2009/03/02 .\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0 "cygbz2-1.dll" v0.0 ts=2009/3/1 19:11 40k 2009/03/01 .\cygform-8.dll - os=4.0 img=1.0 sys=4.0 "cygform-8.dll" v0.0 ts=2009/2/28 22:32 41k 2009/03/27 .\cygform-9.dll - os=4.0 img=1.0 sys=4.0 "cygform-9.dll" v0.0 ts=2009/3/26 22:02 42k 2009/03/12 .\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0 "cyggcc_s-1.dll" v0.0 ts=2009/3/6 3:54 315k 2009/06/06 .\cyggmp-3.dll - os=4.0 img=1.0 sys=4.0 "cyggmp-3.dll" v0.0 ts=2009/6/6 4:23 25k 2009/06/23 .\cyghistory7.dll - os=4.0 img=1.0 sys=4.0 "cyghistory7.dll" v0.0 ts=2009/6/23 8:38 270k 2009/05/07 .\cygicons-0.dll - os=4.0 img=1.0 sys=4.0 "cygicons-0.dll" v0.0 ts=2009/5/6 17:58 981k 2009/05/30 .\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0 "cygiconv-2.dll" v0.0 ts=2009/5/30 12:05 31k 2005/11/20 .\cygintl-3.dll - os=4.0 img=1.0 sys=4.0 "cygintl-3.dll" v0.0 ts=2005/11/19 18:04 31k 2009/04/03 .\cygintl-8.dll - os=4.0 img=1.0 sys=4.0 "cygintl-8.dll" v0.0 ts=2009/4/2 18:15 5k 2009/06/18 .\cyglsa.dll - os=4.0 img=1.0 sys=4.0 "cyglsa.dll" v0.0 ts=2009/6/18 3:52 9k 2009/06/18 .\cyglsa64.dll - os=4.0 img=0.0 sys=5.2 21k 2009/03/01 .\cygmenu-8.dll - os=4.0 img=1.0 sys=4.0 "cygmenu-8.dll" v0.0 ts=2009/2/28 22:31 21k 2009/03/27 .\cygmenu-9.dll - os=4.0 img=1.0 sys=4.0 "cygmenu-9.dll" v0.0 ts=2009/3/26 22:01 211k 2009/06/06 .\cygmp-3.dll - os=4.0 img=1.0 sys=4.0 "cygmp-3.dll" v0.0 ts=2009/6/6 4:23 66k 2009/03/01 .\cygncurses++-8.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++-8.dll" v0.0 ts=2009/2/28 22:39 334k 2009/03/27 .\cygncurses++-9.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++-9.dll" v0.0 ts=2009/3/26 22:12 237k 2009/03/01 .\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0 "cygncurses-8.dll" v0.0 ts=2009/2/28 22:28 164k 2009/03/27 .\cygncurses-9.dll - os=4.0 img=1.0 sys=4.0 "cygncurses-9.dll" v0.0 ts=2009/3/26 21:58 11k 2009/03/01 .\cygpanel-8.dll - os=4.0 img=1.0 sys=4.0 "cygpanel-8.dll" v0.0 ts=2009/2/28 22:30 11k 2009/03/27 .\cygpanel-9.dll - os=4.0 img=1.0 sys=4.0 "cygpanel-9.dll" v0.0 ts=2009/3/26 22:00 190k 2009/04/17 .\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcre-0.dll" v0.0 ts=2009/4/17 9:07 7k 2009/04/17 .\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcreposix-0.dll" v0.0 ts=2009/4/17 9:07 22k 2002/06/09 .\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0 "cygpopt-0.dll" v0.0 ts=2002/6/8 22:45 162k 2009/06/23 .\cygreadline7.dll - os=4.0 img=1.0 sys=4.0 "cygreadline7.dll" v0.0 ts=2009/6/23 8:38 66k 2009/03/27 .\cygtic-9.dll - os=4.0 img=1.0 sys=4.0 "cygtic-9.dll" v0.0 ts=2009/3/26 21:54 64k 2009/03/02 .\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2009/3/1 17:33 2376k 2009/06/18 .\cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=2009/6/18 3:51 Cygwin DLL version info: DLL version: 1.7.0 DLL epoch: 19 DLL old termios: 5 DLL malloc env: 28 Cygwin conv: 181 API major: 0 API minor: 210 Shared data: 5 DLL identifier: cygwin1 Mount registry: 3 Cygwin registry name: Cygwin Program options name: Program Options Cygdrive default prefix: Build date: Thu Jun 18 12:51:49 CEST 2009 Shared id: cygwin1S5 61k 2009/03/02 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0 "cygbz2-1.dll" v0.0 ts=2009/3/1 19:11 40k 2009/03/01 C:\cygwin\bin\cygform-8.dll - os=4.0 img=1.0 sys=4.0 "cygform-8.dll" v0.0 ts=2009/2/28 22:32 41k 2009/03/27 C:\cygwin\bin\cygform-9.dll - os=4.0 img=1.0 sys=4.0 "cygform-9.dll" v0.0 ts=2009/3/26 22:02 42k 2009/03/12 C:\cygwin\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0 "cyggcc_s-1.dll" v0.0 ts=2009/3/6 3:54 315k 2009/06/06 C:\cygwin\bin\cyggmp-3.dll - os=4.0 img=1.0 sys=4.0 "cyggmp-3.dll" v0.0 ts=2009/6/6 4:23 25k 2009/06/23 C:\cygwin\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0 "cyghistory7.dll" v0.0 ts=2009/6/23 8:38 270k 2009/05/07 C:\cygwin\bin\cygicons-0.dll - os=4.0 img=1.0 sys=4.0 "cygicons-0.dll" v0.0 ts=2009/5/6 17:58 981k 2009/05/30 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0 "cygiconv-2.dll" v0.0 ts=2009/5/30 12:05 31k 2005/11/20 C:\cygwin\bin\cygintl-3.dll - os=4.0 img=1.0 sys=4.0 "cygintl-3.dll" v0.0 ts=2005/11/19 18:04 31k 2009/04/03 C:\cygwin\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0 "cygintl-8.dll" v0.0 ts=2009/4/2 18:15 5k 2009/06/18 C:\cygwin\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0 "cyglsa.dll" v0.0 ts=2009/6/18 3:52 9k 2009/06/18 C:\cygwin\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2 21k 2009/03/01 C:\cygwin\bin\cygmenu-8.dll - os=4.0 img=1.0 sys=4.0 "cygmenu-8.dll" v0.0 ts=2009/2/28 22:31 21k 2009/03/27 C:\cygwin\bin\cygmenu-9.dll - os=4.0 img=1.0 sys=4.0 "cygmenu-9.dll" v0.0 ts=2009/3/26 22:01 211k 2009/06/06 C:\cygwin\bin\cygmp-3.dll - os=4.0 img=1.0 sys=4.0 "cygmp-3.dll" v0.0 ts=2009/6/6 4:23 66k 2009/03/01 C:\cygwin\bin\cygncurses++-8.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++-8.dll" v0.0 ts=2009/2/28 22:39 334k 2009/03/27 C:\cygwin\bin\cygncurses++-9.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++-9.dll" v0.0 ts=2009/3/26 22:12 237k 2009/03/01 C:\cygwin\bin\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0 "cygncurses-8.dll" v0.0 ts=2009/2/28 22:28 164k 2009/03/27 C:\cygwin\bin\cygncurses-9.dll - os=4.0 img=1.0 sys=4.0 "cygncurses-9.dll" v0.0 ts=2009/3/26 21:58 11k 2009/03/01 C:\cygwin\bin\cygpanel-8.dll - os=4.0 img=1.0 sys=4.0 "cygpanel-8.dll" v0.0 ts=2009/2/28 22:30 11k 2009/03/27 C:\cygwin\bin\cygpanel-9.dll - os=4.0 img=1.0 sys=4.0 "cygpanel-9.dll" v0.0 ts=2009/3/26 22:00 190k 2009/04/17 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcre-0.dll" v0.0 ts=2009/4/17 9:07 7k 2009/04/17 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcreposix-0.dll" v0.0 ts=2009/4/17 9:07 22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0 "cygpopt-0.dll" v0.0 ts=2002/6/8 22:45 162k 2009/06/23 C:\cygwin\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0 "cygreadline7.dll" v0.0 ts=2009/6/23 8:38 66k 2009/03/27 C:\cygwin\bin\cygtic-9.dll - os=4.0 img=1.0 sys=4.0 "cygtic-9.dll" v0.0 ts=2009/3/26 21:54 64k 2009/03/02 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2009/3/1 17:33 2376k 2009/06/18 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=2009/6/18 3:51 Cygwin DLL version info: DLL version: 1.7.0 DLL epoch: 19 DLL old termios: 5 DLL malloc env: 28 Cygwin conv: 181 API major: 0 API minor: 210 Shared data: 5 DLL identifier: cygwin1 Mount registry: 3 Cygwin registry name: Cygwin Program options name: Program Options Cygdrive default prefix: Build date: Thu Jun 18 12:51:49 CEST 2009 Shared id: cygwin1S5 Warning: There are multiple cygwin1.dlls on your path Can't find the cygrunsrv utility, skipping services check. Cygwin Package Information Last downloaded files to: C:\packages Last downloaded files from: ftp://mirror.cs.vt.edu/pub/cygwin/cygwin/ Package Version _update-info-dir 00826-1 alternatives 1.3.30c-10 ash 20040127-4 base-cygwin 2.0-1 base-files 3.8-4 base-passwd 3.1-1 bash 3.2.49-23 bzip2 1.0.5-10 coreutils 7.0-2 cygutils 1.4.0-1 cygwin 1.7.0-50 cygwin-doc 1.5-1 editrights 1.01-2 findutils 4.5.4-1 gawk 3.1.6-2 grep 2.5.3-1 groff 1.19.2-2 gzip 1.3.12-2 ipc-utils 1.0-1 less 429-1 libbz2_1 1.0.5-10 libgcc1 4.3.2-2 libgmp3 4.3.1-3 libiconv2 1.13-10 libintl3 0.14.5-1 libintl8 0.17-11 libncurses8 5.5-10 libncurses9 5.7-14 libpcre0 7.9-1 libpopt0 1.6.4-4 libreadline7 6.0.3-1 login 1.10-10 man 1.6e-1 rebase 3.0-2 run 1.1.10-1 sed 4.1.5-2 tar 1.22-1 termcap 20050421-1 terminfo 5.7_20090228-10 terminfo0 5.5_20061104-10 texinfo 4.13-3 tzcode 2008h-1 which 2.20-2 zlib0 1.2.3-10 Use -h to see help about each section -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONMoving to this thread:
Vincent R. wrote: >> I backed down on bash version which required install of libreadline6. >> >> bash still fails. This is on NT4. >> >> Maybe I need a different combination of binutils, libreadline, and bash. > I >> will play with this for a bit. >> >> Jerry > > I have installed new binutils and previous bash version and now it works > for me. > > > I am not having the same results so I am going to delete all and start fresh > > again. Fresh install still broken with backing down one rev on bash and using libreadline6. Jerry -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONJerry DeLisle wrote:
> Moving to this thread: > Vincent R. wrote: >>> I backed down on bash version which required install of libreadline6. >>> >>> bash still fails. This is on NT4. >>> >>> Maybe I need a different combination of binutils, libreadline, and bash. >> I >>> will play with this for a bit. >>> >>> Jerry >> >> I have installed new binutils and previous bash version and now it works >> for me. >> >> >> I am not having the same results so I am going to delete all and start > fresh > > again. > > Fresh install still broken with backing down one rev on bash and using > libreadline6. Post cygcheck output, both of you, and let's compare. cheers, DaveK -- 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 |
|
|
|
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION> Post cygcheck output, both of you, and let's compare.
$ cygcheck -c Cygwin Package Information Package Version Status _update-info-dir 00826-1 OK alternatives 1.3.30c-10 OK ash 20040127-4 OK autoconf 6-10 OK autoconf2.1 2.13-10 OK autoconf2.5 2.63-10 OK automake 4-10 OK automake1.10 1.10.2-10 OK automake1.11 1.11-10 OK automake1.4 1.4p6-10 OK automake1.5 1.5-10 OK automake1.6 1.6.3-11 OK automake1.7 1.7.9-10 OK automake1.8 1.8.5-10 OK automake1.9 1.9.6-10 OK base-cygwin 2.0-1 OK base-files 3.8-4 OK base-passwd 3.1-1 OK bash 3.2.49-22 OK binutils 2.19.51-1 OK bzip2 1.0.5-10 OK coreutils 7.0-2 OK cpio 2.9.90-5 OK crypt 1.1-1 OK cvs 1.12.13-10 OK cvsps 2.1-1 OK cygutils 1.4.0-1 OK cygwin 1.7.0-50 OK cygwin-doc 1.5-1 OK diffutils 2.8.7-1 OK editrights 1.01-2 OK expat 2.0.1-1 OK file 5.00-3 OK findutils 4.5.4-1 OK gawk 3.1.6-2 OK gettext 0.17-11 OK gettext-devel 0.17-11 OK git 1.6.3.2-1 OK grep 2.5.3-1 OK groff 1.19.2-2 OK gzip 1.3.12-2 OK ipc-utils 1.0-1 OK less 429-1 OK libbz2_1 1.0.5-10 OK libcurl4 7.19.4-1 OK libdb4.5 4.5.20.2-2 OK libexpat1 2.0.1-1 OK libexpat1-devel 2.0.1-1 OK libgcc1 4.3.2-2 OK libgdbm4 1.8.3-20 OK libgettextpo0 0.17-11 OK libgmp3 4.3.1-3 OK libiconv2 1.13-10 OK libidn11 1.9-1 OK libintl2 0.12.1-3 OK libintl3 0.14.5-1 OK libintl8 0.17-11 OK libltdl7 2.2.7a-13 OK liblzma0 4.999.8beta-10 OK liblzma1 4.999.8betaCYG4-10 OK libncurses8 5.5-10 OK libncurses9 5.7-14 OK libpcre0 7.9-1 OK libpopt0 1.6.4-4 OK libreadline6 5.2.14-12 OK libreadline7 6.0.3-1 OK libssh2_1 1.0-1 OK libtool 2.2.7a-13 OK login 1.10-10 OK m4 1.4.13-1 OK man 1.6e-1 OK openssl 0.9.8k-2 OK perl 5.10.0-5 OK perl-Error 0.17014-1 OK pkg-config 0.23b-10 OK rebase 3.0-2 OK run 1.1.10-1 OK sed 4.1.5-2 OK tar 1.22-1 OK termcap 20050421-1 OK terminfo 5.7_20090228-10 OK terminfo0 5.5_20061104-10 OK texinfo 4.13-3 OK tzcode 2008h-1 OK which 2.20-2 OK xz 4.999.8betaCYG4-10 OK zlib 1.2.3-10 OK zlib-devel 1.2.3-10 OK zlib0 1.2.3-10 OK -- 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 |
|
|
|
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONOn Sun, Jul 05, 2009 at 10:49:10AM -0700, Jerry DeLisle wrote:
>Moving to this thread: >Vincent R. wrote: >>>I backed down on bash version which required install of libreadline6. >>> >>>bash still fails. This is on NT4. >>> >>>Maybe I need a different combination of binutils, libreadline, and >>>bash. >>I >>>will play with this for a bit. >>> >>>Jerry >> >>I have installed new binutils and previous bash version and now it >>works for me. >> >> >>I am not having the same results so I am going to delete all and start >>fresh >>>again. > >Fresh install still broken with backing down one rev on bash and using >libreadline6. FWIW, I had the same problem on Windows 7 and, having read the mailing list, I knew that there was a problem so I dropped back to bash 3.2.49-22 by clicking on the "New" column on the package selection screen. No other action was required to make bash work again. cgf -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONVincent R. wrote:
> bash 3.2.49-22 OK > libreadline6 5.2.14-12 OK > libreadline7 6.0.3-1 OK Jerry DeLisle wrote: > bash 3.2.49-22 > libreadline6 5.2.14-12 > libreadline7 6.0.3-1 Err, ok. So you've got the working versions. So why do you think you're getting the same bug at all? Surely this *has* to be some entirely different issue than the one that's breaking a version of bash that you aren't using on a version of windows that you aren't using? cheers, DaveK -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 According to Jerry DeLisle on 7/5/2009 1:35 PM: > Warning: There are multiple cygwin1.dlls on your path > That's probably your culprit. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpRXy0ACgkQ84KuGfSFAYA3TQCeNEPtzN6k9TSQVjQuHWstrAsQ oI8AnR5e1SM8Z1UPoBzoXScaMhsPgTxO =n8yO -----END PGP SIGNATURE----- -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONEric Blake wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Jerry DeLisle on 7/5/2009 1:35 PM: >> Warning: There are multiple cygwin1.dlls on your path >> > > That's probably your culprit. > I saw that too and did a full search of the disk and there is only one cygwin1.dll I am also seeing a stack dump for id.exe and one for bash.exe. The id.exe stackdump occurs when I execute cygcheck -s The other symptoms are: none of the startup scripts are being sourced (executed). I end up with a bare shell running with /usr/bin as the current working directory. The only reason I can do anything at all is I added the cygwin bin directory to the windows path. Regards, Jerry -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONDave Korn wrote:
> Vincent R. wrote: > >> bash 3.2.49-22 OK >> libreadline6 5.2.14-12 OK >> libreadline7 6.0.3-1 OK > > Jerry DeLisle wrote: > >> bash 3.2.49-22 >> libreadline6 5.2.14-12 >> libreadline7 6.0.3-1 > > Err, ok. So you've got the working versions. So why do you think you're > getting the same bug at all? > > Surely this *has* to be some entirely different issue than the one that's > breaking a version of bash that you aren't using on a version of windows that > you aren't using? > I am very happy to accept that this problem is something else. Vincent sent a note that it is working for him. I am not sure what "working" means. I have a bash prompt, but none of the default environment variables such as prompts and paths and setting up the home directory are complete. My original post was "Bash initialization w/cygwin-1.7" What is next step. Regards, Jerry -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONOn Sun, Jul 05, 2009 at 07:34:24PM -0700, Jerry DeLisle wrote:
>Eric Blake wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> According to Jerry DeLisle on 7/5/2009 1:35 PM: >>> Warning: There are multiple cygwin1.dlls on your path >>> >> >> That's probably your culprit. >> >I saw that too and did a full search of the disk and there is only one cygwin1.dll > >I am also seeing a stack dump for id.exe and one for bash.exe. The id.exe >stackdump occurs when I execute cygcheck -s > >The other symptoms are: none of the startup scripts are being sourced (executed). > >I end up with a bare shell running with /usr/bin as the current working >directory. The only reason I can do anything at all is I added the cygwin bin >directory to the windows path. You're still in the wrong thread. Look at the subject. Does it have anything to do with the problem you are having? Apparently it doesn't. It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION which is known to occur on Windows 7 with your not-so-serious "Bash initialization w/cygwin-1.7". My release of binutils means that Eric can respin bash. It doesn't mean that, if you install binutils, it will somehow fix bash. But, I'm not sure why binutils would be to blame for bash not initializing correctly. cgf -- 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 |
|
|
Re: Bash initialization w/cygwin-1.7Christopher Faylor wrote:
> On Sun, Jul 05, 2009 at 07:34:24PM -0700, Jerry DeLisle wrote: >> Eric Blake wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> According to Jerry DeLisle on 7/5/2009 1:35 PM: >>>> Warning: There are multiple cygwin1.dlls on your path >>>> >>> That's probably your culprit. >>> >> I saw that too and did a full search of the disk and there is only one cygwin1.dll >> >> I am also seeing a stack dump for id.exe and one for bash.exe. The id.exe >> stackdump occurs when I execute cygcheck -s >> >> The other symptoms are: none of the startup scripts are being sourced (executed). >> >> I end up with a bare shell running with /usr/bin as the current working >> directory. The only reason I can do anything at all is I added the cygwin bin >> directory to the windows path. > > You're still in the wrong thread. Look at the subject. Does it have > anything to do with the problem you are having? Apparently it doesn't. > > It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION which > is known to occur on Windows 7 with your not-so-serious "Bash > initialization w/cygwin-1.7". > > My release of binutils means that Eric can respin bash. It doesn't mean > that, if you install binutils, it will somehow fix bash. > > But, I'm not sure why binutils would be to blame for bash not > initializing correctly. > Well, I am moving to this thread now. I presumed this has something to do with bash, maybe execution of the post install scripts has been messed up. Perhaps the default bash startup scripts are not present at all. Regardless, I was seeing the bash stackdump and that is what lead me to believe it was the other problem (other thread) Jerry -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONOn Sun, July 5, 2009 13:49, Jerry DeLisle wrote:
> Fresh install still broken with backing down one rev on bash and using > libreadline6. I ran into this Friday as others have noted. The thing that caught me was that the postinstall scripts in the installer rely on a working bash. Once I had a broken fresh cygwin install, simply backing down one rev of bash didn't help because the postinstall scripts of the OTHER packages that are already installed need to be re-run since they didn't run in the first place. Here's what I did (roughly) in order to get a working cygwin 1.7 installation: - Backup any data I wanted to keep under c:/cygwin/home/username - Removed c:/cygwin and all previously downloaded files by setup-1.7.exe - Launched setup-1.7.exe - Specify additional packages that I wanted to install - Changed the version of bash down to 3.2.49-22 - Added libreadline6 package - Now install the changes Regards, -Edward -- 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 |
|
|
Re: Bash initialization w/cygwin-1.7Jerry DeLisle wrote:
> Well, I am moving to this thread now. Jerry, can I show you something you must not have realised about how email threading works? When you hit "Reply" to an existing post, your mailer adds "In-Reply-To:" and/or "References:" headers to your reply, so that other mailers can display the replies in a threaded display. If you are in the habit of replying to an existing post to save typing the list address into the "From:" line, all your posts really will be indexed and displayed as replies to the posts you reply to. Changing the subject line doesn't help. So for example your initial post wasn't exactly easy to spot, being as it was tagged on the end of a thread that had been dead for a month: http://img191.imageshack.us/img191/9559/jerrypost1.png Likewise, where you say above "I am moving to this thread now", you have in fact done nothing of the sort: http://img8.imageshack.us/img8/4305/jerrypost2.png If you want to save some typing, you need to use your mailer's address book or autocompletion features. Not randomly replying to existing posts. cheers, DaveK -- 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 |
|
|
Re: Bash initialization w/cygwin-1.7Dave Korn wrote:
> Jerry DeLisle wrote: > >> Well, I am moving to this thread now. > > Jerry, can I show you something you must not have realised about how email > threading works? > Thank you for pointing this out. I usually don't use the thread view in my mail client. I will avoid this breakage in the future as best I can. I will attempt to start a fresh thread. Jerry -- 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 |
|
|
Re: Bash initialization w/cygwin-1.7Jerry DeLisle wrote:
> Dave Korn wrote: >> Jerry DeLisle wrote: >> >>> Well, I am moving to this thread now. >> >> Jerry, can I show you something you must not have realised about how >> threading works? >> > > Thank you for pointing this out. I usually don't use the thread view in > my mail client. I will avoid this breakage in the future as best I can. > I will attempt to start a fresh thread. Actually, starting a new thread isn't hard. Just send a new message rather than replying to any existing one. New message = new thread. See, easy! :-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ 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: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONJerry DeLisle wrote:
> I am very happy to accept that this problem is something else. Vincent > sent a note that it is working for him. I am not sure what "working" > means. I have a bash prompt, but none of the default environment > variables such as prompts and paths and setting up the home directory > are complete. Sounds like your the post install scripts didn't run on the initial install. Reinstall from scratch (meaning delete cygwin directory and everything) and select the working bash and libreadline6. - Ian Kelling -- 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 |
|
|
Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATIONChristopher Faylor wrote:
> It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION which > is known to occur on Windows 7 with your not-so-serious "Bash > initialization w/cygwin-1.7". not-so-serious? Cygwin 1.7 install is very broken because of this bug. Seems serious to me. Is anyone able to install a fresh 1.7 with the default settings and not have bash fail? If so, perhaps post cygcheck to compare? - Ian Kelling -- 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 |
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |