FreeBSD threads was RE: consider reopening 1.3
--On Sunday, November 16, 2003 5:20 PM -0400 Marc G. Fournier [EMAIL PROTECTED] wrote: On FreeBSD 4.X it is broken(and will be forever?). On FreeBSD 5.X, use KSE threading (which may become the default in the future 5.2 release anyways?) and it works great. man libmap.conf on a FreeBSD box for information on todo this.(see also: freebsd-threads mailing list) 'k, maybe expand the comment in the INSTALL file to address this? Well, we've asked for confirmation of FreeBSD threading 'working' on the [EMAIL PROTECTED] - which as a platform-specific issue is the 'right' mailing list for this topic - not [EMAIL PROTECTED] FWIW, the FreeBSD port maintainer has asked us to enable threads on all versions, but we've (so far) yet to receive a reply that indicates that the FreeBSD's threading works properly. The only reply we received so far was that it isn't fixed with FreeBSD - even 5.1. So, if you have something to add, please contribute on the right list. Thanks! -- justin
Re: FreeBSD threads was RE: consider reopening 1.3
On Sun, Nov 16, 2003 at 02:34:47PM -0800, Justin Erenkrantz wrote: --On Sunday, November 16, 2003 5:20 PM -0400 Marc G. Fournier 'k, maybe expand the comment in the INSTALL file to address this? Well, we've asked for confirmation of FreeBSD threading 'working' on the [EMAIL PROTECTED] - which as a platform-specific issue is the 'right' mailing list for this topic - not [EMAIL PROTECTED] FWIW, the FreeBSD port maintainer has asked us to enable threads on all versions, but we've (so far) yet to receive a reply that indicates that the FreeBSD's threading works properly. The only reply we received so far was that it isn't fixed with FreeBSD - even 5.1. So, if you have something to add, please contribute on the right list. I compiled it on a 4.9-CURRENT machine two days ago and it failed (even after working around some problems with atomics) by deadlocking. Connections were established but no responses ever returned. I wasn't even able to knock a request out of the blocked state by hitting it from another client. -aaron
Re: FreeBSD threads was RE: consider reopening 1.3
Yup, this is what I tend to see ... One question, what does 'ps auxwl' show, primarily the WCHAN column? On Sun, 16 Nov 2003, Aaron Bannert wrote: On Sun, Nov 16, 2003 at 02:34:47PM -0800, Justin Erenkrantz wrote: --On Sunday, November 16, 2003 5:20 PM -0400 Marc G. Fournier 'k, maybe expand the comment in the INSTALL file to address this? Well, we've asked for confirmation of FreeBSD threading 'working' on the [EMAIL PROTECTED] - which as a platform-specific issue is the 'right' mailing list for this topic - not [EMAIL PROTECTED] FWIW, the FreeBSD port maintainer has asked us to enable threads on all versions, but we've (so far) yet to receive a reply that indicates that the FreeBSD's threading works properly. The only reply we received so far was that it isn't fixed with FreeBSD - even 5.1. So, if you have something to add, please contribute on the right list. I compiled it on a 4.9-CURRENT machine two days ago and it failed (even after working around some problems with atomics) by deadlocking. Connections were established but no responses ever returned. I wasn't even able to knock a request out of the blocked state by hitting it from another client. -aaron
Re: FreeBSD threads was RE: consider reopening 1.3
On Sun, Nov 16, 2003 at 09:43:03PM -0400, Marc G. Fournier wrote: Yup, this is what I tend to see ... One question, what does 'ps auxwl' show, primarily the WCHAN column? I don't have access to the machine right now, but I can check later. -aaron
