Hi,
One of my daemon got crashed.
The coredump is generated and stored in compressed format (.xz)
While analyzing the coredump in gdb, I see that the coredump got truncation.
I was not able to get any backtrace out of this coredump.
BFD: warning: /tmp/60515/data-manager is truncated: expected core file size >= 1034403840, found: 954998784
[Current thread is 1 (LWP 2633)]
(gdb) bt full
#0 0x0000ffff91b3ded4 in ?? ()
No symbol table info available.
#1 0x0000ffff8abb1b6c in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
One of my daemon got crashed.
The coredump is generated and stored in compressed format (.xz)
While analyzing the coredump in gdb, I see that the coredump got truncation.
I was not able to get any backtrace out of this coredump.
BFD: warning: /tmp/60515/data-manager is truncated: expected core file size >= 1034403840, found: 954998784
[Current thread is 1 (LWP 2633)]
(gdb) bt full
#0 0x0000ffff91b3ded4 in ?? ()
No symbol table info available.
#1 0x0000ffff8abb1b6c in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Systemd version : 229.
Size settings:
ProcessSizeMax=4G
ExternalSizeMax=4G
Ulimit is set to unlimited
Initially I thought this could be due to coredump size limit. But the ulimit is set to unlimited and ProcessSizeMax/ExternalSizeMax set to 4G.
What other scenarios could lead to truncated coredump?
Is there any known issue on systemd v299 related to coredump truncation?
With Kind Regards,
P R Dinesh
P R Dinesh
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
