|
From: Nicholas N. <nj...@ca...> - 2004-07-11 16:49:48
|
On Sun, 11 Jul 2004, Tom Hughes wrote: > I can work around that by marking the segments which are not mapped so > that I know I need to pad them, but it turns out the VG_(brk) doesn't > update the segment list which it gives out memory and I've far been > unable to make it do so as it just seems to either segfault or get into > an infinite loop. > > I've cludged around that for now, but now I find that the kernel is > choosing to allocate the io_setup page at the top of the client address > space, immediately below the client stack, thus stopping it from being > extended! > > So it looks like I will have to pad the client address space as well > in order to control where the kernel puts that page... Hmm, sounds like there's some interaction here with my embryonic layout changes... for example, I've got rid of VG_(brk) by merging Valgrind's heap and its mmap-segment, and I want to merge that with the shadow memory area... N |