This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/18862] Cloning with CLONE_VFORK | CLONE_VM stops sending signals internally from working.
- From: "sstewartgallus00 at mylangara dot bc.ca" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 08 Sep 2015 14:27:35 +0000
- Subject: [Bug libc/18862] Cloning with CLONE_VFORK | CLONE_VM stops sending signals internally from working.
- Auto-submitted: auto-generated
- References: <bug-18862-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18862
--- Comment #4 from Steven Stewart-Gallus <sstewartgallus00 at mylangara dot bc.ca> ---
(In reply to Florian Weimer from comment #3)
> There are use cases which are valid (if the appropriate flags are
> specified). We cannot support execve because it needs to set errno on
> failure, so there has to be a valid thread descriptor.
I see. I shall look into alternate ways of accomplishing what I want. The whole
reason I wanted to use clone with CLONE_VM is so that I could do a vfork with
CLONE_UNTRACED.
Thank you for your time.
--
You are receiving this mail because:
You are on the CC list for the bug.