Re: segfault in format_part_sprinter (due to gmime (mis?)parsing empty MIME part?)

Subject: Re: segfault in format_part_sprinter (due to gmime (mis?)parsing empty MIME part?)

Date: Fri, 07 Aug 2026 11:16:48 -0300

To: notmuch@notmuchmail.org

Cc:

From: David Bremner


Štěpán Němec <stepnem@smrk.net> writes:

> On Tue, 04 Aug 2026 09:06:39 +0200
> Štěpán Němec wrote:
>
>> notmuch show --format=raw id:1782193672-98446-mlmmj-36f22ff2@FreeBSD.org >msg.segfault
>
> For convenience and to avoid any uncertainty, I've also
> uploaded the message here:
>
> https://smrk.net/tmp/msg.segfault
>
> (but diff shows no difference from what I sent attached to
> my original report)
>
> -- 
> Štěpán

Interesting. With file from smrk.net I can reproduce the segfault. On my
side there were several differences (At the end of the message). I don't really know how the message
got reencoded, but it's out of scope for notmuch really. Now that I have
a file which crashes, I'll look at the obvious guard.

--- Maildir/tethera/test/cur/mlmmj-service.eml	2026-08-05 21:06:31.698436690 -0300
+++ msg.segfault	2026-08-04 04:23:16.000000000 -0300
@@ -57,32 +57,28 @@
 MIME-Version: 1.0
 Content-Type: multipart/mixed;
  boundary="=_1ed8c5746acfba8105c2de406822921e_="
+Content-Transfer-Encoding: 8bit
 From: freebsd-hackers+owner@FreeBSD.org
 To: stepnem@smrk.net
 Message-ID: <1782193672-98446-mlmmj-36f22ff2@FreeBSD.org>
 Date: Tue, 23 Jun 2026 05:47:52 +0000
 Reply-To: freebsd-hackers+subrelease-0d41b2c07ac29c45@FreeBSD.org
-Content-Transfer-Encoding: 7bit
 
 --=_1ed8c5746acfba8105c2de406822921e_=
 Content-Type: text/plain; charset=utf-8
-Content-Transfer-Encoding: quoted-printable
+Content-Transfer-Encoding: 8bit
 
 Hi, this is the Mlmmj program managing the <freebsd-hackers@FreeBSD.org>
 mailing list.
 
-The message from <stepnem@smrk.net> with subject "Re: rcd(8) - new servic=
-e
-manager daemon" was unable to be delivered to the list because you are no=
-t
+The message from <stepnem@smrk.net> with subject "Re: rcd(8) - new service
+manager daemon" was unable to be delivered to the list because you are not
 a list subscriber.
 
 However, this is an open list. If you wish, you can simultaneously
 subscribe and release your post by sending a message to
-<freebsd-hackers+subrelease-0d41b2c07ac29c45@FreeBSD.org> which can usual=
-ly
-be done simply by replying to this message. The subject and the body of t=
-he
+<freebsd-hackers+subrelease-0d41b2c07ac29c45@FreeBSD.org> which can usually
+be done simply by replying to this message. The subject and the body of the
 message can be anything.
 
 Or you can simultaneously subscribe to the digest version of the list and
@@ -91,19 +87,16 @@
 will receive multiple posts in a single message, at regular intervals, or
 when a lot of posts have accumulated.
 
-Or you can simultaneously subscribe to the no-mail version of the list an=
-d
+Or you can simultaneously subscribe to the no-mail version of the list and
 release your post by sending a message to
 <freebsd-hackers+nomailsubrelease-0d41b2c07ac29c45@FreeBSD.org> and you
 will not receive posts sent to the list. This means you potentially will
 not see replies to your message, unless you follow the list using a web
-archive or have another email address subscribed to another version of th=
-e
+archive or have another email address subscribed to another version of the
 list.
 
 If you believe you are a subscriber, you are probably subscribed with a
-different email address. To find out which address you are subscribed wit=
-h,
+different email address. To find out which address you are subscribed with,
 refer to the message welcoming you to the list, or look at the envelope
 "Return-Path" header of a message you receive from the list.
 
@@ -111,10 +104,8 @@
 
 --=_1ed8c5746acfba8105c2de406822921e_=
 Content-Type: message/rfc822
+Content-Transfer-Encoding: 8bit
 Content-Disposition: inline; filename="message.eml"
-Content-Transfer-Encoding: 7bit
-
-
 
 --=_1ed8c5746acfba8105c2de406822921e_=--
 
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org

Thread: