<<< Date Index >>>     <<< Thread Index >>>

Re: mutt/1443: Sorting mailbox sometimes causes a segmentation fault.



On Mon, Aug 29, 2005 at 04:08:11PM +0100, Paul Walker wrote:
> On Mon, Aug 29, 2005 at 10:58:51AM -0400, Ben Korvemaker wrote:
> 
> > http://bugs.mutt.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=mutt&pr=1443
> > 
> > I think I'm still seeing this with mutt-1.5.9. Sometimes when I hit '$',
> > it coredumps displaying
> > "Sorting mailbox...zsh: segmentation fault (core dumped)  mutt -d 65535"
> 
> The backtrace looks similar, yes.
> 
> > patch-1.5.7.tg.edit_threads.1
> > patch-1.5.6+20040904.tg.mutt-thread.3
> 
> It would be interesting to see whether you can still reproduce the problem
> with 1.5.10 - this has a lot of bugfixes.

I had a feeling I was going to hear that. 
Lucky for me, it showed up in the FreeBSD ports today.

> IIRC, it also has the thread
> editing patch merged, meaning those two you have there should be redundant.
> Since they mess with the threading code, and that's where the fault seems to
> be, that would be a good thing. :-)

Both of them? The FreeBSD port is still including
patch-1.5.6+20040904.tg.mutt-thread.3, and it's not apparant to my
novice eye that it's now in 1.5.10. It's not a thread-editing patch, and
best described by its manual patch:

-------------------------------------------------------------
diff -Nru a/doc/manual.sgml.head b/doc/manual.sgml.head
--- doc/manual.sgml.head.orig   Fri Feb  4 08:15:50 2005
+++ doc/manual.sgml.head        Fri Feb  4 08:19:51 2005
@@ -1903,6 +1903,8 @@
 ~z [MIN]-[MAX]  messages with a size in the range MIN to MAX *)
 ~=              duplicated messages (see $duplicate_threads)
 ~$              unreferenced messages (requires threaded view)
+~(PATTERN)      messages in threads containing messages matching a certain
+                pattern, e.g. all threads containing messages from you:
~(~P)
 </verb></tscreen>

 Where EXPR, USER, ID, and SUBJECT are
-------------------------------------------------------------

That said, I don't use it, so I've yanked it for the time being.


Ben
-- 
Ben Korvemaker                         Public Key Fingerprint:
bfkorvem@xxxxxxxxxxxx                 575B 6BE9 DFE4 0E83 8AA8
                                      6C22 F703 9777 5321 837B

Attachment: pgpGbm59yyqpE.pgp
Description: PGP signature