[Pkg-mutt-maintainers] Bug#838064: Bug#838064: mutt segfaults when sending new message (with backtrace)

[Antonio Radici]

Control: tag -1 +moreinfo

On Sat, Sep 17, 2016 at 07:30:40AM +0100, Edward Betts wrote:
> Package: mutt
> Version: 1.7.0-5
> Severity: important
> 
> mutt segfaults after sending an e-mail. I rebuilt it with debugging symbols.
> 
> Here is the output from "coredumpctl info".
> 
>            PID: 30862 (mutt)
>            UID: 1000 (edward)
>            GID: 1000 (edward)
>         Signal: 11 (SEGV)
>      Timestamp: Sat 2016-09-17 07:15:18 BST (7min ago)
>   Command Line: mutt
>     Executable: /usr/bin/mutt
>  Control Group: /user.slice/user-1000.slice/user at 1000.service/gnome-terminal-server.service
>           Unit: user at 1000.service
>      User Unit: user at 1000.service
>          Slice: user-1000.slice
>      Owner UID: 1000 (edward)
>        Boot ID: 7ca961a058374b49901f1886eedcd540
>     Machine ID: 8afb2a74abdf4af0899f95f7fffc781c
>       Hostname: x1
>       Coredump: /var/lib/systemd/coredump/core.mutt.1000.7ca961a058374b49901f1886eedcd540.30862.1474092918000000000000.xz
>        Message: Process 30862 (mutt) of user 1000 dumped core.
>                 
>                 Stack trace of thread 30862:
>                 #0  0x0000564be79c1743 mutt_pager (mutt)
>                 #1  0x0000564be796b864 mutt_display_message (mutt)
>                 #2  0x0000564be798018a mutt_index_menu (mutt)
>                 #3  0x0000564be79aaa8e main (mutt)
>                 #4  0x00007f0aafdc62b1 __libc_start_main (libc.so.6)
>                 #5  0x0000564be795714a _start (mutt)
> 

This should be fixed for sure in 1.7.1-2, would you mind checking?