fork

来源： https://stackoverflow.com/questions/64164339/why-does-read-block-on-a-pipe-until-the-write-end-is-closed

来源： https://stackoverflow.com/questions/64164339/why-does-read-block-on-a-pipe-until-the-write-end-is-closed

来源： https://stackoverflow.com/questions/64164339/why-does-read-block-on-a-pipe-until-the-write-end-is-closed

来源： https://stackoverflow.com/questions/64164339/why-does-read-block-on-a-pipe-until-the-write-end-is-closed

来源： https://stackoverflow.com/questions/32130868/does-fork-duplicate-all-the-memory-of-the-parent

来源： https://stackoverflow.com/questions/10700982/redirecting-stdout-to-pipe-in-c

来源： https://stackoverflow.com/questions/10700982/redirecting-stdout-to-pipe-in-c

来源： https://stackoverflow.com/questions/32314743/c-proper-range-of-return-status-value

来源： https://stackoverflow.com/questions/32314743/c-proper-range-of-return-status-value

问题 system() function is implemented by using fork() , execve() and wait() functions. I have heard that fork() function is dangerous in multi-threaded programs. So, is the system() function also dangerous in multi-threaded programs? What problems it may cause? 回答1: fork is dangerous in threaded programs unless followed by execve . Since only the current thread is forked there's very little you can do in a forked multi-threaded program other than execve . You should probably make sure you're not