My guess is that the parent thread, started with the relative path, starts a new thread with the EXEC and then exits,
(New process, not new thread)
But what's causing it to exit? An exec emulation should wait for the child to finish. And it does last I checked. (My Windows system is down, at the moment.)
In reply to Re^2: exec on Windows "halfway forks"
by ikegami
in thread exec on Windows "halfway forks"
by rovf
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |