Open bee-rock opened 3 years ago
@klemens-morgenstern
This is still happening.
The line: boost::process::child("");
causes the following:
Of course such scenario should fail, but I don't think it should cause a segmentation fault. I think it should fail in the executer.hpp after a failed execv (In linux). Regarding Windows I will find a similar solution.
Do you want me to create a pull request for this?
You can demonstrate this on the Wandbox online compiler using gcc 11.1.0 and c++11:
The documentation on https://www.boost.org/doc/libs/1_76_0/doc/html/boost_process/tutorial.html#boost_process.tutorial.error_handling leads me to believe that this case should throw a std::system_error rather than segfault.