https://bugs.kde.org/show_bug.cgi?id=470244
Tom Hughes <t...@compton.nu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |t...@compton.nu
--- Comment #1 from Tom Hughes <t...@compton.nu> ---
Disabling mmap support would render valgrind useless - if it doesn't know what
memory has been allocated that it can't track it's state.
Any program has to assume that memory allocations may fail and deal with that
so technically I'm not sure this is really a bug - the behaviour of memory
allocation under valgrind is often very different to when running normally
simply because it has to allocate extra memory to track state and that is all
happening in the same address space.
We certainly don't reject all mremap's that expand out of hand, as you can see
at
https://sourceware.org/git/?p=valgrind.git;a=blob;f=coregrind/m_syswrap/syswrap-generic.c;h=efdae60e10320cbcccd86415fabf6ef8fd7abf57;hb=HEAD#l275
which is the current implementation.
A starting point would probably be to run with --trace-syscalls=yes so we can
see exactly what arguments are being passed and trace out what path it is
following in that handler.
--
You are receiving this mail because:
You are watching all bug changes.
