Re: Chromium/Buster constantly crashing

[Reco <recoverym4n@enotuniq.net>]

	Hi.

On Fri, Aug 27, 2021 at 08:25:51AM +0100, Ottavio Caruso wrote:
> This is what I get after the crash, after launching chromium from the terminal:
> 
> [7966:7966:0827/075828.005688:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled
> Fontconfig error: Cannot load default config file
> Fontconfig error: Cannot load default config file
> Received signal 11 SEGV_MAPERR 000000000000
> #0 0x55f90e2ed6b9 (/usr/lib/chromium/chromium+0x5b4b6b8)

This shows one thing only - in the absence of the debugging symbols
chromium cannot get a meaningful backtrace.

> Anything I can get from that output?

No, but you can get something useful this way:

1) Install "gdb-minimal" and "chromium-dbgsym".
2) Ensure that you have "core file size" (aka "ulimit -c") set to
unlimited for the current shell.
3) Wait for the crash, locate the core dump.
4) Execute gdb to obtain a stack trace:
gdb /usr/lib/chromium/chromium <pathname_to_core> -batch -ex bt

Reco