Jonathan Nieder wrote:
> Reading from gmail's IMAP servers, I just started getting some
> segfaults today. It decides there are 203 messages, seems to start to
> render the index, and then segfaults.
[...]
> It happened about three times, and then didn't happen again.
Reproduction recipe: send m
Jonathan Nieder wrote:
> [Segmentation fault.]
>
> | (gdb) bt full
> | #0 mx_update_context (ctx=0x71c390,
> | new_messages=) at ../mx.c:1650
> | h = 0x0
> | msgno = 201
| (gdb) p msgno
| $2 = 201
| (gdb) p ctx->hdrs[200]
| $3 = (HEADER *) 0x803950
| (gdb) p ctx->hdrs[201]
|
tags 626879 - unreproducible
quit
Jonathan Nieder wrote:
> It happened about three times, and then didn't happen again. Still,
> thought you might like to know (please feel free to close this; I'll
> let you know if it happens again). I'll be running mutt through gdb
> from now on so I can catc
Package: mutt
Version: 1.5.21-5
Tags: unreproducible
Hi,
Reading from gmail's IMAP servers, I just started getting some
segfaults today. It decides there are 203 messages, seems to start to
render the index, and then segfaults.
Backtrace from gdb:
(gdb) bt
#0 mx_update_context (ctx=0x92b780
4 matches
Mail list logo
