Re: Mutt crashing on exit or replying (sometimes)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, March 11 at 10:36 AM, quoth Joshua Tinnin:
>Here it is:
>
>Program received signal SIGSEGV, Segmentation fault.
>0x080cb71f in safe_strdup ()
>(gdb) backtrace
>#0 0x080cb71f in safe_strdup ()
>#1 0x080b4d6a in rfc822_cpy_adr_real ()
>#2 0x080bc09c in mutt_default_from ()
>#3 0x080bc9d0 in ci_send_message ()
>#4 0x080a20d4 in mutt_pager ()
>#5 0x0805d753 in mutt_display_message ()
>#6 0x0806c3c3 in mutt_index_menu ()
>#7 0x0808c6e5 in main ()
>(gdb)
Very strange!
So, from what you've said so far, this crash happens when you tell
mutt to quit. But this backtrace looks *completely* wrong for
quitting. It looks like mutt crashed while attempting to send a
message while viewing a message. Specifically, it crashed while
attempting to copy the value of the $from variable.
I assume that, when run inside the debugger, mutt crashed at a
different place than you originally reported? If so, that means the
reason it crashed *originally* was because it was dealing with memory
that had been corrupted earlier, and inside the debugger we're able to
catch it earlier.
So, let's try a few things. First, let's check the values of $use_from
and $from in your muttrc (obviously, mutt shouldn't crash no matter
what those settings are, but it did crash, so now we're trying to
figure out why). Second, instead of running mutt inside gdb with just
the `run` command, try `run -d 5` so that mutt will create the
~/.muttdebug0 file. And when it crashes, let's see what the last few
lines of that file look like.
~Kyle
- --
In all matters of opinion, our adversaries are insane.
-- Oscar Wilde
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkm35FYACgkQBkIOoMqOI179RwCfW07gW+Shsj0ShzjcOE0plx7v
c+UAoLSHNjNi5T0aSzuf1xbzcOEN4eaS
=11hR
-----END PGP SIGNATURE-----