|
From: Nicholas N. <nj...@cs...> - 2005-06-22 16:36:26
|
On Wed, 22 Jun 2005, Tom Hughes wrote: > It's helpful as Paul says in that it allows us to give the maximum > possible space to the client on 32 bit systems. With a fixed load > address there are two problems that arise: > > - If the user/kernel boundary is higher than expected then > some space that could be given to the client is wasted. Your > planned address space management changes may avoid this. > > - If the user/kernel boundary is higher than expected then > valgrind may fail to load because the fixed load address > is in kernel space. We've floated before the idea of building V for multiple load addresses for the common configurations -- eg. 2GB, 3GB, 4GB. I like the idea of PIE, but you're right that it is fragile. Ideally everyone would switch over to supporting PIE now (it seems like support is slowly increasing) and then we wouldn't have to support non-PIE systesm. N |