On 06-Nov-2021, Ben Finney wrote:
> When I invoke GDB on the core dump, this is the session:
>
> =
> $ coredumpctl gdb
> […]
>PID: 45094 (bash)
>UID: 1000 (bignose)
>GID: 1000 (bignose)
> Signal: 11 (SEGV)
> Timestamp: Sat 2021-11-06 23:01:32
On 06-Nov-2021, Bernhard Übelacker wrote:
> "coredumpctl gdb" might be able to show a backtrace of the crash or
> even the command line parameters.
With ‘systemd-coredump’ installed, I repeat the behaviour (log in
using GDM). The session crashes, back to GDM; a core dump is created.
When I
On 06-Nov-2021, Bernhard Übelacker wrote:
> If possible you could install systemd-coredump.
> Then after such a crash "coredumpctl list" shows maybe
> the crashing bash process.
> If it is the last "coredumpctl gdb" might be able to
> show a backtrace of the crash or even the command line
>
Package: bash
Version: 5.1-3+b2
Severity: important
When starting ‘gnome-session’ as some users, a child ‘bash’ process
exits with a segmentation fault:
=
Nov 6 17:25:29 malva wireplumber[16259]: SPA handle 'api.bluez5.enum.dbus'
could not be loaded; is it installed?
Nov 6 17:25:29 malva
4 matches
Mail list logo
