This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/6910] getpid() wrong in child's signal handler after clone()
- From: "mtk dot manpages at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 23 Sep 2008 01:12:42 -0000
- Subject: [Bug libc/6910] getpid() wrong in child's signal handler after clone()
- References: <20080922114412.6910.mtk.manpages@gmail.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mtk dot manpages at gmail dot com 2008-09-23 01:12 -------
(In reply to comment #2)
> You cannot use clone this way. In fact, nobody should use clone. There are
> assumptions made in the system about the way clone is used. If you want to
use
> clone you have to do everything yourself, including preparing the thread
descriptor.
All of this does kind of beg the question: why does glibc provide a clone()
wrapper then?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6910
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.