Date: Thu, 27 Feb 2003 13:47:18 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: Craig Rodrigues <rodrigc@attbi.com> Cc: freebsd-security@freebsd.org, current@freebsd.org, John Polstra <jdp@polstra.com> Subject: Re: OpenSSL question for id_function() Message-ID: <XFMail.20030227134718.jhb@FreeBSD.org> In-Reply-To: <20030227165915.GA21958@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27-Feb-2003 Craig Rodrigues wrote: > On Thu, Feb 27, 2003 at 08:40:22AM -0800, John Polstra wrote: >> FreeBSD violates POSIX in this respect. > > Doh! I just looked at: > http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libpthread/include/pthread.h > and it looks like OpenBSD does the same thing. > > Just wondering, is the FreeBSD KSE project implementing a > POSIX compliant pthread_t? > >> thread-related types: >> >> pthread_attr_t >> pthread_mutex_t >> pthread_mutexattr_t >> pthread_cond_t >> pthread_condattr_t >> pthread_once_t >> >> We got it right for pthread_key_t, though. :-) > > Cool. Sometimes standards are a pain in the neck, but my main interest > in FreeBSD's POSIX compliance for threads is to be more and more of a > drop-in replacement for Linux. :) > > > So is OpenSSL stuff which requires id_function() broken on > FreeBSD then? > > The C++-style work-around for my code is to do: > > return reinterpret_cast<unsigned long>(pthread_self()); Use uintptr_t or intptr_t rather than unsigned long. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20030227134718.jhb>