Just found rebaseall. After the first run (not as administrator), the
error was still present, but the reported address was different. Ran
it again as administrator, and after that the error went away.
Odd thing is that although I ran setup last week in order to install
something new, I'd been u
> bash-4.1$ ls
> 0 [main] bash 8316 child_info_fork::abort: cygreadline7.dll: Loaded to
> different address: parent(0x3C) != child(0x32)
> bash: fork: retry: Resource temporarily unavailable
> 0 [main] bash 7708 child_info_fork::abort: cygreadline7.dll: Loaded to
> different a
Corinna --
> This problem is fixed in CVS for a while. Please test the latest
> developer snapshot from http://cygwin.com/snapshots/
Aha! Thanks!
-- Pat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin
Got another console / bash oddity that just started...
When I start a bash window with C:\cygwin\Cygwin.bat, which runs bash as...
bash --login -i
...doing ^C gets no response: It doesn't clear typing, it doesn't go
back to the shell, it doesn't stop a running program.
If I start bash from ano
Andrey --
> These keys created when you mess with console properties of a running
> application.
> I don't touch them and I only have one bogus subkey mentioning "summary.bat"
> Don't remember, what was that batch, though. I just deleted the subkey for
> now.
Aha! So those subkeys would likely o
It's even weirder, than you'd think.
Hint: reg:HKEY_CURRENT_USER\Console
>>>
>>The MSYS part of msysgit doesn't muck with registry keys. Maybe
>>something with tksh that it uses does.
>
> Since HKEY_CURRENT_USER\Console has subkeys (on my machine) for bash
> and cmd, perhaps the key is cr
Andrey --
>> Background: Ok, this is really weird...
>
> It's even weirder, than you'd think.
> Hint: reg:HKEY_CURRENT_USER\Console
Oh, that. I could *not* remember "console". I was thinking
"terminal" or "you know, whatever it is that Windows runs its command
prompt in" or "the thing that
Corinna --
> Did you update to Cygwin 1.7.11-1 already?
I ran the latest setup (see post for details, relevant section quoted
below) so I'd assume it attempted to install the latest version.
However, the main problem I'm reporting is that the install fails
repeatedly, so, no, it did not successfu
My Cygwin installation was working fine right up to the point where I
had to restore a Windows command prompt shortcut from backup.
Immediately afterward, commands run in the Cygwin shell window (the
one whose shortcut is created at the end of setup, that runs
Cygwin.bat) failed with errors like:
9 matches
Mail list logo
