Re: Mutt crashing on exit or replying (sometimes)
- To: mutt-users@xxxxxxxx
- Subject: Re: Mutt crashing on exit or replying (sometimes)
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Fri, 6 Mar 2009 14:49:25 -0600
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=TJB900bVpQOsEbO5+zf4QeSKbNc=; b=m50A c0nzMDobBE4TcBVymf1BH6WU3TLEsK7wMncUODJBAbQ81HENn43fnF6qJ7FWZU2p WuhdXM8LiEQ4L4gidgBAc6Rvn2xCOGkWIriy8Vh7SI9/ldaJYceB6QmqHESkWtjr tFJGWyDcMGZJRJj/sHHYiKcmc0hCoikSRqI8Mpo=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=aDH/rT9wPTsr6HJhfYi5q7LUBbo/aW1X7H/umjQFlSsAU26X832V2zm9WNUAmjOIeYfVLkRBPYZ0AlYibjBmNnszha7+uzhhfMdrn10c7UhhLPfsckZwoJwJnPeJCbBWKmqwJSLHxmcxsQ0JCVlboxqS/4QN+ARG7c+lRQjZtpo=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20090306203156.GC2081@xxxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20090306203156.GC2081@xxxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.19 (2009-02-20)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday, March 6 at 01:31 PM, quoth Joshua Tinnin:
> I have a very similar muttrc for three different situations, but
> they refer to different locations for the spool and inbox, and only
> one is crashing. The other two have no issues. All three are set to
> UTF-8 as the charset.
This may have nothing to do with your problem, but: setting the
$charset variable manually is ALMOST NEVER a good idea! I've only ever
seen *one* situation where it's even *useful*.
Mutt is *VERY* good at figuring out what that variable *ought* to be,
and if mutt is wrong, your system libraries (which mutt relies upon)
will also get it wrong. What's worse, if mutt and your system
libraries disagree on how to handle things (like text), you can wind
up with bizarre errors that are nearly impossible to track down.
So, let me be clear:
SETTING THE $charset VARIABLE MANUALLY IS ALMOST NEVER A GOOD
IDEA!
> I can't see any differences between them which would be causing
> this. Here's the relevant end of the debug:
>
> mutt_index_menu[617]: Got op 145
That just means "I received the QUIT command". It'd probably be more
helpful if you ran mutt inside a debugger and gave us a backtrace.
> I looked around and there seems to be a few people who've had a similar
> issue, chalked up to character sets or unicode, but I'm not a programmer
> and I'm not sure how to get any further than this.
>
> Any ideas? Do I need to post my .muttrc?
What version of libiconv do you use? There's some buggy ones out there
(esp. on FreeBSD) that are known to cause crashes. You may just need
to update your iconv library.
~Kyle
- --
Liberty is the only thing you cannot have unless you are willing to
give it to others.
-- William Allen White
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkmxjFUACgkQBkIOoMqOI16YoQCfX0VCVi/uv5ko4ZLh7L9I4Rfk
WqgAn3ygPKOsw/1dmcmUq9B0LufPX3mb
=4gE9
-----END PGP SIGNATURE-----