> >Hmm ... he *could* be suffering from that strcoll() bug, but with no
> >info about his platform I'm hesitant to jump to that conclusion.
>
> It was indeed the strcoll bug in glibc 2.2.2. The database in question
> has some long strings that triggered it.
>
> Upgrading to a later glibc fixed the problem. Thanks for the pointer (and
> your time); I appreciate it.
Can we test for this at configure time and spit out a warning
message to the user that they need to upgrade their version of glibc?
-sc
--
Sean Chittenden