RE: using spawn functions to avoid fork() errors -- FIXED

2014-02-07 Thread Steven Bardwell
On 2/6/2014 8:50 AM, Steven Bardwell wrote: Larry - thanks for the link to the source for the spawn() APIs. It works perfectly on my 32-bit install (where, as it happens, the fork() issue never shows up either). However, on my 64-bit install, the spawnv() call is returning with an

RE: using spawn functions to avoid fork() errors -- FIXED

2014-02-07 Thread Steven Bardwell
On 2/6/2014 8:50 AM, Steven Bardwell wrote: Larry - thanks for the link to the source for the spawn() APIs. It works perfectly on my 32-bit install (where, as it happens, the fork() issue never shows up either). However, on my 64-bit install, the spawnv() call is returning with an

Re: using spawn functions to avoid fork() errors -- FIXED

2014-02-07 Thread Andrey Repin
Greetings, Steven Bardwell! I found the problem that was causing the failure of child creation logic on the 64-bit install but not on the 32-bit version: in an effort to make the output from 'ps' more useful, my application was over-writing the contents of argv[1] in the main process. This

Re: using spawn functions to avoid fork() errors

2014-02-06 Thread Larry Hall (Cygwin)
On 2/6/2014 8:50 AM, Steven Bardwell wrote: On 2/5/2014 7:07 AM, Steven Bardwell wrote: I have no problem doing some recoding of my application to reliably solve my issues with fork() -- can you all point me in the direction of the 'spawn family of calls'? See spawn.cc -

RE: using spawn functions to avoid fork() errors

2014-02-06 Thread Steven Bardwell
On 2/6/2014 8:50 AM, Steven Bardwell wrote: Larry - thanks for the link to the source for the spawn() APIs. It works perfectly on my 32-bit install (where, as it happens, the fork() issue never shows up either). However, on my 64-bit install, the spawnv() call is returning with an

Re: using spawn functions to avoid fork() errors

2014-02-06 Thread Larry Hall (Cygwin)
On 2/6/2014 5:14 PM, Steven Bardwell wrote: On 2/6/2014 8:50 AM, Steven Bardwell wrote: Larry - thanks for the link to the source for the spawn() APIs. It works perfectly on my 32-bit install (where, as it happens, the fork() issue never shows up either). However, on my 64-bit install,

Re: using spawn functions to avoid fork() errors

2014-02-06 Thread David Conrad
On 2/6/2014 8:50 AM, Steven Bardwell wrote: However, on my 64-bit install, the spawnv() call is returning with an error -- 'No such file or directory' -- when I try to spawn /bin/sh. A few things come to mind as possibilities to check, or try. First, there is a certain amount of magic that

Re: using spawn functions to avoid fork() errors

2014-02-05 Thread Larry Hall (Cygwin)
On 2/5/2014 7:07 AM, Steven Bardwell wrote: From reading the Cygwin FAQ (In most cases, you are better off using the spawn family of calls if possible.) and the Cygwin Highlights (Fortunately, in most circumstances the spawn family of calls provided by Cygwin can be substituted for a fork/exec