On Mar 30 16:30, Dave Korn wrote: > On 30 March 2006 16:10, Corinna Vinschen wrote: > > > On Mar 30 14:56, Eric Blake wrote: > >> Jens Wilken <Jens.Wilken <at> osc-es.de> writes: > >> > >>> How does freopen-ing stdout and stderr affect subsequent "system" calls? > >> > >> It shouldn't have any effect on subsequent calls, other than that stderr > >> or stdout is mapped to a new underlying stream. There are other changes, > >> unrelated to freopen, that do affect consoles popping up or not (and by > >> the way, snapshot 20060329 flashes a console when cygrunsrv starts an > > > > This has nothing to do with the snapshot. It's the latest change to > > cygrunsrv which re-introduced the short flash. > > Perhaps so, but perhaps not - see my last post. I'm fairly sure cygrunsrv > should not involved in invoking expect.exe when I write "make -k check" in a > bash shell in a newly-built gcc object dir! I also haven't changed my > cygrunsrv; I can make the condition appear or disappear by using today's dll > or the one I built from the 17th.
I replied only to Eric's observation about cygrunsrv. I didn't talk about other occurences of console windows. As for this spurious console window, it would be very helpful to get a simple testcase... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
