After analyzing this a bit more, I think there is a bug in here. The
indexer doesn't like hitting any 404 URLs in the file: protocol setup.
Here's what I have so far:
This is the trace I had before:
> > #0 0xff036f3c in strlen () from /usr/lib/libc.so.1
> > (gdb) bt
> > #0 0xff036f3c in strl
Actually :),
I wasn't sure if the "file:" protocol URLs needed to be encoded
Apparently they do!
- Danish
On Fri, 11 Jan 2002, Danish Qadri wrote:
>
>
> Hi team,
>
>
> I got a seg fault while doing my inital indexing of my MySQL DB. With our
> setup, we store a filename in the database,
Hi team,
I got a seg fault while doing my inital indexing of my MySQL DB. With our
setup, we store a filename in the database, along with some other
information. Here's the output from the logs and a core dump back trace.
It seems to be dumping core whenever it encounters the file. From the
lo