Upgrade minicoredumper from 2.0.7 to 2.0.8.
Remove below patches because they have been merged by 2.0.8
upstream version:
0001-corestripper-Fix-uninitialized-warning.patch
0002-Fix-2038-year-problem-in-timestamp-handling.patch
0001-coreinject-fix-assignment-of-const-qualified-type.patch
Changelog:
===========
* Address multiple compiler warnings and errors found by more recent
toolchains. The issues existed technically, but were not a problem
for real-world usage scenarios.
* Relocate the man pages for sbin binaries to section 8.
* Fix timestamp value in the core dump directory name for 32-bit
systems with a 64-bit time_t definition after 2038-01-19.
* Improve status query for init script to check core_pattern usage and
handle when the regd daemon is not enabled.
* Known problems:
- If tar is active, core files larger than 8GB will be
truncated. If it is known that the core files will be >8GB and
the full core file is needed, tar must be disabled.
License-Update:
The COPYING changes in upstream commit 941079541a
update Copyright end dates to reflect when changes were last committed.
The COPYING.LGPLv2.1 change in upstream commit 00e3b2fdf7 replaces
the FSF postal mailing address with a URL as recommended by the GNU FAQ.
No license change, no impact on the recipe licensing.
Signed-off-by: Li Zhou <li.zhou@windriver.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The minicoredumper has multiple 2038 year problems where 'long' type
variables and strtol() function calls cause overflow on 32-bit systems
when handling timestamps after 2038-01-19.
This leads to incorrect timestamp formatting in core dump directory
names (e.g., sleep40s.20380119.031407+0000.598).
Fix by changing 'long timestamp' to 'time_t timestamp' and replacing
strtol() with strtoll() to properly handle 64-bit timestamps on
32-bit systems.
Signed-off-by: Jiaying Song <jiaying.song.cn@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
0001-minicoredumper_demo-Use-optnone-attribute-with-clang.patch
removed since it's included in 2.0.3
Changelog:
==========
* Dump zero-blocks as 4KB blocks instead of single bytes to speed up
piping to the compressor. (Only relevant if tar is not used.)
* Drop core data exceeding the ustar 8GB limit. The core file is
appropriately truncated and the actions are logged. This fixes tar
file corruption for core files >8GB.
* Known problems:
- If tar is active, core files larger than 8GB will be
truncated. If it is known that the core files will be >8GB and
the full core file is needed, tar must be disabled.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Maximum number of tries, in rare cases, is insufficient for
elf parse. Backport patch that fixes the issue.
Signed-off-by: Sakib Sajal <sakib.sajal@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The sysv initscript and systemd service assumes minicoredumper is
installed in /usr/bin/. In our case minicoredumper is installed in
/usr/sbin/ by default. Therefore, fix this path.
Signed-off-by: Pierre-Jean TEXIER <texier.pj2@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
COPYING file changed since copyright is now assined to linutronix from Erricson
Fix build on arm
Fixes error like
corestripper.c:1245:4: error: format specifies type 'unsigned long' but the arg
ument has type 'long long' [-Werror,-Wformat]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
minicoredumper provides an alternate core dump facility for Linux
to allow minimal and customized crash dumps
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
