Re: Segfault when reading group

it was still early and I the coffee was missing and ...
On Fri, Feb 18, 2005 at 12:18:37PM +0100, Urs Janßen wrote:
> here is what I would do,
> manually obtain a copy of the overview data from the group and

if you haven't set cache_overview_files=ON, then rfc1522_do_encode()
should only be called (at this stage) if the server doesn't offer
overview data, so my last debugging advice might not be very helpfull
at all.

> examine all the From and Subject fields which are RFC2047 encoded,
> and see if something looks strange, then feed the crashing function
> with that strange data only  and see if it causes the crash.

if the server has overview data and you have cache_overview_files=ON
then you should also look at the unencoded From/Subject lines which
do contain bytes from the range 0x00-0x1f and/or 0x80-0xff.

if the server has no overview data then you might try to use
	XHDR From -
	XHDR Subject -
or
	XPAT From - *
	XPAT Subject - *
or
	HEAD -
to get the From and Subject lines, then again look at the encoded
lines and the ones which do contain chars which need to be encoded
and search for something 'strange' and feed it to the encoder.

you might also want to look at the cached overview data from that
group on your side, it should be available in
${TIN_INDEX_NEWSDIR-"${TIN_HOMEDIR-"$HOME"}/.tin"}/.news${NNTPSERVER:+-$NNTPSERVER}/
(e.g. ~/.tin/.news/ or ~/.tin/.news-news.your.isp.example.org/)
as the filename is a hash of the groupname finding the right file
is a bit more complex, "grep -l comp.unix.bsd.freebsd.misc *" should
help. (this might at least help you to narrow down the problem, as
the broken data should be (partial) in the last line _or_ 'missing',
so have can say it is beyond article number ...

urs
-- 
"Only whimps use tape backup: _real_ men just upload their important stuff
 on ftp, and let the rest of the world mirror it ;)" - Linus