mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-15 07:07:01 +00:00
On some systems an extra warning could occur when a variable in the memcheck/tests/linux/sys-copy_file_range testcase was undefined, but (accidentially) pointed to known bad memory. Fix by defining the variable as 0, but then marking it explicitly undefined using memcheck VALGRIND_MAKE_MEM_UNDEFINED. Followup for https://bugs.kde.org/show_bug.cgi?id=407218