Re: seg fault with tsearch2

I compiled 8.0.1 on linux with --with-debug only, and it seemed to
work. I had also compiled 8.0.1 on Netbsd with the same configure
option. I removed the tsearch trigger from the table and I had no
problem. I tried using to_tsvector directly and the server crashed.

PostgreSQL stand-alone backend 8.0.1
backend> select to_tsvector('foo blah blah');

Program received signal SIGSEGV, Segmentation fault.
0x48b22c84 in find_among () from /usr/pkg/lib/tsearch2.so

Yet on a linux computer with the source compiled the EXACT same
way(--with-debug)

PostgreSQL stand-alone backend 8.0.1
backend> select to_tsvector('foo blah blah');
1: to_tsvector (typeid = 17359, len = -1, typmod = -1, byval = f)
----
1: to_tsvector = "'foo':1 'blah':2,3" (typeid = 17359, len =
-1, typmod = -1, byval = f)
----
backend>

So, the only conclusion I can reach is this problem is some OS
dependant bug, which apparently has been fixed in 8.0.2beta.

--Joel

On Apr 7, 2005 9:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Joel Leyh <hashbang(at)gmail(dot)com> writes:
> > Same problem, same function causing the seg fault. I also tried to
> > narrow down what about the filename is causing the error, but I
> > couldn't figure it out. I also compiled the source on another NetBSD
> > i386 machine, with the same results.
> > Then I compiled 8.0.2beta1 and the above query works just fine. So
> > whatever was causing the problem apparently has been fixed.
>
> Well, that's good news, but it still bothers me that I can't reproduce
> the problem here, and I don't see anything in the CVS logs that looks
> like a fix. I went back to 8.0.1 sources just to be sure, but it worked
> fine. Apparently something platform-specific?
>
> What configure options did you use?
>
> regards, tom lane
>