Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 22 Jul 2003 21:24:15 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: subprocess i/o interaction with shell (bash&cmd): shells compete for input with user program! Message-ID: <20030723012414.GB3329@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030722145702 DOT GA17342 AT redhat DOT com> <20030722172316 DOT GC17916 AT redhat DOT com> <20030722212705 DOT GA26210 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Jul 22, 2003 at 06:12:53PM -0400, Sam Steingold wrote: >> * In message <20030722212705 DOT GA26210 AT redhat DOT com> >> * On the subject of "Re: subprocess i/o interaction with shell (bash&cmd): shells compete for input with user program!" >> * Sent on Tue, 22 Jul 2003 17:27:05 -0400 >> * Honorable Christopher Faylor writes: >> >> If the exec paradigm in cygwin was really broken, the mailing list >> would be filled with people complaining about that fact. > >my fault (gcc does not define UNIX, I should have been more careful, >sorry) > >OK, so -- how do I implement execv() ? >winsup/src/winsup/cygwin/spawn.cc:spawn_guts() is, apparently, >the place to look at, but it is so hairy ... It is hairy but, unfortunately, this is not the place to go for help rolling your own execv. Cygwin already has a nice, functioning execv. As always, I'd suggest google. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.com -- 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/