Hi Thomas,

Thanks for helping.

On Mon, Feb 07, 2005 at 07:07:21PM +0100, Thomas Glanzmann wrote:
> Hello,
> 
> > I also get segfaults from mutt several times a day. It always seems to
> > happen just after mutt displays a message "Sorting mailbox". This also
> > happens when I don't do anything. Mutt is running, I go to sleep and
> > next morning mutt has segfaulted. And no signs of fairies or grues. ;)
> > It only happens when I am in an IMAP folder.
> 
> Which IMAP Server do you use?

cyrus21, version 2.1.17-3. It's on the vanrees.org server to which I
have root access together with my brother. I can also run mutt on that
machine. It has the same muttrc as I have at home, courtesy of
subversion.

I have offlineimap in a cronjob since a few days. The crashes started
long before that.

> If the backtrace of the above has many '???' in it produce a new
> coredump with libs which have framepointers in:

Lots of question marks in the backtrace indeed.

> apt-get install libc6-dbg
> 
> # Run mutt with LD_LIBRARY_PATH=/usr/lib/debug set
> LD_LIBRARY_PATH=/usr/lib/debug mutt
> 
> # GDB, too
> LD_LIBRARY_PATH=/usr/lib/debug gdb /usr/bin/mutt /path/to/core
> bt
> quit
> 

Okay, I did all that, produced a new core dump and here's the gdb
output.

[EMAIL PROTECTED]:~$ LD_LIBRARY_PATH=/usr/lib/debug gdb /usr/bin/mutt core
GNU gdb 6.3-debian
Copyright 2004 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)
Using host libthread_db library "/usr/lib/debug/libthread_db.so.1".

