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?
> I saved 23 core dumps of about 1.5 MB each. I don't have experience
> analyzing them, but they are available in case anyone would want to
> have a look. With some pointers I may be able to analyze it myself.
For starters:
gdb /usr/bin/mutt /path/to/core
bt
quit
But if you produce this coredump on Sarge it is very likely that it is
useless because the framepointers are stripped from the libs.
If the backtrace of the above has many '???' in it produce a new
coredump with libs which have framepointers in:
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
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:
Oh and mutt will be a bit slower using valgrind because valgrind is kind
a virtual machine actually.
apt-get install valgrind
valgrind --tool=memcheck --run-libc-freeres=no --num-callers=10 \
--show-reachable=yes --leak-check=yes --error-limit=no \
--log-file=/tmp/valgrind /usr/bin/mutt
After quiting mutt you will find a /tmp/valgrind.pid logfile. You can
send this privately to me or make it accessible via a webserver (it
might be very big).
> Yesterday I tried "set strict_threads=yes" like was proposed earlier
> in the thread as a workaround. Since then I haven't seen a
> segfault. That post mentions that there may be unbearable side
> effects, but I haven't noticed. So for now I am fine, thanks for the
> tip.
So turn that off again - than it might be possible to find that bug. I
also have a ppc32 user who reports the same bug at a hand, I got an
account on his machine but was unable to reproduce the bug.
He said that it happens at least once a day but with external
modification of the IMAP mailbox and after that moving arrow keys (but
it might take some time).
Maybe you can trigger this segfault faster if you do so.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
