|
From: Nicholas N. <nj...@ca...> - 2005-01-10 12:26:24
|
On Sun, 9 Jan 2005, Jeremy Fitzhardinge wrote: >> That's really amazing. What changes beyond the threading one did you >> have to make? > > 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? >> So, can you complete the trick by making the inner V do allocation >> via malloc/free (or whatever) in such a way that the outer V can >> memcheck it and find real bugs therein? > > Yes, but I haven't done that much. I tried annotating vg_malloc2.c, but > got stuck trying to work it all out and figured that you or Nick would > be better people to do it. 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. N |