--- Comment #6 from Mark Wielaard <m...@klomp.org> ---
(In reply to H.J. Lu from comment #5)
> (In reply to Mark Wielaard from comment #4)
> > The root cause is that ld -z separate-code introduces various new PT_LOAD
> This is very misleading.
I don't know why you say that, or why you removed the rest of the sentence "...
and the code in valgrind interpreting the PT_LOAD mappings is very specific
about what it does and what it doesn't consider a code or data mapping to match
symbols and debuginfo against."
The point is simply that if people want to work around it the simplest thing to
do for now is to use ld -z no-separate-code, which is what fedora is doing for
now till we get valgrind fixed.
I didn't say that it is the only way that valgrind might get confused by
different PT_LOAD segment setups. In fact if you look at the code pointed out
in comment #4 you'll see that there are lots of ways to confuse valgrind. And
that the code is horribly architecture and OS specific. It just doesn't work
with -z separate-code at the moment. We have to fix that (and hopefully fix
other things while we do it). But for now just don't use -z separate-code or
build binutils with --disable-separate-code.
You are receiving this mail because:
You are watching all bug changes.