From: Eliot M. <mo...@cs...> - 2003-11-13 17:26:43
|
>>>>> "Yi" == Yi Guo <gra...@ho...> writes: Yi> Where can I find these tracing tools as you mentioned? >> I was merely stating examples. Loading and things like that access a number >> of library routines, which may allocate strings (e.g., for filenames) and >> buffers (for reading from jar files). All kinds of things are allocated in >> the process of reading and compiling a file. Let's not forget the command >> line arguments, either. Your environment variables will be scanned, and >> perhaps some of them copied to the heap, depending on their relevance to >> argument processing. What I was trying to say is that there's a lot "under >> the hood" that might not occur to you on casual reflection. I can't say >> SPECIFICALLY what is causing things to vary in your case, but various >> people have built tracing tools that (for example) print out a trace of >> object allocations. This might reveal what is varying in your specific >> circumstance. >> >> At present I can't recall the context: Why is this important to you? Maybe >> there is some other way to get at what you are trying to do. You will need to add code yourself to the allocation subroutines. This is not difficult, but you must be careful NOT TO ALLOCATE ANY OBJECTS in the code that does the tracing. Generally, use VM.sysWrite methods and make sure you don't try to create any strings. -- Eliot |