https://bugs.kde.org/show_bug.cgi?id=492549
--- Comment #9 from martin.lu...@ohb.de ---
(In reply to Paul Floyd from comment #7)
> Can you build Valgrind from source? It doesn't have any glic dependencies.
I rebuilt it from the Fedora 40/update sources, but it still fails on my
machine if the char array is non-const, i.e. it still reports a false positive
that the character is found in the string.
~ $ valgrind --version
valgrind-3.23.0
~ $ g++ --version
g++ (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4.3.0.1)
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
~ $ cat test.cpp
#include <iostream>
int main()
{
const char sample[] = { 'h', 0 };
std::cout << (void*) __builtin_memchr(sample, 'x', 1) << std::endl;
}
~ $ g++ test.cpp -o ./a.out
~ $ ./a.out
0
~ $ valgrind -q --tool=massif ./a.out
0
~ $ cat test2.cpp
#include <iostream>
int main()
{
char sample[] = { 'h', 0 };
std::cout << (void*) __builtin_memchr(sample, 'x', 1) << std::endl;
}
~ $ g++ test2.cpp -o ./a.out
~ $ ./a.out
0
~ $ valgrind -q --tool=massif ./a.out
0x1fff00014e
--
You are receiving this mail because:
You are watching all bug changes.
