https://bugs.kde.org/show_bug.cgi?id=290061
Paweł Marczewski <pwma...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pwma...@gmail.com
--- Comment #5 from Paweł Marczewski <pwma...@gmail.com> ---
I've run into this problem trying to use Valgrind on Graphene [1], a project
that functions as a library OS and loads other binaries into its own address
space to execute them. The main executable is a PIE, and after loading, it
loads the target binary.
This works well when running under Linux directly, as Linux will load the PIE
under a high enough address. However, when running under Valgrind *and* loading
a non-PIE binary inside, this often fails because Graphene will get mapped at
0x108000 and the inner binary typically will need to be mapped at 0x400000,
which overlaps with the already loaded PIE binary.
Would it be possible for Valgrind to match Linux's behaviour, or use a high
address by default, or perhaps just include an option to override the default
address? I'd be happy to work on a patch to that effect.
[1] https://graphene.readthedocs.io/en/latest/
--
You are receiving this mail because:
You are watching all bug changes.
