Backport from the upstream crash-gcore.
commit dbb542e10bfe1b2e21c7927bda9be1d301cfef65
Author: HATAYAMA Daisuke <d.hatayama@fujitsu.com>
Date: Fri Jun 17 20:38:19 2022 +0900
coredump: fix unexpected truncation of generated core files
Core files generated by crash gcore command are sometimes unexpectedly
truncated. Then, we can get aware of this from the following warning
message output by gdb:
BFD: warning: /root/./core.1.systemd is truncated: expected core file size >= 43606016, found: 43597824
From the investigation, it turned out that this truncation is
occurring when there is no write() operation after the area skipped by
lseek(). Holes are generated only when there is write() operation.
To fix this issue, use ftruncate() to allocate holes explicitly.
Signed-off-by: HATAYAMA Daisuke <d.hatayama@fujitsu.com>
Signed-off-by: HATAYAMA Daisuke <d.hatayama@fujitsu.com>
