Date: Tue, 04 Aug 2009 18:57:25 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Ed Schouten <ed@80386.nl> Cc: Maslan <maslanbsd@gmail.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, Max Laier <max@love2party.net> Subject: Re: sosend() and mbuf Message-ID: <86ab2f34ay.fsf@ds4.des.no> In-Reply-To: <20090804093036.GN1292@hoeg.nl> (Ed Schouten's message of "Tue, 4 Aug 2009 11:30:36 %2B0200") References: <319cceca0908030119i3432a495ya60aa431dab0e1b1@mail.gmail.com> <86k51k4kvl.fsf@ds4.des.no> <86fxc84ksj.fsf@ds4.des.no> <200908040138.14743.max@love2party.net> <319cceca0908040227hf9a0f92jbf05b11e9f974994@mail.gmail.com> <20090804093036.GN1292@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Ed Schouten <ed@80386.nl> writes: > Maslan <maslanbsd@gmail.com> writes: > > However, when i checked the pid & tid of the new created thread it > > was not the same as the parent nor as the proc0 & thread0 > I am not sure, but sharing another process's address space doesn't have > to imply it shares the same pid, right? The man page explicitly states that if no process is specified, the new thread is assigned to proc0, which has a valid filedesc table, valid creds etc., so this shouldn't be a problem. However, he's getting a different PID, which shouldn't happen. Either the man page is wrong, or things were different in 7. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ab2f34ay.fsf>