• Nemo (17/17) Sep 08 2013 Hi,
• Adam D. Ruppe (10/10) Sep 08 2013 My guess, just looking at it, is that spawnProcess fails because
• Nemo (2/2) Sep 08 2013 Thank you, Config.suppressConsole did not help, but redirecting

"Nemo" <fake nowhere.com> writes:

Hi,

I have win32 program, which takes command line parameters and 
passes them trough socket to another program, running on the same 
machine. If connection fails, it needs to start the another 
program.

I don't want console to popup so I added "-L/SUBSYSTEM:WINDOWS". 
This works fine, except when it would need to start the another 
program, which fails silently. And I guess because console is 
hidden, no error messages or exceptions appear if I try to run it 
from console. Removing the linker directive makes spawnProcess 
work. To make this mysterious, when I run it from eclipse DDT it 
works all the time...

The starting happens in catch:
} catch (SocketException ex) {
    spawnProcess([`c:\Progra~1\XXX\YYY\program.exe`, recipe]);
}

I am all out of ideas, so all help is appreciated.

"Adam D. Ruppe" <destructionator gmail.com> writes:

My guess, just looking at it, is that spawnProcess fails because 
there's  no streams available for stdin, stdout, and stderr. It 
tries to reuse the ones of the parent process, but without a 
console they don't work.

It might help to use Config.suppressConsole.. I'm just guessing 
but maybe try:

spawnProcess(`[c:\.......]`, recipe, Config.suppressConsole);

and see what happens. Alternatively maybe redirect the stdin, 
stdout, and stderr to log files instead of using the default (by 
passing File arguments to spawnProcess too)

"Nemo" <notinuse nowhere.com> writes:

Thank you, Config.suppressConsole did not help, but redirecting 
the std:s did.