That's very bizzarre as the objects appear to be half-initialized. It
would be one thing if they were completely corrupted, but this is
strange and I've never seen something like it.
Are you able to try https://github.com/systemd/systemd/pull/36659 to see
if it at least stops the crashes?
--
You
Here is a crash dump for a case that doesn't appear to be due to reload:
warning: 39 ../sysdeps/unix/sysv/linux/aarch64/syscall.S: No such file or
directory
[Current thread is 1 (LWP 1171)]
(gdb) bt
#0 syscall () at ../sysdeps/unix/sysv/linux/aarch64/syscall.S:39
#1 0xf4676c1df8e4 in pr
I repro'd a case w/o reload but it didn't generate a crash dump (or
didn't flush to disk):
[ 16.538616] temp-vm-cpatterson-eastus2-t02191036311 systemd[1]: Starting
lxd-installer.socket - Helper to install lxd snap on demand...
[ 16.538640] temp-vm-cpatterson-eastus2-t02191036311 systemd[1]:
