This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: subprocess i/o interaction with shell (bash&cmd): shells compete for input with user program!


On Tue, Jul 22, 2003 at 06:12:53PM -0400, Sam Steingold wrote:
>> * In message <20030722212705.GA26210@redhat.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 <cgf-idd@cygwin.com> 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@sourceware.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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]