Date: Wed, 24 Mar 2004 23:48:24 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Daniel Eischen <eischen@vigrid.com> Cc: FreeBSD current users <current@freebsd.org> Subject: Re: SF Bay area hackfest Message-ID: <20040325074824.GB63710@xor.obsecurity.org> In-Reply-To: <Pine.GSO.4.10.10403250112420.18234-100000@pcnet5.pcnet.com> References: <20040325014453.GA65919@troutmask.apl.washington.edu> <Pine.GSO.4.10.10403250112420.18234-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 25, 2004 at 01:22:22AM -0500, Daniel Eischen wrote: > We've said this at other times, but TLS support is already > partially designed in to libpthread (for all archs). We > can (and will) implement it for them regardless of whether > the library functions perfectly for those platforms. >=20 > Both sparc64 and alpha seem to work OK when libpthread is > built in 1:1 mode, so I suspect the real problem is resuming > the thread contexts in userland and/or passing out the > context in the expected format from the kernel. Can it be built that way by default on sparc, since libthr doesn't work very well? I'd like to test this for things like mozilla that cause libthr to crash at startup, except my sparc machine remains unbootable because of broken syscons. Kris --K8nIJk4ghYZn606h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAYo7HWry0BWjoQKURAgeWAJ9S9HBM7qnjgWD1W0GftgsIRyf6NACdEpOf Po8dELMqF6liMirTCcn/od4= =RS7N -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040325074824.GB63710>