[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[leafnode-list] Memory corruption bug in leafnode-2.0.0.alpha20030710a?
I have been playing around with the -0710a release and noticed that
fetchnews was segfaulting after it's run. I got as far as determining
that the change to PCRE newsgroups is at the heart of the problem.
It appears to me as through the code to free the filters loaded from
/etc/leafnode/filterfile is stepping on the list of local news groups in
memory. If I replace /etc/leafnode/filterfile with an empty file, then
the crash is not triggered.
Just for kicks, I put a watch point on local->name in localutils.c and
found the following:
Hardware watchpoint 2: local->name
Old value = 0x8063ec8 "exiter.general"
New value = 0x8066130 ".*"
0x400cff63 in mallopt () from /lib/i686/libc.so.6
#0 0x400cff63 in mallopt () from /lib/i686/libc.so.6
#1 0x400cedfc in free () from /lib/i686/libc.so.6
#2 0x080525ba in free_entry (e=0x4018bf50) at filterutil.c:598
#3 0x0805261e in freeallfilter (f=0x8) at filterutil.c:611
#4 0x0804d736 in main (argc=134635544, argv=0x0) at fetchnews.c:2097
#5 0x400717f7 in __libc_start_main () from /lib/i686/libc.so.6
Unfortunately, I won't have time to look into this further until later
on next week so I though I would post this now just in case someone else
runs into the bug.
GnuPG key: <http://www.exiter.com/gnupg/clark.asc> Key ID: 0xB13B653B
Attachment Converted: "c:\programme\qualcomm\eudora\attach\signature.asc"