X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: freopen irritates system-call/sh.exe Date: Thu, 30 Mar 2006 16:03:25 +0100 Message-ID: <067701c6540b$19beb5a0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Note-from-DJ: This may be spam On 30 March 2006 15:57, Eric Blake wrote: > Jens Wilken 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 > interactive process, which is a regression from snapshot 20060308 - I'll > have to narrow it down to when that regression started happening). To help, it wasn't happening with a dll built from cvs on the 17th, but when I updated and built from CVS this morning I suddenly started getting millions of expect.exe windows spawning when I fired off the gcc testsuite! [ Because I've got work to get on with at the moment I rolled it back, but I'll spend some time trying to understand it later. ] cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/