[systemd-devel] coredumpctl dump, not a core dump: File format not recognized

[Zbigniew Jędrzejewski-Szmek]

On Sun, Sep 11, 2016 at 10:16:05PM -0600, Chris Murphy wrote:
> systemd-229-13.fc24.x86_64
> 
> What does it mean, file format not recognized? How is it not a core
> dump file? Bug?
> 
> 
> [chris at f24m ~]$ sudo coredumpctl gdb 1992
> [sudo] password for chris:
>            PID: 1992 (gnome-terminal-)
>            UID: 1000 (chris)
>            GID: 1000 (chris)
Since this is the coredump for your user, you should be able to access
it without sudo.

>         Signal: 6 (ABRT)
>      Timestamp: Sun 2016-09-11 21:59:35 MDT (13min ago)
>   Command Line: /usr/libexec/gnome-terminal-server
>     Executable: /usr/libexec/gnome-terminal-server
>  Control Group:
> /user.slice/user-1000.slice/user at 1000.service/gnome-terminal-server.service
>           Unit: user at 1000.service
>      User Unit: user at 1000.service
>          Slice: user-1000.slice
>      Owner UID: 1000 (chris)
>        Boot ID: ce148b0a6cad4f33aea5e319956a78fe
>     Machine ID: -
>       Hostname: f24m
>       Coredump:
> /var/lib/systemd/coredump/core.gnome-terminal-.1000.ce148b0a6cad4f33aea5e319956a78fe.1992.1473652775000000000000

Did you turn off compression? By default coredumps use lz4
compression. Should work either way of course.

>        Message: Process 1992 (gnome-terminal-) of user 1000 dumped core.
Normally at this point a stack trace should be also included.
It comes from the original coredump message from systemd-coredump, so
if it's missing than systemd-coredump was unable to provide the backtrace,
so most likely the core dump will also be bad.

> "/var/lib/systemd/coredump/core.gnome-terminal-.1000.ce148b0a6cad4f33aea5e319956a78fe.1992.1473652775000000000000"

Please have a look at this file. Is it empty? Does 'file' say anything
useful?

Zbyszek