I don't recall anyone else reporting this type of problem. You might want to submit an official bug report and/or post the details to the developer list.
Jim On Fri, 11 Jun 2004 [EMAIL PROTECTED] wrote: > Running htdig 3.1.6 on SuSE linux (SLES8) on a big endian architecture > (s390). > > Though it usually works fine, twice now htdig has gotten into a loop at > the same place, using all CPU until killed. > > The loop occurs in __db_shalloc_free (db/common/db_salloc.c) in this > code: > > for (elp = SH_LIST_FIRST(hp, __data), lastp = NULL; > elp != NULL && (void *)elp < (void *)ptr; > lastp = elp, elp = SH_LIST_NEXT(elp, links, __data)) > ; > > It appears that somehow links.sle_next is 0, so each elp = > SH_LIST_NEXT(...) will forever assign elp + 0 to elp. > > I'm not familiar with htdig, but it appears sle_next is only set by > SH_LIST_INSERT_AFTER. Is this a known issue? Any patches? > > Please CC me in reply as I am not subscribed to this list. > > Thanks for any info, > ~ Daniel ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
