On Tuesday, March 29 at 08:44 PM, quoth Marco d'Itri: > > Like the subject says, if you edit (for example, using the > > link-threads command) multiple threads, triggering sync-mailbox will > > cause mutt to segfault. > > This bug report is useless unless you can provide a stack trace from a > binary with debugging symbols.
Sorry - here's a stack trace from gdb:
Program received signal SIGSEGV, Segmentation fault.
0x1008b3b0 in imap_fetch_message (msg=0x10346a78, ctx=0x1024d2a8, msgno=0)
at message.c:470
470 if (ctx->subj_hash && h->env->real_subj)
(gdb) where
#0 0x1008b3b0 in imap_fetch_message (msg=0x10346a78, ctx=0x1024d2a8, msgno=0)
at message.c:470
#1 0x10041e8c in mx_open_message (ctx=0x1024d2a8, msgno=9) at mx.c:1459
#2 0x100181c0 in mutt_append_message (dest=0x102a0e34, src=0x1024d2a8,
hdr=0x1034aa48, cmflags=271870584, chflags=1024) at copy.c:793
#3 0x1001265c in _mutt_save_message (h=0x1034aa48, ctx=0x10343288,
delete=271870584, decode=1024, decrypt=0) at commands.c:682
#4 0x10089884 in imap_sync_mailbox (ctx=0x1024d2a8, expunge=271863128,
index_hint=0x100c0000) at imap.c:1021
#5 0x1004172c in mx_sync_mailbox (ctx=0x1024d2a8, index_hint=0x24)
at mx.c:1214
#6 0x1001e710 in mutt_index_menu () at curs_main.c:1037
#7 0x10036598 in main (argc=1, argv=0x7ffffb24) at main.c:947
Specifically, it seems the h->env at that line is null for some reason
(and isn't checked), which makes the h->env->real_subj die.
If I can provide any more information (like a core dump or something),
let me know.
~Kyle
--
Well, I've wrestled with reality for over thirty five years, doctor, and
I'm happy to state I finally won out over it.
-- Jimmy Stewart, in "Harvey"
signature.asc
Description: Digital signature
