Gcore extension module for the crash utility
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> |
||
---|---|---|
.gitignore | ||
crash-gcore-1.6.3-coredump-fix-segmentation-fault-caused-by-type-misma.patch | ||
crash-gcore-1.6.3-coredump-fix-unexpected-truncation-of-generated-core.patch | ||
crash-gcore-1.6.3-coredump-use-MEMBER_-OFFSET-SIZE-instead-of-GCORE_-O.patch | ||
crash-gcore-1.6.3-elf-fix-warning-message-caused-by-type-mismatch-of-o.patch | ||
crash-gcore-1.6.3-gcore-defs-remove-definitions-and-initializations-fo.patch | ||
crash-gcore-1.6.3-gcore-fix-memory-allocation-failure-during-processin.patch | ||
crash-gcore-1.6.3-x86-Fix-failure-of-collecting-vsyscall-mapping-due-t.patch | ||
crash-gcore-command.spec | ||
README.md | ||
sources |
crash-gcore-command
The crash-gcore-command package