Ferret talk - Jan 2007 - Segmentation fault in Index::Index#add_document

Hello,

Here''s the code that segfaults:

http://pastie.caboo.se/36467

I could have submitted a patch, but I''m not sure
whether this segfault is caused by Ferret or Ruby.

This seems to be triggered only when combining
a split and a gsub on an empty string of the returned
array, and trying to insert it directly into the
index.

However, there''s no problem when you duplicate or
transform the string.

--
maz
Rift Technologies - http://rift.fr/

-- 
Posted via http://www.ruby-forum.com/.

Hi,

reproduced here on Ubuntu Edgy Intel.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1211037504 (LWP 6193)]
0xb79b878e in mb_std_advance_to_start (ts=0x816ae20) at analysis.c:156
156     {
(gdb) bt
#0  0xb79b878e in mb_std_advance_to_start (ts=0x816ae20) at analysis.c:156

Have you reported this on the bug tracker?

http://ferret.davebalmain.com/trac/report/1

John.
--
http://johnleach.co.uk


maz wrote:
> Hello,
> 
> Here''s the code that segfaults:
> 
> http://pastie.caboo.se/36467
> 
> I could have submitted a patch, but I''m not sure
> whether this segfault is caused by Ferret or Ruby.
> 
> This seems to be triggered only when combining
> a split and a gsub on an empty string of the returned
> array, and trying to insert it directly into the
> index.
> 
> However, there''s no problem when you duplicate or
> transform the string.
> 
> --
> maz
> Rift Technologies - http://rift.fr/
>

John Leach wrote:
[...]
> Have you reported this on the bug tracker?
> 
> http://ferret.davebalmain.com/trac/report/1
Done, thanks.
I still think it''s probably a Ruby bug.

--
maz
Rift Technologies - http://rift.fr/

-- 
Posted via http://www.ruby-forum.com/.