Hi,

Today I got a slightly different backtrace but it looks like the same
problem:

Loaded symbols for /usr/lib/gconv/ISO8859-1.so
#0  0x080a5beb in find_subject (ctx=0x81d1f28, cur=0x8252cb0)
    at thread.c:432
432           if (tmp != cur &&                    /* don't match the same 
message */
(gdb) list
422
423       subjects = make_subject_list (cur, &date);
424
425       while (subjects)
426       {
427         hash = hash_string ((unsigned char *) subjects->data,
428                             ctx->subj_hash->nelem);
429         for (ptr = ctx->subj_hash->table[hash]; ptr; ptr = ptr->next)
430         {
431           tmp = ((HEADER *) ptr->data)->thread;
432           if (tmp != cur &&                    /* don't match the same 
message */
433               !tmp->fake_thread &&             /* don't match pseudo 
threads */
434               tmp->message->subject_changed && /* only match interesting 
replies */
435               !is_descendant (tmp, cur) &&     /* don't match in the same 
thread */
436               (date >= (option (OPTTHREADRECEIVED) ?
437                         tmp->message->received :
438                         tmp->message->date_sent)) &&
439               (!last ||
440                (option (OPTTHREADRECEIVED) ?
441                 (last->message->received < tmp->message->received) :
(gdb) print tmp
$3 = (THREAD *) 0xffff0078
(gdb) print tmp->fake_thread
Cannot access memory at address 0xffff0078
(gdb) bt
#0  0x080a5beb in find_subject (ctx=0x81d1f28, cur=0x8252cb0)
    at thread.c:432
#1  0x080a5d9b in pseudo_threads (ctx=0x81d1f28) at thread.c:503
#2  0x080a659d in mutt_sort_threads (ctx=0x81d1f28, init=0)
    at thread.c:956
#3  0x080a465a in mutt_sort_headers (ctx=0x81d1f28, init=0)
    at sort.c:291
#4  0x0805fff5 in update_index (menu=0x81f2858, ctx=0x81d1f28,
    check=1, oldcount=40, index_hint=136496608) at curs_main.c:317
#5  0x080663c4 in mutt_index_menu () at curs_main.c:492
#6  0x08079d80 in main (argc=1, argv=0xbfffdb44) at main.c:934

Again, this is with 1.5.9i.

Thanks,
Eric

On Mon, Mar 21, 2005 at 10:05:57AM -0800, Eric Warmenhoven wrote:
> Hi,
> 
> I tried mutt 1.5.9i from ftp.mutt.org and I still get a crash, but with
> a slightly different backtrace now:
> 
> Loaded symbols for /usr/lib/sasl2/libsasldb.so.2
> #0  is_descendant (a=0x21, b=0x81f4418) at thread.c:38
> 38          a = a->parent;
> (gdb) bt
> #0  is_descendant (a=0x21, b=0x81f4418) at thread.c:38
> #1  0x080a5c36 in find_subject (ctx=0x81d1f28, cur=0x81f4418)
>     at thread.c:453
> #2  0x080a5d9b in pseudo_threads (ctx=0x81d1f28) at thread.c:503
> #3  0x080a659d in mutt_sort_threads (ctx=0x81d1f28, init=0)
>     at thread.c:956
> #4  0x080a465a in mutt_sort_headers (ctx=0x81d1f28, init=0)
>     at sort.c:291
> #5  0x0805fff5 in update_index (menu=0x81f4258, ctx=0x81d1f28,
>     check=1, oldcount=43, index_hint=1) at curs_main.c:317
> #6  0x080663c4 in mutt_index_menu () at curs_main.c:492
> #7  0x08079d80 in main (argc=1, argv=0xbfffeec4) at main.c:934
> (gdb) print a
> $1 = (THREAD *) 0x21
> (gdb) frame 1
> #1  0x080a5c36 in find_subject (ctx=0x81d1f28, cur=0x81f4418)
>     at thread.c:453
> 453     }
> (gdb) print tmp
> $2 = (THREAD *) 0x829cdc0
> (gdb) print tmp->parent
> $3 = (struct thread *) 0x82e7e48
> (gdb) print tmp->parent->parent
> $4 = (struct thread *) 0x21
> 
> Eric
> 
> On Sat, Mar 19, 2005 at 11:43:13AM +0000, Paul Walker wrote:
> > On Sat, Mar 19, 2005 at 10:17:36AM +0100, Marco d'Itri wrote:
> > 
> > > Package: mutt
> > > Version: 1.5.6-20040907+3
> > > Followup-For: Bug #262272
> > > 
> > > This crash happens to me every day, probably three times a day. Finally
> > > I got annoyed and built mutt from debian sources, and put gdb on it:
> > [..]
> > > (gdb) print tmp
> > > $4 = (THREAD *) 0x0
> > [..]
> > > hours (nine hour work day, three times a day). It always dies with the
> > > status line saying "Sorting mailbox..." and always only for IMAP
> > 
> > That sounds virtually identical to a bug which was fixed some time ago,
> > although I can't actually remember which version. Could you get the latest
> > mutt, 1.5.9, from ftp://ftp.mutt.org/mutt/devel/ and see if you can still
> > reproduce the problem with that?
> > 
> > (Doing that also has the advantage of eliminating the patches applied to the
> > Debian version.)
> > 
> > -- 
> > Paul
> 
> 

Attachment: signature.asc
Description: Digital signature

Reply via email to