> Did anybody experience something similar?
i am also using the latest mutt and i have no problem. maybe you can try
strace to identify the problem. try to run a
$ strace -f -o mutt.log mutt
and take a look at the last few lines where the segfault happens.
HTH
cu
--
To UNSUBSCRIBE, emai
On Sarge:
zsh % dpkg -l 'mutt*'
+++-==-==-
ii mutt 1.4.0-4Text-based mailreader supporting
MIME, GPG,
un mutt-i (no description available)
pn mutt-ja (no description available
I seem to remember having similar problems a long time ago and fixed them
by re-ordering the configuration lines in .muttrc. I attributed it to Mutt
corrupting its stack while processing .muttrc, but I really don't know. Good
luck, I hope you get a better answer.
Perhaps you could try upgrading M
I am using Mutt 0.61, mostly happily. I don't understand why very
infrequently, mutt stops loading with a segmentation fault error. In a
number of cases, I noted this happens near a message that is a notification
or warning of undeliverable mail.
Can anyone shed a clue?
Alan
--
Alan Eugene
4 matches
Mail list logo