Re: mutt_free_header -> free -> mutt_sort_headers -> segfault
On Tue, Nov 11, 2003 at 01:17:11AM +0900, qhwt@xxxxxxxxxxxxx wrote:
> On Sat, Nov 08, 2003 at 10:01:46AM +0100, Thomas Roessler wrote:
> > On 2003-11-08 10:05:37 +0900, qhwt@xxxxxxxxxxxxx wrote:
> >
> > > IIRC, you'll have better chance to reproduce this bug if you set
> > > sorting mode to threads,
> >
> > That's what I tried.
>
> Have you tried changing sort_aux? It's usually set to ``date''
> in my ~/.mutt/muttrc, but if I set it to mailbox-order, mutt doesn't
> segfault.
Uh, no, I just managed to make mutt dump core right after I've posted
this message. It just took a bit longer.
(gdb) bt
#0 0x8095a5d in mutt_sort_threads (ctx=0x80dd300, init=0) at thread.c:816
#1 0x8093e3f in mutt_sort_headers (ctx=0x80dd300, init=0) at sort.c:234
#2 0x805c21b in update_index (menu=0x80dd380, ctx=0x80dd300, check=1,
oldcount=0, index_hint=0) at curs_main.c:313
#3 0x805c6a7 in mutt_index_menu () at curs_main.c:488
#4 0x8070401 in main (argc=3, argv=0xbfbff7d4) at main.c:907
(gdb) fram
#0 0x8095a5d in mutt_sort_threads (ctx=0x80dd300, init=0) at thread.c:816
816 } while (thread != &top && !thread->child &&
!thread->message);
(gdb) print thread
$8 = (THREAD *) 0x0