On Tue, 12 Jun 2001, Gilles Detillieux wrote:
> Date: Tue, 12 Jun 2001 17:06:31 -0500 (CDT)
> From: Gilles Detillieux <[EMAIL PROTECTED]>
> To: Joe R. Jah <[EMAIL PROTECTED]>
> Cc: Gilles Detillieux <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
> Subject: Re: [htdig-dev] BSDi segfault revisited;(
>
> Well, I don't know if "revisited" is the right word, as this is not like
"Recurred" would probably be closer to the right word;)
> any of the previous segfault problems you had. It seems to stem from
> shared library constructors, so try configuring with --disable-shared
> and see if the problem goes away.
It doesn't even reach that point; I got the following compilation error:(
_____________________________________________________________________________
/usr/lib/libc_p.a(ctime.po): In function `mktime':
ctime.po(.text+0x1bdc): multiple definition of `mktime'
../htlib/.libs/libht.a(mktime.o):/tmp/htdig-3.2.0b4-061001/htlib/mktime.c:371:
first defined here
ld: Warning: size of symbol `mktime' changed from 88 to 36 in ctime.po
gmake[1]: *** [htdig] Error 1
gmake[1]: Leaving directory
`/tmp/htdig-3.2.0b4-061001/htdig'
gmake: *** [all-recursive] Error 1
_____________________________________________________________________________
> > By the way, have you determined the cause of slow indexing from the
> > profile I posted.
>
> No. As I wrote back on May 14...
>
> What I can't figure out is why there's so many "spontaneous" calls to
> regcomp! That seems to be where it's spending almost all of its time
> (i.e. in children of regcomp) but the profiling gives no clue as to what
> is generating all these calls, as though the function's entry point was
> somehow bypassed. Could it be that a stray pointer somewhere is causing
> the code to just jump somewhere into regcomp? Does anyone have any ideas/
> suggestions about this? I'm afraid I'm out of ideas.
>
> Geoff and I talked about it briefly, but I can't account for the
> millions of mysterious calls to regcomp(). However, with the strange
> behaviour above with segfaults suddenly appearing, I'm wondering if
> it wasn't shared library support all along that was causing problems,
> only it wasn't segfaulting before, just mucking up pointers and causing
> the code to jump to places it shouldn't.
>
> If you weren't using --disable-shared when you did your profiling,
> try it with --disable-shared and see if that changes anything.
I have already tried htdig with --disable-shared on a pre-3.2.0b3 snapshot
without any increase in indexing speed; however, I will try do profiling
with --disable-shared, if I can get it to compile.
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah [EMAIL PROTECTED]
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
