Comment # 8 on bug 1030828 from Fred Blaise

Thanks.

I've been trying to get it... but apparently, systemd is still telling me it
can't coredump because of limited resources, despite having this in limits.conf
(and even a full reboot):

*               soft    core            unlimited
*               hard    core            unlimited

Running your command as-is gives me this output. To be noted that nothing shows
up in "coredumpctl list".

sudo coredumpctl gdb gnome-shell
           PID: 9555 (gnome-shell)
           UID: 1000 (fblaise)
           GID: 100 (users)
        Signal: 11 (SEGV)
     Timestamp: Thu 2017-07-27 11:13:04 CEST (2min 22s ago)
  Command Line: /usr/bin/gnome-shell
    Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-1000.slice
       Session: 1
     Owner UID: 1000 (fblaise)
       Boot ID: 3cf8c8daf6da4996ab3f2a8478489132
    Machine ID: 30ea28100486a6a2e8e4bd2258b1bb01
      Hostname: gimli
       Storage: none
       Message: Process 9555 (gnome-shell) of user 1000 dumped core.

Coredump entry has no core attached (neither internally in the journal nor
externally on disk).

If I try to gdb to the actual running process such as:

gdb -p [one-of-gnome-shell-pid]

I have to get to another tty to kill gdb, as it freezes my entire desktop.

So I am currently down to try to demistify coredumps with systemd... sorry,
it's been a while since I had to troubleshoot anything.