|
From: Jeremy F. <je...@go...> - 2005-01-10 16:39:49
|
On Mon, 2005-01-10 at 12:26 +0000, Nicholas Nethercote wrote: > > Nothing major. A few little bugfixes around the place (ironic that > > vg_to_ucode can't parse the code generated by vg_from_ucode). > > I would have thought the memory layout inflexibilities would have caused > problems. Where in the address space are the two Valgrinds going? It works out naturally. The first Valgrind grabs the top of the address space, and the next one takes the chunk below that; PIE means they can relocate themselves. The only change I had to make was to ignore /proc/self/maps entries above VG_(valgrind_last). > Can you try doing a meaningless jump on an uninitialised variable, or > something else that doesn't involve malloc? It would nice reassuring to > know that it really is working ok. Oh, it definitely works. There are messages coming out, but it mostly looks like ld.so suppressable chaff. And I fixed a leak after I did the malloc/free substitution. J |