Description:

I've been experiencing random segfaults on systemd --user process, which I use quite heavily to manage my processes. I can't reproduce the problem for now, only wait for it to happen again.

Additional info:
package: systemd 210-2

I managed to get a partial stack trace from a coredump and an unstripped systemd binary compiled a posteriori using options=(debug !strip) in the PKGBUILD. Here it is:

$ gdb systemd coredump

Core was generated by `/usr/lib/systemd/systemd --user'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000000000048101e in get_user_creds (username=0x251b2f0, uid=0x3dd, gid=0x7fffa11d002f, home=0x0,
shell=0x7fffa11dec10) at src/shared/util.c:4217
4217 if (p)
(gdb) bt
#0 0x000000000048101e in get_user_creds (username=0x251b2f0, uid=0x3dd, gid=0x7fffa11d002f, home=0x0,
shell=0x7fffa11dec10) at src/shared/util.c:4217
#1 0x00007fffa11dec10 in ?? ()
#2 0x00007fffa11dec10 in ?? ()
#3 0x0000000000000010 in ?? ()
#4 0x000000000248d1b0 in ?? ()
#5 0x000000000042322c in socket_add_default_dependencies (s=0x0) at src/core/socket.c:286
#6 socket_add_extras (s=0x0) at src/core/socket.c:356
#7 socket_load.9848 (u=<optimized out>) at src/core/socket.c:412
#8 0x00000000024ca280 in ?? ()
#9 0x0000000000000011 in ?? ()
#10 0x0000000000000001 in ?? ()
#11 0x00000000000003dd in ?? ()
#12 0x0000000000000000 in ?? ()

Do you have any idea why I still don't get all the debug data?

Any suggestions on how to proceed?