Bug#1103296: systemd: Caught <ABRT> from our own process
Peter Palfrader
weasel at debian.org
Tue Apr 22 07:13:48 BST 2025
On Wed, 16 Apr 2025, Luca Boccassi wrote:
> Control: tags -1 moreinfo
>
> I see there are 3 threads in the full backtrace. In the version in
> bookworm there was still an async cleanup routine that used posix
> threads. This is known to mix really badly with glibc's handling of
> malloc internals, so I strongly suspect that's the issue. This was
> replaced with using subprocesses in trixie.
>
> Are you able to reproduce the issue with stable-backports or
> testing/unstable?
We switched the unit file to a static user (nobody), which seems to have
been successful at triggering this issue. I'll see if I can reproduce
the bug on a less-critical system and then try with a newer systemd.
I'll report back in either case.
And elsewhere it was written:
> Would you be able to provide the core file too?
Unfortunately not, though if it might help we can do an interactive gdb
session together.
Cheers,
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `- https://www.debian.org/
More information about the Pkg-systemd-maintainers
mailing list