segfault causes system freeze

steve dlist at bluewin.ch
Thu Nov 22 15:19:43 UTC 2018


Le 22-11-2018, à 16:09:50 +0100, Jörg Sommer a écrit :

>> #0  0x00005592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024, menu=<optimized out>, num=<optimized out>) at ../../curs_main.c:300
>>         h = 0x5592cbef1670
>>         flag = (MUTT_FORMAT_TREE | MUTT_FORMAT_MAKEPRINT | MUTT_FORMAT_ARROWCURSOR | MUTT_FORMAT_INDEX)
>>         edgemsgno = 40
>>         reverse = <optimized out>
>>         tmp = <optimized out>
>
>This is here
>https://sources.debian.org/src/mutt/1.7.2-1+deb9u1/curs_main.c/#L300 and
>in the current version (of neomutt) here
>https://salsa.debian.org/mutt-team/neomutt/blob/master/curs_main.c#L550
>
>The best would be to create a bug report and if you don't care too much, I
>can send the developer the coredump in a *private* mail. He might dig out
>something more.

That would be really nice of you. But does it mean I also have to open a
bug report?

>I would guess that one of the thread chains is broken. Does the crash
>happen everytime in the same mailbox?

That's a question I also asked myself. I don't know for now. I'll have
to investigate a bit more. The problem is that it doesn't happen so
often.


Thank you very much for your help

Best,
Steve


More information about the Mutt-users mailing list