|
From: Tom H. <to...@co...> - 2005-11-15 11:29:16
|
In message <172...@ca...>
Paul Mackerras <pa...@sa...> wrote:
> Josef Weidendorfer writes:
>
>> According to callgrind debug output, address 0x04027528 is not attributed
>> to any segment by valgrind (using VG_(find_seginfo)()).
>> Looking at proc/XXX/maps, I get:
>>
>> 04000000-04017000 r-xp 00000000 03:03 557124 /lib/ld-2.3.5.so
>> 04017000-0401c000 rw-p 04017000 00:00 0
>> 04026000-04027000 r--p 00016000 03:03 557124 /lib/ld-2.3.5.so
>> 04027000-04028000 rwxp 00017000 03:03 557124 /lib/ld-2.3.5.so
>>
>> Does anybody have an idea what can cause this?
>
> What particular aspect of that are you asking about? It looks OK to
> me; the r--p bit is the relro section (relocation read-only), which is
> read/write while relocations are being done and then gets changed to
> read-only. The rwxp is the rest of the data section.
Why does the data section have execute permission? It wouldn't
normally have that on x86/amd64 systems.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|