mutt/libc? problems after recent sid upgrade
Mutt segmentation faults when I run it on the console (and seems to hang
when run from gnome-terminal). Here's what gdb says about the core file.
More info below the gdb output was posted on debian-user yesterday.
Any suggestions?
freefall ~ $ gdb mutt core
GNU gdb 5.3-debian
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)...
Core was generated by `mutt'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libncurses.so.5...(no debugging symbols found)...
done.
Loaded symbols for /lib/libncurses.so.5
Reading symbols from /usr/lib/libsasl.so.7...(no debugging symbols found)...
done.
Loaded symbols for /usr/lib/libsasl.so.7
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libdb2.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdb2.so.2
Reading symbols from /lib/libcrypt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/libpam.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols found)...
done.
Loaded symbols for /lib/libnss_compat.so.2
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...
done.
Loaded symbols for /lib/libnss_files.so.2
#0 0x400d7bea in mallopt () from /lib/libc.so.6
(gdb) where
#0 0x400d7bea in mallopt () from /lib/libc.so.6
Cannot access memory at address 0xbf800008
(gdb)
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: