|
From: Tom H. <to...@co...> - 2005-11-15 11:30:47
|
In message <yek...@de...>
Tom Hughes <to...@co...> wrote:
> In message <200...@gm...>
> Josef Weidendorfer <Jos...@gm...> wrote:
>
>> 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?
>
> Sounds like the segment list and the maps file are out of sync for
> some reason, which is bad. What does --sanity-level=4 say? Does it
> report a sync check failure?
Oh hang on, you're talking about SegInfo not NSegment... Not finding
a SegInfo just means there is no debug information associated with the
address which is normal if that is the data segment.
You might be better off querying the address space manager which will
have a segment for all mapped memory.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|