mutt problems after recent sid upgrade
After upgrading two machines (first one Saturday, and second one
yesterday), mutt no longer works. When started on the console it
segmentation faults, and when started in a gnome-terminal it seems to
try to grab more memory until it is killed. mutt itself wasn't upgraded
- it remained at version 1.4.0-5 during the upgrade. I've tried several
easy things - remove and reinstall, build the deb package myself and
install that - but the upgraded systems won't run mutt. Evolution and
elm seem to work ok, but I'd rather use mutt. Any ideas what the problem
is?
strace from a segmentation fault on the console is available at
http://www.mindspring.com/~lee.bradshaw/mutt2.log
Version info:
old working system (restored from backup):
freedom ~ $ ldd /usr/bin/mutt
libncurses.so.5 => /lib/libncurses.so.5 (0x4001f000)
libsasl.so.7 => /usr/lib/libsasl.so.7 (0x4005f000)
libdl.so.2 => /lib/libdl.so.2 (0x4006a000)
libc.so.6 => /lib/libc.so.6 (0x4006d000)
libdb2.so.2 => /lib/libdb2.so.2 (0x40180000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x401c1000)
libpam.so.0 => /lib/libpam.so.0 (0x401ee000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
a different system after the upgrade:
freefall ~ $ ldd /usr/bin/mutt
libncurses.so.5 => /lib/libncurses.so.5 (0x40020000)
libsasl.so.7 => /usr/lib/libsasl.so.7 (0x40060000)
libdl.so.2 => /lib/libdl.so.2 (0x4006b000)
libc.so.6 => /lib/libc.so.6 (0x4006e000)
libdb2.so.2 => /lib/libdb2.so.2 (0x4017e000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x401bf000)
libpam.so.0 => /lib/libpam.so.0 (0x401ec000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
Reply to: