This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/17214] Expose a function to reset the PID cache
- From: "sstewartgallus00 at mylangara dot bc.ca" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 26 Aug 2014 18:31:24 +0000
- Subject: [Bug nptl/17214] Expose a function to reset the PID cache
- Auto-submitted: auto-generated
- References: <bug-17214-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17214
--- Comment #8 from Steven Stewart-Gallus <sstewartgallus00 at mylangara dot bc.ca> ---
If I use the GLibc wrapper around clone that resets the PID cache
right? So if people are loathe to expose a function to reset the PID
cache can they make clone or a variation of clone more convenient for
the fork style cases? Maybe my problem can be solved by simply making
clone(NULL, NULL, etc..) behave like fork or doing something else
similar? Because I was calling the system call directly because I
didn't want to create a new stack and function for no reason.
--
You are receiving this mail because:
You are on the CC list for the bug.