[leafnode-list] Re: Fetchnews - glibc detected *** double free or corruption - aborted

[Stroller]

On 6 Jul 2006, at 22:11, Matthias Andree wrote:
> ...
> This looks like an off-by-one error on long lines in the active file,
> where fetchnews will place a '\0' character in the byte immediately
> beyond the allocated buffer when encountering a long line.

I see.

* doesn't *

Thank very much for your quick response.

> Please update to the latest 20060706a snapshot and see if this  
> fixes the
> crashes (DO NOT use _MALLOC_CHECK=0, but either leave this unset ...

Yay! This fixes it!!

Thank you. :D

> or use
> _MALLOC_CHECK=2,  ,,

$ su -
Password:
# fetchnews -vvv
fetchnews mode: get articles, get headers, get bodies, post articles
found 0 articles in in.coming.
news.eclipse.co.uk: connecting to port nntp
   trying:    address 216.196.109.145 port 119...
   connected: address 216.196.109.145 port 119.
news.eclipse.co.uk: connected (200), banner: "200 news.eclipse.net.uk"
news.eclipse.co.uk: getting newsgroups list
Warning: skipping group "alt.", invalid name (NULL component).
fetchnews: 0 articles and 0 headers fetched, 0 killed, 0 posted, in  
10 seconds
# echo $MALLOC_CHECK_

# echo $_MALLOC_CHECK

# fetchnews -vvv
fetchnews mode: get articles, get headers, get bodies, post articles
found 0 articles in in.coming.
news.eclipse.co.uk: connecting to port nntp
   trying:    address 216.196.109.145 port 119...
   connected: address 216.196.109.145 port 119.
news.eclipse.co.uk: connected (200), banner: "200 news.eclipse.net.uk"
news.eclipse.co.uk: getting newsgroups list
Warning: skipping group "alt.", invalid name (NULL component).
Warning: skipping group "alt.binaries.", invalid name (NULL component).
Warning: skipping group "alt.binaries.celebrities.bikini.", invalid  
name (NULL component).
^C
fetchnews: 0 articles and 0 headers fetched, 0 killed, 0 posted, in  
18 seconds
# _MALLOC_CHECK=2
# MALLOC_CHECK_=2
# echo $_MALLOC_CHECK
2
# echo $MALLOC_CHECK_
2
# fetchnews -vvv
fetchnews mode: get articles, get headers, get bodies, post articles
found 0 articles in in.coming.
news.eclipse.co.uk: connecting to port nntp
   trying:    address 216.196.109.145 port 119...
   connected: address 216.196.109.145 port 119.
news.eclipse.co.uk: connected (200), banner: "200 news.eclipse.net.uk"
news.eclipse.co.uk: getting newsgroups list
Warning: skipping group "alt.", invalid name (NULL component).
Warning: skipping group "alt.binaries.", invalid name (NULL component).
Warning: skipping group "alt.binaries.celebrities.bikini.", invalid  
name (NULL component).
^C
fetchnews: 0 articles and 0 headers fetched, 0 killed, 0 posted, in  
19 seconds
#

> ... or even better, run under valgrind supervision as
> suggested above.)

The previous two runs were 20060706a installed using emerge & my  
regular CFLAGS.

So I recompiled manually with:
  # cd leafnode-2.0.0.alpha20060706a && CFLAGS="-ggdb3 -O1" make &&  
make install && valgrind --leak-check=yes --show-reachable=yes --num- 
callers=16 --quiet fetchnews -vvv 2>&1 | tee fetchnews.log

On the previous occasion I started seeing ==22628== output almost  
immediately; this time, not until the run was completed. I will send  
a copy of the output (331 lines) direct to Matthias but interested  
parties can also get a copy from <http://linux.stroller.uk.eu.org/ 
fetchnews.log.gz>.

>> I've been getting the "Warning: skipping group "alt.", invalid name
>> (NULL component)"
>
> It looks like a badly maintained upstream news server at any rate...

That's what I figured. I'll maybe file a support request with my ISP.

>> and "ERROR: FETCHNEWS MUST REFETCH THE WHOLE ACTIVE FILE NEXT RUN."
>> messages for some time, both on this machine & it's predecessor and I
>> always figured it was something to do with my ISP's server. Is this
>> anything to worry about?
>
> This is not overly serious, unless you're paying per time or volume...

Indeed.

> WRT the refetching the whole
> active file, I'm not sure. If it persists with the new version AND  
> if it
> is not fixed by running "fetchnews -f"), then we'll need to debug
> this...

Well, it seems to be fixed.  :D

Thanks very much for your help.

Stroller.