[leafnode-list] [ANNOUNCE] leafnode-2.0b5

[krasel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx (Cornelius Krasel)]

Stefan Fleiter wrote:
> netscape.public.mozilla.builds: considering articles 1-1
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x400bda03 in strchr () from /lib/libc.so.6
> (gdb) backtrace 
> #0  0x400bda03 in strchr () from /lib/libc.so.6
> #1  0x807e3a1 in ?? ()
> #2  0x804b2ef in getgroup (g=0x80601e8, first=1) at ./fetchnews.c:933
> #3  0x804c04b in processupstream (server=0x805f590 "torsten", port=0)
>     at ./fetchnews.c:1287
> #4  0x804c467 in do_server (msgid=0x0, lastrun=972677915) at ./fetchnews.c:1424
> #5  0x804cc43 in main (argc=3, argv=0xbffff9d4) at ./fetchnews.c:1657
> #6  0x40066bcc in __libc_start_main () from /lib/libc.so.6
> (gdb) 

This is fixed in 2.0b5 which I just put up on
	ftp://wpxx02.toxi.uni-wuerzburg.de/pub/leafnode-2.0b5.tar.gz
The cause was, as predicted, that doxover() had problems with XOVER lines
which didn't contain an Xref: field. In addition, news.mozilla.org produces
truncated XOVER lines which do not conform to the specification if
there are too many References in the articles. I built a hack into
doxover() to find this as well and behave properly.

Further good news: filtering works again (it didn't because of a very
dumb error of mine, see ChangeLog); and fetchnews will be faster now
if you download groups with many "to-be-killed" articles in it
(because now fetchnews will *first* check if the article should be
killed; only if this is not the case it looks for the message-id on
the harddrive). I fetched 12 articles and killed 1796 (due to "maxage")
from news.mozilla.org in 17 seconds.

Problems that remain: many. The following is copied-and-pasted from the
announce of 2.0b3 and amended where necessary:

- The documentation is still incomplete. Most notably, the README
  misses sections 4.1 and 4.2, and the TODO is partially in German.
- fetchnews may still sometimes coredump on fixxover() (Joerg?).
- The xover code contains bugs which are currently being discussed
  on the list and may lead to loading of false XOVER info. .overview
  files are written correctly.
- The AUTHINFO support for the nntpd is incomplete and needs fixing.
- Texpire currently doesn't seem to do any threading. Joerg has
  promised to look into this :-)
- The timeout code for fetchnews sucks big time. As a result, fetchnews
  doesn't handle timeouts properly or not at all.
- if HAVE_SNPRINTF and HAVE_VSNPRINTF are undefined, compiling vsnprintf.c
  generates two warnings.
- if HAVE_STRDUP is undefined, strdup.c doesn't compile. It throws
  around a lot of very odd error messages, and I don't know why.
- I did not yet incorporate Joerg's patch for moderated groups due
  to lack of time.
- nntpd cannot report which host connected to it if compiled with IPV6.
  The reason for that is that I have absolutely no documentation
  for IPV6.
- I have no idea why Leafnode-2.0b4 decided to truncate my groupinfo file
  this night. It has not tried this again today. I'll tell you tomorrow
  whether it will do it again this night :-)

If you get coredumps, it helps if you can tell me on which server that
happened. For example, to debug the coredump above it was very helpful
that I could reproduce it locally.

--Cornelius.

-- 
/* Cornelius Krasel, U Wuerzburg, Dept. of Pharmacology, Versbacher Str. 9 */
/* D-97078 Wuerzburg, Germany   email: phak004@xxxxxxxxxxxxxxxxxxxxxx  SP4 */
/* "Science is the game we play with God to find out what His rules are."  */

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list