Date: Thu, 27 Feb 2003 11:59:15 -0500 From: Craig Rodrigues <rodrigc@attbi.com> To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org, freebsd-security@freebsd.org Subject: Re: OpenSSL question for id_function() Message-ID: <20030227165915.GA21958@attbi.com> In-Reply-To: <200302271640.h1RGeMx2029701@vashon.polstra.com> References: <20030225155724.GB9400@attbi.com> <200302271640.h1RGeMx2029701@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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()); which is similar to Lev Walkin's suggestion for a C style cast. This gets things to compile, but seems like trying to fit a square peg in a round hole.... Thanks. -- Craig Rodrigues http://home.attbi.com/~rodrigc rodrigc@attbi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030227165915.GA21958>