https://bugs.kde.org/show_bug.cgi?id=452387
--- Comment #8 from Paul Floyd ---
I don't know all of the details of this, but memcheck has a requirement in the
link loader (ld-xxx.so) that it contain two visible functions, index and strlen
(and a few others depending on the platform). If these
https://bugs.kde.org/show_bug.cgi?id=452387
--- Comment #7 from tdk2...@gmail.com ---
(In reply to Paul Floyd from comment #6)
> It is hitting an assert when reading ld-2.15.so
>
> The program headers say that this only has 312 bytes of executable code
>
> PT_LOAD[1]: p_offset 0, p_filesz
https://bugs.kde.org/show_bug.cgi?id=452387
--- Comment #6 from Paul Floyd ---
It is hitting an assert when reading ld-2.15.so
The program headers say that this only has 312 bytes of executable code
PT_LOAD[1]: p_offset 0, p_filesz 312, perms r-x
then it tris to look at _dl_start
raw symbol
https://bugs.kde.org/show_bug.cgi?id=452387
--- Comment #5 from tdk2...@gmail.com ---
(In reply to Paul Floyd from comment #3)
> A few words on what is happening.
>
> valgrind execs memcheck. memcheck loads the guest and ld.so and starts
> running them in the Valgrind VM. ld.so then loads
https://bugs.kde.org/show_bug.cgi?id=452387
tdk2...@gmail.com changed:
What|Removed |Added
CC||tdk2...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=452387
Paul Floyd changed:
What|Removed |Added
Summary|valgrind: |valgrind:
