Re: [Valgrind-users] Difference in Behaviour between 3.10 and 3.11

[<sim...@do...>]

Hi Julian

Thanks for the pointer - I managed to coax Yocto into not stripping the libraries in my filesystem and then everything worked as expected.

Regards and Thanks
Simon 

-----Julian Seward <js...@ac...> wrote: -----
To: sim...@do...
From: Julian Seward <js...@ac...>
Date: 07/22/2016 11:27AM
Cc: val...@li...
Subject: Re: [Valgrind-users] Difference in Behaviour between 3.10 and 3.11

> The output from readelf is below, as you'll see there is a .eh_frame section.
> Is there any dependency on how the Valgrind applications and libraries are compiled?

Well yes, but in this case it can't even unwind out of a library that is
provided as part of Valgrind itself.  So I don't think that is relevant.

Are you absolutely sure that the vgpreload_memcheck-arm-linux.so that runs
on your target hasn't been stripped on the way there?  And also that the
compile flags used to build Valgrind haven't been changed from their
defaults?

J