It would be cleaner to keep these things in the same package wherever
possible. If we're worried about user code calling NameFinder being a
security risk, we could add a security check to its constructor.
BTW, I notice some evil use of RawData & _Jv_Malloc in StackTrace.
Specifically I don't see 'addrs' getting freed anywhere! I think its
better to avoid RawData wherever possible, and use byte[] instead.
No, that's not right. There are some severe problems with using
byte[] instead of RawData. In particular, the previous equivalent of
this code broke because byte[] and pointer references have differing
alignments.