|
From: Jeremy F. <je...@go...> - 2003-12-19 00:27:49
|
On Thu, 2003-12-18 at 02:32, Tom Hughes wrote: > In message <yek...@au...> > Tom Hughes <th...@cy...> wrote: > > > In message <107...@ix...> > > Jeremy Fitzhardinge <je...@go...> wrote: > > > >> On Thu, 2003-12-18 at 00:24, Tom Hughes wrote: > > > >>> No. It was looking at the symbol tables and was managing to map about > >>> half the libraries then reporting mmap failed for the rest. As I increased > >>> that number it gradually reported fewer and fewer failures. > >> > >> Hm. I'm a bit confused. Can you look at what's mapped at the time it > >> fails? > > > > I'll have a look. > > You are quite right that none of our code is mapped in valgrind's part > of the address space when the mmap fails. They are mapped in the client > part of course, but that shouldn't matter. > > I stopped valgrind in the debugger at the point where the mmap has > just failed, and the resulting map is attached. The stack trace at > that point looks like this: Hm. There's two possibilities: one is that the mmap syscall itself failed; the other is that VG_(find_map_space) failed to return some space. Could you put some debug prints in there to see which case is occurring, and if its mmap, what the error return is? It seems there should be plenty of space in the address space for your mapping. J |