From: "Xavier Noëlle" <xavier.noelle@...>
Date: 2010-01-21T19:00:19+09:00
Subject: Re: Multi-threaded DBI causing segfault

2010/1/20 Roger Pack <rogerpack2005@gmail.com>:
>
>> /usr/lib/ruby/1.8/dbd/mysql/statement.rb:36: [BUG] Segmentation fault
>> ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux]
>>
>> Question: is it a real bug or am I doing something wrong ?
>> If I'm wrong, where ?
>> If I'm not, is there a workaround to thread the execution of code
>> using DBI without a segfault ?
>
> Maybe use the mysql gem?

I think that's the underlying gem used by DBI for dealing with MySQL,
would it really help ?

> Also, you could run it in gdb to try to debug the cause.
>
> http://wiki.github.com/rdp/ruby_tutorials_core/building-mri#debug_build

That was a good idea...in theory ! Because when I compile sources for
the exact same version (and patchlevel) of Ruby, I don't get the same
error...then I tried to run gdb directly on the standard Ubuntu 9.10
binary, but I think the error is not really helpful:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7b77517 in st_foreach () from /usr/lib/libruby1.8.so.1.8

-- 
Xavier NOELLE