segfault causes system freeze

[steve]

Le 21-11-2018, à 23:10:51 +0100, Jörg Sommer a écrit :

>steve hat am Mi 21. Nov, 19:50 (+0100) geschrieben:
>> # coredumpctl info
>>           PID: 1678 (mutt)
>>           UID: 1000 (steve)
>>           GID: 1000 (steve)
>>        Signal: 11 (SEGV)
>>     Timestamp: Wed 2018-11-21 19:45:57 CET (17s ago)
>>  Command Line: mutt -y -n
>>    Executable: /usr/bin/mutt
>> Control Group: /user.slice/user-1000.slice/session-3.scope
>>          Unit: session-3.scope
>>         Slice: user-1000.slice
>>       Session: 3
>>     Owner UID: 1000 (steve)
>>       Boot ID: 75e02422e0584081937ef6fe13f1e8ba
>>    Machine ID: 63a22f7a1c2437b0703353c75343f80e
>>      Hostname: box.maison.mrs
>>       Storage: /var/lib/systemd/coredump/core.mutt.1000.75e02422e0584081937ef6fe13f1e8ba.1678.1542825957000000.lz4
>>       Message: Process 1678 (mutt) of user 1000 dumped core.
>>                Stack trace of thread 1678:
>>                #0  0x00005592c9a59c68 index_make_entry (mutt)
>>                #1  0x00005592c9a822bc menu_redraw_index (mutt)
>>                #2  0x00005592c9a90d3b mutt_pager (mutt)
>>                #3  0x00005592c9a4ea85 mutt_display_message (mutt)
>>                #4  0x00005592c9a5df9c mutt_index_menu (mutt)
>>                #5  0x00005592c9a3ef16 main (mutt)
>>                #6  0x00007f002ec182e1 __libc_start_main (libc.so.6)
>>                #7  0x00005592c9a3ef8a _start (mutt)
>>
>>
>> This does not tell me anything (I'm not a developer). Do you think I should
>> open a bug report on the Debian BTS?
>
>Yes, this would be helpful. Do you have gdb installed? Can you run
>`coredumpctl debug` and run `bt full` on the gdb prompt? This output would
>be very helpful for the developer to see, what was the state before the
>crash.

I will do this this afternoon.

Thank you.

Steve