|
From: Benny C. <bwl...@gm...> - 2005-03-20 16:22:02
|
Hi Tom, Tom Hughes <tom <at> compton.nu> writes: > How do you know what address the region will be mapped at? If you're > trying to use MAP_FIXED to force it then be aware that valgrind will > fail attempts to map memory at some high addresses as only part of the > address space is available for your program - some is reserved for > valgrind to use. Yes I did. But after I remove the MAP_FIXED in mmap() the memory (in 64MB chunks) still cannot be allocated. Maybe I need to change it back to malloc(). > If you're talking about the TRANSLATE line for 0x1B8E4C30 then that > is a function intercept and is nothing to do with any data access in > your program. I see. That clears my doubt. Thanks a lot! > You need to look at how/when multibuff is allocated and what sort of > memory it is pointing at. Turns out multibuff is not needed anyway (it is declared as struct dsmmsg multibuff[BUFFSLOT] as global and then initialized at a init function that causes the fault), but I still doubt why the fault does not happen without using Valgrind. Best Regards, Benny. |