|> Basically, if your code relies on this for its behavior, |> it's likely to break at some point. Different VMs will give |> different output anyway. | |Yep... this is good for dumping info to be read by humans. If |you want a data structure usable from software, you'll need to |implement a profiler through the JVMPI interface.
The same caveat applies even with the JVMPI stuff; depending on the JVM, and particular optimizations you've performed you'll find that either the GetCallTrace interface function, or tracking you do based on METHOD_ENTRY and METHOD_EXIT events will give you results that may surprise you. Eg. either of those may indicate that you were called by foo even though foo never calls the method directly, if foo calls bar which calls you, and the JVM inlined bar into foo. If you really, really have to know who called you, the only failsafe way I can think of is to make the callers identify themselves when they call. ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
