Comment # 8 on bug 1175037 from Dirk Weber

Created attachment 843618 [details]
gdb debug sessions stepping through until the endless loop is entered

with another message triggering the bug I tried to step until the location
where it happens, see the log of the debug session.
Using the current claws-mail version from Tumbleweed (snapshot 20201111)
rpm -q claws-mail
claws-mail-3.17.8-3.2.x86_64

Making a step at textview.c:1204 the endless loop is entered.

Interrupting this with CTRL-C shows e.g. following locations:

^C  
Thread 1 "claws-mail" received signal SIGINT, Interrupt.
0x00007ffff6194188 in ?? () from /usr/lib64/libharfbuzz.so.0

^C
Thread 1 "claws-mail" received signal SIGINT, Interrupt.
0x00007ffff62edbbf in ?? () from /usr/lib64/libpangoft2-1.0.so.0

^C
Thread 1 "claws-mail" received signal SIGINT, Interrupt.
0x00007ffff6506c4d in _int_malloc () from /lib64/libc.so.6

1204:    if (continue_write == FALSE) {
        messageview_show_partial_display(
            textview->messageview, 
            textview->messageview->msginfo,
            mimeinfo->length);
    }
    GTK_EVENTS_FLUSH();




the last lines of stepping are reproducibly
...
1191    in textview.c
(gdb) 
1192    in textview.c
(gdb) 
1193    in textview.c
(gdb) 
1191    in textview.c
(gdb) 
1204    in textview.c
(gdb) p continue_write
$6 = 1
(gdb) step
^C
Thread 1 "claws-mail" received signal SIGINT, Interrupt.
0x00007ffff6506c4d in _int_malloc () from /lib64/libc.so.6
(gdb)