I''m getting this error suddenly: http://rails:3000/ -> /project/list deadlock 0x4081419c: run:-/usr/lib/ruby/1.8/timeout.rb:42: [BUG] Segmentation fault Running rails 0.12.1 and tracks. Both 1.02a and the HEAD. Could this be caused by the sqlite3 driver? OS is Debian/Xen. Nicholas
On May 30, 2005, at 5:31 AM, Nicholas Lee wrote:> I''m getting this error suddenly: > > http://rails:3000/ -> /project/list > deadlock 0x4081419c: run:-/usr/lib/ruby/1.8/timeout.rb:42: [BUG] > Segmentation fault > > Running rails 0.12.1 and tracks. Both 1.02a and the HEAD. > > Could this be caused by the sqlite3 driver? > > OS is Debian/Xen.Are you running under WEBrick? If so, then its a good bet that the sqlite3 driver is the problem, if you aren''t using the native driver (the DL driver has LOTS of issues). Do you have swig installed? If not, please install it and then reinstall the sqlite3 driver. In fact, try reinstalling the sqlite3 driver and sending the output from the installer. Thanks, Jamis
On 5/31/05, Jamis Buck <jamis-uHoyYlH2B+GakBO8gow8eQ@public.gmane.org> wrote:> Are you running under WEBrick? If so, then its a good bet that the > sqlite3 driver is the problem, if you aren''t using the native driver > (the DL driver has LOTS of issues).Yes, WEBrick with: [nic@rails:~] gem list | grep sql sqlite3-ruby (1.1.0) What you mean by native driver? Does rails have a native sqlite3 driver now?> Do you have swig installed? If not, please install it and then > reinstall the sqlite3 driver. In fact, try reinstalling the sqlite3 > driver and sending the output from the installer.Not on the rails machine. I actually compiled bits of sqlite3-ruby elsewhere. But I''ve been using without problem until recently. Nicholas