100% CPU/Bash command substitution fixed

Chris Faylor cgf@cygnus.com
Mon Feb 28 12:26:00 GMT 2000

On Mon, Feb 28, 2000 at 09:03:29PM +0100, Corinna Vinschen wrote:
>Chris Faylor wrote:
>> On Mon, Feb 28, 2000 at 08:39:48AM -0800, Rick Rankin wrote:
>> >Just a quick note and a word of thanks -- I just downloaded and tried the 0227
>> >snapshot. It appears that the 100% CPU problem and the bash command
>> >substitution problem have been fixed.
>> I'm glad that I've finally fixed the problem for you but I still have
>> one report of a failure that I'm tracking down.
>> Btw, I could not have fixed this without the patient and detailed bug
>> reports from people like Kazuhiro Fujieda, Corinna Vinschen, and
>> matt@use.net.
>> I hope to have the remaining problem tracked down soon.
>Hi Chris,
>is the following related to your remaining problem?
>With the latest patch (00/02/28 08:25:34: pinfo.cc, sigproc.cc)
>I can't start any cygwin app anymore:
>Eg. "bash -login" results in
>D:\usr\bin\bash.exe: *** shared region is corrupted.  inited 10
>   0 [main] ? 0 lock_pinfo_for_update: rc 0, pinfo_mutex 0xFFFFFFFF,
>Win32 error 6
>The strace output is an empty file, unfortunately.

That's usually a sign of some other process running with a different
DLL.  I updated some of the cygwin version numbers recently.

Does this happen after you've rebooted?


More information about the Cygwin-developers mailing list