|
From: Nicholas N. <nj...@ca...> - 2004-09-02 10:57:34
|
On Thu, 2 Sep 2004, Julian Seward wrote: > (/me is getting a bit confused here) understandable :) > Let me see if I have this right. If we simply implement Nick's > original proposal, then the whole issue of reading debug info > becomes moot because V can mmap in executables of any size to > read their debug info. At least, assuming some contiguous, > suitably large piece of virtual address space >= client_end > can be found. Correct. I can imagine pathological cases, under my proposal, where the client is already very big and so V cannot find that space (ie. your "at least" assumption fails). In those cases having incremental debug info loading (ie. not mapping in the whole file at once) would help. However, these cases are so unlikely that just reading in the whole file at once (which is much simpler) should be fine. > This is an improvement on the current situation wherein we > essentially are reserving 256M of space for more or less this > purpose (+ misc other V-internal storage), and have to fail on > executables bigger than ~200M. Correct. > Do I understand right? Yes. ---- It might be worth me doing a summary of this thread at some point, like I did for the threads/signals/syscalls discussion, in order to clear up any remaining confusion and clarify our terminology. N |