Menu
▾
▴
#690 memory faults in privoxy-3.0.6 (linux-2.6.18)
Hello,
I'd like to report some memory faults.
privoxy-3.0.6 on linux-2.6.18 (fedora core 6, glibc-2.5)
dies quite often, as opposed to previous versions -
I have used privoxy for many years now.
I attach two files with valgrind output. What I can not
tell you, is, which of my rules triggered actually
the SIGSEGVs. But the line numbers (-ggdb3) given
by valgrind should be helpful, anyway.
Bye, bye,
Juergen
*.txt
Logged In: NO
Ok, it's me for third time. For the sake of completeness
here is a - in my opinion - rather useless backtrace
of glibc-2.5:
*** glibc detected *** /usr/local/sbin/privoxy: double free or corruption (top): 0x08201938 ***
======= Backtrace: =========
/lib/libc.so.6[0x4b723efd]
/lib/libc.so.6(cfree+0x90)[0x4b727550]
/usr/local/sbin/privoxy[0x8062851]
/usr/local/sbin/privoxy[0x8064fea]
/usr/local/sbin/privoxy[0x80656f7]
/usr/local/sbin/privoxy[0x80665c9]
/usr/local/sbin/privoxy[0x8066009]
/lib/libc.so.6(__libc_start_main+0xdc)[0x4b6d3f2c]
/usr/local/sbin/privoxy[0x80497c1]
======= Memory map: ========
Bye, bye
Juergen
Logged In: YES
user_id=875547
Originator: NO
Thanks for the report.
Does the problem go away if you build Privoxy with --disable-dynamic-pcre?
If it does, it's probably the same problem as:
https://sourceforge.net/tracker/index.php?func=detail&aid=1621173&group_id=11118&atid=111118
and should already be fixed in CVS.
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).