(no debugging symbols found)
Core was generated by `/usr/bin/mutt'.
Program terminated with signal 11, Segmentation fault.

warning: current_sos: Can't read pathname for load map: Invoer-/uitvoerfout

# Note from Maurits: "Invoer-/uitvoerfout" is Dutch for: Input/output
# error.

Reading symbols from /usr/lib/libncursesw.so.5...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libncursesw.so.5
Reading symbols from /usr/lib/libsasl2.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libsasl2.so.2
Reading symbols from /usr/lib/libgnutls.so.11...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libgnutls.so.11
Reading symbols from /usr/lib/libidn.so.11...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libidn.so.11
Reading symbols from /usr/lib/libdb-4.2.so...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libdb-4.2.so
Reading symbols from /usr/lib/debug/libc.so.6...done.
Loaded symbols for /usr/lib/debug/libc.so.6
Reading symbols from /usr/lib/debug/libdl.so.2...done.
Loaded symbols for /usr/lib/debug/libdl.so.2
Reading symbols from /usr/lib/debug/libresolv.so.2...done.
Loaded symbols for /usr/lib/debug/libresolv.so.2
Reading symbols from /usr/lib/libtasn1.so.2...done.
Loaded symbols for /usr/lib/libtasn1.so.2
Reading symbols from /usr/lib/libgcrypt.so.11...done.
Loaded symbols for /usr/lib/libgcrypt.so.11
Reading symbols from /usr/lib/libgpg-error.so.0...done.
Loaded symbols for /usr/lib/libgpg-error.so.0
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/ld-linux.so.2...Reading symbols from 
/usr/lib/debug/lib/ld-2.3.2.so...done.
done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/debug/libnsl.so.1...done.
Loaded symbols for /usr/lib/debug/libnsl.so.1
Reading symbols from /usr/lib/debug/libnss_compat.so.2...done.
Loaded symbols for /usr/lib/debug/libnss_compat.so.2
Reading symbols from /usr/lib/debug/libnss_nis.so.2...done.
Loaded symbols for /usr/lib/debug/libnss_nis.so.2
Reading symbols from /usr/lib/debug/libnss_files.so.2...done.
Loaded symbols for /usr/lib/debug/libnss_files.so.2
Reading symbols from /usr/lib/gconv/ISO8859-15.so...Reading symbols from 
/usr/lib/debug/usr/lib/gconv/ISO8859-15.so...done.
done.
Loaded symbols for /usr/lib/gconv/ISO8859-15.so
Reading symbols from /lib/libnss_db.so.2...done.
Loaded symbols for /lib/libnss_db.so.2                                        
Reading symbols from /usr/lib/libdb3.so.3...done.
Loaded symbols for /usr/lib/libdb3.so.3
Reading symbols from /usr/lib/gconv/ISO8859-1.so...Reading symbols from 
/usr/lib/debug/usr/lib/gconv/ISO8859-1.so...done.
done.
Loaded symbols for /usr/lib/gconv/ISO8859-1.so
Reading symbols from /usr/lib/debug/libnss_dns.so.2...done.
Loaded symbols for /usr/lib/debug/libnss_dns.so.2
Reading symbols from /usr/lib/sasl2/libsasldb.so.2...done.
Loaded symbols for /usr/lib/sasl2/libsasldb.so.2
(gdb) bt
#0  0x4025d2cb in _int_free (av=0x4031b060,
    mem=0x81e30c0) at malloc.c:4209
4209    malloc.c: Onbekend bestand of map. 
        in malloc.c

# Note from Maurits: "Onbekend bestand of map." is Dutch for: unknown
# file or directory.

#0  0x4025d2cb in _int_free (av=0x4031b060, mem=0x81e30c0) at malloc.c:4209
#1  0x4025d72c in _int_realloc (av=0x4031b060, oldmem=0x81e3060, 
bytes=136196496) at malloc.c:4541
#2  0x4025c1e0 in __libc_realloc (oldmem=0x81e3060, bytes=200) at malloc.c:3429
#3  0x080aad98 in ?? ()
#4  0x081e3060 in ?? ()
#5  0x000000c8 in ?? ()
#6  0x081fbf78 in ?? ()
#7  0xbfffe4f8 in ?? ()
#8  0x08160930 in ?? ()
#9  0x00000100 in ?? ()
#10 0xbfffe4f8 in ?? ()
#11 0x08087127 in ?? ()
#12 0x08160968 in ?? ()
#13 0x000000c8 in ?? ()
#14 0x00000000 in ?? ()
#15 0xbfffe5b0 in ?? ()
#16 0x00000100 in ?? ()
#17 0x00000019 in ?? ()
#18 0xbfffebc8 in ?? ()
#19 0x080cbc48 in ?? ()
#20 0x08160930 in ?? ()
#21 0x080d6b0b in _IO_stdin_used ()
#22 0x00000064 in ?? ()
#23 0x080e4b00 in _IO_stdin_used ()
#24 0x080d9b70 in _IO_stdin_used ()
#25 0x080d9b70 in _IO_stdin_used ()
#26 0x08136882 in ?? ()
#27 0x081db460 in ?? ()
#28 0xbfffe538 in ?? ()
#29 0x081db460 in ?? ()
#30 0xbfffe5e8 in ?? ()
#31 0x40055848 in tparm () from /usr/lib/libncursesw.so.5
Previous frame inner to this frame (corrupt stack?)
(gdb)

Doesn't seem too useful to me at first sight, with all those question
marks and the possible corrupt stack.

> You can also run it in valgrind (if it runs in valgrind it might be
> possible that it doesn't crash anylonger) However invalid memory
> accesses and 'strange behaviour' will be logged in a logfile:

I'll try that and let you know.

I'll keep mutt open on the server as well (logged in via ssh) and see
if mutt crashes there too. No /usr/lib/debug or valgrind there BTW; I
like to keep it clean. Server is also Debian Sarge. Mutt is the same
version on both machines: 1.5.6-20040907+2.

-- 
Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands] 
Public GnuPG key: keyserver.net ID 0x1735C5C2
"Let your advance worrying become advance thinking and planning."
 - Winston Churchill

Attachment: signature.asc
Description: Digital signature

Reply via email to