I tripped over this issue today while upgrading from mutt 1.x to 2.x
The upstream issue for this bug is:
* "Mutt 2.0.2 - macOS 10.15.7 - segmentation fault"
https://gitlab.com/muttmua/mutt/-/issues/310
The issue was fixed upstream in this commit:
<quote>
commit cfdcfa7ffee69ecdf7a56a6b9c541d1f71496601
Author: Kevin McCarthy <ke...@8t8.us>
Date: Sun Nov 29 13:44:30 2020 -0800
Fix REPLY_TO environment variable handling.
Commit 4e153adf changed this code to reuse the function buffer
variable, but forgot to rewind the buffer for parsing in
parse_my_hdr().
Additionally commit e5a32a61 removed an extra "null termination"
mutt_buffer_addch() at the end of mutt_extract_token(). This caused a
NULL value to be passed to the strpbrk() in parse_my_hdr(), causing a
segv. Change to use a buffer pool token parameter instead.
I actually think, like with the previous IMAP mailbox handling, this
method of adding a my_hdr is dangerous. I'll look into refactoring it
in master instead.
Thanks to Paul Nevai for reporting the problem and tracking down the
backtrace.
</quote>
The fix is in mutt-2.0.3, which was released on 2020-12-04, so we should get
the fix whenever that version makes it into Debian.
--
-----------------------------------------------------------------
a l a n d. s a l e w s k i salew...@att.net
ads@salewski.email
https://github.com/salewski
-----------------------------------------------------------------
