Mail Archives: cygwin/2009/06/26/08:41:35
2009/6/26 Corinna Vinschen:
>> Forgot to say: the occurances of this could at least be reduced by
>> trying AttachConsole to get a hold on the parent process' console, if
>> any. When I attempted that in MinTTY, though, I couldn't make it work.
>
> Yes, I thought of trying AttachConsole first. =C2=A0It's a band-aid since
> it will of course not work if there's just no parent console
That can be dealt with, because AttachConsole reports back whether it
did manage to attach, so if it doesn't, one can then call AllocConsole
and ShowWindowAsync.
But on 64-bit Windows 7 there were some bizarre problems, where it
just wouldn't attach or it would completely block the parent's
console. See http://code.google.com/p/mintty/issues/detail?id=3D83
>> Did you previously mention that MS fixed bug in this area?
>
> Sorry, I don't understand the question. =C2=A0I don't think I ever mentio=
ned
> anything related to a MS bugfix in terms of AttachConsole.
Ah, seems I jumped to conclusions from this, although it does sound
like it might address the problems above:
2009/5/16 Corinna Vinschen:
"That's not a workaround for the problem with consoles popping up, but a
workaround for a W7 x64 specific problem. There's a bug in the W7 x64
console code (which appears to be mostly rewritten in W7 anyway) which
breaks DLL initialization in child processes which have no copy of the
original console handles from console startup anymore. This bug has been
reported upstream and is marked as being resolved, which hopefully
means it will be fixed in the final W7 release."
Andy
--
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
- Raw text -