| Summary: | PPCle erroneous report on strncmp use. | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Rusty Russell <rusty> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | cel |
| Priority: | NOR | ||
| Version First Reported In: | 3.15 SVN | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Rusty Russell
2020-04-30 01:23:26 UTC
Michael Ellerman reports that gcc (GCC) 9.3.1 20200408 (Red Hat 9.3.1-2) needsa "-Og" to reproduce this (though of course, the asm works). He also produced a fix, but he's unsure if it's correct: https://gist.github.com/mpe/fcb6aa57af7db43f27721bb52f4410ac Compiled the included test case and ran on the current upstream Valgrind as of 9/1/2021. The test case seems to run fine now. valgrind ./valgrind-420780 ==2869120== Memcheck, a memory error detector ==2869120== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==2869120== Using Valgrind-3.18.0.GIT and LibVEX; rerun with -h for copyright info ==2869120== Command: ./valgrind-420780 ==2869120== ==2869120== ==2869120== HEAP SUMMARY: ==2869120== in use at exit: 16 bytes in 1 blocks ==2869120== total heap usage: 1 allocs, 0 frees, 16 bytes allocated ==2869120== ==2869120== LEAK SUMMARY: ==2869120== definitely lost: 16 bytes in 1 blocks ==2869120== indirectly lost: 0 bytes in 0 blocks ==2869120== possibly lost: 0 bytes in 0 blocks ==2869120== still reachable: 0 bytes in 0 blocks ==2869120== suppressed: 0 bytes in 0 blocks ==2869120== Rerun with --leak-check=full to see details of leaked memory ==2869120== ==2869120== For lists of detected and suppressed errors, rerun with: -s ==2869120== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0 Compiled the test case wth gcc --version gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0 Marking the issue resolved. Rusty Russell, please verify that the issue is fixed with the current upstream Valgrind source tree. If so, please close the issue. If not, please let us know so we can look into it some more. Thanks. Reopened. Apparently still triggered on valgrind master. With recent gcc's you need to compile with -Og to reproduce (not -O3). Or try the asm directly? |