On 06/11/2018 17:02, Rafael Antognolli wrote:
My (limited) understanding is that valgrind's mremap doesn't let me remap an address that was allocated by the ioctl, since valgrind doesn't "own" that memory. Is there some way around this, or this is never supposed to work?
I don't see any reason why it shouldn't IF the ioctl wrapper is correctly written to update valgrind's internal state and record the mapping that it creates. If the wrapper doesn't do that then you probably have bigger problems than whether you can remap it because it will mean valgrind's state is out of sync with the kernel. Tom -- Tom Hughes ([email protected]) http://compton.nu/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
