[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2024-03-23 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=398569 --- Comment #8 from Paul Floyd --- And the pull request has been merged. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2024-03-16 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=398569 --- Comment #7 from Paul Floyd --- I've submitted a pull request here https://github.com/bavison/arm-mem/pull/12 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2024-01-27 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=398569 --- Comment #6 from Paul Floyd --- Created attachment 165272 --> https://bugs.kde.org/attachment.cgi?id=165272=edit Patch for libarmmem Patch to redirect mem/str functions in libarmmem -- You are receiving this mail because: You are watching all

[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2024-01-27 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=398569 --- Comment #5 from Paul Floyd --- I've added an issue to the raspbian bug tracker along with an initial patch https://bugs.launchpad.net/raspbian/+bug/2051392 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2024-01-26 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=398569 --- Comment #4 from Paul Floyd --- --- Reading (ELF, standard) dynamic symbol table (14 entries) --- raw symbol [ 1]: LOC SEC : svma 0x000374, sz0 NONAME raw symbol [ 2]: LOC SEC : svma 0x014024, sz0 NONAME raw symbol [ 3]: WEA

[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2024-01-26 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=398569 --- Comment #3 from Paul Floyd --- Well the libarmmem.so library has a NULL soname. At the moment I think that is causing the debuginfo detection to fail. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2024-01-23 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=398569 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr CC|

[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2019-03-09 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=398569 --- Comment #1 from Julian Seward --- This happens because the partial-loads-ok heuristic inside Memcheck only applies to word-sized loads on arm32, not to double-word-sized loads, as would be required here. It *might* be possible to make it do so

[valgrind] [Bug 398569] invalid reads reported in libarmmem memcmp when using strings

2018-09-13 Thread Bjorn
https://bugs.kde.org/show_bug.cgi?id=398569 Bjorn changed: What|Removed |Added CC||bjorn.vant...@gmail.com -- You are receiving this