Anecdotally people recommend not using libpthread
with Ruby on FreeBSD. I’ve duly always told the port to not use it, but ldd
has always shown that it’s linked. autoconf insists on configuring the build with it, despite the
--disable-pthread
flag.
My long time response to this was *shrug* – Ruby seems fine. Until a weird production problem, unrepeatable on stage, where certain Rails stacks (those running in development mode to expose some aspect of the Globalize plugin to translators) crashed badly, with SIGBUS or SIGILL.
I came across this script:
$ ruby -e 'def d(x); p x; d x+1; end; d 0'
which exposes the problem perfectly. With a pthread
’d Ruby it dumps core, with a no-thread Ruby it gracefully raises stack level too deep (SystemStackError)
Update:
I discussed this on the FreeBSD ports list, discussion here.
Seems like the problem is on its way out.
Leave a Reply
Recent articles
- Docker, SELinux, Consul, Registrator
(Wednesday, 04. 29. 2015 – No Comments) - ZFS performance on FreeBSD
(Tuesday, 09. 16. 2014 – No Comments) - Controlling Exim SMTP behaviour from Dovecot password data
(Wednesday, 09. 3. 2014 – No Comments) - Heartbleed OpenSSL vulnerability
(Tuesday, 04. 8. 2014 – No Comments)
Archives
- April 2015
- September 2014
- April 2014
- September 2013
- August 2013
- March 2013
- April 2012
- March 2012
- September 2011
- June 2011
- February 2011
- January 2011
- October 2010
- September 2010
- February 2010
- September 2009
- August 2009
- January 2009
- September 2008
- August 2008
- July 2008
- May 2008
- April 2008
- February 2008
- January 2008
- November 2007
- October 2007
- September 2007
- August 2007
- December 2006
- November 2006
- August 2006
- June 2006
- May 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005