On Wed, 25 Sep 2019 at 17:23:30 +0530, Pirate Praveen wrote:
>
>
> On Wed, 25 Sep, 2019 at 16:59, Pirate Praveen <prav...@onenetbeyond.org>
> wrote:
> > Let me try downgrading libgcr-base-3-1 and reproduce the crash.
> Do I need to install some -dbgsym packages?
Yes, please install at least gdb, libgcr-base-3-1-dbgsym and
libglib2.0-0-dbgsym (the versions corresponding to the libraries you
already have installed), then use
coredumpctl gdb 1648
to use gdb to inspect the core dump that was captured by
systemd-coredump. The stack traces printed by systemd-coredump are only
intended as a brief summary of the core dump, and detailed debugging
(including use of detached debug symbols) is outside the scope of
systemd-coredump itself.
For more details see <https://wiki.debian.org/HowToGetABacktrace>.
> Attaching core dump.
FYI that's a stack trace, not a core dump. A core dump is a large binary
file, and is not usually useful or desirable to send to bugs (it is likely
to contain information that you would prefer to keep confidential).
You can get a more detailed stack trace from the core dump by using
gdb and -dbgsym packages, and that more detailed stack trace is what
maintainers will usually need to be able to act on crash reports.
smcv
