On Tue, Feb 12, 2002 at 09:29:28AM -0500, Jason Tishler wrote: >Command completion specs causes bash 2.05a specifically *and* Cygwin >in general to behave "poorly." By "poorly," I mean that bash becomes >unusable after attempting command completion and Cygwin cannot start >new processes: > >$ ps >C:\cygwin\bin\bash.exe: *** mount table size version mismatch detected - 0x11/0x4068. >You have multiple copies of cygwin1.dll on your system. >Search for cygwin1.dll using the Windows Start->Find/Search facility >and delete all but the most recent version. The most recent version *should* >reside in x:\cygwin\bin, where 'x' is the drive on which you have >installed the cygwin distribution. >5895398 [main] bash 1648 sync_with_child: child 1560(0x1D4) died before >initialization with status code 0x1 >5901389 [main] bash 1648 sync_with_child: *** child state waiting for longjmp >bash: fork: Resource temporarily unavailable > >After killing all Cygwin processes, the above problem is cleared.
Sounds like a *bad* problem with a wild pointer in bash. Anyone interested in tracking this down with gdb? I know that Corinna is sort of swamped right now. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
