This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/18862] Cloning with CLONE_VFORK | CLONE_VM stops sending signals internally from working.


https://sourceware.org/bugzilla/show_bug.cgi?id=18862

--- Comment #2 from Steven Stewart-Gallus <sstewartgallus00 at mylangara dot bc.ca> ---
(In reply to Florian Weimer from comment #1)
> fork_routine does not set up a glibc thread descriptor, and calling write
> and _Exit corrupts the main thread descriptor.  This means that the raise
> call inside abort uses the wrong PID.
> 
> This is not a bug in glibc.  If you call clone directly, you need to make
> sure that you take care of the thread descriptor situation in some way.

Why even expose clone if you are not going to support it? I would be willing to
accept that only execve and _Exit are supported system calls though I guess.
That would be very sparse but proportionate to how vfork is usually used.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]