On 21-Jul-2016 07:17, Julian Seward wrote:
> On 21/07/16 16:09, Julian Seward wrote:
>>
>>> - aspacem_maxAddr = (Addr) 0x7fff;
>>> + aspacem_maxAddr = (Addr) 0x40 - 1; // 256G
>>
>> Are you sure this frag is right? It seems to have drastically
>> reduced aspacem_maxAddr. It
> - aspacem_maxAddr = (Addr) 0x7fff;
> + aspacem_maxAddr = (Addr) 0x40 - 1; // 256G
Are you sure this frag is right? It seems to have drastically
reduced aspacem_maxAddr. It may be that this is a constant
that shouldn't change.
You can see what the initial memory layout loo
On 21/07/16 16:09, Julian Seward wrote:
>
>> - aspacem_maxAddr = (Addr) 0x7fff;
>> + aspacem_maxAddr = (Addr) 0x40 - 1; // 256G
>
> Are you sure this frag is right? It seems to have drastically
> reduced aspacem_maxAddr. It may be that this is a constant
> that shouldn't cha
This is most likely a problem caused by missing unwind info on the 3.11
vgpreload_memcheck-arm-linux.so. What does
readelf -S vgpreload_memcheck-arm-linux.so
say about them? In particular, do they both have .eh_frame, .extab and
.exidx sections? Basically you need either .eh_frame or (.extab
