X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 26 Jun 2009 15:36:18 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: popup consoles on Windows 7 Message-ID: <20090626133618.GA14187@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <416096c60904210835jd93a1b8w742bb8ebe0802c9c AT mail DOT gmail DOT com> <20090421160026 DOT GJ8722 AT calimero DOT vinschen DOT de> <20090508090737 DOT GA15230 AT calimero DOT vinschen DOT de> <416096c60905131134l21aa53dqe7c3f99130dddb4e AT mail DOT gmail DOT com> <20090626083640 DOT GF30864 AT calimero DOT vinschen DOT de> <416096c60906260239r5bdaf60bw6a9febe885726f55 AT mail DOT gmail DOT com> <20090626102313 DOT GA12963 AT calimero DOT vinschen DOT de> <416096c60906260503o52ae73ben1140bbbd2db993bb AT mail DOT gmail DOT com> <20090626121215 DOT GJ30864 AT calimero DOT vinschen DOT de> <416096c60906260541t56687113p9c940d4251f68405 AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <416096c60906260541t56687113p9c940d4251f68405@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jun 26 13:41, Andy Koppe wrote: > 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.  It'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. Yes, I'm aware how this would work. What I mean is, it's *still* a band-aid since in case of a fail to attach, you still have to alloc a console and you're back to the original problem. What we could do using that technique is to minimize the number of console windows. But it doesn't help to avoid them entirely. You have still cluttered your desktop, or rather, your taskbar with console windows. > 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=83 I assume this... > >> Did you previously mention that MS fixed bug in this area? > > > > Sorry, I don't understand the question.  I don't think I ever mentioned > > 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." ...and that problem are related. It's not the same problem as the AllocConsole shows up on the wrong WindowStation problem we're talking about in this thread, though. The problem with the console handles in 64 bit Windows is fixed in the latest builds. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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