Re: [Valgrind-users] [2.4.0] Getting an "Access not within mapped region" in /lib/ld?

[Jeremy F. <je...@go...>]

Paul Smith wrote:

>  jf> This address (0xBF7FFC61) is within Valgrind's address space, so
>  jf> it looks like a Valgrind-internal error, though for some reason it
>  jf> didn't trigger the normal internal-error printing code.
>
>Do I need to build valgrind with any flags to get better reporting?
>  
>
No, the internal error reporting is always enabled; it helps a lot with
remote diagnosis when it works.

>No, all the other tools work, including addrcheck.  Except helgrind;
>that says:
>
>  # /opt/tools/bin/valgrind --tool=helgrind /bin/echo hi
>  Can't open tool "helgrind": /opt/tools/lib/valgrind/vgskin_helgrind.so: undefined symbol: vgPlain_get_current_or_recent_tid
>  valgrind: couldn't load tool
>
>but that seems to be something different.
>  
>
Yes. 2.4.0 doesn't support helgrind, so I suspect it's picking up a 2.2
helgrind.so file.

It would be interesting to see what valgrind --tool=none cat
/proc/self/maps under each environment.

    J