On Wed, 2005-08-24 at 14:47 -0700, Ross Boylan wrote: > Every time an install or upgrade attempts to configure I get this error: > *** glibc detected *** double free or corruption (!prev): 0x089a79c8 *** > > The problems this is causing are rapidly spreading. debconf in now not > installed properly, most installs don't configure for that reason alone. > > I filed a bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323849, > but I'm increasingly convinced the package I filed it against was just > an accidental bystander. > > I suspect the problem arises from the fact that I've pulled some > unstable packages, in particular glibc, into my mostly testing system. > I'd appreciate any advice, including how to fix or at least better > diagnose this problem. > > Thanks. > Thanks to GOTO Masanori for catching that this is a known bug, now merged with 304604 322746. I found the second of those particularly useful, since it provides the following workaround, courtesy of martin f. krafft: A workaround to this problem is to start APT/dpkg with MALLOC_CHECK_=0 in the environment:
MALLOC_CHECK_=0 dpkg --configure -a I can confirm that this works for me. Some reports sound as if switching to some debconf front-end other than readline will also work. It appears libterm-readline-gnu-perl does a double free, and the new libc is stricter about this and catches the error. Thus any install using debconf and the readline front-end runs into this problem if the new libc is present. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
