<<< Date Index >>>     <<< Thread Index >>>

Re: how to debug (and fix) mutt?



Bram Mertens wrote:
> (gdb) bt
> #0  0xb7cf6aa8 in strncpy () from /lib/tls/i686/cmov/libc.so.6
> #1  0x080d8943 in ?? ()
> #2  0x00000000 in ?? ()

Corrupted stack.  That core file is unusable and I wouldn't know where
to start to debug such a thing.  But I'm a gdb newbie :)

I stand by my opinion that a library mismatch is causing it.
Do you have any LD_* environment variables set?  Anything unusual in
/etc/ld.so.conf or /etc/ld.so.preload?

Try "ldd /usr/bin/mutt" and see if something points to the wrong place.
My Mutt 1.5.9i 2005-03-13 from Debian Unstable looks like this:
        linux-gate.so.1 =>  (0xffffe000)
        libncursesw.so.5 => /lib/libncursesw.so.5 (0x4115c000)
        libgnutls.so.11 => /usr/lib/libgnutls.so.11 (0x419d3000)
        libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x41314000)
        libidn.so.11 => /usr/lib/libidn.so.11 (0x4110d000)
        libdb-4.3.so => /usr/lib/libdb-4.3.so (0x41351000)
        libc.so.6 => /lib/tls/libc.so.6 (0x4fe2e000)
        libdl.so.2 => /lib/tls/libdl.so.2 (0x4ff8e000)
        libtasn1.so.2 => /usr/lib/libtasn1.so.2 (0x4114a000)
        libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0x41205000)
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x41037000)
        libz.so.1 => /usr/lib/libz.so.1 (0x4133b000)
        libresolv.so.2 => /lib/tls/libresolv.so.2 (0x41018000)
        /lib/ld-linux.so.2 (0x4fe01000)
        libnsl.so.1 => /lib/tls/libnsl.so.1 (0x41000000)
don't ask me what that linux-gate.so.1 is supposed to be though.

Maybe you could try verifying your system files.  "debsums" is sort of 
a Debian version of Tripwire: run it against a Debian archive.


Toby

-- 
Signed/encrypted mail welcome.  GPG/PGP Key-Id: 0x15C5C2EA