Bug#926212: gnome-shell crashed: segfault in libgnome-shell.so after printing email from evolution

[Simon McVittie]

Control: retitle -1 gnome-shell crashed: segfault in libgnome-shell.so after printing email from evolution
Control: tags -1 + moreinfo
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/issues/750

I'm retitling this bug to try to stop other people using it to represent
different segfaults, because after someone starts doing that it becomes
really difficult to disentangle who has which bug and which bugs have
been solved.

Upstream bug 750 seems particularly similar.

On Tue, 02 Apr 2019 at 08:11:23 +0200, Guenter Grodotzki wrote:
> [39719.061358] gnome-shell[1279]: segfault at 0 ip 00007fd4fa6ae3bf sp
> 00007ffcf4dbaea0 error 4 in libgnome-shell.so[7fd4fa6a6000+1f000]

How often has this happened? Is it reproducible, or is it something
that happened once and has not recurred?

On Fri, 05 Apr 2019 at 22:01:58 +0200, Bernhard Übelacker wrote:
> As this information is still kind of small, you might consider
> to install a coredump collector like systemd-coredump.
> That way you could list crashes of the current boot by:
>     coredumpctl list
> And some more information is entered into journal that would
> help a lot to triage such crashes ("Stack trace of thread...".
>     journalctl --no-pager
> 
> Even better would be if you could install the debug symbol
> packages e.g. gnome-shell-dbgsym like described in [1].
> Then following commands should print a backtrace
> with source line information.

This would be very useful information.

> Nevertheless, I tried if that little information brings
> us somewhere and I think it leads into function
> shell_app_dispose. There, I assume, we reach line 1485,
> unfortunately dereferencing a null pointer
> in app->running_state->windows.
>
> crash instruction  - start .init    == diff
> 0x00007fd4fa6ae3bf - 0x7fd4fa6a6000 == 0x83BF

How sure are you that the virtual memory area starting at 0x7fd4fa6a6000
starts with .init and not .text?

    smcv