Package: manpages-dev Version: 2.02-2 Severity: normal Tags: patch
The clone(2) manpage incorrectly states that CLONE_PARENT_SETTID stores the child TID. In fact it stores the parent TID (verified on a live system). The following note on the same page implies that this behavior is intentional, and the documentation incorrect: "the parent thread ID will be written in case CLONE_PARENT_SETTID" Patch below. Paul --- man2/clone.2.old 2005-08-14 14:29:18.000000000 +0100 +++ man2/clone.2 2005-08-14 14:29:40.000000000 +0100 @@ -360,7 +360,7 @@ .TP .BR CLONE_PARENT_SETTID " (since Linux 2.5.49)" -Store child thread ID at location +Store parent thread ID at location .I parent_tidptr in parent and child memory. (In Linux 2.5.32-2.5.48 there was a flag CLONE_SETTID that did this.) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.3-w Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages manpages-dev depends on: ii manpages 2.02-2 Manual pages about using a GNU/Lin manpages-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
