mirror of
https://git.yoctoproject.org/poky
synced 2026-02-20 08:29:42 +01:00
75a7b04641
Declare riscv64 as a COMPATIBLE_HOST since upstream now support it. For that target 'valgrind /bin/ls' warns with: --253-- WARNING: unhandled riscv64-linux syscall: 258 --253-- You may be able to write your own handler. --253-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --253-- Nevertheless we consider this a bug. Please report --253-- it at http://valgrind.org/support/bug_reports.html. This is a known issue: https://bugs.kde.org/show_bug.cgi?id=503253 but the tool does work, despite this warning with glibc. For riscv64 with musl, the build is fine but running: # valgrind /bin/ls produces the fatal error: ==306== Process terminating with default action of signal 4 (SIGILL) ==306== Illegal opcode at address 0x1002015952 ==306== at 0x40E5F26: map_library (dynlink.c:845) ==306== by 0x40E6C97: load_library (dynlink.c:1183) ==306== by 0x40E7B63: load_preload (dynlink.c:1365) ==306== by 0x40E7B63: __dls3 (dynlink.c:1963) ==306== by 0x40E75D9: __dls2 (dynlink.c:1767) ==306== by 0xFFFFFFFFFFFFFFFF: ??? which is not yet reported. Patches reviewed, manually fix-up one word change in: 0001-none-tests-fdleak_cmsg.stderr.exp-adjust-tmp-paths.patch and refresh patches with devtool. * ==================== CORE CHANGES =================== * The valgrind gdbserver now supports the GDB remote protocol packet 'x addr,len' (available in GDB release >= 16). The x packet can reduce the time taken by GDB to read memory from valgrind. * Valgrind now supports zstd compressed debug sections. * The Linux Test Project (ltp) is integrated in the testsuite try 'make ltpchecks' (this will take a while and will point out various missing syscalls and valgrind crashes!) * ================== PLATFORM CHANGES ================= * Added RISCV64 support for Linux. Specifically for the RV64GC instruction set. * Numerous bug fixes for Illumos, in particular fixed a Valgrind crash whenever a signal handler was called. * On FreeBSD, a change to the libc code that runs atexit handlers was causing Helgrind to produce an extra error about exiting threads still holding locks for. This applied to every multithreaded application. The extra error is now filtered out. A syscall wrapper had been added for getrlimitusage. * On Linux various new syscalls are supported (landlock*, io_pgetevents, open_tree, move_mount, fsopen, fsconfig, fsmount, fspick, userfaultfd). * s390x has support for various new instructions (BPP, BPRP, PPA and NIAI). * ==================== TOOL CHANGES =================== * The --track-fds=yes and --track-fds=all options now treat all inherited file descriptors the same as 0, 1, 2 (stdin/out/err). And when the stdin/out/err descriptors are reassigned they are now treated as normal (non-inherited) file descriptors. * A new option --modify-fds=high can be used together with --track-fds=yes to create new file descriptors with the highest possible number (and then decreasing) instead of always using the lowest possible number (which is required by POSIX). This will help catch issues where a file descriptor number might normally be reused between a close and another open call. * Helgrind: There is a change to warnings about calls to pthread_cond_signal and pthread_cond_broadcast when the associated mutex is unlocked. Previously Helgrind would always warn about this. Now this error is controlled by a command line option, --check-cond-signal-mutex=yes|no. The default is no. This change has been made because some C and C++ standard libraries use pthread_cond_signal/pthread_cond_broadcast in this way. Users are obliged to use suppressions if they wish to avoid this noise. The full 3.25.0 bug fix list can be found here: https://valgrind.org/docs/manual/dist.news.html (From OE-Core rev: 04b3e0c1384469167ddfb4d22e2b513f9a59aca9) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>