Hello
Sorry for the delay...
Actually, you only need the parent to get the status from the child,
which can be passed in other way than through common memory.
The idea is to use pipefd to actually wait for the child to either
terminate or successfully call execve. As follow:
When the TARGET_N
Ok, I taught that could be an issue, but as I said, I don't really know
all the internals of QEMU.
Another idea would be to fork the child, without CLONE_VM, on the
initial call to the clone syscall, like it's done right now, and then
wait for that child until he call execve or exit syscall. Mayb
Ok, yes you are right...
I have looked a bit more on the source code, and indeed, I think
understand the issue with the VFORK with QEMU. Please correct me if I'm
wrong...
- In the syscall trap handler, it has to use the fork() function to emulate the
vfork() due to restriction of the vfork() fu
Ok, thank you for clearing that up.
I'm noticing in 4b4d4056bb154 this comment:
"...we just make explicit use of the fact the the child and parent run
in the same VM, so the child can write an error code to a field of the
posix_spawn_args struct instead of sending it through a pipe. To ensure
th
This should probably be put under 'glibc', since this is really an issue
with that package, which is fixed by the way since Oct 2017.
https://sourceware.org/git/?p=glibc.git;a=commit;h=fe05e1cb6d64dba6172249c79526f1e9af8f2bfd
This should also be backported to 17.10
--
You received this bug noti
