https://bugs.kde.org/show_bug.cgi?id=407218

Mark Wielaard <m...@klomp.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #6 from Mark Wielaard <m...@klomp.org> ---
(In reply to Petar Jovanovic from comment #5)
> (In reply to Mark Wielaard from comment #4)
> > Does the following work on mips32?
> 
> Yes, it does. Can you commit the change?

commit c212b72a63e43be323a4e028bbdbe8b023c22be8
Author: Mark Wielaard <m...@klomp.org>
Date:   Wed May 15 21:30:00 2019 +0200

    Explicitly make testcase variable for sys-copy_file_range undefined.

    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

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to